Difference between revisions of "Google Summer of Code"
(redo update for 2016) |
|||
| (14 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
| − | ''' | + | Since 2005, Google has run an awesome open source software development program originally just for ''students'', but now any ''contributor'' called the [http://code.google.com/soc/ Google Summer of Code] (GSoC). Under this program, Google funds people to write code for open source projects during the northern hemisphere's summer timeframe: |
| − | + | * The contributor writes a project proposal for BRL-CAD. | |
| − | + | ** Sometimes their project idea caters to something the open source organization suggests and sometimes it's a contributor's idea. | |
| − | * The | ||
| − | **Sometimes their project idea caters to something | ||
* Proposals are reviewed, evaluated, and ranked by the open source organization's mentors. | * Proposals are reviewed, evaluated, and ranked by the open source organization's mentors. | ||
* Google allocates a certain number of slots to each participating organization | * Google allocates a certain number of slots to each participating organization | ||
| − | ** That, in turn, determines how many | + | ** That, in turn, determines how many contributors will work with that organization. |
=Getting Started [[Summer_of_Code/Checklist|Checklist]]= | =Getting Started [[Summer_of_Code/Checklist|Checklist]]= | ||
| Line 17: | Line 15: | ||
== The Selection Process == | == 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 | + | 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 people 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. | '''''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 | + | 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 applicants 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. | 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. | ||
| Line 30: | Line 28: | ||
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/2024|GSoC 2024]]== | ||
| + | |||
| + | Our umbrella hopes to select 7 contributors for Manifold, IfcOpenShell, BRL-CAD, KiCad, Appleseed, and OpenSCAD. | ||
| + | |||
| + | ==[[Google_Summer_of_Code/2023|GSoC 2023]]== | ||
| + | |||
| + | Our umbrella selected 5 contributors that prepared proposals for IfcOpenShell, BRL-CAD, KiCad, Appleseed and OpenSCAD. | ||
| + | |||
| + | ==[[Google_Summer_of_Code/2022|GSoC 2022]]== | ||
| + | |||
| + | Our umbrella selected 7 students that prepared proposals for IfcOpenShell, BRL-CAD, KiCad, LibreCAD and OpenSCAD. | ||
| + | |||
| + | ==[[Google_Summer_of_Code/2021|GSoC 2021]]== | ||
| + | |||
| + | With global turmoil in full effect, we again reigned back participation, only accepting 6 students, all of which were successful. Students worked with IfcOpenShell, FreeCAD, OpenSCAD, and BRL-CAD. | ||
| + | |||
| + | ==[[Google_Summer_of_Code/2020|GSoC 2020]]== | ||
| + | |||
| + | We reigned participation back a bit in 2019, accepting 8 students, all of which were successful. Students worked with FreeCAD, BRL-CAD, OpenSCAD, and LibreCAD. | ||
| + | |||
| + | ==[[Google_Summer_of_Code/2019|GSoC 2019]]== | ||
| + | |||
| + | Our umbrella selected 10 students that prepared proposals for BRL-CAD, OpenSCAD, LibreCAD, FreeCAD, and Slic3r. students passed successfully. | ||
| + | |||
| + | ==[[Google_Summer_of_Code/2018|GSoC 2018]]== | ||
| + | |||
| + | Our umbrella selected 9 students that prepared quality proposals for BRL-CAD, FreeCAD, LibreCAD, 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]]== | ==[[Google_Summer_of_Code/2016|GSoC 2016]]== | ||
Latest revision as of 17:35, 16 February 2024
Overview[edit]
Since 2005, Google has run an awesome open source software development program originally just for students, but now any contributor called the Google Summer of Code (GSoC). Under this program, Google funds people to write code for open source projects during the northern hemisphere's summer timeframe:
- The contributor writes a project proposal for BRL-CAD.
- Sometimes their project idea caters to something the open source organization suggests and sometimes it's a contributor's idea.
- 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 contributors will work with that organization.
Getting Started Checklist[edit]
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.
The Selection Process[edit]
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 people 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 applicants 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[edit]
You can check out promotional flyers that have been prepared in the past on our GSoC flyers page.
GSoC 2024[edit]
Our umbrella hopes to select 7 contributors for Manifold, IfcOpenShell, BRL-CAD, KiCad, Appleseed, and OpenSCAD.
GSoC 2023[edit]
Our umbrella selected 5 contributors that prepared proposals for IfcOpenShell, BRL-CAD, KiCad, Appleseed and OpenSCAD.
GSoC 2022[edit]
Our umbrella selected 7 students that prepared proposals for IfcOpenShell, BRL-CAD, KiCad, LibreCAD and OpenSCAD.
GSoC 2021[edit]
With global turmoil in full effect, we again reigned back participation, only accepting 6 students, all of which were successful. Students worked with IfcOpenShell, FreeCAD, OpenSCAD, and BRL-CAD.
GSoC 2020[edit]
We reigned participation back a bit in 2019, accepting 8 students, all of which were successful. Students worked with FreeCAD, BRL-CAD, OpenSCAD, and LibreCAD.
GSoC 2019[edit]
Our umbrella selected 10 students that prepared proposals for BRL-CAD, OpenSCAD, LibreCAD, FreeCAD, and Slic3r. students passed successfully.
GSoC 2018[edit]
Our umbrella selected 9 students that prepared quality proposals for BRL-CAD, FreeCAD, LibreCAD, and Slic3r. By the end of GSoC, all but 1 passed successfully.
GSoC 2017[edit]
Our umbrella accepted 10 students that prepared quality proposals and demonstrated commitment. Students were selected for LibreCAD, Slic3r, BRL-CAD, and FreeCAD.
GSoC 2016[edit]
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.
GSoC 2015[edit]
This year we had a whopping 12 students accepted to work on projects. As an umbrella organization, we expanded our cooperation to include LinuxCNC.
GSoC 2014[edit]
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.
GSoC 2013[edit]
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.
GSoC 2012[edit]
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.
GSoC 2011[edit]
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.
GSoC 2010[edit]
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[edit]
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[edit]
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.
