From: Till Kamppeter <till.kamppeter@gmail.com>
To: printing-architecture@lists.linux-foundation.org,
Printing-japan <printing-japan@lists.linux-foundation.org>,
Markus Rex <msrex@suse.de>,
"'printing-summit@lists.linux-foundation.org'"
<printing-summit@lists.linux-foundation.org>
Cc: Jeff Licquia <licquia@debian.org>
Subject: [Printing-architecture] Google Summer of Code 2008: Application period for mentoring organizations: March 3-12
Date: Wed, 27 Feb 2008 16:55:58 +0100 [thread overview]
Message-ID: <47C5880E.4070703@gmail.com> (raw)
Hi,
the Google Summer of Code 2008 got announced these days:
http://code.google.com/soc/2008
The application period for mentoring organizations is March 3 - 12.
It would be great if this year we get some implementation work done by
means of the Google Summer of Code. My ideas for student projects are:
* libjtapi: C implementation of JTAPI to be shipped by Linux
distribution and Unix operating systems.
* PAPI integration in CUPS: Seems that no one is working on that
currently
* Filling the holes in the PDF workflow with CUPS: It is still not
determined who will code the CUPS filters pdftoraster, texttopdf,
pdftoijs
* Common Printing Dialog: Coding on the dialog designed by
OpenUsability, for KDE and/or GNOME
* OpenPrinting database: Web-based (CGI) software for efficiently
reviewing and triaging user-contributed printer entries and comments
and integrating them into OpenPrinting XML database (Foomatic
database). Also to join duplicates and to remove bad entries.
Please post your ideas up to Monday, March 10 at the latest, so that we
have time to include them in our application.
As agreed with Jeff Licquia, the Linux Foundation will enter as one
mentoring organization, with projects from all workgroups, especially
also LSB.
Please enter your project ideas on
https://www.linux-foundation.org/en/Google_Summer_of_Code
Should we schedule a conference call about the application for the
Google Summer of Code?
Till
------------------------------------------------------------------------
Hi,
the main weakness of OpenPrinting is the lack of man power, so we should
make use of all means to raise man power. A very good opportunity is the
Google Summer of Code (http://code.google.com/soc/), but we must be well
prepared when they open their call for mentoring organizations. Between
the opening and the application deadline there is only one week and so
we will possibly not be able to schedule a phone meeting in that week.
Remember that we have missed last year's deadline by finalizing in the
OP Steering Committee phone meeting. As there are no announcements of
the opening we should already start to prepare the definitions of the
projects we want to offer so that when they open we have the application
ready.
So please anyone, make your suggestions for projects to be offered for
Google Summer of Code students.
My suggestions are (the order is not the order of importance):
* libjtapi: C implementation of JTAPI to be shipped by Linux
distribution and Unix operating systems.
* PAPI integration in CUPS: Seems that no one is working on that currently
* Filling the holes in the PDF workflow with CUPS: It is still not
determined who will code the CUPS filters pdftoraster, texttopdf, pdftoijs
* Common Printing Dialog: Coding on the dialog designed by
OpenUsability, for KDE and/or GNOME
* OpenPrinting database: Web-based (CGI) software for efficiently
reviewing and triaging user-contributed printer entries and comments and
integrating them into OpenPrinting XML database (Foomatic database).
Also to join duplicates and to remove bad entries.
Last year the deadline for mentor organizations to apply was March 12,
please keep an eye on the Google Summer of Code web site to not miss the
opportunity again.
What about phone meetings to talk about this subject?
Till
next reply other threads:[~2008-02-27 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 15:55 Till Kamppeter [this message]
2008-02-27 23:09 ` [Printing-architecture] [Printing-japan] Google Summer of Code 2008: Application period for mentoring organizations: March 3-12 TORATANI Yasumasa
2008-02-27 23:19 ` Till Kamppeter
[not found] ` <47C5A86B.2030602@licquia.org>
2008-02-28 23:35 ` [Printing-architecture] [Printing-summit] " Till Kamppeter
2008-02-28 23:48 ` Till Kamppeter
[not found] ` <47C78897.6080307@licquia.org>
2008-02-29 21:19 ` Till Kamppeter
2008-02-29 22:34 ` Ira McDonald
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=47C5880E.4070703@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=licquia@debian.org \
--cc=msrex@suse.de \
--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.