2018 Email Announcements

This is an archive of all broadcast emails sent to Mentors and Org Admins.

May 7, 2018: GSoC 2018: Removing an Inactive Student before coding begins

TO: Mentors and Org Admins

Removing Inactive students

If you have a student that has not been actively involved in the community bonding period now is the time to let us know and we can remove them from the program.

Please contact us at gsoc-support@google.com with the name of the student and your org name before May 14th and we will send them an email telling them they have been removed from the program.

Future Emails for Mentors and Org Admins

This is the last email some of you will receive from Google for GSoC 2018. Starting May 15th we will only send emails to mentors with an assigned student project in the system and to all org admins.

Important Upcoming Dates

  • May 14: Deadline to notify Google Admins of an inactive student that you wish to be removed from the program
  • May 14: Coding begins
  • June 11-15: First evaluation period - mentors evaluate students, students evaluate mentors
  • July 9-13: Second evaluation period - mentors evaluate students, students evaluate mentors
  • August 6-14: Students wrap up their projects and submit final evaluation of their mentor
  • August 14-21: Mentors submit final evaluations of students

If you haven't done so already, please read the Mentor Guide and the Roles and Responsibilities doc to help you navigate the next few months of GSoC.

Email Archive

All emails sent to Org Admins and Mentors during this year's program are stored in the 2018 GSoC OA and Mentor email archive.

Please email Google Administrators at gsoc-support@google.com if you have any questions.

April 26, 2018: GSoC 2018: Community Bonding and FAQs from Mentors

TO: Mentors and Org Admins

Please read the Mentor Guide and the Roles and Responsibilities doc to help you navigate the next few months of GSoC. We've also prepared answers to some common FAQs below.

If you haven't already contacted your student please do so as soon as possible. Early communication and engagement with your student will help build a strong relationship for the rest of the program. Reach out to your student now and welcome them into your community.

Some Recent FAQs

What am I supposed to be doing during the Community Bonding period?

The Community Bonding period is intended to help get students ready to start contributing to your organization at full speed starting May 14th. Be sure to read the last email we sent, (always available in the email archive) where we go into more detail about how you and your student can take full advantage of this stage of GSoC.

If a student does not participate in community bonding, you have the option of removing them from the program before coding starts.

Can my student start coding now, before the official coding period starts?

Yes, your student can start coding if they wish.

Some students may have already talked to you about a planned vacation/week of unavailability, etc. You are welcome to get them started early to make up for that time.

How many hours a week should my student be working on their GSoC project?

Your student should consider this to be a full time commitment and allocating about 30 hours a week to the project (some weeks may be more, some less). If your student is planning to only work on their project part-time for 20 hours a week during the whole program then your project is too easy and you should work with the student to add more to the project.

My student is dropping out of GSoC, what do I do?

Please instruct your student to officially withdraw from the program by visiting their dashboard on the GSoC site and pressing the withdraw button on their profile page. Unfortunately it is too late to add another student to replace that student slot.

My student is asking me about changing dates on their CPT/Acceptance letter, what does that mean?

Some students that are on student visas to the USA require CPT (Curricular Practical Training) letters to be able to participate in GSoC under the restrictions on their visas. Some students didn't research in advance what their visas allow them to do (or not do). Unfortunately, this means that there will likely be a few students who will have to drop out because the official CPT letters from Google can only indicate the official coding dates of May 14-August 6. Some students may not be allowed to work during part of that time because of their visa restrictions which means they can not participate in GSoC.

Upcoming Important Dates

  • April 23 - May 13: Community Bonding Period
  • May 13: Deadline to notify Google Admins of an inactive student that you wish to be removed from the program
  • May 14: Coding begins
  • June 11 - 15: First evaluation period - mentors evaluate students, students evaluate mentors
  • July 9 - 13: Second evaluation period - mentors evaluate students, students evaluate mentors
  • August 6 - 14: Students wrap up their projects and submit final evaluation of their mentor
  • August 14 - 21: Mentors submit final evaluations of students

Email Archive

All emails sent to Org Admins and Mentors during this year's program are stored in the 2018 GSoC OA and Mentor email archive.

Thank you all for helping bring new contributors into the open source community this summer!

Please email Google Administrators at gsoc-support@google.com if you have any questions.

April 17, 2018: GSoC 2018: Next Steps for all Mentors and Org Admins

TO: Org Admins

Thank you for being a Mentor or Org Admin for GSoC 2018! We value your commitment to helping students learn about and participate in open source development. You are the reason this program has continued to grow and evolve since 2005. Thank you!

This email is long, but it contains a lot of important information. Please read everything carefully.

Accepted Students Announcement

GSoC 2018 accepted students will be announced on Monday, April 23rd at 16:00 UTC on the GSoC program site. At that time, emails will be sent to all students (both accepted and rejected). It may take a few hours for the thousands of emails to be sent out. Emails will also be sent to all of the mentors assigned to a project.

Do NOT pre-announce the results in any fashion before the information is publicly visible on the GSoC website. Once it is visible (after 16:01 UTC on April 23rd) you are welcome to send out tweets, publish blog posts, etc.

Congrats, you are a mentor -- now it's time to mentor!

Google Summer of Code works best when the student and mentor work together closely. GSoC is not a "code for hire" program. The student is not there to do exactly what you tell them to do or to fend for themselves and figure out everything on their own. Check-ins should be regular -- at least weekly. If you planned less frequent check-ins please adjust your plan. If you're not willing or able to commit the time, please inform your org so they can replace you.

Proactive, productive communication early on (i.e over the next couple of weeks) is the key to setting up the partnership that leads to a successful student project. Successful relationships lead to successful students who often become long term contributors to your project and open source.

What do I do now?

  1. Please read the Roles and Responsibilities to make sure you understand what is expected of you over the next 4 months but also what you should expect from your students. We rely on you to help enforce the program rules and to keep your student on track for success.
  2. If you haven't looked at the GSoC Mentor Guide recently, please (at least) read the Communication and Mentoring sections.
  3. Watch the 5 minute YouTube video: "Being a Great GSoC Mentor". It contains helpful information about the program and how to participate successfully at each step in GSoC.

The Community Bonding Period

As part of the student's acceptance into GSoC they are expected to actively participate in the Community Bonding period (April 23 - May 13). The Community Bonding period is intended to help get students ready to start contributing to your organization at full speed starting May 14th.

Community Bonding activities may involve:

  • Becoming familiar with the community practices and processes. (This often involves a mix of observation and participation.)
  • Participating on Mailing Lists / IRC / etc. (Not just lurking.)
  • Setting up their development environment.
  • Small (or large) patches/bug fixes. (These do not need to be directly related to their GSoC project.)
  • Participating in code reviews for others. (Even someone who isn't familiar with the project can contribute by pointing out potential inefficiencies, bad error handling, etc.)
  • Working with their mentor and other org members on refining their project plan. This might include finalizing deadlines and milestones, adding more detail, figuring out potential issues, etc.
  • If the student is already familiar with the organization, they could be helping others get involved in the community.
  • Reading (and updating!) documentation they will need to understand to complete their project.
  • Reporting or replicating bugs.

Active means active. Students have committed to the program schedule, and we would like you to hold them to it. There is no single standard, as every org is different, every student has different time constraints, and there are many different ways to interact. Some students may require coaxing and encouragement in order to get them to actively participate.

If you do not see regular public interaction from the student, you should strongly encourage it. Public interaction is important -- it is a key principle of open source -- work happens where everyone can see it. Similarly, all work done by the students should be shared in a publicly available repository.

The past thirteen years of GSoC have demonstrated that students who don't interact early and often are much more likely to fail later. Often they just disappear. We don't want you to waste your time on students who don't care about the project/organization and don't even attempt to show interest during the first few weeks of the program. Small contributions early on are a very positive signal.

Students who do not participate in community bonding may be removed from the program.

Changes to a Student's Accepted Project

You and your student can decide to change the project from what was originally proposed but you both need to agree on the change. Neither the mentor nor the student should feel pressured into making large project changes. Be fair to your students -- set them up for success. In return they should also be flexible to change the scope of the project (within reason) if the org finds it necessary.

Last year we had students who were upset because they felt they couldn't tell their mentor "no". Many took on more than they could handle. In some of these cases the new project was completely different from what had been originally proposed and many students did not have the appropriate background knowledge or skills to complete it.

Students are able to edit their project title and abstract until coding officially begins May 14th.

Students will not receive any of their stipend until after they successfully pass their first evaluation in the middle of June.

Email Archive

All emails sent to Org Admins and Mentors during this year's program are stored in the 2018 GSoC OA and Mentor email archive.

If you have any questions please contact us at gsoc-support@google.com

April 15, 2018: GSoC 2018: Final Hours to Select GSoC students

TO: Org Admins

The deadline for Org Admins to enter their organization's student selections is in less than 36 hours - Tuesday, April 17th at 16:00 UTC.

This email is being sent to all Org Admins to check and make sure their selections are in order before the deadline.

Right now there are 41 organizations that have not entered any of their student selections and there are many others that have only entered selections for a handful of their given slots.

  • Org Admins must go to their dashboard and select the student proposals their org would like to make into 2018 student projects based on the slots allocated to their org.

  • At least one mentor must be assigned to each project. You can not select a project without assigning at least one of your mentors to the project.

  • You can add or change mentors to a project until May 15th. But ideally you will have already identified the primary mentor for the project when students are announced on April 23rd. This way the student can get to know their mentor at the very start of the community bonding period.

We would much rather you select only the excellent proposals rather than fill student slots for the sake of filling all slots allocated to your org.

Email Archive

All emails sent to Org Admins and Mentors during this year's program are stored in the 2018 GSoC OA and Mentor email archive.

If you have any questions please contact us at gsoc-support@google.com

April 10, 2018: GSoC 2018: Student Project Selection

TO: Mentors and Org Admins

Slot allocations have been granted to each organization and are now visible in each OA's dashboard.

It's now time to make the final decisions on which student projects your org will accept using your slot allocations and which mentors will help guide the students on their summer projects.

As of right now 35% of the student slots we allocated have already been assigned to student projects by OAs.

Student Project Selection

Tuesday, April 17th at 16:00 UTC: Deadline for OAs to submit their student selections

  • Org Admins must go to their dashboard and select the student proposals your org would like to make your 2018 student projects based on the slots allocated to your org.
  • At least one mentor must be assigned to each project. You can not select a project without assigning at least one of your mentors to the project.
  • You can add or change mentors to a project until May 14th. But ideally you will have already identified the primary mentor for the project when students are announced on April 23rd. This way the student can get to know their mentor at the very start of the community bonding period.
  • Remember the sooner you make your selections the sooner you lock in your student selection. If you know there is a student or two that your org has to have we encourage you to go ahead and select them now rather than risk another org "taking" that student (assuming the student applied to multiple orgs which 29.5% of students this year did).

Read Slot Allocation and Project Selection for more information.

Conflict Resolution

If you try to accept a student that has already been accepted by another organization, you will see a notice to that effect. Contact info for that org's admins will be displayed so you can ask if they would be willing to release the student. They can choose a different student for that slot.

Google does not get involved in these decisions. It is up to the organization that first chose the student to decide how they wish to proceed. Do not ask the student, as this will leak the information that they are accepted before the decision is finalized.

Adding more Mentors

Many orgs were waiting to see how many slots they would receive so they can decide which student projects they will be selecting and thus which mentors will be mentoring those specific student projects. This is fine, but please be sure to invite the additional mentors you may need in the next couple of weeks.

Program Administrators 2nd Review

Google Program Admins are doing an additional review of the student's eligibility for the program once you have all locked in your students on April 17th. There is a very small possibility that one of the students you selected will be found ineligible for the program during the second review. If this is the case Google will give you the opportunity to fill that student slot with another student before April 23rd.

You may wish to think about whether there is another student proposal that would be your "backup" student project should one of the students you selected be ineligible or withdraw from the program before the April 23rd announcement.

Why would a student be rejected at this point? 5200 proof of enrollment forms were reviewed in a very short period of team by multiple people and it is possible an ineligible student was not discovered in the initial review and upon closer review it is discovered. Last year there were only a few students (out of 1300+) where this was an issue.

Communication Reminders leading up to Accepted Students Announcement

Do not tell students that they have been accepted into the program before the public announcement on April 23rd after 16:00 UTC. Decisions are not official until it is on the website and emails are sent.

On April 23rd after 16:00 UTC -

  • OA's will receive a confirmation email for each student that they have accepted. For large orgs this will be a lot of emails - we apologize in advance.
  • Mentors with accepted projects will receive an email letting them know they are a mentor for the project.
  • Students will receive an email letting them know which org they were accepted with or if rejected they will receive a rejection email.

Upcoming Important Dates

  • April 10 - 17 16:00 UTC: Select the proposals to become student projects. At least 1 mentor must be assigned to each project before it can be selected. (OAs enter selections)
  • April 17 - April 23: Google Program Admins perform additional review of student eligibility
  • April 23: Accepted GSoC 2018 students/projects are announced
  • April 23 - May 14: Community Bonding Period
  • May 13: Deadline to notify Google Admins of an inactive student that you wish to be removed from the program
  • May 14: Coding begins
  • June 11-15: First evaluation period - mentors evaluate students, students evaluate mentors

Email Archive

All emails sent to Org Admins and Mentors during this year's program are stored in the 2018 GSoC OA and Mentor email archive.

If you have any questions please contact us at gsoc-support@google.com

April 8, 2018: 11 hours to submit GSoC Slot requests

TO: Org Admins

As of right now 43 of the 212 organizations have not submitted their slot requests. This is a reminder for all Org Admins to look at their dashboard and make sure that one of the Org Admins from your Org has submitted your request before tomorrow's deadline (in 11 hours - 16:00 UTC Monday, April 9th).

Slot Requests, Slot Allotment and Project Selection

  • Deadline for OAs to submit their slot requests: Monday, April 9th at 16:00 UTC.
  • Google will release slot allotments on Tuesday, April 10th. OA's will see the slots in their dashboard.
  • Deadline for OAs to select projects (students) / assign mentors: Tuesday, April 17th at 16:00 UTC.

Slot Requests

Deadline: Monday, April 9th at 16:00 UTC.

Org Admins must request a minimum and maximum number of project slots for their organization based on good proposals received and available mentors - both of these should be met when deciding on your numbers. Also remember that good mentors are vital to this process- just getting a person to agree to be a mentor does not make a good mentor. Just like when selecting students quality is ALWAYS better than quantity. Find mentors familiar with the project they would be mentoring and who want to mentor, don't make someone be a mentor, that only results in a disaster for everyone.

Slot request numbers are used to help Google allocate slots. Orgs may receive less than their requested minimum. New orgs will likely only receive a couple of slots, no matter how many they request.

There is a 1:1 mapping between projects and students. A student may only complete one GSoC project per year. Slots should only be requested for projects which you think are likely to succeed. Do not plan to accept "okay" proposals just to have more students working with your org this year.

And remember, students are applying to work on the proposed project - it's not cool to accept a student and then tell them we don't want you working on that project we want you to do this completely different project. Students don't feel like they can say no and usually when an org tries to do this it results in failure for the student and the org. You want a student to be excited about the project they are working on and forcing something completely new on them is inconsiderate. If you were planning to do this and have asked for student slots with this scenario in mind stop and go back and reduce your slot request numbers.

Read Slot Allocation and Project Selection for more information.

Student Eligibility

Deadline: Monday, April 9th at 16:00 UTC.

April 9th is also the deadline for students to have any re-submitted proof of enrollment documents reviewed. Students have been informed of this and have all been sent multiple reminder emails to correct their form before the deadline, many have ignored the reminders or simply aren't eligible and thus don't have valid proof of enrollments they can supply. Students without valid proof of enrollment documents will not be eligible to participate. There will be no exceptions. Any students who did not submit an acceptable proof of enrollment before the April 9th deadline will disappear from your list of student projects you can accept on April 10th.

Every year we have mentors ask us to reconsider and to give the student another chance. Students have literally received 3 direct emails about their forms not being okay and reminders to fix them before the deadline on April 9th. If they choose to ignore the emails and reminders there isn't anything to be done. We have to do this because it's clear there are some students applying who are not actual students and this is a requirement to participate in GSoC 2018 so we have to enforce the rules.

Upcoming Important Dates
  • April 9, 16:00 UTC: Deadline to submit slot requests (OAs enter requests)
  • April 10, 16:00 UTC: Slot allocations are announced by Google
  • April 10 - 17 16:00 UTC: Select the proposals to become student projects. At least 1 mentor must be assigned to each project before it can be selected. (OAs enter selections)
  • April 17 - April 23: Google Program Admins perform additional review of student eligibility
  • April 23: Accepted GSoC 2018 students/projects are announced
  • April 23 - May 14: Community Bonding Period
  • May 13: Deadline to notify Google Admins of an inactive student that you wish to be removed from the program
  • May 14: Coding begins
  • June 11-15: First evaluation period - mentors evaluate students, students evaluate mentors

Email Archive

All emails sent to Org Admins and Mentors during this year's program are stored in the 2018 GSoC OA and Mentor email archive.

If you have any questions please contact us at gsoc-support@google.com

March 24, 2018: Final PDF review and Slot Allocation

TO: Mentors and Org Admins

The student submission period is nearly over - you can expect a lot of proposals coming in over these last 2.5 days - we're already at record numbers of students registering for GSoC! We know you are all quite busy responding to students and giving them feedback on their draft proposals. In the next phase of GSoC, you select which of these proposals you choose for GSoC projects.

Reviewing Final PDF Proposals: March 27-April 8

The deadline for students to submit their Final PDF proposal is Tuesday, March 27 at 16:00 UTC. Students without Final PDF proposals cannot be accepted, and there will be no exceptions.

After March 27 at 16:00 UTC, org members will be able to see the Final PDFs submitted by students.

March 27 16:00 UTC is also the deadline for students to submit a proof of enrollment in an eligible university program. Students who fail to do this are ineligible for GSoC this year. We will be reviewing the forms and students will have a chance to resubmit if there are any problems.

Your decision about whether or not to select a student should be based on the Final PDF proposal. You will also be able to reference the draft proposal -- but should not make your decision based on it. A draft proposal is intended to be used to view the comment thread and maybe see how the student interacted with you and responded to comments, etc. Do not use it to let the student make more changes after the deadline. That is not fair to all the other applicants.

Want to Mentor?

If you are interested in being a mentor for a given proposal then you can clickthe purple "Want to Mentor" button to help your Org Admin know that you are interested. This is particularly helpful for the org admins when determining if they have enough mentors for their slot requests.

Slots Request - deadline April 9 16:00 UTC (Org Admin responsibility)

  • Org Admins will request a minimum and maximum number of project slots.
  • Slots should only be requested for projects where there is at least one confirmed mentor and where the student has a good chance of succeeding.
  • Do not accept "okay" proposals.
  • Do not request more slots than you have mentors for - if we grant you the slots you request and you can't use all of them you have essentially taken away these slots from other orgs that could have used them and also taken away the opportunity for that number of students to participate in GSoC 2018.
  • New orgs will likely only receive 1-2 slots, no matter how many they request.
  • Mentors should be mentoring 1 project generally. In rare cases a mentor can mentor 2 projects.

April 9th is also the deadline for students to have any re-submitted proof of enrollment forms approved. Note that students with invalid forms will not appear in your list of student projects you can choose from starting April 10th (when slots are announced).

All Org Admins should read Slot Allocation and Project Selection for more detailed information.

Upcoming Important Dates

  • March 27 - April 8: Review all submitted student proposals with your org and consider how many you want to select and how many you can handle. Decide on the minimum/maximum number of student slots to request- do not request more than your org can handle - this could take students away from orgs who have excellent student prospects and need the slots.
  • April 9, 16:00 UTC: Deadline to submit slot requests (OAs enter requests)
  • April 10, 16:00 UTC: Slot allocations are announced by Google
  • April 10 - 17 16:00 UTC: Select the proposals to become student projects. At least 1 mentor must be assigned to each project before it can be selected. (OAs enter selections)
  • April 17 - April 23: Google Program Admins perform additional review of student eligibility
  • April 23: Accepted GSoC 2018 students/projects are announced
  • April 23 - May 14: Community Bonding Period
  • May 13: Deadline to notify Google Admins of an inactive student that you wish to be removed from the program
  • May 14: Coding begins
  • June 11-15: First evaluation period - mentors evaluate students, students evaluate mentors
  • July 9 - 13: Second evaluation period - mentors evaluate students, students evaluate mentors
  • August 6-14: Students wrap up their projects and submit final evaluation of their mentor
  • August 14 - August 21: Mentors submit final evaluations of students
  • August 21: Students passing GSoC 2018 are announced

If you haven't done so already, be sure to read the Roles and Responsibilities to understand what is expected of you and of students during the program.

Please contact us at gsoc-support@google.com with any questions.

March 7, 2018: Tips on Reviewing Student Proposals

TO: Mentors and Org Admins

Thank you for registering to be a GSoC 2018 mentor or organization administrator! We have many new mentors and organizations (44!) this year so we wanted to go through some important details to help you understand the process for the next few months.

[Action Required] Please take the time to do the following:

  • Reach out to your organization administrator to learn more about what is expected of you this year as a mentor.
  • Read the Google Summer of Code mentor guide and the Roles and Responsibilities doc.
  • Watch the 5 minute YouTube video: "Being a Great GSoC Mentor". The video was shot with GSoC veteran Org Admins and Mentors. It contains helpful information about the program and how to participate successfully at each step in GSoC.

Student Proposals

Student Proposal Submission period: March 12-27

Starting next week students will be able to submit their proposals via the program website. Each student may submit up to 3 proposals to the program. This is a change from last year when we allowed 5 proposals. They can submit multiple proposals to the same organization for different projects if they wish.

Historically, the students with the best proposals reach out to the orgs early to receive feedback before submitting their final proposal - those students who have already been reaching out to you are likely to be among your best student options this year.

To encourage more students to seek feedback on their proposals, draft proposals are part of the official proposal workflow. Be sure to refresh your dashboard periodically so that you can see when new drafts are ready to review. You will not receive an email. We are encouraging the use of Google Docs for proposals as this will allow you to comment directly on the proposal.

Over the next few weeks you will be interacting with dozens and in some cases hundreds of students interested in working with your project. We know many of you may become overwhelmed and some students can be impatient, so you may want to have an auto-responder or some sort of canned response to let students know you are looking at their proposals but it could take X days to receive a response.

Post Student Proposal Period: March 27 - April 8

Students must submit their final proposal as a PDF through the website. It will be visible to mentors/org admins after the deadline for student applications (March 27 16:00 UTC). You should make your decisions on which students to accept based on the contents of the final PDF proposal and your interactions with the student.

Students can delete their proposals after the submission period and you will not receive an email of the deletion. If a proposal disappears from your list, it is likely because they deleted it.

Working with Students

All student projects must have at least one mentor assigned. We strongly encourage assigning a second mentor as a backup mentor or co-mentor. A mentor should not be the primary mentor for more than one or two students maximum. Mentoring can be a lot of work and we don't want anyone to burn out and become frustrated with the program.

GSoC 2018 Dates and Deadlines

  • Now - March 12: Proactive students will reach out to you and ask questions about your ideas list and receive feedback from your org so they can start crafting their project proposals. Org Admins should be inviting mentors.
  • March 12 - March 27 16:00 UTC: Students will submit their draft proposals through the program website for you to give solid feedback on.
  • March 27 - April 8: Review all submitted student proposals with your org and consider how many you want to select and how many you can handle. Decide on the minimum/maximum number of student slots to request- do not request more than your org can handle - this could take students away from orgs who have excellent student prospects and need the slots.
  • April 9, 16:00 UTC: Deadline to submit slot requests (OAs enter requests)
  • April 10, 16:00 UTC: Slot allocations are announced by Google
  • April 10 - 17 16:00 UTC : Select the proposals to become student projects. At least 1 mentor must be assigned to each project before it can be selected. (OAs enter selections)
  • April 17 - April 23: Google Program Admins perform additional review of student eligibility
  • April 23: Accepted GSoC 2018 students/projects are announced
  • April 23 - May 14: Community Bonding Period
  • May 13: Deadline to notify Google Admins of an inactive student that you wish to be removed from the program
  • May 14: Coding begins
  • June 11-15: First evaluation period - mentors evaluate students, students evaluate mentors
  • July 9 - 13: Second evaluation period - mentors evaluate students, students evaluate mentors
  • August 6-14: Students wrap up their projects and submit final evaluation of their mentor
  • August 14 - August 21: Mentors submit final evaluations of students
  • August 21: Students passing GSoC 2018 are announced

Mentors Mailing List

If you want to be included on the GSoC mentors mailing list be sure to opt in on your User Profile page. You can always opt out once you have been added by unsubscribing using the link on any of the emails.

Email Archive

To see all emails sent to mentors and org admins visit the 2018 GSoC OA and Mentor email archive that will continue to be updated throughout the program.

Contact Us

Please use the gsoc-support@google.com email address for questions so that anyone on our team can answer your question for you.

February 16, 2018: Thanks for being a part of GSoC 2018 - welcome!

TO: Mentors and Org Admins

Welcome to the biggest GSoC program ever with 212 open source organizations participating in GSoC 2018 and we expect to accept more students than ever before too. And a special welcome to 41 organizations participating in GSoC for the first time!

As you have probably noticed many proactive, excited students have already started reaching out to your orgs to discuss project ideas - this is a very good thing!

We want to give you a quick overview of the next few months and address some of the common questions you may have these first few weeks of the program.

Important Info for 2018

  • There are 3 evaluation periods where mentors are required to complete an evaluation of their student. After the first 4 weeks of coding, after 8 weeks of coding and then at the end (after 12 weeks of coding). The evaluation forms are relatively short with multiple choice questions and a couple of free form responses to give your student feedback (which hopefully is being done weekly already by the mentor).
  • Students can only be accepted into GSoC 2 times. Google Admins will do a sanity check on all accepted students once you select your students in early April so you do not need to be concerned about this.
  • UNIVERSITIES: If you are a university, we expect you to select students outside of your program. Selecting students from your university is okay (1-2 students tops) but if all of the students you select are from your university then you likely won't be accepted into GSoC again.
  • Students can only submit 3 proposals. After discussions at the Mentor Summit last year we have decided to implement this for 2018 (last year we allowed 5). This should eliminate many of the low quality proposals.
  • We allow 13-17 year olds to be mentors for GSoC as long as they have parental consent to be a part of the program. An additional form is required. We will send the form to the student once they have registered.

Inviting Mentors to your Organization

Organization Administrators should be reaching out to mentors and sending them invitations to be a part of their organization now. The mentor will then click the link in the email they receive to create their account.

GSoC Mentor-invite Mailing List

For those that have opted into the GSoC mentor mailing list (available on your profile page) we will bulk add you to the list on February 26. Then we will add additional folks who opt in about once a week throughout the program period. You can remove yourself through the groups interface at any time. You can also update your settings to receive a daily digest of emails and other options. This generally is not a very high traffic list but there will be more questions over the next two months on this list than probably later in the program.

The GSoC mentor mailing list is a great way to ask questions of other org admins and mentors and to get their feedback and help.

Important Upcoming Dates

  • Now - March 12: Proactive students will reach out to you and ask questions about your ideas list and receive feedback from your org so they can start crafting their project proposals. Org Admins should be inviting mentors.
  • March 12 - March 27 16:00 UTC: Students will submit their draft proposals through the program website for you to give solid feedback on.
  • March 27 - April 8: Review all submitted student proposals with your org and consider how many you want to select and how many you can handle. Decide on the minimum/maximum number of student slots to request- do not request more than your org can handle - this could take students away from orgs who have excellent student prospects and need the slots.
  • April 9, 16:00 UTC: Deadline to submit slot requests (OAs enter requests)
  • April 10, 16:00 UTC: Slot allocations are announced by Google
  • April 10 - 17 16:00 UTC : Select the proposals to become student projects. At least 1 mentor must be assigned to each project before it can be selected. (OAs enter selections)
  • April 17 - April 23: Google Program Admins will do another review of student eligibility
  • April 23: Accepted GSoC 2018 students/projects are announced
  • April 23 - May 14: Community Bonding Period
  • May 13: Deadline to notify Google Admins of an inactive student that you wish to be removed from the program
  • May 14: Coding begins
  • June 11-15: First evaluation period - mentors evaluate students, students evaluate mentors
  • July 9 - 13: Second evaluation period - mentors evaluate students, students evaluate mentors
  • August 6-14: Students wrap up their projects and submit final evaluation of their mentor
  • August 14 - August 21: Mentors submit final evaluations of students
  • August 21: Students passing GSoC 2018 are announced

Organization Payments

Complete details regarding GSoC 2018 payments will be sent out in April to Org Admins. In the meantime, please note that Google will pay each organization after final evaluations are submitted.

  • Orgs who participated in 2017: do not need to create a new Payoneer account (if your banking details changed, please update them through your Payoneer dashboard).
  • Orgs new to GSoC or not yet signed up with Payoneer: we will send you an invitation in late April to create your account - do not go and create your own account now.

Quick Glossary

Proposal: A document which describes the project the student wants to work on for your organization. Should include a timeline containing clear milestones and specific deliverables.

Slot: Google will grant each org a certain number of project "slots" based on requests and history with GSoC. Each slot can hold one student/project.

Project: Once a student has been selected and projects are announced, their proposal becomes a project for the remainder of the program.

More Information

If you have not yet read the Roles and Responsibilities page created with the help of GSoC Org admins and mentors, we highly encourage you to read this and share it with your prospective mentors - it will help everyone understand what is expected of them over the next 6 months. You may also want to check out the Mentor Guide, which contains important information for both Mentors and Org Admins at each stage of the program.

Email Archive

All emails sent to Org Admins and Mentors during this year's program are stored in the 2018 GSoC OA and Mentor email archive.

If you have any questions please contact us at gsoc-support@google.com

February 12, 2018: GSoC 2018: Welcome Org Admins!

TO: Org Admins

This year will be our biggest program ever! We have 212 open source organizations accepted to participate in GSoC 2018 and we expect to accept more students than ever before. An extra special welcome to the 41 organizations participating in GSoC for the first time!

Be Prepared for Student Inquiries!

Over the next month, you'll be meeting potential students. Be prepared and responsive! Students who engage with their organization early (and often) are more likely to be accepted and then succeed. We encourage you to get to know the students and help them get to know you! Please continue to flesh out your ideas lists and documentation over the next few weeks.

What is Expected of Org Admins

  • Ensure that your organization's profile page is complete and accurate.
  • Keep your Project Ideas List up to date and easy to access.
  • Some Orgs currently have ideas lists that are buried two or three clicks underneath the provided link. We strongly encourage you to make the ideas front and center on the page the link points to.
  • Make sure your logo looks good on the site. A logo that contains the organization name in readable letters is suggested. You may also need to tweak the aspect ratio.
  • Verify the short description makes sense on the main organizations list. This is very important for grabbing attention quickly. Look at other organizations for examples.
  • Ensure that the "Application Instructions" for students is thorough and complete.
  • Communicate with prospective students about possible project ideas. Mentors should be helping too.
  • Invite mentors to your org (see more below). Make sure you have enough mentors to handle the amount of students showing interest.

Inviting Mentors to your Org

Org Admins should now be sending potential mentors invitations to be a part of their organization. The mentor will need to click the link in the email they receive to accept the invitation and create their account. All mentors must be invited by an Org Admin.

Email Archive

All emails sent to Org Admins and Mentors during this year's program are stored in the 2018 GSoC OA and Mentor email archive.

More emails coming very soon

We will send another (longer) email on Friday once you have had time to invite more mentors to your org. We want them to receive (and read it) too. We know we send a lot of emails, but we try to keep them focused on the important stuff -- please read them carefully.

Contact Us

Please use the gsoc-support@google.com for questions so that anyone on our team can assist you.