2017 Email Announcements

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

January 18, 2018: GCI 2017 has come to an end - thank you all

TO: Mentors and Org Admins

This has been our largest GCI ever with 25 orgs, 710 mentors, and over 3500 students completing an astounding 16,437 tasks -- we had a total of 1340 students complete 6,379 tasks in 2016 for reference.

Choosing your Grand Prize Winners and Finalists

Org Admins can now visit their dashboard and must select:

  • 2 Grand Prize winners
  • 1 Backup Winner (in case another org chooses one of your Grand Prize winners or they are disqualified for some reason, etc.)
  • 2 more Finalists

The candidates for these slots are restricted to the top 10 students who completed the most tasks for your organization.

These 5 students will all be considered your Finalists and will receive the GCI finalist hoodie and a special certificate designating them as a finalist for your org in GCI 2017. The two Grand Prize Winners will receive a 4 day trip for themselves and a parent or legal guardian to Google headquarters in California.

Per the Contest Rules, orgs should choose their Grand Prize Winners and Finalists based on the comprehensive body of work the student completed in the contest period from November 28, 2017 to January 17, 2018. As stated in the Contest Rules: Each entry will be judged according to the following factors: creativity, thoroughness, and quality of work. The Organization may additionally factor the contestant's involvement in the Organization's community in the judging.

Students who have been Grand Prize Winners in the past are not eligible to be winners again. They can be named as Finalists however. You don't need to investigate if the student was a previous winner, we will check before issuing prizes. If there is an issue we will move the backup winner into a Grand Prize Winner slot. We don't expect this to happen as most previous grand prize winners became mentors for orgs or just completed a handful of tasks to earn another t-shirt.

Announcing GCI winners and finalists

We will be contacting Grand Prize Winners and Finalists around January 24th as we need additional paperwork from the students and their parents before we can release their information publicly. So it is possible they may reach out to you directly to say thank you - we tell them not to post anything publicly which includes to the org's mailing lists until after the Jan 31st announcement.

Please do not announce your org's winners or finalists before the announcement is live on the Google Open Source blog January 31st at 17:00 UTC (9am PT).

Feedback form

Please take a few minutes to fill out our post-GCI feedback survey: https://goo.gl/forms/1BlLVqga4m9DAD0k1

We read all of the comments. It's a very important tool as we strive to continuously improve and grow the contest. Your feedback is instrumental to that process. Thank you in advance for any feedback, ideas, or comments you provide.

Important Dates

  • Tuesday, January 23rd 17:00 UTC - GSoC Org Apps close (since many of you are OAs for GSoC too)
  • Wednesday, January 24th 17:00 UTC - Deadline for organizations to choose their 2 Grand Prize Winners, their backup winner and the other 2 finalists.
  • Wednesday, January 31st - Winners announced on g.co/gci and Google Open Source blog

Any questions? Email gci-support@google.com!

You can find all the previous emails we've sent out in the Mentor/Org Admin email archive.

January 11, 2018: Final Week Updates for Mentors and Org Admins: Prepare to Choose Winners!

TO: Mentors and Org Admins

We are in the final days of GCI 2017!

Thank you, thank you, thank you!

This has been the smoothest GCI yet even with almost triple the number of student participants. This success is due to your dedication and hard work towards helping these students learn about your organizations and open source!

Important Dates

  • Monday, January 15th 17:00 UTC - Deadline for students to claim their final task
  • Wednesday, January 17th 17:00 UTC - Deadline for students to submit their work - you can not request additional work after this deadline
  • Thursday, January 18th 17:00 UTC - Deadline for mentors to review student’s work
  • Tuesday, January 23rd 17:00 UTC - GSoC Org Apps close (FYI - since many of you are OAs for GSoC too)
  • Wednesday, January 24th 17:00 UTC - Deadline for organizations to choose their 2 Grand Prize Winners, backup winner and two more finalists
  • Wednesday, January 31st - Winners announced on g.co/gci and Google Open Source blog

Choosing your Grand Prize Winners and Finalists

Starting on Thursday, January 18th at 17:00 UTC, an Org Admin must visit their dashboard and select:

  • 2 Grand Prize winners
  • 1 Backup Winner (in case another org chooses one of your Grand Prize winners or they are disqualified for some reason, etc.)
  • 2 more Finalists

The candidates for these slots are restricted to the 10 students who completed the most tasks for your organization.

These five students will all be considered your Finalists and will all receive the GCI Finalist hoodie and a special certificate. Grand Prize Winners will receive a four day trip for themselves and an adult to Google headquarters in California.

Per the Contest Rules, orgs should choose their Grand Prize Winners and Finalists based on the comprehensive body of work the student completed in the contest period from November 28, 2017 to January 17, 2018. As stated in the Contest Rules: Each entry will be judged according to the following factors: creativity, thoroughness, and quality of work. The Organization may additionally factor the contestant’s involvement in the Organization’s community in the judging.

Students who have been Grand Prize Winners in the past are not eligible to be winners again. They can be named as Finalists. You don’t need to check if the student was a previous winner, we will. If there is an issue (very unlikely) we will move the backup winner into a Grand Prize Winner slot.

Announcing Winners and Finalists

We will announce the Grand Prize Winners publicly on Wednesday, January 31st at 17:00 UTC. Please do not announce your org’s winners or finalists before the announcement is live on the Google Open Source blog January 31st at 17:00 UTC (9am PT).

T-shirt size and shipping details

Please verify that your t-shirt size and style and shipping details are correct on your profile before January 24th. Changes made after that date will not be honored. T-shirts will ship from the US on or around February 15th to mentors and students and may take as long as a month to arrive. If you provide an incorrect or invalid address, we will not re-ship.

Men’s Sizing Chart (measurements are in inches)

  XS S M L XL XXL XXXL
Body Length 27 28 29 30 31 32 33
Body Width 16.5 18 20 22 24 26 28
Sleeve Length 8 8.25 8.63 9.13 9.63 10.25 10.25

Women’s Sizing Chart (measurements are in inches)

  S M L XL XXL
Body Length 26.13 26.75 27.38 28 28.63
Body Width 16.25 18.25 20 22.25 24.5
Sleeve Length 7.5 8 8.75 9.25 10

Live in a Restricted Country? We have some good news for you. We are using a new shipment logistics company that should be able to deliver to you. No guarantees yet, but we're cautiously optimistic, so please make sure your address is correct or update it by January 24th! Please keep in mind that we cannot ship to PO boxes, so please provide a physical address.

Call for blog posts

We'd love it if you (or one of your students) would like to write guest a blog post for the Google Open Source Blog about GCI 2017. We want to hear about the cool projects, inspirational experiences, and success stories. Even if you don't have a whole post, we'd love to hear short stories or quotes that we can aggregate. Please send all blog posts and content to gci-support@google.com.

In closing

Whew, that was a long read... almost done! Only a week to go before you can stop worrying about reviewing tasks for another 10+ months. ☺

Thank you again for the countless hours you have dedicated to help thousands of teens learn about open source development. This year was a whirlwind with a huge number of students from around the world participating. We can't do this without you.

If you have any questions or concerns feel free to contact us at gci-support@google.com.

As always, you can find all the previous emails we've sent out in the Mentor/Org Admin email archive.

January 4, 2018: GCI Week 6 Updates for Mentors and Org Admins

TO: Mentors and Org Admins

Expect increased student activity these final weeks

Last year we noticed a 30% increase in tasks being completed in the final 2 weeks of the program. This is pretty normal as there is always a mad rush for those students who procrastinated and are trying to get their 3 tasks completed to earn the tshirt or those in the race for finalist and winner positions. This will likely continue until the deadline for task claims - January 15. Yes, I know that is hard to believe. We’ve been looking at charts of the number of tasks in progress each week and the numbers just keep going up!

Important Dates

  • Thursday, January 4th 17:00 UTC - GSoC 2018 Org Apps open
  • Monday, January 15th 17:00 UTC - Deadline for GCI students to claim their final task
  • Wednesday, January 17th 17:00 UTC - Deadline for GCI students to submit their work. Note that you have to either approve the work or reject it, you can not send it back for more work after this deadline.
  • Thursday, January 18th 17:00 UTC - Deadline for mentors to review student’s work
  • Tuesday, January 23rd 17:00 UTC - GSoC Org Apps close (since many of you are OAs for GSoC too- apologies in advance for the crossover this year)
  • Wednesday, January 24th 17:00 UTC - Deadline for organizations to choose their 2 Grand Prize Winners, their backup winner and the other 2 finalists.
  • Wednesday, January 31st - Winners announced on g.co/gci and Google Open Source blog

You can find all the previous emails we've sent out in the Mentor/Org Admin email archive.

December 28, 2017: GCI Week 5 Updates for Mentors and Org Admins

TO: Mentors and Org Admins

Thank you all for holding up to the busy holiday week. We reviewed over 100 forms yesterday and 70+ every day since last week so we know you all have been doubly busy. Thank you for staying on top of all of the tasks, there were only 2 orgs that had more than 1 task go more than 36 hours without review during this past week - great job everyone!

Important Dates

  • Thursday, January 4th 17:00 UTC - GSoC 2018 Org Apps open
  • Monday, January 15th 17:00 UTC - Deadline for GCI students to claim their final task
  • Wednesday, January 17th 17:00 UTC - Deadline for GCI students to submit their work. Note that you have to either approve the work or reject it, you can not send it back for more work after this deadline.
  • Thursday, January 18th 17:00 UTC - Deadline for mentors to review student’s work
  • Tuesday, January 23rd 17:00 UTC - GSoC Org Apps close (since many of you are OAs for GSoC too- apologies in advance for the crossover this year)
  • Wednesday, January 24th 17:00 UTC - Deadline for organizations to choose their 2 Grand Prize Winners, their backup winner and the other 2 finalists.
  • Wednesday, January 31st - Winners announced on g.co/gci and Google Open Source blog

You can find all the previous emails we've sent out in the Mentor/Org Admin email archive.

December 20, 2017: GCI Week 4 Updates for Mentors and Org Admins

TO: Mentors and Org Admins

This year's contest is one for the record books! Over 1600 tasks are currently in progress! And over 2,000 students have completed more than 7,250 tasks! See this blog post for more details.

On to business... a few things to keep in mind:

  • Please pay attention to response times. 36 hours max, 24 hours or less preferred. A few orgs were slipping last week -- after some reminder emails they're mostly back on track. Timely responses are very important to keeping the contest running smoothly.
  • Please don't change the beginner status after a task has been published. Either the task is a beginner task when you publish it or it's not. Changing it later can mess with the student being able to only complete 2 beginner tasks.
  • Always press "needs more work" when sending the task back to the student. This will restart the timer and make it clear who then has the next action. (Just like a chess clock.) You can always give the student more time if necessary.
  • If you're a member of a slammed org, there may be ways to slow things down a bit. That might mean reducing the availability of simpler tasks or encouraging slower response times. (Think about responding in a few hours, instead of minutes.) Mentor burnout for some orgs is only going to get worse as the contest continues to ramp up to historical proportions. We're not at the halfway point yet -- we don't want any of you to get frustrated and quit. :)
  • With many students now on holiday break (or about to be) there will be another round of new students starting in the next few days checking GCI out and likely going for the certificates and tshirts. Please be sure you have a holiday plan in place for every day for the next 4 weeks.

A huge thank you to all of you for working so hard and helping these students learn more about open source! We couldn't do this without you.

At the end of the contest we would like to highlight some fun stories on our blog. If something fun/interesting happens with your students, or you have a couple of all star students going above and beyond, etc. please let us know.

You can find all the previous emails we've sent out in the Mentor/Org Admin email archive.

Thanks and Happy Holidays!

December 12, 2017: GCI Week 3 Updates for Mentors and Org Admins

TO: Mentors and Org Admins

Hi Mentors and Org Admins,

A quick email this week. Things continue to go amazingly well! More students are completing more tasks than ever before!

On Monday, we pushed a new version of the website. It contains a variety of bug fixes, and some cool new features:

  • Emails now contain a X-For-Filtering footer that you can use to keep your email under control. Filter on "Interacted-True" to find emails related to tasks you've commented on.
  • URLs are now auto-linked in comments!
  • For orgs using the experimental webhooks, we've increased coverage and now have parity with the task update display.

The holidays are coming up fast (some have already started) -- be sure your organization has a holiday plan in place. We want you to be able to spend time with your friends and family (assuming that's what you want to do) but it's also important to maintain the response time for the students.

You can find all the previous emails we've sent out in the Mentor/Org Admin email archive.

Happy (early) Holidays!

Please continue to let us know if you run into any issues or glitches.

Keep up the great work everyone!

December 8, 2017: Week 2 GCI Updates for Mentors and Org Admins

TO: Mentors and Org Admins

Thank you for your hard work to make this the biggest (and best) GCI ever! You have done an amazing job keeping up with more students than ever before!

We hope you aren't getting burnt out. 12 orgs have already had over 150 tasks completed (with 2 orgs having over 325)!

In the first 10 days we have had 1,355 students complete tasks -- that is more than for the entire contest last year (1,340)! There is still 5+ weeks to go. The number of new students may slow down, with existing participants trying for a finalist or winner position. (But don't plan for that. School holidays may cause an influx of new participants.)

Personal Information

Don't ask students for personal information. Remember, these are all minors. They may not be aware of the effects of giving out too much information about themselves. Pretend you were a parent: How much information you would be okay with having on the internet about your child? Don't ask for specific location (country is ok) or gender. Students don't have filters and can inadvertently share personal and private information. We understand you are trying to build a community -- but safety comes first. As a mentor, please guide them towards appropriate and safe sharing.

Plagiarism and Cheating

Tasks that can be easily completed by copying things verbatim from elsewhere often lead to plagiarism. Students often don't understand that it's not okay to take text from Wikipedia or elsewhere on the internet and copy and paste it into their work. They haven't been taught it. One org asked students to write a short 3-4 paragraph essay explaining open source to a grandparent and several students searched Google for "What is open source?" and cut and pasted. That's not ok.

We encourage you to treat the first incident of this with a student as a teaching opportunity and send any task where you suspect they have copied work from elsewhere back for more work. Students who do it repeatedly or blatantly copy another student's work will be immediately removed from the contest once you notify us.

The best way to avoid plagiarism and cheating is to write tasks that require individual new work. If there's nowhere to copy from -- they can't copy.

Mentor Response Time and Other Issues

A record low number of participants (4) have complained to us about mentors taking more than 36 hours to respond. This is amazing, please keep it up.

Overall, from our side, this is the smoothest GCI ever.

We encourage orgs that are being slammed to try and find a way to give overloaded mentors a break to rest. This is a marathon not a sprint. We don't anyone burning out. We are trying this on our team too. 😃

Website

We have a website release scheduled next week to address a few minor bugs in the website. We're also sneaking some new features in there -- we think you're going to be very excited!

Please continue to let us know if you run into any issues or glitches.

Keep up the great work everyone!

November 29, 2017: Day 2 clarifications and translation tasks

TO: Mentors and Org Admins

You've made it to day 2 of GCI 2017! Congratulations!

First day stats

The last 32 hours have been insanely busy for a few of you (one new org had 184 tasks completed in the last 32 hours, the next highest task completion rate was 96 for another org). Seven organizations have had less than 10 tasks completed so far, don't worry, it will get busier. There are always ebbs and flows so don't get too comfortable yet. : )

We are very glad we have 25 orgs this year as the students are being spread out amongst all orgs. We have had as many students register in the first 32 hours of GCI 2017 as we had in the first 7 days last year!

Translation tasks

One thing that we didn't specifically ban this year (that we have for the past 6 years) was translation tasks. Some background on why this has been a concern - we banned translation tasks because it was a HUGE source of cheating by students. And with even more online translation tools available today, we suspect it is even easier to cheat with translation tasks now than it was 7 years ago. We have been reluctant to let translation tasks into GCI.

We decided not to specifically ban them this year BUT please think carefully about any translation tasks that you offer. If a task can be mostly completed with Google Translate or another automated translation tool, that's not a good task and you should not offer it. Good translation tasks should require deep knowledge of the target language -- and you must be able to verify that the work done is correct. These tend to not be "translation" tasks, but "language" tasks.

Good examples:

  • Developing a language specific style guide for translators to use.
  • Research into UI changes/challenges for different languages. (For example: German has above average word length, and might not fit on your normal buttons.)
  • Find and fix examples where a current translation has a word that doesn't make sense (and explain why it's wrong). (For example: Many languages have multiple different words that mean "button". Are you using the right one?")

Zulip has written some documentation as to different classes of "translation" tasks and what to look for.

Bad examples:

  • Translate our app/documentation/etc. into language X.

It's worth repeating, you must be able to validate any translation work done. For example, if you don't speak Klingon, you have no way of knowing if the student translated into proper Klingon, or into Romulan. (And the consequences of that could be dire.)

If you're not sure if you can make the right kind of translation tasks, we suggest you just don't offer them. Even if you say do not use automated translation tools, many students will.

Website

If you discover a bug, typo or have a feature request for next year please send it to us at gci-support. For bug reports please give us as much info as possible (screenshots when relevant are appreciated).

We've already made some fixes and tweaks based on your feedback over the past day.

Please don't forget that the team is here to help! If you need any advice or guidance do not hesitate to reach out to us directly. Here's to the most successful GCI yet!

November 22, 2017: GCI Final Reminders before Contest begins Nov 28th

TO: Mentors and Org Admins

With less than a week to go before GCI 2017 starts for students, we wanted to go over a few things to prepare you for the busy weeks ahead.

  1. Read the Roles and Responsibilities

    • There are always a lot of questions about what the expectations are for each role in the GCI and GSoC programs. This documentation aims to standardize expectations across all participating organizations.
    • Individual organizations may have additional roles and responsibilities. Talk to your Organization Administrator for more information.
  2. Enter your tasks into the system now

    • Org Admins: Be sure to have your minimum of 50 unique tasks (we strongly encourage you to have 75) entered into system before Tuesday, November 28th at 9am PT. We encourage you to enter them ASAP so if there is a problem or any confusion we can help you fix it (definitely don't wait until a few hours before the contest starts).
    • Don't publish all your tasks at the start of the program. This way you can easily (and quickly) publish more over the first few weeks of the program as your initial load of tasks rapidly disappear.
  3. Mentor Count

    • Great job everyone on rounding up your mentors. Right now 75% of orgs have 15 or more mentors. Remember, tasks can't be published without an assigned mentor. You can continue to add more mentors throughout the program as needed.
  4. Webhooks and API

    • If you wish to receive webhook notifications of task instance activity, you must email us the URL to send them to. We need to configure it manually for each organization.
    • Several organizations have contributed samples of how they use the API to manage tasks. We're listing those samples on our API page.

As always, please contact us at gci-support@google.com if you have any questions or concerns. We're looking forward to the biggest and best GCI ever! Thank you all for being a part of the program.

November 14, 2017: Updates - 2 Weeks before GCI starts

TO: Mentors and Org Admins

We are 2 weeks from the start of GCI 2017! We know you are all very busy creating tasks, inviting mentors, and getting your community ready for GCI but please read this email carefully. It's long, but it contains very important information.

gci-mentors mailing list

All Org Admins and Mentors who opted in have been added to the gci-mentors mailing list. Many of you have already started using the mailing list to ask for, and offer, advice. This is especially useful for new organizations and mentors. We hope that you all continue to support each other throughout the contest!

Task API and Webhooks

You can use the API or provided CSV Uploader to bulk upload tasks. If you wish to receive webhook notifications of task instance activity, you must email us your endpoint URL.

Mentoring with multiple organizations

We realize some of you wish to mentor with more than one organization. The system does allow for this but before doing it, please consider that GCI will be a very time consuming couple of months, please don't spread yourself too thin by trying to help multiple organizations. We highly encourage you to focus on only one organization.

GCI begins Tuesday, November 28th 17:00 UTC for students

By November 28th, all orgs should:

  • Have published a minimum of 75 unique tasks comprising at least 100 task instances across all 5 task categories (we strongly encourage you to have at least 100 unique tasks ready - even if some of these are not published yet).
  • Have 5+ beginner tasks (each with multiple instances available) - have a bunch of these ready for the first few weeks of the contest as most students will claim a beginner task for their first task.
  • The more tasks you have in your queue at the start of the contest, the easier your life will be (really, we can't stress this enough).
  • Have at least 10 mentors registered in the system (15+ would be ideal)
  • Have discussed how your org is going to decide on its finalists and winners at the end of the contest. Be sure all mentors are aware of the criteria and how your org will be evaluating community involvement, etc so that everyone is on the same page for the whole contest.

Process for students to register

Every year mentors are a bit confused by the process for students to register so below is the general flow of how the contest works for students once the contest opens:

  • Students go to the contest site and register for the contest.
  • During their registration they will send a link to their parent to complete the online parental consent form (or have their parent sign a paper copy and scan and upload it to their dashboard).
  • Once the parent has signed the Parental Consent form the student can claim their first task.
  • Students will work on the task, asking questions either through the GCI webapp or on one of the communication channels you have noted on the task itself or your org's homepage.
  • Student submits the work through the GCI webapp when they are ready. This can either be an uploaded file or a URL pointing to the work. Your choice.
  • Mentor reviews the work, if the task is complete the mentor marks it as complete. But if the task needs more work the mentor will send it back to the student with comments on what the student needs to do differently to successfully complete the task. The student will work on the task again and resubmit then mentor reviews the work and accepts it (hopefully it is complete, if not the mentor can reject it again and send it back to the student). NOTE: Don't accept incomplete/bad work. The students need to learn quality is important -- send it back if it is not what you want.
  • Once the student's first task is accepted by the mentor, Google Program Administrators will review the Parental Consent form for the student. If the form is complete, we will approve it and the student will then be able to accept their 2nd task. If the Parental consent form is incomplete/has errors, we will send it back to the student for their parent to fix. Students can not claim a 2nd task until their parental consent form has been approved by Google Admins.
  • Google Admins review forms multiple times a day so a student's form should be reviewed in under 18 hours (usually under 8 hours). (But we also need to sleep, so students should be patient.)

Help promote GCI through your community and contacts

Please help raise awareness of GCI to 13-17 year olds across the world. If you know people that are teachers or anyone involved in other communities that may reach pre-university students please spread the word about the program. Below is a sample short snippet you can send to folks (you can add additional details as you see fit).

Sample email snippet:

I wanted to contact you personally to tell you about the start of Google Code-in, a global, online contest introducing 13-17 year old pre-university students to open source software development. The contest starts on Tuesday, November 28th. Prizes include certificates, t-shirts, hoodies and 50 grand prize winners will win a trip to Google headquarters in California, USA next summer for themselves and a parent or legal guardian.

Over the past 7 years 4,553 students from 99 countries have completed 23,651 open source tasks in the contest. We expect this year to be the largest contest yet and would appreciate your help to spread the word to local students.

You can learn more about the details of the contest and the 25 open source organizations students can work with by visiting the contest site and reviewing the timeline and FAQs. Additional flyers and slide decks are available.

Thanks in advance for your help. If you have any questions about the GCI contest please contact me or the GCI program administrators at gci-support@google.com.

Students Plagiarizing/Cheating

This is a contest for teenagers, which unfortunately means it is likely some cheating and plagiarizing will occur. It is not the norm, but having just one student who cheats can be incredibly frustrating. Here is what to do:

  • If you believe a student copied someone else's work or is cheating in some other way please contact us immediately at gci-support@google.com.

    Include as much information as you can as to why you suspect this is cheating. This should include a link to the task instance, as well as any other documentation, information (the work they copied from) or logs you have.

  • We will review the information promptly. If we agree that it is cheating we will freeze the student's account (preventing them from accessing the system and making them ineligible to receive any prizes). We will also email them to let them know why they have been removed from the program.

  • Do not feel bad about reporting a student cheating or plagiarizing - it is not fair to the other 99% of students who are working hard in the contest.
  • This is a valuable lesson the students need to learn. Our team has no problem banning a student for bad behavior and cheating, neither should you.

Bad Behavior

In many cases student participants don't realize when they are acting or communicating poorly. They may not be familiar with your community standards and code of conduct.

  • We urge you to give the student the benefit of the doubt during initial interactions. Try to teach them the correct way to interact with other students and your community. They will often be thankful -- many may not realize what they were doing was wrong/inappropriate.
  • Threatening or harassing other participants (Students, Mentors, or Google representatives) is a violation of the Contest Rules. Please report cases promptly, and we will take swift action to remove the offender from the contest.

Expectations

Some questions have come up around the goals of GCI. Check out an extensive email we wrote that you can find on the GCI-mentor list from 11/11/2016.

GCI Mentor Email Archive

We will keep an archive of all of these information emails that we send to all mentors and OAs for GCI 2017 and we will keep adding it to the footer of all emails for the rest of the contest so that as new mentors are added they can easily go back and read the previous emails and it is easier for folks to reference the emails.

Please let us know if you have questions about any of this information. You can always reach us at gci-support@google.com. We hope you are all getting excited about GCI 2017! Long, deep breaths everyone, here we go! :)

Best, Stephanie