Summer of Code/SL application: Difference between revisions

Homunq (talk | contribs)
 
(4 intermediate revisions by 3 users not shown)
Line 11: Line 11:
===Describe your organization.===
===Describe your organization.===


[http://sugarlabs.org Sugar Labs] is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
[http://sugarlabs.org/ Sugar Labs] is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.


Sugar Labs, a volunteer, non-profit organization, is a member project of the [http://conservancy.softwarefreedom.org/ Software Freedom Conservancy]. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.
Sugar Labs, a volunteer, non-profit organization, is a member project of the [http://sfconservancy.org/ Software Freedom Conservancy]. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.


===Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating?===
===Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating?===
Line 41: Line 41:
===What is the URL for your ideas page?===
===What is the URL for your ideas page?===


http://wiki.sugarlabs.org/go/DevelopmentTeam/ProjectIdeas (Note: this is probably temporary; I'll see if we can get something better by the 13th. [[User:Mchua|Mchua]] 22:36, 4 March 2009 (UTC))
http://wiki.sugarlabs.org/go/Development Team/ProjectIdeas (Note: this is probably temporary; I'll see if we can get something better by the 13th. [[User:Mchua|Mchua]] 22:36, 4 March 2009 (UTC))


===What is the main development mailing list or forum for your organization?===
===What is the main development mailing list or forum for your organization?===
Line 67: Line 67:


===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
All of our mentors have experience with the Sugar code base and most of them have been with the project since the beginning - more than 2 years ago. Also, they have been active in our software development support community and a regular presence on our support IRC channel.
All of our mentors have experience with the Sugar code base and around half of them have been with the project since the beginning - more than 2 years ago. Most have successful mentoring experience (including combined 6 years' experience as successful GSoC mentors) and/or are teachers. All have been active in our software development support community and a regular presence on our support IRC channel.


We also plan to pair mentors to ensure that there is an experienced "second" associated with each project. Finally, our IRC channel is active 24/7, and we will give all students a list of IRC handles whom they can consult specifically. There is a safety net for any software developer who needs it.
List of mentors:
name <gmail account name>
#Walter Bender <walter.bender>
#Jameson Quinn <Jameson.Quinn>
#Nirav Patel <nrpatel>
#Tomeu Vizoso <tomeu.vizoso>
#Bobby P <bobbypowers> nteon on IRC
#Sebastian Silva <sebastian at fuentelibre.org> (alternative: sebatustra)
#Wade Brainerd <wadetb>
#Luis Gustavo Lira, BSc, MSc <lira.lg at pucp.edu.pe>
#Ben Lau <xbenlau>
#Sayamindu Dasgupta <sayamindu>
#Austin Appel <scorche15>


===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing students?===
Line 77: Line 89:
===What is your plan for dealing with disappearing mentors?===
===What is your plan for dealing with disappearing mentors?===


Our mentors have a history of being deeply involved and invested with the project and in constant and reliable contact with the community, so we think it is unlikely that this will happen. We plan to have secondary (paired mentors) and tertiary (general IRC channel) support for each project as described above, and mentors will also be expected to attend the weekly check-in meetings on IRC.
Our mentors have a history of being deeply involved and invested with the project and in constant and reliable contact with the community, so we think it is unlikely that this will happen. We also plan to pair mentors to ensure that there is an experienced "second" associated with each project. If a mentor misses the weekly check-in meetings on IRC, their "backup" will track them down as they temporarily cover for them. Finally, our IRC channel is active 24/7, and we will give all students a list of IRC handles whom they can consult specifically. There is a safety net for any software developer who needs it.  


===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
Line 84: Line 96:
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
The best we can do is infect the students with enthusiasm for our project's goals. We will launch a Sugar pilot near each accepted project so that students can see immediate results and feedback from children and teachers using their work, thus investing them further in longer-term sustainability and getting their local communities involved as well.
The best we can do is infect the students with enthusiasm for our project's goals. We will launch a Sugar pilot near each accepted project so that students can see immediate results and feedback from children and teachers using their work, thus investing them further in longer-term sustainability and getting their local communities involved as well.
[[Category:GSoC]]