2017 Email Announcements

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

September 8, 2017: GSoC 2017: Wrap up Notes for 2017 Mentors and Org Admins

TO: Mentors and Org Admins

Thank you for being a GSoC 2017 Mentor or Org Admin! Your dedication and commitment to bringing new contributors into the open source community is greatly appreciated. We applaud you for your awesome efforts this season.

By now all of your students have received their pass/fail emails and the announcement blog post is up. We know that making the decision to fail a student can be very difficult, but it is a vital part of the program.

Blog Posts

We want to hear from you! Tell us about your GSoC experience in a wrap-up post that we may feature on the Google Open Source blog. Posts can include organization and project descriptions, interesting stories/anecdotes, or anything else you'd like to tell the world about. Please send draft blog posts (don't forget to include pictures and logos!) to joshuasimmons@google.com and he will work with you to get your article posted. Examples of past posts are here and here.

Org Payments

By September 30th we will deposit the mentor and travel stipends to into the Payoneer accounts of organizations that successfully completed their Payoneer registration and tax forms. Email maryr@google.com with any payment questions.

Mentor Certificates

We will be sending Mentor and Org Admin digital certificates of appreciation in the next couple of weeks. Please note we can not do these retroactively (ie. you were a mentor in 2014 and 2015 and want a certificate saying as much).

Tshirts

T-Shirts are being sent to Mentors with assigned projects and all Org Admins (this includes projects that were failed). T-shirts will start being shipped on October 5th and should arrive to folks by October 25th. If you have not received your tshirt by October 26th then please contact us at gsoc-support@google.com. We will NOT respond to missing shipping inquiries before October 26th.

The deadline to update your shipping address has passed, we will not update any more addresses. Your package will be shipped to the address you had on your profile as of September 8th at 20:00 UTC.

Mentor Summit

The GSoC Mentor Summit is only 5 weeks away! Right now 147 organizations and 315 mentors have registered for this year's Summit. The registration deadlines have passed and we have filled our room blocks. We are not taking any new registrations. You can add your name to the waitlist and we will continue to randomly draw names as other mentors have to cancel. Remember, wait list folks are responsible for their own travel costs to the event.

Thank you all again for spending over 4 months working with this year's GSoC students and helping them become better open source contributors!

Feel free to reach out to our team at gsoc-support@google.com with any questions.

September 4, 2017: Final Evaluation of your student due in less than 19 hours

TO: Mentors and Org Admins

Our records indicate you have not submitted the final evaluation of your GSoC student yet.

Please remember you must complete the final evaluation of your student before Tuesday, September 5th at 16:00 UTC. Go to your dashboard on the GSoC program site to complete the evaluation. We encourage you to complete the evaluations ASAP - it should take you less than 10 minutes to complete.

6 Orgs missed the 2nd evaluation, please don’t let that be you. If your org misses an evaluation your org will lose $1100 of the mentor summit travel stipend and one less person will be able to attend the summit. If you miss the evaluation you will not be invited to the Mentor Summit.

Remember that September 5th is also the deadline to register for the mentor summit if you are one of your org’s designated attendees.

August 29, 2017: Final Evaluation of your student is due by Sept 5 16:00 UTC

TO: Mentors and Org Admins

You can now visit your dashboard on the GSoC program site to submit your Final Evaluation of your student. Be sure to submit the Evaluation before Tuesday, September 5th at 16:00 UTC.

Please make sure to validate the target of the URL the student has supplied to their work product for GSoC 2017 (which you will see in the evaluation form). Make sure it meets your requirements as well as those mentioned in the Work Product Submission Guidelines. The URL supplied by the student will be public on the GSoC site - please ensure it represents your project and your student’s work accordingly.

We would like to request that if your student’s link was particularly great (had all of the relevant information in an organized and clear fashion) to please just paste the URL into this 1 question form so that we can gather some good examples for students for next year. This is not required, just a helpful thing for students in future GSoC programs. Thanks!

Mentor Summit

This is the final reminder for the delegate(s) from your organization to sign up for the GSoC 2017 Mentor Summit if they haven’t already. September 5th is also the deadline to book your hotel room at the Aloft Santa Clara (Sunnyvale Sheraton is sold out). We strongly suggest you do this ASAP as rooms are filling up quickly.

We have a lengthy wait list and we will be taking more people off the list September 5th after 16:00 UTC.

Important Dates

  • August 29-Sept 5: Mentors submit Final Evaluations of their students
  • September 1: Final date for students and mentors to update their shipping address
  • September 5 16:00 UTC: Deadline for submission of Mentor’s Final Evaluation of Student
  • September 5 16:00 UTC: Deadline to register for GSoC Mentor Summit
  • September 6: Successful students are announced
  • September 10: Students who pass receive their final payment
  • Early October: T-shirts are shipped to mentors with assigned projects and to all org admins

As always, please reach out to our team at gsoc-support@google.com with any questions.

August 18, 2017: Final Evaluations open soon

TO: Mentors and Org Admins

GSoC 2017 is almost over - what a busy summer for all!

Next week students will begin submitting their Final Evaluations for GSoC 2017. We have encouraged students to reach out to you to share a preview of their submission URL and let you verify it meets Google’s and your requirements before they submit. Students can not edit their evaluations once they have submitted them — it’s in their best interest to have you review the link first.

Mentor Final Evaluations (of students) Start Tuesday, August 29th at 16:01 UTC

Mentors are responsible for validating the target of the URL (provided in the evaluation), making sure it points to the GSoC 2017 work product, and meets the other requirements. Mentors will use this information as part of their pass/fail decision. The deadline to submit Final Evaluations is September 5th at 16:00 UTC.

You can preview the final evaluation questions here.

Mentor Summit

As of today, 101 organizations have registered sending at least 1 mentor to the Summit to represent their organization. We haven’t heard from 80 orgs a to whether they are sending any delegates. Be sure to talk to your organization if you wish to be one of their designated delegates for the Summit.

Tuesday, September 5th is the deadline to Register for the Summit and to make your hotel reservation. There are only a few rooms left at the Sheraton so you should book in the next couple of days or it will be sold out and you will need to book at Aloft Santa Clara.

If your organization is not sending anyone to the 2017 GSoC Mentor Summit please fill out this form so we can make note of it and take more people off the wait list (there are over 40 folks on the wait list still).

Read the GSoC 2017 Mentor Summit website for many more details about the weekend. Please note events at the Google campus will begin at 6pm on Friday, October 13th.

Important Dates

  • August 21 at 16:00 UTC: Student Final Evaluation period starts
  • August 21-29: Students submit their Final Evaluation which includes

    1) link to their work product (code) and

    2) their Final Evaluation of their Mentor

  • August 29 16:00 UTC: Deadline for Students to submit their Final Evaluation

  • August 29-Sept 5: Mentors submit Final Evaluations of their students
  • September 1: Final date for students and mentors to update their shipping address
  • September 5: Deadline for submission of Mentor’s Final Evaluation of Student
  • September 5: Deadline to register for GSoC Mentor Summit
  • September 6: Successful students are announced
  • September 10: Students who pass receive their final payment
  • Early October: T-shirts are shipped to mentors with assigned projects and to all org admins

As always, please reach out to our team at gsoc-support@google.com with any questions.

July 31, 2017: GSoC Student Work Submission Guidelines and Final Evaluations

TO: Mentors and Org Admins

With a little over 3 weeks left for students to complete their GSoC 2017 projects we want to remind you about the requirements for the final evaluation that we have already shared with the students.

As part of their final evaluations, students will provide a single URL to the code they produced. Then, as part of their final evaluation of the student, mentors will validate the target of the URL (provided in the evaluation), making sure it points to the GSoC 2017 work product. Mentors will also make sure the code compiles and there is adequate documentation provided for the work the student has completed.

Please read the Student Work Product Submission Guidelines now to help your student find the best option for their situation. It is very important that you work with your student and let them know exactly what you expect from them in their submission well before August 29th. Ideally you will work with your student over the next few weeks and they will be prepared to send you the link to their work when the final eval period opens August 21st or on the 22nd. This will give you time to validate the target of their URL and let them know if you want them to make any changes, etc. before they have to make their final submission in the system by August 29th.

Don't forget to encourage your students to spend some time on code cleanup, documentation, testing and other best practices.

Mentor Summit

If you are one of the 2 designated mentors that your org has decided to send to the Mentor Summit please complete the Mentor Summit Registration form as soon as possible. And be sure to book your hotel room (if needed) at either Sheraton Sunnyvale or Aloft Santa Clara.

Read the GSoC 2017 Mentor Summit website for many more details about the weekend. Please note that we are changing things up a bit this year and the opening evening’s events will begin at the Google campus starting at 6pm on Friday, October 13th.

Not sending anyone to the Mentor Summit?

If your org does not plan to send anyone to the Mentor Summit please fill out the form as soon as possible so we can start to take anxious mentors off of the growing wait list. Thanks.

Important Dates

  • August 1: Deadline for Organizations to register with Payoneer to receive mentor and travel stipends
  • August 21-29: Students submit their work product (code) and a final evaluation of their Mentor
  • August 29-Sept 5: Mentors evaluate Students on their final work submissions
  • September 1: Final date for students and mentors to update their shipping address
  • September 5: Deadline to register for GSoC Mentor Summit
  • September 6: Successful students are announced
  • September 10: Students who pass receive their final payment
  • Early October: T-shirts are shipped to mentors with assigned projects and to all org admins

As always, please reach out to our team at gsoc-support@google.com with any questions.

July 24, 2017: GSoC 2017: 2nd Evaluations of your students are now open

TO: Mentors and Org Admins

Second evaluations are now open!

One mentor for each student project must complete an evaluation of their student before Friday, July 28th at 16:00 UTC. If you haven't done so already, go to your dashboard on the GSoC program site and complete your evaluation of your student before July 28th at 16:00 UTC. We encourage you to complete the evaluations ASAP so you don't forget to do it - it should take you less than 10 minutes to complete.

If your org misses an evaluation your org will lose $1100 of the mentor summit travel stipend and one less person will be able to attend the summit.

Org Admins -- we encourage you to verify all evaluations for your org's student projects are complete 36-48 hours before the deadline, giving you time to contact the mentors directly if they have outstanding evaluations. Org Admins can complete the evaluation if needed.

Only 1 mentor can submit an evaluation for a student. If there are multiple mentors for a single student project you should decide in advance which mentor will complete the evaluation.

Important Dates

  • July 24-28: Mentors submit second evaluation of Student (and Students submit eval of Mentor)
  • August 1: Deadline for Organization to register with Payoneer to receive mentor and travel stipends
  • August 21-29: Students submit their work product (code) and a final evaluation of their Mentor
  • August 29-Sept 5: Mentors evaluate Students on their final work submissions
  • September 1: Final date for students and mentors to update their shipping address
  • September 5: Deadline to register for GSoC Mentor Summit
  • September 6: Successful students are announced
  • September 10: Students who pass receive their final payment
  • Early October: T-shirts are shipped to mentors with assigned projects and to all org admins

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

Thanks for being a mentor or org admin for GSoC 2017!

July 11, 2017: Google Summer of Code Mentor Summit

TO: Mentors and Org Admins

The GSoC 2017 Mentor Summit is 3 months away! Read below for all the details.

Event Dates

Friday, October 13 - Sunday, October 15

Location

Purpose

As a way to say thank you and to continue to keep GSoC evolving we hold an annual summit. We bring two mentors from each participating organization to the Googleplex in Northern California for a weekend to talk about GSoC, the greater FOSS community, what can be done to make the program better, how to keep students involved in their communities post-GSoC, and many other topics. It’s also a fun way to meet up with other mentors and org admins across the GSoC universe.

The event is an unconference: at the beginning of the weekend, attendees help determine the schedule. There will be a track related to Google open source projects and to discuss some specific GSoC and GCI topics, but otherwise y’all make the weekend what you want it to be!

Who can come?

Two* Mentors or Org Admins are invited from each GSoC 2017 organization. It is up to the Organization Administrators and your community to decide on which two people will be attending (but they must be 2017 Mentors with assigned student projects or a 2017 Organization Administrator).

Where can I find more information?

Please visit the Mentor Summit website for information about the plan for the weekend, hotels, shuttle schedules, local information, instructions for requesting visa letters and more. We’ll be adding more information to the site as the date gets closer, so make sure to check back often!

How do I get reimbursed for travel expenses?

Each organization will receive $2200* from Google to cover the costs of travel to the Mentor Summit. Org Admins are responsible for re-distributing the funds to their delegates. Talk to your Org Admin to find out what receipts they may require for reimbursement.

*What if we miss an evaluation?

Organizations that miss an evaluation during the program will only be able to send one delegate and will only receive $1100 in travel funding. Any organizations missing two or more evaluations will not be able to send any delegates to the summit and will not receive any travel funding.

Waitlist

Many orgs wish to send more than two delegates to the Mentor Summit at their own expense. If your organization has more than two delegates that wish to attend the Mentor Summit, please have them put their name on the waitlist. As we get closer to the event we will contact any additional people that we can accommodate. Google will cover the two hotel nights, but no other additional funds will be provided. Please do not book a hotel room until Google admins have contacted you directly about an open space.

Not sending any Mentors to the Summit?

If your organization does not wish to send anyone to the Mentor Summit at all please let us know via the registration form so that we can make note of it and take some of the people off of the waitlist.

Sign Up Here!

If your Org has decided that you should attend the Mentor Summit please complete all 3 of these steps before September 5th, preferably at the same time. (The sooner the better to guarantee you a hotel room.)

  1. Please complete the Mentor Summit Registration form as soon as you are sure you will be able to attend.
  2. Book your hotel room before September 5. We encourage you to book as soon as you know you will be attending to guarantee your room. You get to choose which hotel you wish to stay at.

    To book your room, use these GSoC specific hotel registration links: Sheraton Sunnyvale or Aloft Santa Clara

    When booking your hotel you will need to supply a credit card number for incidentals and extra nights. You will not be charged for the nights of October 13 and 14.

  3. Read the GSoC 2017 Mentor Summit website for many more details about the weekend.

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

June 29, 2017: URGENT GSoC 2017: Final hours to submit your evaluation of your student

TO: Mentors and Org Admins

Our records indicate you have not submitted the evaluation of your GSoC student.

You must complete an evaluation of your student before Friday, June 30th at 16:00 UTC. Go to your dashboard on the GSoC program site to complete the evaluation. We encourage you to complete the evaluations ASAP - it should take you less than 10 minutes to complete.

If your org misses an evaluation your org will lose $1100 of the mentor summit travel stipend and one less person will be able to attend the summit. If you miss the evaluation you will not be invited to the Mentor Summit.

June 26, 2017: Evaluations of your students are now open!

TO: Mentors and Org Admins

First Evaluations

First evaluations are now open!

One mentor for each student project must complete an evaluation of their student before June 30th at 16:00 UTC. If you haven't done so already, go to your dashboard on the GSoC program site and complete your evaluation of your student before June 30th at 16:00 UTC. We encourage you to complete the evaluations ASAP so you don't forget to do it - it should take you less than 10 minutes to complete.

If your org misses an evaluation your org will lose $1100 of the mentor summit travel stipend and one less person will be able to attend the summit.

Org Admins -- we encourage you to verify all evaluations for your org's student projects are complete 48 hours before the deadline, giving you time to contact the mentors directly if they have outstanding evaluations. Org Admins can complete the evaluation if needed.

To fail or not to fail?

Every year we tell organizations and mentors to fail students who are not doing their work. Often people will want to give the student the benefit of the doubt that they will improve - this rarely happens. 12 years of experience has taught us if you are considering failing a student then you probably should.

Google Summer of Code requires students to write quality code for the open source organizations they are working with while meeting their scheduled milestones. Students should not receive a stipend for being good proposal writers and nice people. They must also produce quality code that lives up to the expectations of your community. If they don't they should be failed. Period.

In the evaluation there is a section where you can leave feedback directly for the student that they will see after the evaluation deadline passes. This is the place to say what they did well and also why you failed them (what they should have been doing - example: communicating with the mentor/community and meeting their scheduled milestones, etc.).

Failing students is expected and encouraged (when appropriate)

Each year, when Google admins are considering the Org Applications we look at the pass/fail status of an org's previous GSoC experience(s). We expect to see some failures from orgs who have participated several times. Orgs who never fail anyone makes us wonder if the they are being too lenient with their students. Failing a student can be a good thing for the student. It can teach them the importance of deadlines, responsibilities, and also not over-committing or overselling their skills. Many students have said they failed their first GSoC and then reapplied the next year and succeeded, because they learned from where they went wrong.

When deciding whether to pass or fail your student you should be considering the actual code produced and their involvement in the community. It is your responsibility to your organization, to all of the other students participating in GSoC, to yourself, and to Google, to evaluate the student on the quality of their code contributions they have produced during these first 4 weeks of the program. Things happen and students get sick or have other issues pop up that don't allow them to work as much on GSoC as they planned. This happens. But just like with a job, if you don't do your work and meet the requirements of your job you are let go. Students that aren't meeting their deadlines and producing quality code should be failed.

The mentors list has had several productive discussions about whether failing is appropriate in certain circumstances. You can find them in the archive.

Only 1 mentor can submit an evaluation for a student. If there are multiple mentors for a single student project you should decide in advance which mentor will complete the evaluation.

Important Dates

  • June 30th 16:00 UTC: First Evaluation Deadline (for both mentors and students)
  • July 24-28: Second Evaluation (for both mentors and students)
  • August 1: Deadline for designated finance person from Org to complete Payoneer registration

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

June 20, 2017: Please complete the Payment Request Form

TO: Org Admins

There are only 4 days left for your organization to complete the payment request form. Please complete the form if you want to accept or decline payment from Google for your GSoC students and mentor summit travel stipend. For more information about the payment process, please see our 2017 GSoC Payment Instruction page. You can disregard this email if you've already completed the form.

Orgs that do not fill out the form by Friday, June 23 will not be paid. The deadline cannot be extended.

If you have any questions about the payment process or Payoneer, please contact us directly at gsoc-suppport@google.com.

June 14, 2017: Important GSoC First Evaluation Information

TO: Mentors and Org Admins

We hope you are enjoying working with your students during these first few weeks of coding.

Below is important information regarding your required First Evaluation of your student(s) - please read everything very carefully.

IMPORTANT DEADLINE for ALL MENTORS: First Evaluations open June 26 and are DUE before June 30, 16:00 UTC

This first evaluation is a required part of your participation in GSoC 2017 and should take you about 10 minutes to complete. If you do not complete the first evaluation of each of your students by June 30, your organization will automatically lose $1100 of the mentor travel stipend for the mentor summit. There are no exceptions. Missed evaluations also contribute to our decision on whether to accept an organization in future years of GSoC.

Starting at 16:00 UTC on June 26th you can go to your dashboard on the GSoC program site to complete the first evaluation. Just click on the “Complete Evaluation” button and fill out the form. You must complete the entire evaluation form at once — you can not submit a partially completed evaluation and you can not edit the evaluation once it has been submitted. You must submit your first evaluation by June 30th at 16:00 UTC.

Can’t submit the Evaluation between June 26-30?

If you know you will be unable to complete the evaluation of your student between June 26 - June 30 at 16:00 UTC, please ask the other mentor working with your student to complete the form. Your Org Admin can also fill out the form on your behalf. If you have the Org Admin complete the form be sure to provide them the answers (link to questions below) so they can fill out the form for you when the evaluation period opens.

Only one Mentor can complete an evaluation for a student

If there are multiple mentors working with a student you will need to decide which of you will be filling out the first evaluation of the student. Only one mentor can complete the evaluation. Once the evaluation has been submitted it can not be edited, so be sure you both agree on the outcome (pass versus fail) and who will be filling out the form ahead of time.

Frequently Asked Questions

What if I have multiple students?

If you are a Mentor for multiple students then you will see all of the First Evaluations that need to be completed in your Dashboard. From there you can click on the name of the student you wish to complete an evaluation for.

Can I see the evaluation questions in advance?

Yes, you can view the evaluation questions now.

Should I fail my student?

This is a very common question and you can check out some of the threads on the GSoC Mentors list that discuss this as well as the “Evaluations” chapter of the Mentor Manual.

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

May 18, 2017: Mentor Summit dates and FAQs from Mentors

TO: Mentors and Org Admins

We wanted to send an email to address a few of the common questions that have popped up over the last couple of weeks. If you haven’t done so already, please read the Mentor Manual and the Roles and Responsibilities doc to help you navigate the next few months of GSoC.

Mentor Summit Dates

The GSoC 2017 Mentor Summit will be held from October 13-15 in Sunnyvale, California. Each Org will be able to send two representatives (they can be assigned mentors or org admins). It will be up to the Org to decide who their two representatives will be (registration will happen later this summer). Orgs will receive a total of $2200 for the travel for both mentors/org admins.

IMPORTANT: If you miss any evaluation deadlines we will reduce the travel stipend and the number of representatives your Org can send to the Mentor Summit. Any mentor missing an evaluation during the program will not be allowed to attend the Mentor Summit.

We will be sending more details on the process for obtaining the mentor summit travel stipends and mentor stipends to Org Admins in a few weeks.

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 30th. 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.

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

    Yes, your student can start coding (it is not forbidden - unless they are specifically under a CPT requirement that does not allow them to code until May 30 - you should ask them if this is the case). 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. And in some cases students need to finish their coding a few days before August 21 (due to their CPT requirements) so they may ask to start a bit earlier so they can accomplish their project before August 21.

  • 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 add more facets to the project. The student shouldn’t be expecting to only work on their project for 20 hours a week.

  • 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. Then email us at gsoc-support@google.com when your student notifies you that they have left the program. Unfortunately it is too late to add another student to replace that student slot.

Future Emails for Mentors and Org Admins

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

Only mentors with assigned projects and org admins will be eligible to attend the Mentor Summit and receive the mentor tshirt at the end of the program.

Important Upcoming Dates

  • May 4 - 29: Community Bonding Period
  • May 30: Coding begins!
  • June 26 - 30: First evaluation period - mentors evaluate students, students evaluate mentors
  • July 24 - 28: Second evaluation period - mentors evaluate students, students evaluate mentors
  • August 21 - 29: Students wrap up their projects and submit final evaluation of their mentor
  • August 29 - September 5: Mentors submit final evaluations of students
  • October 13 - 15: Mentor Summit in Sunnyvale, California

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.

May 2, 2017: Next Steps for All Mentors and Org Admins

TO: Mentors and Org Admins

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

Accepted Student Announcement

GSoC 2017 accepted students will be announced on Thursday, May 4th at 16:00 UTC on the GSoC program site. At that time, emails will also be sent to all students (both accepted and rejected). It may take a few hours for the 1300+ accepted and 3200+ rejected student emails to be sent out.

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 May 4th) you are welcome to send out tweets, publish blog posts, etc. but not before then.

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

Google Summer of Code works best when the student and mentor work together. 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 -- weekly at the minimum -- not monthly. If this is what you planned, please notify your org immediately so they can find a replacement mentor for your student and then you need to withdraw from the program. Yes, we're serious about the commitment level required from mentors.

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

What do I do now?

Please read the Roles and Responsibilities page 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.

If you haven’t looked at the GSoC Mentor Manual please at least read the Communication and Mentoring sections.

Community Bonding Period

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

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 twelve years of GSoC have demonstrated that students who don't interact early and often are 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.

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 pressure the other person into making huge changes.

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 most 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 sometimes barely knew the particular coding language required. 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.

Students are able to edit their project title and abstract for the next month.

This year students will not receive any of their stipend until after they successfully pass their first evaluation at the end of June.

Email Archive

Remember to check out the archive of all messages sent to Mentors and Org Admins during GSoC 2017 in case you missed some of the earlier ones or just want to easily see all of them in one place. We update that page within 2 days of each email being sent out.

We will continue to send emails to all Mentors that have registered for the program until May 30th because some orgs are still adding mentors. After May 30th we will only send emails to Mentors with an assigned student project and to all Org Admins.

April 23, 2017: 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 13 hours - Monday, April 24th 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 25 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 2017 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 30th. But ideally you will have already identified the primary mentor for the project when students are announced on May 4th. This way the student can get to know their mentor at the very start of the community bonding period.

We understand some orgs won’t use all of their allocated slots and that is fine, 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.

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

April 19, 2017: Student Project Selection

TO: Org Admins

We have allocated 1400 student slots to the 201 open source organizations participating this year, making this the biggest GSoC ever!

Now it’s time to make the final decisions on which student projects your org will accept and which mentors will help guide the students on their summer projects. Slot allocations have been granted and are now visible in each OA's dashboard.

Student Project Selection

Monday, April 24th 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 2017 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 30th. But ideally you will have already identified the primary mentor for the project when students are announced on May 4th. This way the student can get to know their mentor at the very start of the community bonding period.

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.

Program Administrators 2nd Review

This year Google Program Admins are doing an additional review of each student’s eligibility for the program. 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 May 4th.

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 May 4th announcement.

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 May 4th after 16:00 UTC. Decisions are not official until it is on the website and emails are sent.

On May 4th 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.

Important Dates

  • April 19 - 24 16:00 UTC: Select the proposals to become projects (OAs enter selections)
  • April 24 - May 3: Google completes another review of student eligibility
  • May 4: Accepted GSoC 2017 students/projects are announced
  • May 4 - 29: Community Bonding Period
  • May 30: Coding begins!
  • June 26 - 30: First evaluation period - mentors evaluate students, students evaluate mentors
  • July 24 - 28: Second evaluation period - mentors evaluate students, students evaluate mentors
  • August 21- 29: Students wrap up their projects and submit final evaluation of their mentor
  • August 29 - September 5: Mentors submit final evaluations of students
  • September 6: Students passing GSoC 2017 are announced

Please contact us at gsoc-support@google.com if you have any questions at all.

April 16, 2017: Less than 21 hours to submit GSoC Slot requests

TO: Org Admins

As of right now 44 of the 201 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 less than 21 hours - 16:00 UTC Monday, April 17th).

Slot Selection and Project Selection

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

Slot Requests

Deadline: Monday, April 17th 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. These numbers are used to help Google allocate slots. Orgs may receive less than your 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.

Read Slot Allocation and Project Selection for more information.

Student Eligibility

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

April 17th 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. 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 17th deadline will disappear from your list of student projects you can accept on April 19th.

Upcoming Important Dates

  • April 17, 16:00 UTC: Deadline to submit slot requests (OAs enter requests)
  • April 19, 16:00 UTC: Slot allocations are announced by Google
  • April 19 - 24 16:00 UTC: Select the proposals to become projects. (OAs enter selections)
  • April 24 - May 4: Google will do another review of student eligibility
  • May 4: Accepted GSoC students/projects are announced
  • May 4 - 29: Community Bonding Period
  • May 30: Coding begins!
  • June 26 - 30: First evaluation period - mentors evaluate students, students evaluate mentors

April 7, 2017: Reviewing Proposals and Other Important Info

TO: Mentors and Org Admins

This year we had a record number of registered students, and we hope you're enjoying reviewing their proposals! This email contains important information and answers to questions we've seen a few times on the mentors list. Please read it carefully.

Reviewing Proposals

Decisions should be made on the content of the uploaded Final PDF and interactions you have had with the student. Do not use the content of any draft for your decision.

The goal of GSoC is to encourage new open source contributors, and Google frowns upon organizations who select participants who are already affiliated with them. (This does not include students participating in GSoC with the same org for a second year.)

We encourage you to set a high bar. Do not accept "okay" proposals.

Tips
  • Change the sort order of most tables by clicking on a column header.
  • Org Admins can export a CSV of Proposal details from the EXPORTS menu on their dashboard.
  • Make obvious "no" proposals (spam, empty, or just not good enough) disappear from the default view by clicking IGNORE in the individual view or the eye in the list view.

Slot Requests

Deadline: Monday, April 17th at 16:00 UTC

Before April 17th, Org Admins should request a minimum and maximum number of project slots based on the final proposals you want to and can mentor. Slots should only be requested for projects with at least one confirmed mentor where the student has a good chance of succeeding. First-time orgs will likely only receive 1-2 slots, no matter how many they request.

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

What's after Slot Requests?

On April 19th, slot allocations will be announced. Then you must decide which of your students will fill those slots. An Org Admin will enter your selections on the website, including assigning at least one mentor to each project.

FAQ

  • Can I be a mentor for multiple organizations?

    Yes. Mentors can be mentors on multiple orgs. But - we encourage mentors to minimize the number of students they are mentoring so that they have enough time for each student.

  • Can we add more mentors later?

    Yes. Mentors can be added throughout the program. If you find that someone is taking an active mentoring role on a project, we encourage you to officially add them. (It helps keep our statistics accurate.)

  • Is it ok to talk to the students during this phase?

    Yes. It is in a student's best interest to interact with your organization (fixing bugs, etc.) or for you to ask them questions that will help you make a decision. This can help you identify dedicated students who are likely to succeed. Do not communicate any information around (potential) acceptance or rejection. (i.e. "You're our number one pick") until the results are visible on the GSoC site on May 4th.

Upcoming Important Dates

  • April 17, 16:00 UTC: Deadline to submit slot requests (OAs enter requests)
  • April 19, 16:00 UTC: Slot allocations are announced by Google
  • April 19 - 24 16:00 TC: Select the proposals to become projects. (OAs enter selections)
  • April 24 - May 4: Google will do another review of student eligibility
  • May 4: Accepted GSoC students/projects are announced
  • May 4 - 29: Community Bonding Period
  • May 30: Coding begins!
  • June 26 - 30: First evaluation period - mentors evaluate students, students evaluate mentors

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

March 31, 2017: 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 72 hours! 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: April 3 - 16

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

After 16:00 UTC April 3rd, org members will be able to see the Final PDFs submitted by students.

April 3rd 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 click the 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 17 16:00 UTC

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. New orgs will likely only receive 1-2 slots, no matter how many they request.

April 17th 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 19th (when slots are announced).

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

Upcoming Important Dates

  • April 3 16:00 UTC: Mentors and Org Admins review student draft proposals and give students feedback on their proposals.
  • April 3 - 16: 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.
  • April 17, 16:00 UTC: Deadline to submit slot requests (OAs enter requests)
  • April 19, 16:00 UTC: Slot allocations are announced by Google
  • April 19 - 24 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 24 - May 4: Google Program Admins will do another review of student eligibility
  • May 4: Accepted GSoC students/projects are announced
  • May 4 - 29: Community Bonding Period
  • May 30: Coding begins!
  • June 26-30: First evaluation period - mentors evaluate students, students evaluate mentors

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 20, 2017: Tips on Reviewing Student Proposals

TO: Mentors and Org Admins

Thank you for registering to be a GSoC 2017 mentor or organization administrator!

We have many new mentors and organizations this year so we wanted to go through some important details to help you understand the process for the next couple of months.

Please take the time to reach out to your organization administrator about what is expected of you this year as a mentor. We also encourage you to read the entire Google Summer of Code mentor manual and the Roles and Responsibilities doc if you haven't done so already. Both the manual and Roles and Responsibilities doc were written by GSoC veteran Org Admins, Mentors, former students and Google Program Admins. They have helpful information about the program and how to participate successfully at each step in GSoC.

New GSoC Orgs: the section about participating in your first GSoC has some great tips.

To see all emails sent to mentors and org admins visit this page that will continue to be updated throughout the program.

Student Proposals

As of today, students are able to submit their proposals via the website. Each student may submit up to 5 proposals to the program. 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. To encourage more students to seek feedback on their proposals we made draft proposals 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 (if the student sets their sharing settings correctly).

Over the next couple of 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.

Students must submit their final proposal as a PDF through the website. It will be visible to you after the deadline for student applications (April 3 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 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 1 mentor assigned to the project. 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. Mentoring can be a lot of work and we don’t want anyone to burn out and become frustrated with the program.

Important GSoC 2017 Dates and Deadlines

  • **March 20 - April 3 16:00 UTC: Mentors and Org Admins review student draft proposals and give students feedback on their proposals.
  • April 3 - 16: 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.
  • April 17, 16:00 UTC: Deadline to submit slot requests (OAs enter requests)
  • April 19, 16:00 UTC: Slot allocations are announced by Google
  • April 19 - 24 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 24 - May 4: Google Program Admins will do another review of student eligibility
  • May 4: Accepted GSoC students/projects are announced
  • May 4 - 29: Community Bonding Period
  • May 30: Coding begins
  • June 26 - 30: First evaluation period - mentors evaluate students, students evaluate mentors
  • July 24 - 28: Second evaluation period - mentors evaluate students, students evaluate mentors
  • August 21- 29: Students wrap up their projects and submit final evaluation of their mentor
  • August 29 - September 5: Mentors submit final evaluations of students
  • September 6: Students passing GSoC 2017 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. We will add anyone who has opted in to the list every few days for the next month. And then every couple of weeks throughout the program. You can always opt out once you have been added by unsubscribing using the link on any of the emails.

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.

We look forward to working with all of you over these next 6 months! Thanks again for being a mentor for GSoC 2017!

March 3, 2017: Notes for Org Admins

TO: Org Admins

We have many new Org Admins this year as well as some changes to the program so we wanted to go over a few quick items.

Inviting Mentors to your Org

We have fixed the validation error and you many now invite new mentors to GSoC. Sorry for the delay.

All mentors must be invited by an Org Admin. If you need a way to track people who want to mentor for you, we suggest using a Google Form or just having them send you an "I want to mentor" email.

Org Admins can also be mentors. (The website considers the Org Admin role to be a superset of the Mentor role.) In smaller orgs this is very common. In larger orgs, Org Admins often act as a backup mentor. If an assigned mentor does not perform their duties (evaluations, communication, mentoring) it is the Org Admins' responsibility to find a replacement mentor or step in and mentor themselves.

What is expected of Org Admins

  • Ensure that your organization's profile page is complete and accurate. Keep your ideas list up to date. We noticed many organizations have their projects still broken up in milestones based on midterm and finals - be sure to update the milestones into three sections (for each of the three phases of the program).
  • Make sure the logo looks good. (A logo that contains the organization name in readable letters is suggested.)
  • Verify the short description makes sense on the main organization page -- this is the page many students will read through to quickly find orgs that interest them. Some orgs have unclear descriptions or just list their org name again. You can easily edit this in the “Org Profile”.
  • 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. Make sure you have enough.

After student applications conclude:

  • Request project slots
  • After slot allocation, select students and assign mentors.
  • Negotiate with other organizations in the case of a conflict over a student.
  • Ensure that your org is set up as a supplier with Payoneer in order to receive org stipends and mentor travel stipends (more info coming in May).
  • Make sure your mentors are communicating with students regularly (minimum of once a week).
  • Make sure all mentor evaluations of students are completed. Remember there are 3 evaluations this year - after the first month of coding, after the second month of coding and then the final evaluation at the end of the program. It is your responsibility to nag the mentor or complete it for them if they are unable to.

Contact Us

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

If you want to be included on the GSoC mentors mailing list be sure to opt in on your user profile page. We will add anyone who has opted in to the list on March 6th. We will continue to add people to the mailing list about once a week throughout the program.

Quick Glossary

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

Slot: Google will grant each org a certain number of project “slots” based on slots requested 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.

March 1, 2017: Welcome to GSoC 2017!

TO: Org Admins

This year marks our biggest program ever! We have 201 open source organizations participating in GSoC 2017 and we expect to accept more students than ever before as well. And welcome to 37 organizations participating in their first GSoC!

Right now you should be chatting with proactive, excited students. Remember to keep your Ideas List updated and make it clear and simple to understand so students can easily find your Ideas - if it requires multiple clicks to get to the Ideas List that is not ideal.

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.

New changes (and some reminders) for 2017

  • There are 3 evaluation periods this year 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 shorter than previous years so they should take less time to complete.
  • 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 late April so you do not need to be concerned about this.
  • If you are a university, we expect you to select students outside of your program. Selecting students from your university is okay but if all of the students you select are from your university then you likely won’t be accepted into GSoC again.
  • New org payment system using Payoneer. We are no longer requiring OAs to register for a Google supplier account and instead orgs will do what students do and create an account with Payoneer. This will allow for orgs to receive payments much faster, with orgs receiving their stipend payments in September. (more details to come in May)
  • We are now allowing 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.

Inviting Mentors to your Organization

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

PLEASE NOTE: Right now first time mentors should wait a few days to register until we have announced that we have fixed a small validation error on the site not allowing mentors to choose “0” as an option to the question ‘How many times have you participated as a GSoC mentor previously?’ They can’t edit that field once they put a number into it and we are trying to get a good idea of how many new mentors we have each year. Thank you for your patience.

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 March 6th. 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 20: 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.
  • March 20 - April 3 16:00 UTC: Students will submit their draft proposals through the program website for you to give solid feedback on.
  • April 3 - 16: 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.
  • April 17, 16:00 UTC: Deadline to submit slot requests (OAs enter requests)
  • April 19, 16:00 UTC: Slot allocations are announced by Google
  • April 19 - 24 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 24 - May 4: Google Program Admins will do another review of student eligibility
  • May 4: Accepted GSoC students/projects are announced
  • May 4 - 29: Community Bonding Period
  • May 29: Deadline to notify Google Admins of an inactive student that you wish to be removed from the program
  • May 30: Coding begins
  • June 26 - 30: First evaluation period - mentors evaluate their students and students evaluate mentors
  • July 24 - 28: Second evaluation period - mentors evaluate students, students evaluate mentors
  • August 21- 29: Students wrap up their projects and submit final evaluation of their mentor
  • August 29 - September 5: Mentors submit final evaluations of students
  • September 6: Students passing GSoC 2017 are announced

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 Manual, which contains important information for both Mentors and Org Admins at each stage of the program.

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