This wiki is archived and useful information is being migrated to the main bzflag.org website

Difference between revisions of "Google Summer of Code"

From BZFlagWiki
Jump to: navigation, search
(intro paragraph)
(add a getting started section, and merge in application detail sections)
Line 5: Line 5:
 
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 BZFlag, 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.  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.
 
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 BZFlag, 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.  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.
  
= BZFlag participation =
+
Students that participate with the BZFlag project are required to adhere to specified [[Google Summer of Code Acceptance|development requirements]], selected students then work on their projects through the summer.  Students are expected to be fully integrated with the BZFlag development community throughout the program, actively engaged in their work, and intently working ''with'' the other BZFlag developers throughout the design and implementation of their projects.  If the student successfully completes what they propose, they are ultimately paid $4500 for their work and the BZFlag community hopefully gains a new long-term developer.  In all, the program is a pretty darn good deal for many students, great publicity and marketing for both Google and BZFlag, and a great opportunity for BZFlag development initiatives.
  
== [[Google Summer of Code/2008|2008 (more details here)]] ==
+
= Getting started =
  
The Google Summer of Code 2008 was announced on February 25, 2008. Given the substantial successes and opportunities provided by the program, BZFlag will continue to participate in the program. BZFlag has been accepted as a mentoring organization, and will accept student project proposals from March 24 to March 31. Please click the link above for more information and for project proposal ideas.
+
* Read this page
 +
* Read our [[Google Summer of Code/2008|proposal ideas]] page
 +
* Read our [[Google_Summer_of_Code/Application_Guidelines|application guidelines]]
 +
* Read our [[Google Summer of Code Acceptance|development requirements]]
 +
* Read our [http://bzflag.svn.sourceforge.net/viewvc/*checkout*/bzflag/trunk/bzflag/DEVINFO DEVINFO] file
 +
* Join our [[BZFlag on IRC|#bzflag on Freenode]] IRC channel
 +
* Formulate a proposal idea, communicate with devs
 +
* [http://sourceforge.net/tracker/?group_id=3248&atid=303248 Submit a patch]
 +
* [http://code.google.com/soc/2008 Apply] between March 24 and March 31
  
== [[Google Summer of Code/2007|2007 (more details here)]] ==
+
= Preparing an application =
{|align="right"
+
|[[Image:Gsoc_postmortem_preview.png|thumb|left|128px|http://my.bzflag.org/gsoc/bzflag_gsoc2007_post_mortem.pdf]]
+
|}
+
BZFlag first participated during GSoC's third year in 2007.  A detailed after-the-fact discussion and analysis of BZFlag's first-year participation is included in the article ''[http://my.bzflag.org/gsoc/bzflag_gsoc2007_post_mortem.pdf “Postmortem” Perspectives of a First-year Participant in the 2007 Google Summer of Code for BZFlag]''.  This article was given to Google in August 2007 as a final report, per se, of our involvement (you're only a first-year participant once).
+
  
==== [[Google Summer of Code/2007#Promotion Flyers|Promotion Flyers]] ====
+
There is intentionally no specific format to our applications. '''BUT'''... students are '''strongly''' encouraged to be detailed, creative, and interactive with the BZFlag 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 you intend to deliver, a reasonable development timeline, and any implementation details that are relevant such as what language(s) you intend to use.  C/C++ proposals are generally preferred since that is our predominant codebase and developer expertise though others are considered.  See our '''[[Google_Summer_of_Code/Application_Guidelines|Application Guidelines]]''' for more details.
  
= [[Google_Summer_of_Code/Application_Guidelines|Preparing an application]] =
+
Early proposal submissions are encouraged as it gives the mentors more time to review the proposal in detail, comment on it, potentially ask for additional input, and iterate with the student on your ideas.  In the past, submitting closer to the deadline hasn't been a negative consideration, as all submissions are predominantly judged on merit, but submitting and discussing early do tend to be an advantage if there are others applications that have similar goals.
  
There is intentionally no specific format to our applications. '''BUT'''... students are '''strongly''' encouraged to be detailed, creative, and interactive with the BZFlag developers throughout the application processProposals that are detailed in their approach and contain useful background information about the individual's abilities and their ideas will generally receive more attentionApplications 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 usedC/C++ proposals are generally preferred since that is our predominant codebase and developer expertise though others are considered.  See our '''[[Google_Summer_of_Code/Application_Guidelines|Application Guidelines]]''' for more details.
+
Students should propose what they actually want to work on, how you intend to work on it, what you intend to DO, what you know about that task, some details about yourself, etcBe detailed and articulate.  Brief proposals do not generally do very wellYour 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.
  
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.  In the past, submitting closer to the deadline hasn't been 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.
+
If you talk with us on IRC about your SoC proposal, be sure to include your IRC nickname somewhere in your proposal.
  
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 applicationStudents should propose a task that they are comfortable and knowledgeable with performing within the timeframe of the program and considering any extenuating circumstances.
+
You should also [http://sourceforge.net/tracker/?group_id=3248&atid=303248 submit a patch] before you submit your application, and be sure to include a link to the tracker item in your proposal submissionSee the [[Google Summer of Code Acceptance|development requirements]] for details.
  
= The application process =
+
Students are expected to interact on the [http://my.bzflag.org/irc/ #bzflag IRC channel] on the Freenode network, abide by the [http://bzflag.svn.sourceforge.net/viewvc/*checkout*/bzflag/trunk/bzflag/DEVINFO DEVINFO] rules, and agree to the [[Google Summer of Code Acceptance|development requirements]] before submitting an application.
  
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 BZFlag.
+
Thanks for your interest and we look forward to seeing you apply!
  
In the end, submissions are selected according to the overall long-term impact that accepting the proposal can make for the game, 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 BZFlag.  Particular notice is made of students that are responsive to questions and readily interactive in the IRC channel.  Communication is a good thing.
+
= The application review process =
  
While there's never any guarantee that work on any code will be integrated, this is very much the desire and one of the core '''intentions''' of participation in the Summer of CodeStudents are expected to interact on the [http://my.bzflag.org/irc/ #bzflag IRC channel] on the Freenode network, abide by the [http://bzflag.svn.sourceforge.net/viewvc/*checkout*/bzflag/trunk/bzflag/DEVINFO DEVINFO] rules, agree to the [[Google Summer of Code Acceptance|development requirements]], and focus on providing a clean maintainable implementation.
+
Just about every participating GSoC organization receives considerably more project proposals than can be accepted.  All the applications are reviewed, evaluated, and critiqued individually.  Of those applications, only a few can be selected to work on BZFlag.  We expect to receive many good applications, making the selection process very competitive and difficult (so make sure your application is excellent).  ''This cannot be stressed enough.''  It is rather hard for most projects to narrow down the submissions but in the end there are only 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 and hope to see many of you become involved in BZFlag software development regardless of acceptance.
 +
   
 +
In the end, submissions are selected according to the overall long-term impact that accepting the proposal can make for the game, perception of the submitter's abilities to complete the task within the program timeframe, general consensus on the technical approach being proposed, how well the student communicates with other developers, the perception that the individual is interested in being a long-term BZFlag developer, and our overall interest in having the proposed modifications made to BZFlag.  Particular notice is made of students that are responsive to questions and readily interactive in the IRC channel.  Communication is one of the most important criteria.
  
= Integrated development =
+
Be sure to follow the aforementioned application preparation steps mentioned above.  The final list of selected proposals will be announced on April 14, 2008 at 12:00 noon PDT.
  
Students that participate with the BZFlag project are required to adhere to specified [[Google Summer of Code Acceptance|development requirements]], selected students then work on their projects through the summer.  Students are expected to be fully integrated with the BZFlag development community throughout the program, actively engaged in their work, and intently working ''with'' the other BZFlag developers throughout the design and implementation of their projects.  If the student successfully completes what they propose, they are ultimately paid $4500 for their work and the BZFlag community hopefully gains a new long-term developer.  In all, the program is a pretty darn good deal for many students, great publicity and marketing for both Google and BZFlag, and a great opportunity for BZFlag development initiatives.
 
  
Thanks for your interest and we look forward to seeing students apply!
+
= BZFlag participation in GSoc =
 +
 
 +
== [[Google Summer of Code/2008|2008 (more details here)]] ==
 +
 
 +
The Google Summer of Code 2008 was announced on February 25, 2008. Given the substantial successes and opportunities provided by the program, BZFlag will continue to participate in the program. BZFlag has been accepted as a mentoring organization, and will accept student project proposals from March 24 to March 31. Please click the link above for more information and for project proposal ideas.
 +
 
 +
== [[Google Summer of Code/2007|2007 (more details here)]] ==
 +
{|align="right"
 +
|[[Image:Gsoc_postmortem_preview.png|thumb|left|128px|http://my.bzflag.org/gsoc/bzflag_gsoc2007_post_mortem.pdf]]
 +
|}
 +
BZFlag first participated during GSoC's third year in 2007.  A detailed after-the-fact discussion and analysis of BZFlag's first-year participation is included in the article ''[http://my.bzflag.org/gsoc/bzflag_gsoc2007_post_mortem.pdf “Postmortem” Perspectives of a First-year Participant in the 2007 Google Summer of Code for BZFlag]''.  This article was given to Google in August 2007 as a final report, per se, of our involvement (you're only a first-year participant once).
 +
 
 +
==== [[Google Summer of Code/2007#Promotion Flyers|Promotion Flyers]] ====
 +
 
  
 
[[Category: Development]]
 
[[Category: Development]]

Revision as of 04:33, 22 March 2008

For the second year in a row, BZFlag has been accepted to participate in the 2008 Google Summer of Code!

Please see our Proposal Ideas for a list of the project that are currently of interest to the BZFlag developers. Student applications for GSoC 2008 will be accepted via the GSoC website between March 24 and March 31 at http://code.google.com/soc/2008

Since 2005, Google has run an 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 efforts are focused on projects that they themselves propose to projects such as BZFlag, 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. 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.

Students that participate with the BZFlag project are required to adhere to specified development requirements, selected students then work on their projects through the summer. Students are expected to be fully integrated with the BZFlag development community throughout the program, actively engaged in their work, and intently working with the other BZFlag developers throughout the design and implementation of their projects. If the student successfully completes what they propose, they are ultimately paid $4500 for their work and the BZFlag community hopefully gains a new long-term developer. In all, the program is a pretty darn good deal for many students, great publicity and marketing for both Google and BZFlag, and a great opportunity for BZFlag development initiatives.

Getting started

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 BZFlag 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 you intend to deliver, a reasonable development timeline, and any implementation details that are relevant such as what language(s) you intend to use. C/C++ proposals are generally preferred since that is our predominant codebase and developer expertise though others are considered. See our Application Guidelines for more details.

Early proposal submissions are encouraged as it gives the mentors more time to review the proposal in detail, comment on it, potentially ask for additional input, and iterate with the student on your ideas. In the past, submitting closer to the deadline hasn't been a negative consideration, as all submissions are predominantly judged on merit, but submitting and discussing early do tend to be an advantage if there are others applications that have similar goals.

Students should propose what they actually want to work on, how you intend to work on it, what you intend to DO, what you know about that task, some details about yourself, etc. Be detailed and articulate. Brief proposals do not generally do very well. Your 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.

If you talk with us on IRC about your SoC proposal, be sure to include your IRC nickname somewhere in your proposal.

You should also submit a patch before you submit your application, and be sure to include a link to the tracker item in your proposal submission. See the development requirements for details.

Students are expected to interact on the #bzflag IRC channel on the Freenode network, abide by the DEVINFO rules, and agree to the development requirements before submitting an application.

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

The application review process

Just about every participating GSoC organization receives considerably more project proposals than can be accepted. All the applications are reviewed, evaluated, and critiqued individually. Of those applications, only a few can be selected to work on BZFlag. We expect to receive many good applications, making the selection process very competitive and difficult (so make sure your application is excellent). This cannot be stressed enough. It is rather hard for most projects to narrow down the submissions but in the end there are only 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 and hope to see many of you become involved in BZFlag software development regardless of acceptance.

In the end, submissions are selected according to the overall long-term impact that accepting the proposal can make for the game, perception of the submitter's abilities to complete the task within the program timeframe, general consensus on the technical approach being proposed, how well the student communicates with other developers, the perception that the individual is interested in being a long-term BZFlag developer, and our overall interest in having the proposed modifications made to BZFlag. Particular notice is made of students that are responsive to questions and readily interactive in the IRC channel. Communication is one of the most important criteria.

Be sure to follow the aforementioned application preparation steps mentioned above. The final list of selected proposals will be announced on April 14, 2008 at 12:00 noon PDT.


BZFlag participation in GSoc

2008 (more details here)

The Google Summer of Code 2008 was announced on February 25, 2008. Given the substantial successes and opportunities provided by the program, BZFlag will continue to participate in the program. BZFlag has been accepted as a mentoring organization, and will accept student project proposals from March 24 to March 31. Please click the link above for more information and for project proposal ideas.

2007 (more details here)

BZFlag first participated during GSoC's third year in 2007. A detailed after-the-fact discussion and analysis of BZFlag's first-year participation is included in the article “Postmortem” Perspectives of a First-year Participant in the 2007 Google Summer of Code for BZFlag. This article was given to Google in August 2007 as a final report, per se, of our involvement (you're only a first-year participant once).

Promotion Flyers