Difference between revisions of "Summer of Code/Application Guidelines"

From BRL-CAD
(reorder for clarity)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
= Application Format=
+
=Writing a Successful Application=
−
There is intentionally no specific format to our applications. '''BUT'''... students are '''strongly''' encouraged to be detailed, creative, and interactive with the BRL-CAD developers throughout the application process.  
+
 
 +
Students should propose what they actually intend to accomplish, what they know about that task, and details about their background. Ability to perform the task is outright ''presumed'' by submitting a proposal. Students should propose a project catered to their ability that can be completed within the timeframe of the program. Students can demonstrate coding experience with patches.
 +
 
 +
Early submissions are encouraged as it gives more time to review proposals in detail, offer feedback, and maybe ask questions.  Submitting closer to the deadline isn't bad other than not getting feedback in advance.
 +
 
 +
== Do's ==
 +
 
 +
'''Be Detailed and Articulate.''' Go into detail about what you intend to do and how you intend to do it.  Don't have typos and be clear in your writing.  Cite academic references if they're relevant to your work.  Create diagrams, show prototypes, create mock-up visuals, and provide more information via external links.  You don't have to solve everything, but we need to see that you've thought things through.
 +
 
 +
'''Get Involved Early.'''  Join IRC, say hi on the mailing list, download the source code, and try things out.  Talk to others, get to know who is who.  Communicate early, communicate often.
  
−
As such, there are several things that you should and should not do when applying.  Be sure to check out the [[Google_Summer_of_Code/Checklist|checklist]] of things that you need to do before, during, and after GSoC.   As for your actual application, make sure it ''at least'' includes the following:
+
'''Be Bold.'''  We love innovative ideas.  Make sure yours is in scope and is something we're interested in mentoring, but you're not limited to our ideas.  Be ambitious and thorough in your solution.  
  
−
*Personal Information
+
'''Be Realistic.'''  Make sure the scope of your work is feasible and that you will have the necessary skills to implement your project on time.  No bonus for proposing to reinvent the Internet.  If you've got another job or commitment, your proposal should account for that obligation.
−
**Name
 
−
**E-mail address
 
−
**IRC username
 
−
**Brief background info
 
−
*Project Information
 
−
**Project Title
 
−
**Brief project summary (<500 words)
 
−
**Detailed project description (>500 words)
 
−
**Development timeline with at least three milestones
 
−
**References to any code or algorithms you want to use
 
  
−
=Writing a Successful Application=
+
'''Be Passionate.'''  Show enthusiasm for your idea.  Be excited.  Passion is never a substitute for competence, but vastly helps your chances all other factors being equal.
−
Early proposal submissions are strongly encouraged as it gives us more time to review the proposal in detail, comment on it, potentially ask for additional input, and iterate with the student on their ideas.  Submitting closer to the deadline isn't necessarily a negative consideration as all submissions are predominantly judged on merit, but submitting and discussing early is an advantage for submissions that have similar goals.
 
  
−
Students should propose what they actually want to work on, how they intend to work on it, what they intend to DO, what they know about that task, some details about themselves, etc.  Their ability to perform the task is outright ''presumed'' by the nature of submitting a detailed application.  Students should propose a task that they are comfortable and knowledgeable with performing within the timeframe of the program and considering any extenuating circumstances.
+
== Don'ts ==
  
−
= Do's =
+
'''Don't copy/paste.'''  If all you have to say about the project idea is what we wrote, it will be rejected.  They are just meant to be starting points.
  
−
'''Be Detailed and Articulate.'''  Go into detail about what you intend to do and how you intend to do it.  Don't have typos and be clear in your writing. Cite academic references if they're relevant to your work. Create diagrams, show prototypes, create mock-up visuals, and provide more information via external links.  You don't have to solve everything, but we need to see that you've thought things through.  Impress us.
+
'''Don't be brief.''' Anticipate questions, include details.  If your application is less than a few hundred words, you're probably not including necessary detail about your plans or yourself.  Brief proposals very quickly get cut.
  
−
'''Get Involved Early.'''  You need to join our IRC channel, compile the code, try things out, and get involved in our community.  Talk to the other developers, find a mentor that likes your proposal idea.  Don't forget to mention your IRC nick in your application.  We interact with a lot of people so give us a personality that we can recognize when it comes to reviewing the applications.  Communicate early, communicate often.
+
'''Don't be intimidated.'''  We don't bite.  Your ideas will be questioned, we might disagree, and that's okay.  It means we're interested.  You will need to be able to talk about your ideas without getting defensive, be open to compromise, and take suggestions from others.
  
−
'''Be Bold.'''  We love new innovative ideas.  You should make sure your idea fits into the scope of our project and is something we're interested in mentoring, but new projects are welcome.  If your proposal is for one of our ideas, be innovative and ambitious in your solution.  
+
'''Don't be discouraged.'''  We have accepted those with no experience to experts and everything in between.  Cater your application to your skills and you'll do just fine.  You're expected to work hard and do your homework researching questions, but you're encouraged ask for help if you truly get stuck too.
  
−
'''Be Realistic.'''  Make sure the scope of your work is feasible and that you will have the necessary skills to implement your project on time.  Don't be so bold that you are unrealistic, keep your abilities and time constraints in mind.  If you've got another part-time or full-time job, you probably won't be able to put in the effort or time necessary.
+
'''Don't forget to tell us about yourself.'''  Most of what we know about you and your abilities is going to come from your application.  Include details about your background, experience, and anything else relevant to your work.  If you have obligations that will impact your proposal, be upfront.  You should be interacting with our community on IRC or on the developer mailing list long before you submit your proposal so we have an idea how you interact.  Don't forget to mention your IRC nick in your application.
  
−
'''Be Passionate.'''  Show enthusiasm for your idea.  Be excited to work with us.  Excitement and passion are never a substitute for competence, but they vastly help your chances all other factors being equal.  Express your passion and any background information about yourself that reinforces your interests.
 
  
−
= Don'ts =
+
= Application Format=
  
−
'''Don't copy/paste our ideas.''' If all you have to say about the idea is what we've said, it will be rejected.  They are just meant to be starting points.
+
There is intentionally no specific format to our applications. '''BUT'''... students are '''strongly''' encouraged to be creative, detailed, and discuss throughout the application process.  Use a wiki page or the mailing list so your proposal can be reviewed before it's officially submitted.  Final proposals should include ''at least'' the following information:
  
−
'''Don't be brief.'''  Anticipate questions, include details.  If your application isn't any more than a few hundred words or less, then you're probably not including useful/necessary detail about the project, your plans, or yourself.  Brief proposals very quickly get cut, especially when compared to proposals in similar areas that do include detail.
+
*Personal Information
 +
**Name
 +
**E-mail address
 +
**IRC username
 +
**Brief background info
 +
**(optional) Link to resumé
 +
*Project Information
 +
**Project Title
 +
**Brief project summary (<500 words)
 +
**Detailed project description (>500 words)
 +
**Links to any code or algorithms you intend to use
 +
**Deliverables (specific, measurable goals)
 +
**Development schedule
 +
***List at least three milestones
 +
**Describe time availability (40+ hours/week assumed)
 +
***List all commitments (e.g., exams, vacations)
 +
**(optional) Why us?
 +
**(optional) Why you?
 +
**(optional) Anything else?
  
−
'''Don't forget to tell us about yourself.'''  Most of what we know about you and your abilities is going to come from your application.  Include details about your background, experience, and anything else relevant to your work.  If you have obligations that will impact your proposal, be upfront.  You should be interacting with our community on IRC or on the developer mailing list long before you submit your proposal so we have an idea how you interact.
+
You must agree to our [[Summer_of_Code/Acceptance|participation requirements]] should you get selected.
  
−
'''Don't be intimidated.'''  Your ideas will be questioned and critiqued.  We don't all agree, even amongst ourselves often.  You will need to be able to openly and publicly talk about your ideas without being defensive.  Be open to the ideas and suggestions of others and be willing to amicably engage in discussions.
 
  
−
'''Don't be discouraged.'''  During the application process, we receive a lot of applications.  Be patient.  If we don't respond to your application for more information, it usually means that it's either really bad or really good.  Understand that we have a lot to sort through and discuss.  It's a very competitive process given we can only accept a limited number of students.  If you have specific questions, engage the mentors.
+
[[category:Summer of Code]]
−
[[category:Google Summer of Code]]
 

Latest revision as of 17:35, 4 March 2014

Writing a Successful Application[edit]

Students should propose what they actually intend to accomplish, what they know about that task, and details about their background. Ability to perform the task is outright presumed by submitting a proposal. Students should propose a project catered to their ability that can be completed within the timeframe of the program. Students can demonstrate coding experience with patches.

Early submissions are encouraged as it gives more time to review proposals in detail, offer feedback, and maybe ask questions. Submitting closer to the deadline isn't bad other than not getting feedback in advance.

Do's[edit]

Be Detailed and Articulate. Go into detail about what you intend to do and how you intend to do it. Don't have typos and be clear in your writing. Cite academic references if they're relevant to your work. Create diagrams, show prototypes, create mock-up visuals, and provide more information via external links. You don't have to solve everything, but we need to see that you've thought things through.

Get Involved Early. Join IRC, say hi on the mailing list, download the source code, and try things out. Talk to others, get to know who is who. Communicate early, communicate often.

Be Bold. We love innovative ideas. Make sure yours is in scope and is something we're interested in mentoring, but you're not limited to our ideas. Be ambitious and thorough in your solution.

Be Realistic. Make sure the scope of your work is feasible and that you will have the necessary skills to implement your project on time. No bonus for proposing to reinvent the Internet. If you've got another job or commitment, your proposal should account for that obligation.

Be Passionate. Show enthusiasm for your idea. Be excited. Passion is never a substitute for competence, but vastly helps your chances all other factors being equal.

Don'ts[edit]

Don't copy/paste. If all you have to say about the project idea is what we wrote, it will be rejected. They are just meant to be starting points.

Don't be brief. Anticipate questions, include details. If your application is less than a few hundred words, you're probably not including necessary detail about your plans or yourself. Brief proposals very quickly get cut.

Don't be intimidated. We don't bite. Your ideas will be questioned, we might disagree, and that's okay. It means we're interested. You will need to be able to talk about your ideas without getting defensive, be open to compromise, and take suggestions from others.

Don't be discouraged. We have accepted those with no experience to experts and everything in between. Cater your application to your skills and you'll do just fine. You're expected to work hard and do your homework researching questions, but you're encouraged ask for help if you truly get stuck too.

Don't forget to tell us about yourself. Most of what we know about you and your abilities is going to come from your application. Include details about your background, experience, and anything else relevant to your work. If you have obligations that will impact your proposal, be upfront. You should be interacting with our community on IRC or on the developer mailing list long before you submit your proposal so we have an idea how you interact. Don't forget to mention your IRC nick in your application.


Application Format[edit]

There is intentionally no specific format to our applications. BUT... students are strongly encouraged to be creative, detailed, and discuss throughout the application process. Use a wiki page or the mailing list so your proposal can be reviewed before it's officially submitted. Final proposals should include at least the following information:

  • Personal Information
    • Name
    • E-mail address
    • IRC username
    • Brief background info
    • (optional) Link to resumé
  • Project Information
    • Project Title
    • Brief project summary (<500 words)
    • Detailed project description (>500 words)
    • Links to any code or algorithms you intend to use
    • Deliverables (specific, measurable goals)
    • Development schedule
      • List at least three milestones
    • Describe time availability (40+ hours/week assumed)
      • List all commitments (e.g., exams, vacations)
    • (optional) Why us?
    • (optional) Why you?
    • (optional) Anything else?

You must agree to our participation requirements should you get selected.

Retrieved from "https://brlcad.org/w/index.php?title=Summer_of_Code/Application_Guidelines&oldid=6532"