From: Till Kamppeter <till.kamppeter@gmail.com>
To: printing-architecture@lists.linux-foundation.org,
Printing-japan <printing-japan@lists.linux-foundation.org>,
"'printing-summit@lists.linux-foundation.org'"
<printing-summit@lists.linux-foundation.org>
Subject: [Printing-architecture] Google Summer of Code 2008 - Mentors urgently needed
Date: Fri, 07 Mar 2008 19:59:47 +0100 [thread overview]
Message-ID: <47D190A3.4010708@gmail.com> (raw)
Hi,
there are still three project proposals on the list for which we do not
have mentors:
1. PAPI integration in CUPS
2. JTAPI implementation (for this I have already a student, Lars
Uebernickel, who currently works on the PDF-capable foomatic-rip 4.0)
3. texttopdf and pdftoijs CUPS filters for the PDF workflow
See also
https://www.linux-foundation.org/en/Google_Summer_of_Code
For the PAPI CUPS integration we also need a project description,
perhaps also for the JTAPI implementation (to make the Linux Foundation
more attractive for Google by listing more projects). Volunteers welcome.
Norm, what do you think about mentoring the PAPI CUPS integration?
Claudia, what do you think about mentoring the JTAPI
implementation?
Anyone volunteering for the CUPS filters? For texttopdf it would be
great to have someone familiar with CJK text, so that the filter can
also cover these text files? Anyone in Japan?
Note: One person can mentor more than one student.
See more about mentoring at http://code.google.com/soc/2008/faqs.html
And note that the application deadline is on March 12. To do the
organization smoothly, please answer on Monday March 10 at the latest.
Till
next reply other threads:[~2008-03-07 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 18:59 Till Kamppeter [this message]
2008-03-10 18:50 ` [Printing-architecture] Google Summer of Code 2008 - Mentors urgently needed Claudia Alimpich
2008-03-10 19:04 ` Till Kamppeter
2008-03-11 0:17 ` Ira McDonald
2008-03-11 0:40 ` 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=47D190A3.4010708@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=printing-japan@lists.linux-foundation.org \
--cc=printing-summit@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.