Summer of Code

Revision as of 20:50, 17 February 2009 by Homunq (talk | contribs) (→‎Get involved)
Pencil.png NOTICE:  This page is a draft in active flux...
Please contribute to these contents and discuss issues on the discussion page.


Introduction

The purpose of this project is to get Sugar Labs ready for a Google Summer of Code mentor organization application, and to coordinate a Sugar Labs Summer of Code effort if accepted. (From the 2009 FAQ: "Google Summer of Code (GSoC) is a global program that offers student developers stipends to write code for various open source projects.")

This is a project under DevelopmentTeam. Mchua is the current project coordinator and can be contacted with any questions.

What makes a good project

Our focus is on collaboration and community for the summer 2009 round of projects, though we'll also consider thoughtful proposals that lie outside these two areas and can make a strong case for how they would support the Sugar Labs mission.

Collaboration

This refers to API or activity work that makes collaboration "work better." A good metric for "works better" is to ask the following: "6 months after the summer ends, which projects are likely to have caused the highest increase in children-hours spent collaborating over Sugar Activities?"

Community

This refers to meta-work that makes it easy for Sugar to reach a broader community; this includes development tools (and accompanying implementation of processes and training), internationalization/localization, accessibility, infrastructure-building, and porting Sugar to other platforms.

A good metric for "reaches a broader community" is to ask the following: "6 months after the summer ends, which projects are likely to cause the highest increase in SL community members that have participated consistently on a team for a minimum of 3 months?"

Get involved

The preliminary /Mentors' application page is now up. Student applications are not yet open; we have to get accepted first!

We're currently in the "get ideas" phase; please see DevelopmentTeam/ProjectIdeas for a list of potential projects, and add your own. (There are some more project ideas from a brainstorming session at Sugar Camp.)

We're looking into running a brainstorm on Sugar Labs project ideas, likely in late Feb 2009. The objective of such a brainstorm would be to reach a rough consensus on what kind of working code is most useful to us (in other words, how to prioritize projects). The secondary objective of the brainstorm would be to generate a lot of nifty project ideas. The idea is that consensus on prioritization will make it easier for people to fit their own ideas in. If you can help plan or participate in such a brainstorm, post your ideas here.

We would welcome help coordinating the overall effort as well; please contact Mchua if you'd like to get involved with this.

Community-building ideas

The mentoring org application includes the following questions:

  1. What steps will you take to encourage students to interact with your project's community before, during and after the program?
  2. What will you do to ensure that your accepted students stick with the project after GSoC concludes?

This is a place for brainstorming these issues.

[11:59] <mchua> homunq: we also need a general plan for how we're going to use this as a good community building tool for new developers, though that's a little vague [11:59] <mchua> homunq: stuff like "would a weekly check-in email be a good idea?" "do we require mentor meetings on IRC?" "are students mandated to blog about their work?"