5
edits
Changes
Jump to navigation
Jump to search
Line 27:
Line 27: − + − Not applicable; see above.+ − + Line 51:
Line 51: − + − {{:Summer_of_Code/Student_application_template}}+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 75:
Line 105: − + +
Summer of Code/SL application (view source)
Revision as of 05:12, 12 March 2009
, 05:12, 12 March 2009no edit summary
As Sugar Labs only officially became a member project of the SFC in June 2008, as an organization we have not been around long enough to have participated in past GSoCs. However, we have many community members with prior GSoC experience (former mentors, students, and organization administrators from multiple open-source projects, more details available upon request) who have offered their help specifically to make our first GSoC summer a success.
As Sugar Labs only officially became a member project of the SFC in June 2008, as an organization we have not been around long enough to have participated in past GSoCs. However, we have many community members with prior GSoC experience (former mentors, students, and organization administrators from multiple open-source projects, more details available upon request) who have offered their help specifically to make our first GSoC summer a success.
OLPC handled many Sugar-related GSoC applications last year and they are applying to GSoC again this year. Sugar Labs, although independent of OLPC, is in friendly, day-to-day communication with them. Together, we are making a clear distinction between our GSoC goals: anything related to the XS school server or to specific hardware issues on the OLPC XO-1 laptops would be covered by OLPC; The Sugar-related projects—the user-facing bits—are covered by Sugar Labs. Nevertheless, we expect some amount of confusion from students; both organizations are prepared to help redirect the applications of any students who apply to the wrong place.
For the past three summers, OLPC has handled many Sugar-related GSoC applications. Sugar Labs, although independent of OLPC, is in friendly, day-to-day communication with them. There is a clear distinction between each project's GSoC goals: anything related to the XS school server or to specific hardware issues on the OLPC XO-1 laptops would be covered by OLPC; The Sugar-related projects (the user-facing bits) would be covered by Sugar Labs. Nevertheless if both organizations are accepted, we expect some amount of confusion from students; both organizations are prepared to help redirect the applications of any students who apply to the wrong place.
===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.
===What license(s) does your project use?===
===What license(s) does your project use?===
The Sugar core is GPLv2+; some activity developers use other FOSS licenses, such as MIT, LGPL, etc.
The Sugar core is GPLv2+. Activity developers may choose other FOSS licenses - usually licenses such as MIT, LGPL, etc.
===What is the URL for your ideas page?===
===What is the URL for your ideas page?===
===What is the main IRC channel for your organization?===
===What is the main IRC channel for your organization?===
irc.freeenode.net #sugar
#sugar on irc.freenode.net
===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.===
====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 hours do you tend to work? (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====
[[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.]]
# 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 be your backup organization administrator? Please include Google Account information.===
===Who will be your backup organization administrator? Please include Google Account information.===
===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 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.
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.
===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.