From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <47D6426F.6050800@gmail.com> Date: Tue, 11 Mar 2008 09:27:27 +0100 From: Till Kamppeter MIME-Version: 1.0 References: <47D57DD5.6080007@gmail.com> <47D5D9B3.80307@linux-foundation.org> In-Reply-To: <47D5D9B3.80307@linux-foundation.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Printing-architecture] [lsb-discuss] Google Summer of Code 2008 -- Finalization of the application of the Linux Foundation List-Id: Printing architecture under linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jeff Licquia Cc: lsb-discuss@lists.linux-foundation.org, Jim Zemlin , webdevel@lists.linux-foundation.org, Dan Kohn , Linux Foundation Staff , "printing-summit@lists.linux-foundation.org" , Printing-japan , printing-architecture@lists.linux-foundation.org, lf_driver_backport@lists.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. >