Skip to content
Vivek Kumar edited this page May 5, 2020 · 7 revisions

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 protected]>, Brian Peterson <[email protected]>, 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 protected] (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).

Overview of GSOC

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.

Proposed Projects

See: table of proposed coding projects

Status and Timeline

Selected events from the official timeline: (Dates have been updated in accordance with the shifted schedule)

When What
Feb 20 List of accepted orgs published
March 31 Student applications due
April 21 Student slot requests due from Org Admins
April 30 Student Project selections due from Org Admins
May 4 Accepted students/projects announced
May 4 - 31 Community bonding period
June 1 - Aug 31 Student coding period
June 29 - July 3 Phase 1 evals
July 27 - July 31 Phase 2 evals
Aug 24-31 Students submit project along with final evaluation of their mentor(s)
Sept 7 Mentors submit final evaluations of students
Sept 8 Passing students/projects announced