Difference between revisions of "Google Summer of Code"

m (Reverted edits by 91.124.110.50 (Talk); changed back to last version by Sean)
Line 1: Line 1:
__NOTOC__
+
= Overview =
  
'''BRL-CAD has been accepted to participate in the [http://code.google.com/soc/2008/ 2008 Google Summer of Code]!'''
+
'''BRL-CAD has been ACCEPTED to participate in the [[Google_Summer_of_Code/2011|2011 Google Summer of Code]]!'''
  
Please see our [[Google_Summer_of_Code/Project_Ideas|Project Ideas]] page for a list of project suggestions that are of particular interest to our mentors.  There are several [http://brlcad.org/~sean/ideas.html other areas] of development that are of high-interest as wellStudents are welcome to submit their own unique ideas as well and are encouraged to collaborate with our mentors on formulating those projects.  Student applications for GSoC 2008 will be accepted on Google's project website between March 24 and March 31 at http://code.google.com/soc/2008/
+
Since 2005, Google has run an awesome open source software development program specifically for ''students'' called the [http://code.google.com/soc/ Google Summer of Code] (GSoC)Under this program, Google funds students to write code for open source projects during the northern hemisphere's summer timeframe:
  
Since 2005, Google has run an open source software development program specifically for students called the [http://code.google.com/soc/ Google Summer of Code] (GSoC).  Under this program, Google funds students to write code for open source projects during the northern hemisphere's summer timeframe.  The student efforts are focused on projects that they themselves propose to projects such as BRL-CAD, sometimes catering to ideas that the project suggests or ideas entirely of the student's own conception. Student proposals are then reviewed, evaluated, and ranked by the project mentors. Google allocates a certain number of slots to each participating project/organization which in turn determines how many student developers we get to work with.
+
* The student writes a project proposal for BRL-CAD.
 +
**Sometimes their project idea caters to something that the open source organization suggests and sometimes it's an idea entirely of the student's conception.
 +
* Proposals are reviewed, evaluated, and ranked by the open source organization's mentors.
 +
* Google allocates a certain number of slots to each participating organization
 +
** That, in turn, determines how many student developers work with that organization.
  
=Getting Started=
+
=Getting Started [[Summer_of_Code/Checklist|Checklist]]=
* Read this page
+
* Read our [[Google_Summer_of_Code/Project_Ideas|Project Ideas]]
+
* Read our [[Google_Summer_of_Code/Application_Guidelines|Application Guidelines]]
+
* Read our [[Google Summer of Code/Acceptance|Development Requirements]]
+
* Interact on the [http://irc.brlcad.org #brlcad] Freenode IRC channel
+
* Interact on the [http://lists.sourceforge.net/lists/listinfo/brlcad-devel mailing list]
+
* [http://sourceforge.net/tracker/?func=add&group_id=105292&atid=640804 Submit a patch]
+
* Prepare an application, discuss and share with mentors
+
* [http://code.google.com/soc/2008 Apply] between March 24 and March 31
+
  
=Preparing an application=
+
Whether you're applying or accepted, we've itemized everything you need to do into a simple '''[[Summer_of_Code/Checklist|CHECKLIST]]'''.  We're here to help you become new open source developers, so don't be shy if you have any questions.  See our [[Google_Summer_of_Code/2011|GSoC 2011]] page for more details.
  
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.  Proposals that are detailed in their approach and contain useful background information about the individual's abilities and their ideas will generally receive more attention.  Applications should specify what they intend to deliver, a reasonable development timeline, and any implementation details that are relevant such as what language(s) are intended to be used.  See our '''[[Google_Summer_of_Code/Application_Guidelines|Application Guidelines]]''' for more details.
+
== The Selection Process ==
  
Early proposal submission are 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 ideasSubmitting 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.
+
GSoC is about getting people involved and contributing to open source over the long-termAs such, we heavily weight our application selection process towards students that are interested in remaining involved in BRL-CAD and open source software development long after GSoC has ended.  
  
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, etcTheir ability to perform the task is outright presumed by the nature of submitting a detailed applicationStudents should propose a task that they are comfortable and knowledgeable with performing within the timeframe of the program and considering any extenuating circumstances.
+
'''''GSoC is not a job.''''' If you think this is just a summer job, then GSoC is probably not for youIt's only like a job in terms of planning your time commitment over the summer.
  
= The application review and selection process =
+
Additionally, submissions are graded based on perception of the submitter's abilities to complete the task within the program timeframe, general consensus on the technical approach being proposed, and overall interest in having such modifications made to BRL-CAD.  Particular notice is made of students that are responsive to questions and readily interactive in the IRC channel or on the mailing list.  Communication is a great thing.
  
Just about every GSoC project receives considerably more project proposals than can be accepted.  Each proposal is reviewed, evaluated, and critiqued.  Of those applications, only a small subset are selected so keep in mind that the selection process is rather competitive and difficult.  ''This cannot be stressed enough..''  It remains rather hard for most projects to narrow down the submissions but in the end we all  only have so many slots to work with and the line eventually has to be drawn.  Every application gets read multiple times and reviewed in detail.  We thank '''everyone''' that submits a proposal to work on BRL-CAD.
+
Just about every GSoC organization receives considerably more project proposals than can be accepted.  Every application gets read multiple times and reviewed in detail.  Of those applications, only a small subset are selected so keep in mind that the selection process is rather competitive and difficult.  
  
In the end, submissions are selected according to the overall long-term impact that accepting the proposal can make, perception of the submitter's abilities to complete the task within the program timeframe, general consensus on the technical approach being proposed, and overall interest in having such modifications made to BRL-CADParticular notice is made of students that are responsive to questions and readily interactive in the IRC channel or on the mailing listCommunication is a good thing.
+
Whether or not you are accepted, contributing to open source outside of GSoC is one of the main goals of the program and is the best way to be noticed and get your proposal acceptedKeep that in mindThanks for your interest and we look forward to working with new BRL-CAD developers!
  
Students are expected to interact on the [http://irc.brlcad.org/ #brlcad IRC channel] on the Freenode network, abide by the [http://brlcad.svn.sourceforge.net/svnroot/brlcad/brlcad/trunk/HACKING HACKING] rules, agree to the [[Google Summer of Code/Acceptance|Development Requirements]], and focus on providing a clean maintainable implementation.
+
=BRL-CAD participation in GSoC =
   
+
 
Thanks for your interest and we look forward to seeing students apply!nnnn
+
You can check out promotional flyers that have been prepared in the past on our [[Google_Summer_of_Code/Flyers|GSoC flyers]] page.
 +
 
 +
==[[Google_Summer_of_Code/2011|GSoC 2011]]==
 +
 
 +
{|align="right"
 +
|[[Image:BRL-CAD_GSoC2011_flyer.png|thumb|left|165px]]
 +
|}
 +
 
 +
After a year off focusing on a major development initiative, BRL-CAD once again has been accepted to participate in the Google Summer of Code!  For this year, we will be accepting no fewer than two students and no more than six students.  We generally get several dozen applications, less that ten of which tend to be of the quality we're looking for.  Regardless, chances of acceptance for highly passionate students is very high.
 +
 
 +
==GSoC 2010==
 +
 
 +
We [http://brlcad.org/d/node/47 took a break] and didn't apply to participate in 2010.  We wanted to give another org the chance to participate and allow ourselves a little extra time to focus on our own development priorities.
 +
 
 +
 
 +
==[[Google_Summer_of_Code/2009|GSoC 2009]]==
 +
 
 +
{|align="right"
 +
|[[Image:brlcad_gsoc2009_flyer.png|thumb|left|128px]]
 +
|}
 +
 
 +
For the second year in a row, BRL-CAD is participating in the Google Summer of Code.  BRL-CAD was accepted as a participating organization and took upon five students, four of which successfully worked their projects and integrated with the development team.
 +
 
 +
 
 +
==[[Google_Summer_of_Code/2008|GSoC 2008]]==
 +
 
 +
{|align="right"
 +
|[[Image:brlcad_gsoc2008_flyer.jpg|thumb|left|128px]]
 +
  |}
 +
 
 +
The Google Summer of Code 2008 was announced on February 25, 2008. BRL-CAD was accepted as a participating organization and took upon four students, all of which successfully worked their projects and integrated with the development team.
 +
[[Category: Summer of Code]]

Revision as of 09:59, 1 September 2011

Overview

BRL-CAD has been ACCEPTED to participate in the 2011 Google Summer of Code!

Since 2005, Google has run an awesome open source software development program specifically for students called the Google Summer of Code (GSoC). Under this program, Google funds students to write code for open source projects during the northern hemisphere's summer timeframe:

  • The student writes a project proposal for BRL-CAD.
    • Sometimes their project idea caters to something that the open source organization suggests and sometimes it's an idea entirely of the student's conception.
  • Proposals are reviewed, evaluated, and ranked by the open source organization's mentors.
  • Google allocates a certain number of slots to each participating organization
    • That, in turn, determines how many student developers work with that organization.

Getting Started Checklist

Whether you're applying or accepted, we've itemized everything you need to do into a simple CHECKLIST. We're here to help you become new open source developers, so don't be shy if you have any questions. See our GSoC 2011 page for more details.

The Selection Process

GSoC is about getting people involved and contributing to open source over the long-term. As such, we heavily weight our application selection process towards students that are interested in remaining involved in BRL-CAD and open source software development long after GSoC has ended.

GSoC is not a job. If you think this is just a summer job, then GSoC is probably not for you. It's only like a job in terms of planning your time commitment over the summer.

Additionally, submissions are graded based on perception of the submitter's abilities to complete the task within the program timeframe, general consensus on the technical approach being proposed, and overall interest in having such modifications made to BRL-CAD. Particular notice is made of students that are responsive to questions and readily interactive in the IRC channel or on the mailing list. Communication is a great thing.

Just about every GSoC organization receives considerably more project proposals than can be accepted. Every application gets read multiple times and reviewed in detail. Of those applications, only a small subset are selected so keep in mind that the selection process is rather competitive and difficult.

Whether or not you are accepted, contributing to open source outside of GSoC is one of the main goals of the program and is the best way to be noticed and get your proposal accepted. Keep that in mind. Thanks for your interest and we look forward to working with new BRL-CAD developers!

BRL-CAD participation in GSoC

You can check out promotional flyers that have been prepared in the past on our GSoC flyers page.

GSoC 2011

BRL-CAD GSoC2011 flyer.png

After a year off focusing on a major development initiative, BRL-CAD once again has been accepted to participate in the Google Summer of Code! For this year, we will be accepting no fewer than two students and no more than six students. We generally get several dozen applications, less that ten of which tend to be of the quality we're looking for. Regardless, chances of acceptance for highly passionate students is very high.

GSoC 2010

We took a break and didn't apply to participate in 2010. We wanted to give another org the chance to participate and allow ourselves a little extra time to focus on our own development priorities.


GSoC 2009

Brlcad gsoc2009 flyer.png

For the second year in a row, BRL-CAD is participating in the Google Summer of Code. BRL-CAD was accepted as a participating organization and took upon five students, four of which successfully worked their projects and integrated with the development team.


GSoC 2008

Brlcad gsoc2008 flyer.jpg

The Google Summer of Code 2008 was announced on February 25, 2008. BRL-CAD was accepted as a participating organization and took upon four students, all of which successfully worked their projects and integrated with the development team.