Home

Welcome to the gsoc2017 wiki, which will be the central hub of information about the R Project participation in the Google Summer of Code (GSoC) for 2017. Administrators are Toby Dylan Hocking <toby.hocking@r-project.org>, Brian Peterson <brian.peterson@r-project.org>, and Virgilio Gomez Rubio as a backup. Everyone who wants to participate in Google Summer of Code with R should join the low-traffic google group gsoc-r@googlegroups.com (when you sign up, make sure to mention for which project you want to be a mentor or student as your Reason for joining). Please read the R-GSOC-FAQ and the Google FAQ before posting questions to the google group!

Overview of GSOC

In short, each student 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 getting approval from the project mentors, each student should write an application with a detailed timeline, following our application template. Students should send their application to their mentors for proofreading before submitting it to 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 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:

When	What
19 Jan - 9 Feb	Org applications
20 Mar - 3 Apr	Student applications
30 May - 29 Aug	Student coding period
30 June	Phase 1 evals
24 July	Phase 2 evals
29 Aug - 5 Sep	Final evals

Previous GSOC ideas and projects

2017 is the third GSOC for which will use GitHub to organize the R project participation in GSOC. Organization info for previous years can be found on the RGSOC2016 wiki.

Below is some LaTeX beamer code that may be useful for explaining R-GSOC.

\section{Google Summer of Code}

\begin{frame}
  \frametitle{Google Summer of Code (GSOC)}
  Student gets \$5500 for writing open source code for
  3 months.
  \begin{description}
  \item[Feb] \textbf{Admins} for open source organizations e.g. R,
    Bioconductor (MUGQIC?) apply to Google.
  \item[Mar] \textbf{Mentors} suggest projects for each org.\\
    \textbf{Students} submit project proposals to Google.\\
    Google gives funding for $n$ students to an org.
  \item[April] The top $n$ students get \$500 and begin coding.
  \item[July] Midterm evaluation, pass = \$2250.
  \item[Aug] Final evaluation, pass = \$2750.
  \item[November] Orgs get \$500/student mentored.
  \end{description}

  I have participated since 2012 as an \textbf{admin} and
  \textbf{mentor} for the R project.
\end{frame}

\begin{frame}
  \frametitle{What makes a good GSOC project?}
  Coding projects should:
  \begin{itemize}
  \item Result in free/open-source software.
  \item Be 3 months of full time work for a student.
  \item Include writing documentation and tests.
  \item Not include original research.
  \end{itemize}
  Examples: 
  \begin{itemize}
  \item Mathieu/François can be \textbf{admins} for MUGQIC org.
  \item Robert/Dan can be \textbf{mentors} for a project to implement
    new features in Gemini.
  \item Any undergrad/master/PhD candidates (at McGill or not)
    can be \textbf{students}.
  \end{itemize}
  
\end{frame}