Editing Google Summer of Code

= Overview =

'''BRL-CAD is applying 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 [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 writes up a project proposal to an open source organization such as 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 then reviewed, evaluated, and ranked by the open source organization's mentors.  Google allocates a certain number of slots to each participating organization which in turn determines how many student developers work with that organization.

=Getting Started=

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=

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.

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 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.

= The application selection process =

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.

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-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 good thing.

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.

Thanks for your interest and we look forward to seeing students apply!

=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.

==[[Google_Summer_of_Code/2009|GSoC 2011]]==

After a year off focusing on a major development initiative, BRL-CAD will once again be applying to participate in the Google Summer of Code.
 

==[[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: Google Summer of Code| Google Summer of Code]]
[[category:Projects]]
@@ Line 1: / Line 1: @@
 = 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:
+'''BRL-CAD is applying to participate in the 2011 Google Summer of Code!'''
-* The contributor writes a project proposal for BRL-CAD.
+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.  The student writes up a project proposal to an open source organization such as 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 then reviewed, evaluated, and ranked by the open source organization's mentors.  Google allocates a certain number of slots to each participating organization which in turn determines how many student developers work with that organization.
-** 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 [[Summer_of_Code/Checklist|Checklist]]=
+=Getting Started=
-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.
-== The Selection Process ==
+=Preparing an application=
-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.
+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.
-'''''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.
+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 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.
-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.
+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.
-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.
+= The application selection process =
-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!
+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.
-=BRL-CAD participation in GSoC =
+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-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 good thing.
-You can check out promotional flyers that have been prepared in the past on our [[Google_Summer_of_Code/Flyers|GSoC flyers]] page.
+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.
-==[[Google_Summer_of_Code/2024|GSoC 2024]]==
+Thanks for your interest and we look forward to seeing students apply!
-Our umbrella hopes to select 7 contributors for Manifold, IfcOpenShell, BRL-CAD, KiCad, Appleseed, and OpenSCAD.
+=BRL-CAD participation in GSoC =
-==[[Google_Summer_of_Code/2023|GSoC 2023]]==
+You can check out promotional flyers that have been prepared in the past on our [[Google_Summer_of_Code/Flyers|GSoC flyers]] page.
-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]]==
-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]]==
-{|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 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==
-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 2011]]==
+After a year off focusing on a major development initiative, BRL-CAD will once again be applying to participate in the Google Summer of Code.
 ==[[Google_Summer_of_Code/2009|GSoC 2009]]==
@@ Line 110: / Line 52: @@
 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]]