Skip to content
Toby Dylan Hocking edited this page Mar 30, 2022 · 5 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 <toby.hocking@r-project.org>, Brian Peterson <brian.peterson@r-project.org>, Vijay Barve <vijay.barve@gmail.com>, Narayani Barve <TODO>. 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 gsoc-r@googlegroups.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).

Overview of GSOC

In short, each contributor selected for a GSoC project will get paid to work on an R package for 10 weeks during the summer:

  • Mentors can add projects to give ideas to possible contributors, see the Google FAQ to see if you are eligible as a contributor.
  • Possible contributors 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 contributor 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 contributor 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.
  • Contributors 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:

When What
Feb 7 Mentoring organizations can begin submitting applications to Google
Feb 21 Org app deadline
Apr 19 Contributor applications due
May 12 Contributor slot requests due from Org Admins
May 20 Accepted contributors/projects announced
May 20-June 12 Community bonding period
June 13-Sept 12 Coding/work period
July 29 Phase 1 evals due
Sept 12 Contributors submit final work product and mentor evals
Sept 19 Mentors submit final evaluations of contributors
Nov 21 Extended timeline: Contributors submit final work product
Nov 28 Extended timeline: Mentors submit final evaluations of contributors