All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ira McDonald <blueroofmusic@gmail.com>
To: Till Kamppeter <till.kamppeter@gmail.com>,
	Ira McDonald <blueroofmusic@gmail.com>
Cc: "printing-architecture@lists.linux-foundation.org"
	<Printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Projects for GSoC 2015: Implementing PWG standards
Date: Tue, 27 Jan 2015 11:01:57 -0500	[thread overview]
Message-ID: <CAN40gSvS+q2Sd61TqF62tHo5a=GkcsUjcxXi7mFZBTm0zZJF6Q@mail.gmail.com> (raw)
In-Reply-To: <54C79494.20402@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3093 bytes --]

Hi Till,

I'm not sure that there are recent IPP standards that are suitable for GSoC
2015
projects.

I have reservations about SANE, because it competes with new IPP Scan
Service,
but doesn't add any value (that I can see).

IPP Everywhere self-certification is moving forward, but slower than we all
hoped.

IPP Finishings 2.0, IPP FaxOut, IPP Scan are all good technology, but much
too
new to be widely deployed in shipping printers.

IPP MSN 2.0 (Media Standardized Names) does do important extensions to
media properties that would be worth reflecting in client print UIs, but it
might be hard to get
a student excited about more complete and accurate media properties.

IPP JPS3 (Job and Printer Extensions Set 3) is full of good stuff - high
value
new attributes include "ipp-features-supported", "job-contraints-supported",
"media-source-supported", "preferred-attributes-supported",
"printer-geo-location", "printer-get-attributes-supported", "printer-icons",
"printer-mandatory-job-attributes", and "printer-supply".  Many of these are
required by the subsequent IPP Everywhere spec, but it's IPP Everywhere
that will be the impetus for widespread adoption, I think.

We should talk about GSoC 2015 more after next week's PWG F2F meeting.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto: blueroofmusic@gmail.com
Winter  579 Park Place  Saline, MI  48176  734-944-0094
Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434


On Tue, Jan 27, 2015 at 8:37 AM, Till Kamppeter <till.kamppeter@gmail.com>
wrote:

> On 27.01.2015 10:53, Michael Sweet wrote:
>
>> Ira,
>>
>>  On Jan 26, 2015, at 8:59 PM, Ira McDonald <blueroofmusic@gmail.com>
>>> wrote:
>>> ...
>>> <ira> The IPP standard for uploading firmware will only be in the
>>> work-in-progress
>>> IPP System Service (milestone of Q3/Q4 2015 for Prototype draft).
>>>  Actually doing
>>> the reboot to the new firmware is currently just an idea of mine for a
>>> new operation
>>> in IPP System Service.
>>>
>>
>> There are a lot of security issues to address with firmware updates, and
>> we'll need widespread adoption to make this useful.  On the consumer end of
>> printers, most now offer updates via their control panels and/or web
>> interfaces, and on the high end you need a service engineer to apply the
>> update.
>>
>> In any case, I don't see this as a GSoC 2015 project (2016?)
>>
>>
> OK, so my suggestions (1) and (3) are not (yet) suitable for a GSoC
> project.
>
> WDYT about my suggestion (2), the SANE drier for IPP network scanners? Is
> the standard already in a usable state? Are there already MF devices with
> standard-conforming scanners?
>
> Ira, what were your ideas of implementing PWG standards in GSoC projects?
>
>    Till
>
>
>

[-- Attachment #2: Type: text/html, Size: 4533 bytes --]

  parent reply	other threads:[~2015-01-27 16:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 14:33 [Printing-architecture] Projects for GSoC 2015: Implementing PWG standards Till Kamppeter
2015-01-26 16:20 ` Michael Sweet
2015-01-26 21:55   ` Till Kamppeter
2015-01-27  1:59 ` Ira McDonald
2015-01-27 12:53   ` Michael Sweet
2015-01-27 13:34     ` Till Kamppeter
2015-01-27 13:37     ` Till Kamppeter
2015-01-27 14:25       ` Michael Sweet
2015-01-27 16:01       ` Ira McDonald [this message]
2015-01-27 16:44         ` Till Kamppeter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN40gSvS+q2Sd61TqF62tHo5a=GkcsUjcxXi7mFZBTm0zZJF6Q@mail.gmail.com' \
    --to=blueroofmusic@gmail.com \
    --cc=Printing-architecture@lists.linux-foundation.org \
    --cc=till.kamppeter@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.