All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Jeff Licquia <licquia@linux-foundation.org>
Cc: lsb-discuss@lists.linux-foundation.org,
	Jim Zemlin <jzemlin@linux-foundation.org>,
	webdevel@lists.linux-foundation.org, Dan Kohn <dan@dankohn.com>,
	Linux Foundation Staff <lf_staff@lists.linux-foundation.org>,
	"printing-summit@lists.linux-foundation.org"
	<printing-summit@lists.linux-foundation.org>,
	Printing-japan <printing-japan@lists.linux-foundation.org>,
	printing-architecture@lists.linux-foundation.org,
	lf_driver_backport@lists.linux-foundation.org
Subject: Re: [Printing-architecture] [lsb-discuss] Google Summer of Code 2008 -- Finalization of the application of the Linux Foundation
Date: Tue, 11 Mar 2008 09:27:27 +0100	[thread overview]
Message-ID: <47D6426F.6050800@gmail.com> (raw)
In-Reply-To: <47D5D9B3.80307@linux-foundation.org>

Thank you for your suggestions of answers for the application form. I 
will wait a little bit to get some comments, and independent whether I 
get comments and/or further improvements I will submit the application 
(with all improvements up to then) today in the (European) afternoon.

    Till


Jeff Licquia wrote:
> I'm not entirely sure if these changes constitute improvement or not. 
> Feel free to run them by some people, and not use whatever parts are 
> weak (or even none of it).
> 
> Till Kamppeter wrote:
>> 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.
> 
>> 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.
> 


  parent reply	other threads:[~2008-03-11  8:27 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       ` Till Kamppeter [this message]
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   ` [Printing-architecture] Google Summer of Code 2008 -- APPLICATION SUBMITTED Till Kamppeter
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=47D6426F.6050800@gmail.com \
    --to=till.kamppeter@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=licquia@linux-foundation.org \
    --cc=lsb-discuss@lists.linux-foundation.org \
    --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.