Clone this wiki locally
Welcome to the R-GSOC wiki, which will be the central hub of information about the R Project participation in the Google Summer of Code (GSoC). Administrators are Toby Dylan Hocking <email@example.com>, Brian Peterson <firstname.lastname@example.org>, and Virgilio Gomez Rubio as a backup. Everyone who wants to participate in Google Summer of Code with R should
- first please read the R-GSOC-FAQ and the Google FAQ so you know how GSOC works,
- then join the low-traffic google group email@example.com (when you sign up, make sure to write your GSOC project idea in the text box “You can send additional information to the manager by filling in the text box below” – we have a policy of rejecting applicants who leave it blank).
In short, each student selected for a GSoC project will get paid to work on an R package for 3 months during the summer:
- Mentors can add projects to give ideas to students.
- Students should look at the list of projects to see if any project interests them. Before emailing project mentors, please do at least one project Test and post a link to your solution on the proposal’s wiki page. Then email the project mentors to express your interest, and describe any prior experience.
- After opening communication with project mentors, each student must write an application with a detailed timeline, following our application template. Successful applications are shared with mentors for feedback before submission of a final application on Google.
- Google will award a certain number of student slots to the R project.
- The GSOC-R administrators and mentors will rank projects in order of application quality and importance to the R project, and the top projects will be funded.
- Students get paid a stipend by Google for writing free/open-source R packages for 3 months during the summer.
- Mentors get code written for their project, but no money.
Selected events from the official timeline:
|Feb 6||Org applications due|
|Feb 26||List of accepted orgs published|
|April 9||Student applications due|
|May 27 - Aug 26||Student coding period|
|June 28||Phase 1 evals|
|July 26||Phase 2 evals|
|Sept 2||Final evals|