8,288
edits
Changes
Jump to navigation
Jump to search
mLine 11:
Line 11: − + − + Line 41:
Line 41: − + Line 58:
Line 58: − ====About you====+ − + − # What is your name? − # What is your email address? − # What is your Sugar Labs wiki username? − # What is your IRC nickname? − # What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.) − # Where are you located, and what between which hours do you anticipate being active and available to work on your project? (We also try to match mentors by general time zone if possible.) − # Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, what has motivated you to work on an open-source project this summer? − − ====About your project==== − − # Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using? − # What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) − # Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant. − − ====You and the community==== − − # If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors. − # Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it? − # What will you do if you get stuck on your project and your mentor isn't around? − # How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project? − − ====Miscellaneous==== − − # We want to make sure that you can set up a development environment before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help. − # What is your t-shirt size? (Yes, we know Google asks for this already; humor us.) − # Describe a great learning experience you had as a child. − # Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more? − − Note: you will post this application on the wiki in the category "GSoC applications". We encourage you to browse this category and comment on the talk page of other applications. Also, comments and responses on the talk page of your own application are viewed favorably, and, while we don't like repetitive spam, we welcome honest questions and discussion of your project idea on the mailing list and/or IRC. − ===Who will your mentors be? Please include Google Account information.=== − (Note: it is much easier to have the mentors apply to the organization itself after it has been accepted than to invite them in this section.) + + + + Line 106:
Line 79: − + − + − + − ===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. − − 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. − + − + Line 127:
Line 96: + + + +
Summer of Code/SL application (view source)
Revision as of 12:49, 7 August 2014
, 12:49, 7 August 2014→Describe your organization.: update link
===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?===
===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?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
(origin: [[Summer_of_Code/Student_application_template]])
{{:Summer_of_Code/Student_application_template}}
[[Image:New-developer-challenge.png|thumb|right|An example of the kind of screenshot you should send us of your first modification to your development environment. Note that the drop-down menu text has Mel's email address in place of the word "Restart" - your screenshot should contain your email instead.]]
===Who will be your backup organization administrator? Please include Google Account information.===
===Who will be your backup organization administrator? Please include Google Account information.===
:Jameson Quinn <jameson.quinn -AT- gmail.com>
:Jameson Quinn <jameson.quinn -AT- gmail.com>
===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 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.
List of mentors:
name <gmail account name>
name <gmail account name>
#Walter Bender <walter.bender>
#Walter Bender <walter.bender>
#Wade Brainerd <wadetb>
#Wade Brainerd <wadetb>
#Luis Gustavo Lira, BSc, MSc <lira.lg at pucp.edu.pe>
#Luis Gustavo Lira, BSc, MSc <lira.lg at pucp.edu.pe>
#Ben Lau < xbenlau at gmail.com >
#Ben Lau <xbenlau>
#Sayamindu Dasgupta <sayamindu at gmail.com>
#Sayamindu Dasgupta <sayamindu>
#Austin Appel <scorche15>
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing students?===
We will set the expectation that students will not be out of communications for more than 60 hours (ie, the length of a weekend) without prior notification to their mentor. We'll also hold mandatory weekly meetings in IRC for all the students to report on progress made, problems encountered, and proposed next steps.
We will set the expectation that students will not be out of communications for more than 60 hours (ie, the length of a weekend) without prior notification to their mentor. We'll also hold mandatory weekly meetings in IRC for all the students to report on progress made, problems encountered, and proposed next steps. If a student does disappear, their mentor will attempt to contact them through all reasonable means to see what happened.
===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?===
===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]]