From: Till Kamppeter <till.kamppeter@gmail.com>
To: "printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>,
Printing-japan <printing-japan@lists.linux-foundation.org>,
OpenICC Liste <openicc@lists.freedesktop.org>
Subject: [Printing-architecture] Project ideas for OpenPrinting in the Google Summer of Code 2009
Date: Wed, 21 Jan 2009 19:19:02 +0100 [thread overview]
Message-ID: <49776716.4000004@gmail.com> (raw)
Hi,
I will again apply for the Linux Foundation to participate in the Google
Summer of Code. So I want to ask you for your suggestions of coding work
at OpenPrinting which could be done by GSoC students and also whether
you would volunteer mentoring.
Important is that the code will really be used in the near future. Last
year we had for example one student implementing the PAPI in CUPS but it
seems that in our current printing environments there is no real need
for the PAPI.
We also need to try to assign projects which students can finish in
time. If projects are too big we should split them into two.
Note that the students in reality do less than you expect and that if
the GSoC is over and they are not ready that they usually do not have
time to finish what is still missing.
Work which needs to be done is for example:
- Patching individual applications to get the DBUS interface for a
Common Printing Dialog
- Writing a web app to manage printer drivers and PPDsd uploaded by
manufacturers
- Implementing JTAPI and integrating in foomatic-rip to add job ticket
support to the PDF work flow
- Coding test suites for printer self certification
- Coding on color management integration (TBD by the color management
experts and by the OpenPrinting Summit outcomes).
Till
next reply other threads:[~2009-01-21 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:19 Till Kamppeter [this message]
2009-01-21 19:10 ` [Printing-architecture] Project ideas for OpenPrinting in the Google Summer of Code 2009 Alex Wauck
2009-01-21 21:05 ` 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=49776716.4000004@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=openicc@lists.freedesktop.org \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=printing-japan@lists.linux-foundation.org \
/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.