Editing Summer of Code/Application Guidelines

From BRL-CAD

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
=Writing a Successful Application=
+
There is intentionally no specific format that students need to use to apply to BRL-CAD.  There are, however, several things that you should and should not do when applying.
  
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.
+
= Do's =
  
Early submissions are encouraged as it gives more time to review proposals in detail, offer feedback, and maybe ask questionsSubmitting closer to the deadline isn't bad other than not getting feedback in advance.
+
'''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 linksYou don't have to solve everything, but we need to see that you've thought things through.  Impress us.
  
== Do's ==
+
'''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.
  
'''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 writingCite 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.
+
'''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 welcomeIf your proposal is for one of our ideas, be innovative and ambitious in your solution.  
  
'''Get Involved Early.'''  Join IRC, say hi on the mailing list, download the source code, and try things outTalk to others, get to know who is who.  Communicate early, communicate often.
+
'''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 mindIf you've got another part-time or full-time job, you probably won't be able to put in the effort or time necessary.
  
'''Be Bold.'''  We love innovative ideasMake sure yours is in scope and is something we're interested in mentoring, but you're not limited to our ideasBe ambitious and thorough in your solution.  
+
'''Be Passionate.'''  Show enthusiasm for your idea.  Be excited to work with usExcitement and passion are never a substitute for competence, but they vastly help your chances all other factors being equalExpress your passion and any background information about yourself that reinforces your interests.
  
'''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.
+
= Don'ts =
  
'''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't copy/paste our ideas.'''  If all you have to say about the idea is what we've said, it will be rejectedThey are just meant to be starting points.
  
== Don'ts ==
+
'''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.
  
'''Don't copy/paste.'''  If all you have to say about the project idea is what we wrote, it will be rejectedThey are just meant to be starting points.
+
'''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 upfrontYou 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 be brief.'''  Anticipate questions, include detailsIf your application is less than a few hundred words, you're probably not including necessary detail about your plans or yourselfBrief proposals very quickly get cut.
+
'''Don't be intimidated.'''  Your ideas will be questioned and critiqued.  We don't all agree, even amongst ourselves oftenYou will need to be able to openly and publicly talk about your ideas without being defensiveBe open to the ideas and suggestions of others and be willing to amicably engage in discussions.
  
'''Don't be intimidated.'''  We don't bite.  Your ideas will be questioned, we might disagree, and that's okayIt means we're interestedYou 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.'''  During the application process, we receive a lot of applicationsBe patientIf we don't respond to your application for more information, it usually means that it's either really bad or really goodUnderstand that we have a lot to sort through and discussIt's a very competitive process given we can only accept a limited number of studentsIf you have specific questions, engage the mentors.
 
 
'''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 applicationInclude 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=
 
 
 
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 submittedFinal 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 [[Summer_of_Code/Acceptance|participation requirements]] should you get selected.
 
 
 
 
 
[[category:Summer of Code]]
 

Please note that all contributions to BRL-CAD may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see BRL-CAD:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)