Difference between revisions of "BeagleBoard/GSoC"

From eLinux.org
Jump to: navigation, search
(BeagleBoard.org Summer of Code)
(Key Dates for 2011)
Line 14: Line 14:
 
* [[BeagleBoard/GSoC/2010_Projects|2010 projects page]]
 
* [[BeagleBoard/GSoC/2010_Projects|2010 projects page]]
  
== Key Dates for 2011 ==
+
== Key Dates for 2013 ==
* Mentoring organizations application window is February 28-March 11.
+
* February 11: Program announced.
* Continue to provide your [[BeagleBoard/GSoC/Ideas|Ideas]] page updates right up to the March 18 publishing of accepted mentoring organizations.
+
* March 18: 19:00 UTC Mentoring organizations can begin submitting proposals to Google.
* Student discussion window March 18-March 27.
+
* March 29: 19:00 UTC Mentoring organization proposal deadline.
* Student application window March 28-April 8.
+
* April 1 - 5: Google program administrators review organization proposals.
* Mentors review and rank student proposals before April 22.
+
* April 8: 19:00 UTC List of accepted mentoring organizations published on the Google Summer of Code 2013 site.
** All mentors must be signed up and all student proposals matched with a mentor
+
* April 9 - 21: Would-be student participants discuss proposal ideas with mentoring organizations.
** IRC meeting to resolve any outstanding duplicate accepted students - 19:00 UTC #gsoc
+
* April 22: 19:00 UTC Student proposal period opens.
* Accepted proposals published April 25.
+
* May 3: 19:00 UTC Student proposal deadline.
* Students and mentors work together on refining the task definition and solution April 25-May 23.
+
* Interim Period: Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant.
* First half project execution May 23-July 11.
+
* May 6: Mentoring organizations should have requested slots in Google Summer of Code 2013 site at this point.
* Mid-term evaluations done July 11-15.
+
* May 8: Slot allocations published to mentoring organizations.
* Second half project execution July 15-August 15.
+
* Interim Period: Slot allocation trades happen amongst organizations. Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant.
* Final evaluations done August 22-26.
+
* May 22: First round of de-duplication checks happens; organizations work together to try to resolve as many duplicates as possible.
* Final results announced August 29.
+
* May 24: All mentors must be signed up and all student proposals matched with a mentor - 07:00 UTC
* Student code sample submission beings August 30.
+
Student acceptance choice deadline.
* Mentor Summit at Google will be held October 22-23.
+
IRC meeting to resolve any outstanding duplicate accepted students - 19:00 UTC #gsoc (organizations must send a delegate to represent them in this meeting regardless of if they are in a duplicate situation before the meeting.)
 +
* May 27: 19:00 UTC Accepted student proposals announced on the Google Summer of Code 2013 site.
 +
* Community Bonding Period: Students get to know mentors, read documentation, get up to speed to begin working on their projects.
 +
* June 17: Students begin coding for their Google Summer of Code projects.
 +
Google begins issuing initial student payments provided tax forms are on file and students are in good standing with their communities.
 +
* Work Period: Mentors give students a helping hand and guidance on their projects.
 +
* July 29: 19:00 UTC Mentors and students can begin submitting mid-term evaluations.
 +
* August 2: 19:00 UTC Mid-term evaluations deadline;
 +
Google begins issuing mid-term student payments provided evaluation is on file.
 +
* Work Period: Mentors give students a helping hand and guidance on their projects.
 +
* September 16: Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc.
 +
* September 23: 19:00 UTC Firm 'pencils down' date. Mentors, students and organization administrators can begin submitting final evaluations to Google.
 +
* September 27: 19:00 UTC Final evaluation deadline
 +
Google beings issuing student and mentoring organization payments provided forms and evaluations are on file.
 +
* September 27: 19:00 UTC Students can begin submitting required code samples to Google.
 +
* October 1: Final results of Google Summer of Code 2013 announced
 +
* October 19 & 20: Mentor Summit at Google: Representatives from each successfully participating organization are invited to Google to greet, collaborate and code. Our mission for the weekend: make the program even better, have fun and make new friends.
  
 
== Links ==
 
== Links ==

Revision as of 11:48, 25 March 2013


BeagleBoard.org Summer of Code

This is the BeagleBoard specific page for Google Summer of Code. BeagleBoard.org was accepted as a mentoring organization for 2010 and is looking for apply again in 2013. BeagleBoard.org is currently recruiting mentors to assist with the ideas page and students to submit applications for BeagleBoard related projects.

Here are some links to help students with their applications:

Projects

Key Dates for 2013

  • February 11: Program announced.
  • March 18: 19:00 UTC Mentoring organizations can begin submitting proposals to Google.
  • March 29: 19:00 UTC Mentoring organization proposal deadline.
  • April 1 - 5: Google program administrators review organization proposals.
  • April 8: 19:00 UTC List of accepted mentoring organizations published on the Google Summer of Code 2013 site.
  • April 9 - 21: Would-be student participants discuss proposal ideas with mentoring organizations.
  • April 22: 19:00 UTC Student proposal period opens.
  • May 3: 19:00 UTC Student proposal deadline.
  • Interim Period: Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant.
  • May 6: Mentoring organizations should have requested slots in Google Summer of Code 2013 site at this point.
  • May 8: Slot allocations published to mentoring organizations.
  • Interim Period: Slot allocation trades happen amongst organizations. Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant.
  • May 22: First round of de-duplication checks happens; organizations work together to try to resolve as many duplicates as possible.
  • May 24: All mentors must be signed up and all student proposals matched with a mentor - 07:00 UTC

Student acceptance choice deadline. IRC meeting to resolve any outstanding duplicate accepted students - 19:00 UTC #gsoc (organizations must send a delegate to represent them in this meeting regardless of if they are in a duplicate situation before the meeting.)

  • May 27: 19:00 UTC Accepted student proposals announced on the Google Summer of Code 2013 site.
  • Community Bonding Period: Students get to know mentors, read documentation, get up to speed to begin working on their projects.
  • June 17: Students begin coding for their Google Summer of Code projects.

Google begins issuing initial student payments provided tax forms are on file and students are in good standing with their communities.

  • Work Period: Mentors give students a helping hand and guidance on their projects.
  • July 29: 19:00 UTC Mentors and students can begin submitting mid-term evaluations.
  • August 2: 19:00 UTC Mid-term evaluations deadline;

Google begins issuing mid-term student payments provided evaluation is on file.

  • Work Period: Mentors give students a helping hand and guidance on their projects.
  • September 16: Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc.
  • September 23: 19:00 UTC Firm 'pencils down' date. Mentors, students and organization administrators can begin submitting final evaluations to Google.
  • September 27: 19:00 UTC Final evaluation deadline

Google beings issuing student and mentoring organization payments provided forms and evaluations are on file.

  • September 27: 19:00 UTC Students can begin submitting required code samples to Google.
  • October 1: Final results of Google Summer of Code 2013 announced
  • October 19 & 20: Mentor Summit at Google: Representatives from each successfully participating organization are invited to Google to greet, collaborate and code. Our mission for the weekend: make the program even better, have fun and make new friends.

Links