Google Summer of Code
- Home page
- Terminology and rules
- Google Melange: past editions
- Wikipedia:Google Summer of Code
- Best practices for mentoring
General process description
- Key actors: mentors, mentor organizations, students and Google
- Google organizes and funds
- Mentors submit topics
- Mentor organizations groups topics
- Not sure if mentors can submit alone, it seems it was the case before but not this year
- JPA got contacted by 'beam' organization which groups erlang topics, then submitted 3 topics for the project 'erlang DBus' and students have picked this topics and made a proposal based on that topics
- Then the mentor organization told Google 1/ who was the mentors 2/ which student got chosen and their proposal
- Given that there were more proposals / students than slots allocated by Google, a selection was made internally in the beam group, trying to have at least one topic by project (2 proposals were received for DBus, ejabberd had 3...)
- Google rule is 1 mentor = 1 student
Various links
- https://opensource.com/business/15/4/interview-carol-smith-google-summer-code
- https://opensource.com/tags/google-summer-code
Mailing-lists
- Announcement only list
- Program discussion list
- Students list (private; past and current accepted student participants)
- Mentors list (private; past and current mentor participants)
"If you are a past participant in the program, now would be an ideal time to revisit and update your subscription preferences to the program mailing lists."
Source: GSoC help
Legal aspects
- Attached: Mentor and Organization participant agreements:
- https://summerofcode.withgoogle.com/rules/
NB:
- 2 persons from the organization must sign the agreement
- check the indeminification clauses