1. Notes on Summer of Code 2006

• GNOME Summer of Code 2006 - A window into the world, work and lives of GNOME Summer of Code 2006 participants. Many thanks to Google!

• join the #soc channel on irc.gnome.org!

If you have any question that is not answered in the SoC FAQs, don't hesitate to contact the administrators on the GNOME side: BehdadEsfahbod, VincentUntz

1.1. Accepted proposals

The accepted proposals have been announced! They are:

• Project	Student	Mentor(s)
  Annotations and bookmarks support on evince	P. Henrique Silva	BryanClark
  Audio/Video Conferencing using OSCAR for Telepathy	Antoine Perdaens	RobertJamesTaylor
  BluetoothManager	Matthew Garrett	BastienNocera
  Ekiga, IAX2	StephenCook	DamienSandras
  /GSmartMix, a smart audio mixer for gnome	Marc-André Lureau	StefanKost
  Gazpacho	LuizCarlosIrberJunior	JohanDahlin
  Generic user-to-user connection interface for collaborative applications using telepathy	Mads Chr. Olesen	RobertMcQueen
  Gnome Scan Infrastructure	ÉtienneBersac	VincentUntz
  GStreamer Graphical Pipeline Editor	BrendanHowell	EdwardHervey
  Improving Emblems in GNOME	James Barrett	ChristianHammond
  Improving nautilus login performance & ease of profiling	Phillip Ezolt	ChrisBall
  Interactive forms support for Evince	Julien Rebetez	JonathanBlandford
  libgnome-applet	Ryan Lortie	VincentUntz
  library.gnome.org	Goran Rakić	ShaunMcCance
  Long Running Task Manager & Nautilus/Epiphany Download Integration	Steve Frécinaux	RaphaelSlinckx
  Making a library for single-instance apps	Vytautas Liuolia	ElijahNewren, MatthiasClasen
  Evolution Automation and 'Performance' verification & Tinderbox integration / LDTP regrssion suite	Prasanth Mohan	VeerapuramVaradhan
  Networked Tomboy	Sebastian Rittau	AlexGraveley
  Vertical writing support for Pango	Maciej Katafiasz	BehdadEsfahbod
  Work on gtksourceview library	Yevgen Muntyan	PaoloMaggi

Please feel free to edit this page to link to a copy of your application.

1.2. Pool of project ideas

See /Ideas

/Performance projects

1.3. Mentoring

See this mail for explanations of all the steps to apply for mentorship. Mentorship shouldn't take much time, not more than one hour per project per week. Moreover, we will almost surely assign at least two mentors to each project, so it will be even less work.

1.4. Applying

The application form is available at http://code.google.com/soc/student_step1.html (it will be closed on Monday, May 8th)

If you feel strong about an idea that is not listed in the pool of project ideas, feel free to contact the administrators to know if it looks like a good idea, but generally it is perfectly Ok to submit proposals for ideas not listed in the pool, and is neither an advantage, nor a disadvantage. Same about ideas that do not have a mentor yet. When writing proposals do note that however, quality is much more important than quantity. Some of the projects listed in the ideas pool are really hard to accomplish in a limited time technically. So simply saying I want to do this does not mean much, you need to convince us that you can do it in the three months period with a high quality.

Based on the Perl page explaining how to write a proposal: http://www.perlfoundation.org/gc/grants/proposals.html

A good format for applying is:

• Name

• Email

• Project Title

• Benefits to the GNOME Community

• Deliverables - It is very important to list quantifiable results here e.g.

  • "Improve X modules in ways Y and Z."
  • "Implement new library in ways Y and Z."
  • "Improve performance in X by Y%."

• Project Schedule - How long will the project take? When can you begin work?

• Bio - Who are you? What makes you the best person to work on this project?

Miguel also wrote some nice notes for the projects at Mono: http://www.mono-project.com/StudentProjects

See also http://code.google.com/soc/studentfaq.html#26 and Application Tips from last year's participants.