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

From MusicBrainz Wiki
Jump to navigationJump to search
Line 106: Line 106:
|BookBrainz, SpamBrainz and lots of other stuff.
|BookBrainz, SpamBrainz and lots of other stuff.
|[[User:Zas|zas (Laurent Monin)]] ([https://github.com/zas @GitHub], [[Editor:Zas|@MusicBrainz]])
|System Administrator at MetaBrainz, Maintainer of Picard and few importers.

Revision as of 11:50, 19 October 2017

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 full timeline). MetaBrainz is participating for the third 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.


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.


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.


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
Caroline Gschwend (@MusicBrainz) gcilou UTC-0600 No Google Code-in 2015 Winner from MetaBrainz
Ben Ockmore (@MusicBrainz, @BookBrainz) LordSputnik UTC+0000 BookBrainz Lead Developer. GCI mentor for 2015, 2016. Also knows MusicBrainz.
Sean Burke (@MusicBrainz, @BookBrainz) Leftmost UTC-0700 BookBrainz lead, ne'er-do-well, once wrote some Perl for MusicBrainz
CatQuest, the Endeavouring Cat! (@MusicBrainz, @BookBrainz) CatQuest UTC+0200 (always DST) Instrument Inserter at musicbrainz, member for 13 years, knows about all kinds of weird stuff.
reosarevok (@MusicBrainz, @BookBrainz) reosarevok UTC+0200 Style leader at MusicBrainz, occasional code monkey, 1.5 million edits.
Wizzup (Merlijn Boris Wolf Wajer) Wizzup UTC+0100 No Whipper developer, will mentor tasks related to whipper
samj1912 (Sambhav Kothari) samj1912 UTC+0530 No Software Engineer at MetaBrainz. Maintainer for Picard and SOLR Search.
sampsyo (Adrian Sampson) sampsyo UTC-0400 No Maintainer of beets.
Param Singh (iliekcomputers) (@ListenBrainz) iliekcomputers UTC+0530 No Writes code for ListenBrainz (and MessyBrainz and other projects).
ferbncode (@CritiqueBrainz) ferbncode UTC+0530 No Loves MetaBrainz (and writes code mainly for CritiqueBrainz).
yvanzo (@GitHub, @MusicBrainz) yvanzo UTC+0100 No Software Engineer at MetaBrainz, for MusicBrainz Server.
Leo Verto (@MusicBrainz, @BookBrainz) Leo_Verto UTC+0200 No BookBrainz, SpamBrainz and lots of other stuff.
zas (Laurent Monin) (@GitHub, @MusicBrainz) zas UTC+0100 No System Administrator at MetaBrainz, Maintainer of Picard and few importers.