Difference between revisions of "Google Code In 2018"

From OSGeo
Jump to navigation Jump to search
(Added GCI Grand Trip Report)
 
(30 intermediate revisions by 6 users not shown)
Line 2: Line 2:
 
[[Image:GCI-logo.jpg|400px|link=https://developers.google.com/open-source/gci/]] <font size="+3"> @ </font> [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
 
[[Image:GCI-logo.jpg|400px|link=https://developers.google.com/open-source/gci/]] <font size="+3"> @ </font> [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
 
</center>
 
</center>
 +
 +
[[Image:GCI-2018-results.png|thumb|right|333px|Top 5 OSGeo students from the GCI 2018 contest]]
  
 
Central page for administering OSGeo participation in Google Code In 2018
 
Central page for administering OSGeo participation in Google Code In 2018
Line 10: Line 12:
 
* [https://codein.withgoogle.com/ Google Code In main page]
 
* [https://codein.withgoogle.com/ Google Code In main page]
 
* [https://developers.google.com/open-source/gci/how-it-works How Google Code-in Works]
 
* [https://developers.google.com/open-source/gci/how-it-works How Google Code-in Works]
* [https://developers.google.com/open-source/gci/resources/example-tasks Examples of Google Code-in Tasks]
+
* [https://developers.google.com/open-source/gci/resources/example-tasks Examples of Google Code-in Tasks] (also see OSGeo's tasks from the 2017 contest [https://codein.withgoogle.com/archive/2017/organization/5168183002529792/task/ here])
 
* [https://developers.google.com/open-source/gci/resources/media Logo, flyer and presentation]
 
* [https://developers.google.com/open-source/gci/resources/media Logo, flyer and presentation]
 
* [https://developers.google.com/open-source/gci/help/responsibilities Roles and responsibilities of Students, Mentors and Admins]
 
* [https://developers.google.com/open-source/gci/help/responsibilities Roles and responsibilities of Students, Mentors and Admins]
Line 18: Line 20:
 
* [https://developers.google.com/open-source/gci/timeline Full timeline]
 
* [https://developers.google.com/open-source/gci/timeline Full timeline]
 
* Sept 7 2018: organizations can start drafting application to be mentoring organizations
 
* Sept 7 2018: organizations can start drafting application to be mentoring organizations
* Sept 17 2018: application deadline ([https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=09&day=17&hour=16&min=0&sec=0 exact time]) for mentoring organizations (we should have mentors and tasks by then - "between 150 to 500 tasks")
+
* Sept 17 2018: application deadline ([https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=09&day=17&hour=16&min=0&sec=0 exact time]) for mentoring organizations (we should have mentors and tasks by then - we need a minimum of 25 tasks by 17 Sept, but we should aim to have between 150 & 500 tasks in total before the contest begins)
 
* Sept 18 2018: Mentoring organizations announced
 
* Sept 18 2018: Mentoring organizations announced
* Oct 23 2018: Contest opens for entries by student participants
+
* Oct 23 2018: Contest opens for entries by student participants ([https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=10&day=23&hour=16&min=0&sec=0 exact time])
 
* Dec 10 2018: Deadline for students to claim new tasks
 
* Dec 10 2018: Deadline for students to claim new tasks
 
* Dec 12 2018: All student work must be submitted; contest ends
 
* Dec 12 2018: All student work must be submitted; contest ends
Line 46: Line 48:
  
 
* [[Jeff McKenna]] <libravatar email="jmckenna@gatewaygeomatics.com"/> (IRC nickname: "jmckenna")
 
* [[Jeff McKenna]] <libravatar email="jmckenna@gatewaygeomatics.com"/> (IRC nickname: "jmckenna")
 +
* [[Victoria Rautenbach]] <libravatar email="victoria.rautenbach@gmail.com"/> (IRC nickname: "vrautenbach")
 +
''Contact OSGeo's administrators: gci-admin at osgeo dot org''
  
 
= Interested mentors / volunteers =
 
= Interested mentors / volunteers =
  
* fill out the Google form mentioned at [[Google Code In 2018 Mentors]]
+
* please fill out the Google form mentioned at [[Google Code In 2018 Mentors]]
  
 
= Recommendations for Students =
 
= Recommendations for Students =
  
* https://wiki.osgeo.org/wiki/Google_Code_In_2017_Recommendations_for_Students
+
* https://wiki.osgeo.org/wiki/Google_Code_In_2018_Recommendations_for_Students
  
 
= Tasks =
 
= Tasks =
  
* available on the GCI Dashboard when the contest starts on 28 November: https://codein.withgoogle.com/
+
* available on the GCI Dashboard when the contest starts on 23 October: https://codein.withgoogle.com/
* mentors: for bulk uploading tasks see steps [https://wiki.osgeo.org/wiki/Google_Code_In_2017_Tasks#Bulk_Uploading_Tasks here]
+
* see the archive of OSGeo's tasks from the 2017 contest: https://codein.withgoogle.com/archive/2017/organization/5168183002529792/task/
 +
* mentors: for bulk uploading tasks see steps [https://wiki.osgeo.org/wiki/Google_Code_In_2018_Tasks#Bulk_Uploading_Tasks here]
  
 
= Application =
 
= Application =
  
* our OSGeo application as a mentor organization, see: [[Google Code In 2017 Application]]
+
* our OSGeo application as a mentor organization, see: [[Google Code In 2018 Application]]
  
 
= Kickoff (virtual) meeting =
 
= Kickoff (virtual) meeting =
  
* 2017-09-25 at [https://www.timeanddate.com/worldclock/fixedtime.html?year=2017&month=09&day=25&hour=20&min=0 20.00 UTC]
+
* 2018-09-13 at [https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=09&day=13&hour=16&min=0 16.00 UTC]
 
* On IRC in the '''#osgeo-gsoc''' channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])
 
* On IRC in the '''#osgeo-gsoc''' channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])
 
* agenda:
 
* agenda:
** discuss ideas for tasks for the students
+
** discuss ideas for tasks for the students (we need 25 tasks minimum for the application due 17 Sept)
 
** plan to share mentor invites to all OSGeo projects
 
** plan to share mentor invites to all OSGeo projects
** Collect questions to discuss with other mentor orgs at mentor summit
 
  
= Q&A =
+
= Lessons Learned =
 
 
Adrien Destugues (PulkoMandy) mentor for Haiku has replied to some of our questions:
 
  
'''Q''': It is not clear to me if it's possible to use more than one bug tracker or we must use the osgeo tracker for all the projects <libravatar email="diregola@gmail.com"/>
+
* [https://wiki.osgeo.org/wiki/Google_Code_In_2018_Lessons_Learned 2018], [https://wiki.osgeo.org/wiki/Google_Code_In_2017_Lessons_Learned 2017]
  
'''A''': You don't need a single bugtracker. You will have to import your tasks into the dedicated GCI website, and student work from that. The goal is that they learn how to find their way in your project and GSoC in general. In the case of Haiku, some tasks involve the OS itself (with a dedicated bugtracker), some involve contributing to existing projects (on github, for example), and some tasks are about writing an application from scratch so there isn't even a bugtracker to start with
+
= Mentor Representation at the Grand Prize Winners Trip =
  
'''Q''': The [https://developers.google.com/open-source/gci/how-it-works how it works] page doesn't mention how the word of this gets out to students, or does Google handle that?? How is promotion to students handled?? <libravatar email="jmckenna@gatewaygeomatics.com"/>
+
* 1 mentor will represent OSGeo at the GCI Grand Prize Winners trip on June 24-27, 2019 (more information on the [https://sites.google.com/view/2018-grand-prize-trip/home trip site]
 +
* a travel stipend of 2200 USD will be available for flight & travel costs (Google will pay for 4 nights in hotel)
 +
* Please sign your name below if you are interested to represent OSGeo as a mentor at the GCI trip:
 +
** [[Rahul Chauhan]] <libravatar email="rahulnitsxr@gmail.com"/> (IRC nickname: "rahulworld")
 +
**[[Frikan Erwee]] <libravatar email="ferwee@gmail.com"/> (IRC nickname: "FrikanRw")
 +
**[[User:Cvvergara]] <libravatar email="vicky@georepublic.de"/> (IRC nickname: "cvvergara")
 +
** your name here
  
'''A''': Google handles some of it, students from past years handle some of it, and you can have a task like "make a 20 minute talk about our project and GCI for other students around you" so the students help you spread the word. Of course you can also do your own communication.
+
= Grand Prize Winner Trip Mentor Report =
 +
Every year Google invites the Grand-Prize winners and their parents, and a mentor to it’s headquarters in San Francisco, California for a 4 days trip. I ([[Rahul Chauhan]] (rahulworld)) was offered the opportunity to go and represent OSGeo in the summit and meet these 2 brilliant folks in person. This report covers activities and other things that happened there.
  
'''Q''': Discuss the opportunity to create "virtual environments" for the students to play with, and eventually come up with a patch? For example, for tasks that would otherwise require access to sensitive systems, e.g. SAC, web pages, etc.. <libravatar email="diregola@gmail.com"/>
+
I was visiting Google San Francisco, meeting with the two winner students from Google Code-In as well as the students and mentors from the 14 other organisations participating in GCI.
 +
Our two winning students : Matthew Murzaku from the USA, and Shubham Sharma from India. Both our winners were amazing and did the tasks with great quality.  I am still surprised to see their work at such a young age. I am also hoping to see them as GCI mentors or GSoC students in the future.
  
'''A''': About setting up the environment for building the project: if that part of your project is really complex, providing a preset environment might be a good idea. We went a different way: GCI has "beginner" tasks which are things the students should do first before moving on to other tasks in the project. In our cases, these were something like "get the source, compile it, and add your name to the about box" or even "get the Haiku operating system running, open a text document and put your name in it, then take a screenshot". This allows the students to get points for just getting started with these things. Our documentation tasks also included tasks to write or update pages about setting up the development environment.
+
=== Day 1 (Reception) ===
 +
I met with Matthew and Shubham and the other students and mentors in the Hotel lobby where there was a “meet and greet” reception in the evening. Students were given a list of traits (“Did I ride bike last week”, “can speak 3 or more languages fluently”, etc) and had a few minutes to find as much students and mentors as possible matching the traits. This was a good way for the students to get to know each other and the mentors a bit. We then stayed in the hotel lobby for some discussion or hacking.
  
'''Q''': Is it necessary for the students to pick from different "types" of tasks or they can decide to complete only one type? <libravatar email="diregola@gmail.com"/>
+
=== Day 2 (Full Day at Google headquarters in Mountain View) ===
 +
This day was special since we were going to explore Googleplex and talk to Google Engineers at Google Cloud office. We were also offered $75 and $150 to mentors and students respectively to buy our choice of Google Merchandise. Students met  with Google employees of their home country and parted to have lunch with them. We had a line up of talks by great folks from Google.
 +
* Recruiting – Lauren Alpizar
 +
* Android OS: Ally Sillins
 +
* Cloud: Ryan Matsumoto
 +
* Chrome OS – Grant Grundler
 +
* Google Assistant – Daniel Myers
 +
* Google TensorFlow – Paige Bailey
 +
We had Dinner at the same office and then head back to the hotel.
  
'''A''': The student can mix types of tasks as they wish. At Haiku we are unfortunately putting a lot more coding tasks than anything else, mostly because that's what we can mentor best.
+
=== Day 3 (Fun Day in San Francisco) ===
 +
Probably the day most of us would remember. We had option to select one of Segway tour or cable car tour. We split into 2 groups for different activities. I Selected the Segway tour. We later met for lunch in a park by the sea, and boarded the bus once again to visit the Golden Gate bridge. The day ended with a Yacht course across the bay, and we could enjoy a beautiful view of San Francisco from there.
  
'''Q''': When is the deadline to prepare the tasks: Oct 9th (Open source organizations can apply to be mentoring organizations) or Nov 28th (Contest opens for entries by student participants)? What is the minimum number of tasks we need to get ready by the deadline?  <libravatar email="diregola@gmail.com"/>
+
=== Day 4 (Closing reception in Google SF office) ===
 +
On the last day, we had to go the office a bit early. We had breakfast in the office itself followed by the award ceremony (to grand prize winners). We were given 4 minutes per org time to share something if we wished. A lot of students shared their experience with GCI. we shared a little intro on OSGeo projects and my GCI experience as mentor and Metthew shared his favourite task experience. We had lunch after than and meanwhile a video crew was taking interview of people who signed up for it. I and Matthew went for video interview. We had left the office by 3pm after taking a lot of pictures in front of the San Francisco – Oakland bridge.
  
'''A''': The deadline for tasks is, AFAIK, just before the contest opens to students. In fact you can continue adding new tasks to the contest after it opens and all the way until january, to keep the students busy. However, be prepared to have a few hundred tasks ready when the contest opens.  
+
=== People who made this possible ===
 +
Thanks to every student who participated. Everyone of you were amazing and I hope to see you all.
 +
Thanks to [[Victoria Rautenbach]], [[Jeff McKenna]] and Michael for being there when needed, and keeping the conversation alive. A very special thanks to [[Victoria Rautenbach]] for being the backbone of this. Of course all the mentors, Thank you for giving all the time and I hope to be a part of this along with all of you in the coming years.
  
'''Q''': How many mentors do other organizations have (to be on the safe side and not underestimate the work load)? <libravatar email="diregola@gmail.com"/>
+
= 2017 pages =
 
 
'''A''': I don't remember the exact number of mentors, but I'd say about 10 to 12 is a minimum. Expect hundreds of students trying to complete tasks, lot of activity on your IRC channel and other communication mediums. It always feels strange to us when things come back to their normal quiet state after GCI ends.I have started to work on a tool to edit Haiku tasks. You may not find it of much use as it runs only in the Haiku operating system. However, alongside it is a JSON file with our tasks from the 2016 edition. This can give you an idea of the number of tasks and their contents: https://github.com/pulkomandy/gcitool
 
 
 
 
 
= Open questions =
 
 
 
* Add yours
 
 
 
= Insights from other orgs =
 
 
 
Tim Abbot from the Zulip project says:
 
 
 
The Zulip project did GCI for the first time last year, and we learned basically everything we needed to know at the mentor summit GCI session.
 
If you're spending time on preparation in advance of that, I'd encourage you to focus on a few things:
 
  * Recruiting volunteers to help the students; we had over 30 people organized in 4-hour shifts to provide continuous coverage.
 
  * Writing really good developer onboarding documentation, and testing it on inexperienced programmers.
 
  * Creating a few really polished starter tasks (e.g. we had one that was basically "figure out how to do manual and automatic testing in Zulip, including writing a simple unit test"
 
  * Planning out some larger categories of tasks (e.g. where you want 15 similar things done) that you can write really good guides for.
 
 
 
See more insights in the summary about GCI from Mentor summit [[Google_Summer_of_Code_2017_Mentor_Summit#Report_from_Margherita_Di_Leo | report]]
 
 
 
= Lessons Learned =
 
  
* see https://wiki.osgeo.org/wiki/Google_Code_In_2017_Lessons_Learned
+
* see https://wiki.osgeo.org/wiki/Google_Code_In_2017
  
 
[[Category:Google Code In]]
 
[[Category:Google Code In]]

Latest revision as of 03:42, 11 August 2019

GCI-logo.jpg @ Osgeo-logo.png

Top 5 OSGeo students from the GCI 2018 contest

Central page for administering OSGeo participation in Google Code In 2018

Background

Timeline

  • Full timeline
  • Sept 7 2018: organizations can start drafting application to be mentoring organizations
  • Sept 17 2018: application deadline (exact time) for mentoring organizations (we should have mentors and tasks by then - we need a minimum of 25 tasks by 17 Sept, but we should aim to have between 150 & 500 tasks in total before the contest begins)
  • Sept 18 2018: Mentoring organizations announced
  • Oct 23 2018: Contest opens for entries by student participants (exact time)
  • Dec 10 2018: Deadline for students to claim new tasks
  • Dec 12 2018: All student work must be submitted; contest ends
  • Dec 13 2018: Mentoring organizations complete all evaluations of students’ work
  • Jan 7 2019: Grand Prize Winners and Finalists announced
  • June (exact dates TBD): Grand Prize Winner’s Trip

Rules

  • Contest rules
    • Ineligible individuals (according to the above rules):
      • a resident of a United States embargoed country, Brazil, Italy, or Quebec (see Google's reasons; link to the Italian law about online contests),
      • ordinarily resident in a United States embargoed country,
      • participating as a Mentor in the 2018 Contest, or
      • otherwise prohibited by applicable export controls and sanctions programs.

Communication

Administrators

  • Jeff McKenna <libravatar email="jmckenna@gatewaygeomatics.com"/> (IRC nickname: "jmckenna")
  • Victoria Rautenbach <libravatar email="victoria.rautenbach@gmail.com"/> (IRC nickname: "vrautenbach")

Contact OSGeo's administrators: gci-admin at osgeo dot org

Interested mentors / volunteers

Recommendations for Students

Tasks

Application

Kickoff (virtual) meeting

  • 2018-09-13 at 16.00 UTC
  • On IRC in the #osgeo-gsoc channel on irc.freenode.net (connect directly in your browser via webchat)
  • agenda:
    • discuss ideas for tasks for the students (we need 25 tasks minimum for the application due 17 Sept)
    • plan to share mentor invites to all OSGeo projects

Lessons Learned

Mentor Representation at the Grand Prize Winners Trip

  • 1 mentor will represent OSGeo at the GCI Grand Prize Winners trip on June 24-27, 2019 (more information on the trip site
  • a travel stipend of 2200 USD will be available for flight & travel costs (Google will pay for 4 nights in hotel)
  • Please sign your name below if you are interested to represent OSGeo as a mentor at the GCI trip:
    • Rahul Chauhan <libravatar email="rahulnitsxr@gmail.com"/> (IRC nickname: "rahulworld")
    • Frikan Erwee <libravatar email="ferwee@gmail.com"/> (IRC nickname: "FrikanRw")
    • User:Cvvergara <libravatar email="vicky@georepublic.de"/> (IRC nickname: "cvvergara")
    • your name here

Grand Prize Winner Trip Mentor Report

Every year Google invites the Grand-Prize winners and their parents, and a mentor to it’s headquarters in San Francisco, California for a 4 days trip. I (Rahul Chauhan (rahulworld)) was offered the opportunity to go and represent OSGeo in the summit and meet these 2 brilliant folks in person. This report covers activities and other things that happened there.

I was visiting Google San Francisco, meeting with the two winner students from Google Code-In as well as the students and mentors from the 14 other organisations participating in GCI. Our two winning students : Matthew Murzaku from the USA, and Shubham Sharma from India. Both our winners were amazing and did the tasks with great quality. I am still surprised to see their work at such a young age. I am also hoping to see them as GCI mentors or GSoC students in the future.

Day 1 (Reception)

I met with Matthew and Shubham and the other students and mentors in the Hotel lobby where there was a “meet and greet” reception in the evening. Students were given a list of traits (“Did I ride bike last week”, “can speak 3 or more languages fluently”, etc) and had a few minutes to find as much students and mentors as possible matching the traits. This was a good way for the students to get to know each other and the mentors a bit. We then stayed in the hotel lobby for some discussion or hacking.

Day 2 (Full Day at Google headquarters in Mountain View)

This day was special since we were going to explore Googleplex and talk to Google Engineers at Google Cloud office. We were also offered $75 and $150 to mentors and students respectively to buy our choice of Google Merchandise. Students met with Google employees of their home country and parted to have lunch with them. We had a line up of talks by great folks from Google.

  • Recruiting – Lauren Alpizar
  • Android OS: Ally Sillins
  • Cloud: Ryan Matsumoto
  • Chrome OS – Grant Grundler
  • Google Assistant – Daniel Myers
  • Google TensorFlow – Paige Bailey

We had Dinner at the same office and then head back to the hotel.

Day 3 (Fun Day in San Francisco)

Probably the day most of us would remember. We had option to select one of Segway tour or cable car tour. We split into 2 groups for different activities. I Selected the Segway tour. We later met for lunch in a park by the sea, and boarded the bus once again to visit the Golden Gate bridge. The day ended with a Yacht course across the bay, and we could enjoy a beautiful view of San Francisco from there.

Day 4 (Closing reception in Google SF office)

On the last day, we had to go the office a bit early. We had breakfast in the office itself followed by the award ceremony (to grand prize winners). We were given 4 minutes per org time to share something if we wished. A lot of students shared their experience with GCI. we shared a little intro on OSGeo projects and my GCI experience as mentor and Metthew shared his favourite task experience. We had lunch after than and meanwhile a video crew was taking interview of people who signed up for it. I and Matthew went for video interview. We had left the office by 3pm after taking a lot of pictures in front of the San Francisco – Oakland bridge.

People who made this possible

Thanks to every student who participated. Everyone of you were amazing and I hope to see you all. Thanks to Victoria Rautenbach, Jeff McKenna and Michael for being there when needed, and keeping the conversation alive. A very special thanks to Victoria Rautenbach for being the backbone of this. Of course all the mentors, Thank you for giving all the time and I hope to be a part of this along with all of you in the coming years.

2017 pages