Editing Google Summer of Code

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:
 
= Overview =
 
= Overview =
  
'''BRL-CAD is accepted as a mentoring organization in the [[Google_Summer_of_Code/2019|2019 Google Summer of Code]]!'''
+
'''BRL-CAD has been ACCEPTED to participate in the [[Google_Summer_of_Code/2011|2011 Google Summer of Code]]!'''
  
 
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 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:
Line 11: Line 11:
 
** That, in turn, determines how many student developers work with that organization.
 
** That, in turn, determines how many student developers work with that organization.
  
=Getting Started [[Summer_of_Code/Checklist|Checklist]]=
+
=Getting Started [[Google_Summer_of_Code/Checklist|Checklist]]=
  
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.
+
Whether you're applying or accepted, we've itemized everything you need to do into a simple '''[[Google_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.
 +
 
 +
==Preparing an Application==
 +
 
 +
If you're a student interested in working on a project proposal for BRL-CAD, refer to our '''[[Google_Summer_of_Code/Application_Guidelines|application guidelines]]'''.  It's full of submission details, do's and don't hints, and more.
  
 
== The Selection Process ==
 
== The Selection Process ==
 +
 +
'''''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.
  
 
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 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 youIt'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-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 great thing.
  
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-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 great thing.
+
Just about every GSoC organization receives considerably more project proposals than can be accepted.  Each proposal is reviewed, evaluated, and critiquedOf 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...''
  
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.  
+
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 appreciate '''everyone''' that submits a proposal to work on BRL-CAD.
  
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!
+
Thanks for your interest and we look forward to working with new BRL-CAD developers!
  
 
=BRL-CAD participation in GSoC =
 
=BRL-CAD participation in GSoC =
  
 
You can check out promotional flyers that have been prepared in the past on our [[Google_Summer_of_Code/Flyers|GSoC flyers]] page.
 
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/2019|GSoC 2019]]==
 
 
To be announced!
 
 
==[[Google_Summer_of_Code/2018|GSoC 2018]]==
 
 
Our umbrella selected 9 students that prepared quality proposals for BRL-CAD, FreeCAD, LibreCAD, or/and Slic3r. By the end of GSoC, all but 1 passed successfully.
 
 
==[[Google_Summer_of_Code/2017|GSoC 2017]]==
 
 
Our umbrella accepted 10 students that prepared quality proposals and demonstrated commitment. Students were selected for LibreCAD, Slic3r, BRL-CAD, and FreeCAD.
 
 
==[[Google_Summer_of_Code/2016|GSoC 2016]]==
 
 
This year we tamed it back to 9 students working on projects for BRL-CAD, OpenSCAD, LibreCAD, and FreeCAD (new partner).  We were not going to apply at all, but we also didn't want to lose momentum with our umbrella partners or leave them to fend for themselves.
 
 
==[[Google_Summer_of_Code/2015|GSoC 2015]]==
 
 
This year we had a whopping 12 students accepted to work on projects. As an umbrella organization, we expanded our cooperation to include LinuxCNC.
 
 
==[[Google_Summer_of_Code/2014|GSoC 2014]]==
 
 
Hoping to foster collaboration and communication, we actively reached out to a number of related and active open source CAD communities.  We expanded our umbrella to include cooperation with STEPcode, LibreCAD, and OpenSCAD.
 
 
==[[Google_Summer_of_Code/2013|GSoC 2013]]==
 
 
Middle ground, not too many, not too few.  It was just right.  We accepted seven students that all participated successfully.  This was also our first year participating as an umbrella organization, coordinating one of those slots with the STEPcode community.
 
 
==[[Google_Summer_of_Code/2012|GSoC 2012]]==
 
 
This year, we aimed big.  Lots of mentors, lots of students.  Compared to some of the larger notable orgs, students had a really great chance of acceptance if they were actively communicative and highly passionate about their project idea and BRL-CAD.  Overall, we accepted eleven students.
 
  
 
==[[Google_Summer_of_Code/2011|GSoC 2011]]==
 
==[[Google_Summer_of_Code/2011|GSoC 2011]]==
Line 69: Line 43:
 
  |}
 
  |}
  
After a year off focusing on a major development initiative, BRL-CAD once again was accepted to participate in the Google Summer of Code. We structured our participation minimally, however, intending to only accept a couple students.  In the end, we only accepted two students, both of whom did outstanding work.
+
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]]==
 
==[[Google_Summer_of_Code/2009|GSoC 2009]]==
Line 92: Line 61:
  
 
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.
 
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]]
+
[[Category: Google Summer of Code| Google Summer of Code]]
 +
[[category:Projects]]

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)