Difference between revisions of "Google Code-in/2018"

From MusicBrainz Wiki
(Copy from [Google Code-in/2017])
 
(Change 2017-isms to 2018-isms)
Line 1: Line 1:
[https://codein.withgoogle.com/ Google Code-in] is a contest to introduce pre-university students (ages 13-17) to the many kinds of contributions that make free and open source software (FOSS) development possible. Students must complete tasks, one at a time. It is sponsored and run by Google.  
+
[https://codein.withgoogle.com/ Google Code-in] is a contest to introduce pre-university students (ages 13–17) to the many kinds of contributions that make free and open source software (FOSS) development possible. Students must complete tasks, one at a time. It is sponsored and run by Google.  
The Google Code-in 2017 contest runs from November 28, 2017 to January 17, 2018 (see the [https://developers.google.com/open-source/gci/timeline full timeline]). MetaBrainz is participating for the third time.
+
The Google Code-in 2018 contest runs from October 23, 2018 to December 12, 2018 (see the [https://developers.google.com/open-source/gci/timeline full timeline]). MetaBrainz will hopefully be participating for the fourth time.
  
 
== General instructions for GCI students ==
 
== General instructions for GCI students ==
Line 34: Line 34:
 
|Yes
 
|Yes
 
|Official MetaBrainz Community Manager (yes, that's his actual job), all-round MetaBrainz knowledge
 
|Official MetaBrainz Community Manager (yes, that's his actual job), all-round MetaBrainz knowledge
|-
 
|[[User:Caroline-g|Caroline Gschwend]] ([[Editor:caroline-g|@MusicBrainz]])
 
|gcilou
 
|UTC-0600
 
|Yes
 
|Google Code-in 2015 Winner from MetaBrainz, general MetaBrainz knowledge, UX and graphic design, community outreach
 
|-
 
|[[User:LordSputnik|Ben Ockmore]] ([[Editor:LordSputnik|@MusicBrainz]], [[BBEditor:4|@BookBrainz]])
 
|LordSputnik
 
|UTC+0000
 
|Yes
 
|BookBrainz Lead Developer. GCI mentor for 2015, 2016. Also knows MusicBrainz.
 
|-
 
|[[User:Leftmostcat|Sean Burke]] ([https://musicbrainz.org/user/Leftmost%20Cat @MusicBrainz], [[BBEditor:2|@BookBrainz]])
 
|Leftmost
 
|UTC-0700
 
|No
 
|BookBrainz lead, ne'er-do-well, once wrote some Perl for MusicBrainz
 
|-
 
|[[User:CatCat|CatQuest, the Endeavouring Cat!]] ([[Editor:CatCat|@MusicBrainz]], [[BBEditor:16|@BookBrainz]])
 
|CatQuest or ZaphodBeeblebrox
 
|UTC+0200 (always DST)
 
|No
 
|Instrument Inserter at musicbrainz, member for 13 years, knows about all kinds of weird stuff.
 
|-
 
|[[User:Reosarevok|reosarevok]] ([[Editor:reosarevok|@MusicBrainz]], [[BBEditor:9|@BookBrainz]])
 
|reosarevok
 
|UTC+0200
 
|No
 
|Style leader at MusicBrainz, occasional code monkey, 1.5 million edits.
 
|-
 
|[[User:Wizzup|Wizzup (Merlijn Boris Wolf Wajer)]]
 
|Wizzup
 
|UTC+0100
 
|No
 
|[https://github.com/JoeLametta/whipper Whipper] developer, will mentor tasks related to whipper
 
|-
 
|[https://github.com/samj1912 samj1912 (Sambhav Kothari)]
 
|samj1912
 
|UTC+0530
 
|No
 
|Software Engineer at MetaBrainz. Maintainer for Picard and SOLR Search.
 
|-
 
|[[User:Asampson|sampsyo (Adrian Sampson)]]
 
|sampsyo
 
|UTC-0400
 
|No
 
|Maintainer of [http://beets.io/ beets].
 
|-
 
|[[User:iliekcomputers|Param Singh (iliekcomputers)]] ([https://listenbrainz.org/user/iliekcomputers @ListenBrainz])
 
|iliekcomputers
 
|UTC+0530
 
|No
 
|2017 Google Summer of Code student working on ListenBrainz (and MessyBrainz and other projects).
 
|-
 
|[[User:ferbncode|ferbncode]] ([https://critiquebrainz.org/user/bab9d7f9-0b0a-4483-8225-909b94c8a939 @CritiqueBrainz])
 
|ferbncode
 
|UTC+0530
 
|No
 
|2017 Google Summer of Code student working on CritiqueBrainz. Loves MetaBrainz.
 
|-
 
|[[User:Yvanz|yvanzo]] ([https://github.com/yvanzo @GitHub], [[Editor:yvanzo|@MusicBrainz]])
 
|yvanzo
 
|UTC+0100
 
|No
 
|Software Engineer at MetaBrainz, Co-Maintainer of MusicBrainz Server.
 
|-
 
|[[User:Leo Verto|Leo Verto]] ([[Editor:Leo Verto|@MusicBrainz]], [[BBEditor:3|@BookBrainz]])
 
|Leo_Verto
 
|UTC+0100
 
|No
 
|BookBrainz, SpamBrainz and lots of other stuff.
 
|-
 
|[[User:Arthelon|arthelon (Daniel Hsing)]] ([https://github.com/arthelon @GitHub], [[BBEditor:403|@BookBrainz]])
 
|arthelon
 
|UTC+0800
 
|No
 
|2016 Google Code-in Winner. Full-stack JavaScript developer.
 
|-
 
|[[User:Anshuman73|anshuman73 (Anshuman Agarwal)]] ([https://github.com/anshuman73 @GitHub])
 
|anshuman73
 
|UTC+0530
 
|No
 
|Google Code-In 2016 Grand Prize Winner
 
|-
 
|[[User:Jflory|Justin W. Flory]] ([https://github.com/jflory7 @GitHub], [[Editor:jflory|@MusicBrainz]], [https://listenbrainz.org/user/jflory @ListenBrainz])
 
|jwf
 
|UTC-0500
 
|No
 
|ListenBrainz contributor, MusicBrainz metadata contributor, documentation lover.
 
|-
 
|[[User:MajorLurker|Major Lurker (Andrew C) ]] ([[Editor:MajorLurker|@MusicBrainz]])
 
|MajorLurker
 
|UTC+1100
 
|No
 
|MusicBrainz editor. Will be mentoring tasks related to MusicBrainz editing.
 
|-
 
|[[User:Drsaunde|David Saunders]] ([[Editor:drsaunde|@MusicBrainz]])
 
|drsaunders
 
|UTC-0500
 
|No
 
|MusicBrainz editor. Will be mentoring tasks related to MusicBrainz editing.
 
 
|}
 
|}
  
Line 142: Line 40:
 
{{note|Mentors are humans who eventually leave their computers to sleep, work, study, etc. and they may also be in a different timezone than you. It could take your mentor(s) up to 36 hours to review the work you have submitted. You should be reasonably patient and should not ask for a review of your work after only a few hours of waiting. Google Code-In is about the quality of your contributions and learning how FOSS development works, not about the number of tasks that you have worked on.}}
 
{{note|Mentors are humans who eventually leave their computers to sleep, work, study, etc. and they may also be in a different timezone than you. It could take your mentor(s) up to 36 hours to review the work you have submitted. You should be reasonably patient and should not ask for a review of your work after only a few hours of waiting. Google Code-In is about the quality of your contributions and learning how FOSS development works, not about the number of tasks that you have worked on.}}
  
{{note|Feel free to [[Google Code-in/2017/Task suggestions|suggest additional tasks]].}}
+
{{note|Feel free to [[Google Code-in/2018/Task suggestions|suggest additional tasks]].}}
  
 
== Subpages ==
 
== Subpages ==
  
 
{{Special:Prefixindex/Google Code-in/}}
 
{{Special:Prefixindex/Google Code-in/}}

Revision as of 06:29, 30 August 2018

Google Code-in is a contest to introduce pre-university students (ages 13–17) to the many kinds of contributions that make free and open source software (FOSS) development possible. Students must complete tasks, one at a time. It is sponsored and run by Google. The Google Code-in 2018 contest runs from October 23, 2018 to December 12, 2018 (see the full timeline). MetaBrainz will hopefully be participating for the fourth time.

General instructions for GCI students

Tasks are divided into the following categories:

  • Code: Tasks related to writing or refactoring code
  • Documentation/Training: Tasks related to creating/editing documents and helping others learn more
  • Outreach/research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
  • Quality Assurance: Tasks related to testing and ensuring code is of high quality
  • User Interface: Tasks related to user experience research or user interface design and interaction

Quality Over Quantity: It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner.

Collaboration: Open source is not just about coding but very much about working with other people to find the best solution. Being a part of the community is an essential part of success in Google Code-in. Mentors like students who worked hard on their projects but also participated on IRC and helped answer questions other students had. IRC channels for MetaBrainz are #metabrainz and #musicbrainz on the Freenode IRC network.

Communications

All communications should happen in the public and publicly logged IRC channels, #metabrainz and #musicbrainz. Private discussions are highly discouraged, unless it's personally sensitive. If you must message someone in private, be sure to ask in public first.

Mentors

Name IRC Nick Timezone Org. admin Introduction
Freso (Frederik S. Olesen) (@MusicBrainz, @BookBrainz) Freso UTC+0100 Yes Official MetaBrainz Community Manager (yes, that's his actual job), all-round MetaBrainz knowledge

If you're interesting in being a mentor for the MetaBrainz organisation and you're already an active community member, contact Freso on IRC. If you're not currently an active member of the MetaBrainz community, read up on How to Contribute to get involved and consider asking next year.

Note: Mentors are humans who eventually leave their computers to sleep, work, study, etc. and they may also be in a different timezone than you. It could take your mentor(s) up to 36 hours to review the work you have submitted. You should be reasonably patient and should not ask for a review of your work after only a few hours of waiting. Google Code-In is about the quality of your contributions and learning how FOSS development works, not about the number of tasks that you have worked on.
Note: Feel free to suggest additional tasks.

Subpages