From: Till Kamppeter <till.kamppeter@gmail.com>
To: Ira McDonald <blueroofmusic@gmail.com>,
printing-architecture@lists.linux-foundation.org,
"printing-summit@lists.linux-foundation.org"
<printing-summit@lists.linux-foundation.org>,
Printing-japan <printing-japan@lists.linux-foundation.org>,
lsb-discuss@lists.linux-foundation.org,
lf_driver_backport@lists.linux-foundation.org,
Linux Foundation Staff <lf_staff@lists.linux-foundation.org>,
webdevel@lists.linux-foundation.org,
Jim Zemlin <jzemlin@linux-foundation.org>,
Dan Kohn <dan@dankohn.com>, Markus Rex <msrex@suse.de>,
Amanda McPherson <amanda@linux-foundation.org>
Subject: [Printing-architecture] Google Summer of Code 2008 -- APPLICATION SUBMITTED
Date: Tue, 11 Mar 2008 17:49:29 +0100 [thread overview]
Message-ID: <47D6B819.7000004@gmail.com> (raw)
In-Reply-To: <e395be80803061312k489b1eco6085410a936dee68@mail.gmail.com>
Hi,
thanks everyone for your cooperation on the application of the Linux
Foundation to participate in the Google Summer of Code.
I have submitted our application now. Google will decide on which
mentoring organizations will participate until March 17, ~12 noon
PDT/19:00 UTC and publish the list of mentoring organizations on
http://code.google.com/soc/
This does not mean that we cannot accept ideas for student projects any
more. If you still have ideas, please add them before the student's
application period starts (March 24).
If you are a mentor or backup admin, check your Google account regularly
or let it forward your mail to your usual mail address. There can be
e-mails which you are required to answer to validate the application.
Note also that as soon as our participation gets published (March 17)
that students will find our project ideas list via the GSoC web site and
so students will ask questions on the mailing lists or on IRC. Or they
will contact mentors via their Google accounts. Please answer the
student's questions to not loose potential candidates for your
project/workgroup.
I will forward student applications to the appropriate mentors or
workgroups as soon as they roll in.
Till
Our ideas list:
https://www.linux-foundation.org/en/Google_Summer_of_Code
Our submitted application:
APPLICATION FORM
================
About Your Organization
-----------------------
1. What is your Organization's Name?
The Linux Foundation
2. What is your Organization's Homepage?
http://www.linux-foundation.org/
3. Describe your organization.
The Linux Foundation is a nonprofit consortium dedicated to fostering
the growth of Linux. Founded in 2007 as a merger of the former Free
Standards Group (FSG) and the former Open Source Developer Lab (OSDL),
the LF sponsors the work of Linux creator Linus Torvalds and is
supported by leading Linux and open source companies and developers from
around the world. The Linux Foundation promotes, protects and
standardizes Linux by providing unified resources and services needed
for open source to successfully compete with closed platforms.
More: https://www.linux-foundation.org/en/About
4. Why is your organization applying to participate in GSoC 2008? What
do you hope to gain by participating?
Our goals are twofold: to meet specific technical goals, and to gain new
members of our community (and the open-source community, by extension).
For both printing and kernel work, having a specific goal and a mentor
are important in penetrating areas which can be more complex than some
other projects. And none of the projects in question are "filler"; each
will provide a very specific, in-demand benefit.
5. Did your organization participate in previous GSoC years? If so,
please summarize your involvement and the successes and failures of your
student projects. (optional)
No, we did not participate.
6. If your organization has not previously participated in GSoC, have
you applied in the past? If so, for what year(s)? (optional)
No, this is our first application.
7. What license does your project use?
All the work produced by the Linux Foundation is free software according
to the OSI definitions, but there is no requirement for a specific
license. The licenses are selected depending on what is most suitable
for each individual project.
*LSB: mostly GPL, some tools Artistic
*PAPI: CDDL
*JTAPI: MIT
*CUPS filters: GPL
*Foomatic (including web software): GPL
*Kernel: GPL
8. URL for your ideas page
https://www.linux-foundation.org/en/Google_Summer_of_Code
9. What is the main development mailing list for your organization?
LSB: lsb-discuss Mailing List,
http://lists.linux-foundation.org/mailman/listinfo/lsb-discuss
OpenPrinting: printing-architecture Mailing List,
http://lists.linux-foundation.org/mailman/listinfo/printing-architecture
Kernel: http://kernelnewbies.org/MailingList
Driver Backport: Lf_driver_backport Mailing List,
http://lists.linux-foundation.org/mailman/listinfo/Lf_driver_backport
10. Where is the main IRC channel for your organization?
For LSB work: irc://irc.freestandards.org/#lsb is being used.
For Kernel work: http://kernelnewbies.org/IRC
OpenPrinting is not using IRC currently.
11. Does your organization have an application template you would like
to see students use? If so, please provide it now. (optional)
12. Who will be your backup organization administrator? Please enter
their Google Account address. We will email them to confirm, your
organization will not become active until they respond. (optional)
jeff.licquia@gmail.com
About Your Mentors
------------------
1. What criteria did you use to select these individuals as mentors?
Please be as specific as possible.
We selected the principal editors/developers of the Linux Foundation
working groups or free software project where the proposed student
projects are part of. Very important is also that the mentors are coding
on things similar to what the student is supposed to do and that they
are not only designers or managers.
2. Who will your mentors be? Please enter their Google Account address
separated by commas. If your organization is accepted we will email each
mentor to invite them to take part. (optional)
till.kamppeter@gmail.com, HinTak.Leung@gmail.com,
josef.spillner@googlemail.com, riddell@gmail.com, penberg@gmail.com,
jonmasters@gmail.com
About The Program
-----------------
1. What is your plan for dealing with disappearing students?
If possible (early enough) we would like to replace the disappearing
student by another one. Otherwise, we will transition their
work-in-progress to a caretaker (i.e., the appropriate mentor).
2. What is your plan for dealing with disappearing mentors?
We will transition their mentor role to another active member of the
appropriate Linux Foundation working group.
3. What steps will you take to encourage students to interact with your
project's community before, during and after the program?
Each of the projects has methods for community interaction, whether
through conference calls, IRC, or face-to-face meetings. To the extent
possible, we intend to give our students time to report on their
project, both in the progress they make and in the things they learn.
Invitations to these events will be given at the earliest opportunity.
Some of the projects may take more time than just the summer, or may
involve integration work after the project is complete. Even if the
project is done, we will work to keep the student involved in the
integration process. And we hope to suggest other ways the student can
participate that mesh well with their strengths once this project is done.
4. What will you do to ensure that your accepted students stick with the
project after GSoC concludes?
We will gauge each student's progress, and suggest other projects they
may wish to work on after their summer project is done.
Integration with the main upstream projects will likely be an important
part of the task. Our students will be encouraged to take part in that
process, and not just "throw the patch over the wall".
Occasionally, other internships and even contracting jobs can come up.
In these cases, previous participants in GSoC who have continued to
participate in their respective projects may find themselves with job
opportunities, either within a Linux Foundation workgroup or in the
general community.
next prev parent reply other threads:[~2008-03-11 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 18:49 [Printing-architecture] [Printing-summit] Mon/Tue 10/11 March - Google Summer of Code 2008 -- 2nd Conference Call Ira McDonald
2008-03-06 21:12 ` [Printing-architecture] [Printing-summit] [US Daylight Saving Time] " Ira McDonald
2008-03-07 16:26 ` [Printing-architecture] [US Daylight Saving Time] Mon/Tue 10/11 March - TIMES CHANGED FOR THE US " Till Kamppeter
2008-03-10 15:43 ` [Printing-architecture] REMINDER: Mon/Tue 10/11 March " Till Kamppeter
2008-03-10 18:28 ` [Printing-architecture] Google Summer of Code 2008 -- Finalization of the application of the Linux Foundation Till Kamppeter
[not found] ` <1205175495.27299.36.camel@perihelion>
2008-03-10 19:21 ` [Printing-architecture] [Lf_driver_backport] " Till Kamppeter
[not found] ` <1205181725.27299.63.camel@perihelion>
2008-03-10 21:07 ` Till Kamppeter
[not found] ` <1205175707.27299.40.camel@perihelion>
2008-03-10 19:23 ` Till Kamppeter
[not found] ` <47D5D9B3.80307@linux-foundation.org>
2008-03-11 8:27 ` [Printing-architecture] [lsb-discuss] " Till Kamppeter
2008-03-11 15:37 ` [Printing-architecture] Google Summer of Code 2008 -- LAST CALL: Submission of the application Till Kamppeter
[not found] ` <3F62CBEE02D6404E98C65934617EB58203F137EC@fmsmsx414.amr.corp.intel.com>
2008-03-11 16:16 ` [Printing-architecture] [lsb-discuss] Google Summer of Code 2008 -- LAST CALL: Submissionof " Till Kamppeter
2008-03-11 16:49 ` Till Kamppeter [this message]
2008-03-18 16:46 ` [Printing-architecture] Google Summer of Code 2008 -- THE LINUX FOUNDATION IS ACCEPTED! 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=47D6B819.7000004@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=amanda@linux-foundation.org \
--cc=blueroofmusic@gmail.com \
--cc=dan@dankohn.com \
--cc=jzemlin@linux-foundation.org \
--cc=lf_driver_backport@lists.linux-foundation.org \
--cc=lf_staff@lists.linux-foundation.org \
--cc=lsb-discuss@lists.linux-foundation.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 \
--cc=webdevel@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.