From Fedora Project Wiki

m (moved Summer Coding 2010 student proposal to Summer Coding 2010 student proposal application: Yeah, I'm wishy-washy. It's not exactly a sample page, it _is_ an application that requires all proposal details therein. We'll throw in the word a)
m (Reverted edits by Richards (Talk) to last version by Crimsonshadow)
 
(16 intermediate revisions by 6 users not shown)
Line 1: Line 1:
This is the application form.  To use it do the following:
For information how to complete this form, refer to [[Summer Coding 2010 step-by-step for students]].
 
# Open a new browser tab.
# In the new tab navigate to a new page http://fedoraproject.org/wiki/


== Random list of application requirements ==
== Random list of application requirements ==


# Must include a schedule that was worked out with mentor
# Must include a schedule that was worked out with mentor
# Keep on eye on the ''Talk:'' page that is associated with the proposal page you create.  Click on the ''discussion'' link on the top of your proposal page.  The Talk: page is where mentors comment on your proposal.
# Make sure you have clicked on the ''watch'' link on the top of your proposal page(s) and Talk: page(s).  Use the link to ''my preferences'' at the top of the page to set your ''Watchlist'' preferences to email you when changes are made.


== About you ==


<!-- below to update from sugarlabs page-->
<!-- This is a transclusion, where the entire contents of another page are pulled in to be included as-is here.  You need to create a [[Summer Coding 2010 student application - Your Name]] that is pulled in here. For more information, read [[Summer Coding 2010 step-by-step for students]]. -->
Please keep an eye on your talk page (the "discussion" link above). If you hit "watch" above, you can set up your "prefs" to email you the first time it changes since you last saw it.
 
== About you ==


# What is your name?
{{:Summer Coding 2010 student application - Example Student}}
# What is your email address?
# What is your wiki username?
# What is your IRC nickname?
# What is your primary language? (We have mentors who may speak your preferred languages and can match you with one of them if you request.)
# 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, why do you want to work on an open-source project this summer?


== About your project ==
== About your project ==
Line 27: Line 18:
# Does your project come from an idea on the [[Summer Coding 2010 ideas]] page?  If so, provide a link for reference, as well as a link to any discussions with mentors about your proposal.
# Does your project come from an idea on the [[Summer Coding 2010 ideas]] page?  If so, provide a link for reference, as well as a link to any discussions with mentors about your proposal.
# 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?
# 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 Fedora Summer Coding work period is 11 weeks long, May 24 - August 9; 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.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 5-12); the last steps always take longer than you think, and we will consider cancelling projects that are not mostly working by then.
# What is the timeline for development of your project? The Fedora Summer Coding work period is 11 weeks long, May 24 - August 9; 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.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 5-12); the last steps always take longer than you think, and we will consider canceling projects that are not mostly working by then.
#* If your project development progresses differently so there is not 90% functionality by the mid-term, you '''must''' be in regular contact with your mentor about this.  Your mentor must not be surprised about the state of your project when the mid-term comes.
#* If your project development progresses differently so there is not 90% functionality by the mid-term, you '''must''' be in regular contact with your mentor about this.  Your mentor must not be surprised about the state of your project when the mid-term comes.
#* If you are not progressed this far in mid-term, you must have a plan with your mentor to fix the situation.
#* If you are not progressed this far in mid-term, you must have a plan with your mentor to fix the situation.
Line 45: Line 36:
# Describe a great learning experience you had as a child.
# 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?
# 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?
<!-- Delete this paragraph and the following one when preparing your application. -->Note: you will post this application on the wiki in the category [[:Category:Summer Coding 2010 applications]]. We encourage you to browse this category and comment on the talk page of other applications. Also, others' comments and your 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.
The NeL project has some good general recommendations for [http://dev.ryzom.com/projects/nel/wiki/GSoC2009WritingProposals writing proposals]. We encourage Summer Coding code to include tests.
[[Category:Summer Coding 2010]]
[[Category:Summer Coding 2010 applications]]

Latest revision as of 17:04, 21 May 2010

For information how to complete this form, refer to Summer Coding 2010 step-by-step for students.

Random list of application requirements

  1. Must include a schedule that was worked out with mentor
  2. Keep on eye on the Talk: page that is associated with the proposal page you create. Click on the discussion link on the top of your proposal page. The Talk: page is where mentors comment on your proposal.
  3. Make sure you have clicked on the watch link on the top of your proposal page(s) and Talk: page(s). Use the link to my preferences at the top of the page to set your Watchlist preferences to email you when changes are made.

About you

  1. What is your name?
  2. What is your email address?
  3. What is your wiki username?
  4. What is your IRC nickname?
  5. What is your primary language? (We have mentors who may speak your preferred languages and can match you with one of them if you request.)
  6. Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
  7. 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, why do you want to work on an open-source project this summer?

About your project

  1. What is the name of your project?
  2. Does your project come from an idea on the Summer Coding 2010 ideas page? If so, provide a link for reference, as well as a link to any discussions with mentors about your proposal.
  3. 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?
  4. What is the timeline for development of your project? The Fedora Summer Coding work period is 11 weeks long, May 24 - August 9; 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.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 5-12); the last steps always take longer than you think, and we will consider canceling projects that are not mostly working by then.
    • If your project development progresses differently so there is not 90% functionality by the mid-term, you must be in regular contact with your mentor about this. Your mentor must not be surprised about the state of your project when the mid-term comes.
    • If you are not progressed this far in mid-term, you must have a plan with your mentor to fix the situation.
  5. 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

  1. If your project is successfully completed, what will its impact be on the Fedora 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 Fedora community, at least one of whom should be a Fedora Summer Coding mentor. Provide email contact information for non-Summer Coding mentors.
  2. What will you do if you get stuck on your project and your mentor isn't around?
  3. In addition to the required blogging minimum of twice per week, how do you propose to keep the community informed of your progress and any problems or questions you might have over the course of the project?

Miscellaneous

  1. We want to make sure that you are prepared before the project starts
    • Can you set up an appropriate development environment?
    • Have you met your proposed mentor and members of the associated community?
  2. What is your t-shirt size?
  3. Describe a great learning experience you had as a child.
  4. 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?
Retrieved from "https://fedoraproject.org/w/index.php?title=Summer_Coding_2010_student_proposal_application&oldid=175702"