All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: 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 14:44:02 -0200	[thread overview]
Message-ID: <54C7C052.30306@gmail.com> (raw)
In-Reply-To: <CAN40gSvS+q2Sd61TqF62tHo5a=GkcsUjcxXi7mFZBTm0zZJF6Q@mail.gmail.com>

On 27.01.2015 14:01, Ira McDonald wrote:
> Hi Till,
>
> I'm not sure that there are recent IPP standards that are suitable for
> GSoC 2015
> projects.
>

So then I will simply re-post what did not get taken last year.

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

The value is that common scan frontends (simple-scan, X-Sane, scan 
functionality of LibreOffice, ...) can be used with IPP scanners.

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

And I do not see where this would benefit from a GSoC project.

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

Are the standard ready for use? Is it only the manufacturers not 
adopting them? If the standard is ready and at least one somewhat 
available device on the market it should already be enough for a GSoC 
project (at least if there is a good chance of wide adoption in the near 
future).

> 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.
>

This looks like some of the boring thingies which one can get only done 
if one pays someone for it. And if one is not able to find students to 
make a Common Print Dialog then one will never, ever find one for this.

> 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.
>

This is what could perhaps make up a project, like "Extend 
system-config-printer to poll printer capabilities and features via IPP 
based on IPP JPS3)".

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

OK, you could also talk about the GSoC as possible implementation 
platform for standards on the meeting.

    Till


      reply	other threads:[~2015-01-27 16:44 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
2015-01-27 16:44         ` Till Kamppeter [this message]

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=54C7C052.30306@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=Printing-architecture@lists.linux-foundation.org \
    --cc=blueroofmusic@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.