From Fedora Project Wiki

(first pass at a Fedora application, generously swiped under CC BY from http://wiki.sugarlabs.org/go/Summer_of_Code/Student_application_template)
 
(some fixes from this morning's meeting)
Line 1: Line 1:
This is the application form.  To use it do the following:
# 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




Line 7: Line 12:
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.
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====
== About you ==


# What is your name?
# What is your name?
Line 13: Line 18:
# What is your wiki username?
# What is your wiki username?
# What is your IRC nickname?
# 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.)
# 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.)
# 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?
# 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 ==


# What is the name of your project?
# What is the name of your project?
# 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 cancelling 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.
# 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.
# 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====
== You and the community ==


# 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.
# 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.
# What will you do if you get stuck on your project and your mentor isn't around?
# 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?  
# 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====
== Miscellaneous ==
# We want to make sure that you can set up an appropriate development environment before the summer starts.
# 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?
# What is your t-shirt size?
# What is your t-shirt size?
# Describe a great learning experience you had as a child.
# Describe a great learning experience you had as a child.

Revision as of 01:07, 8 April 2010

This is the application form. To use it do the following:

  1. Open a new browser tab.
  2. In the new tab navigate to a new page http://fedoraproject.org/wiki/

Random list of application requirements

  1. Must include a schedule that was worked out with mentor


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

  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 cancelling 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?

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 writing proposals. We encourage Summer Coding code to include tests.