Google Code-in/2015
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. Check MetaBrainz's list of tasks in Google Code-in. The Google Code-in 2015 contest runs from December 07, 2015 to January 27, 2016 (see the full timeline). MetaBrainz is partcipating for the first 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 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 channel for MetaBrainz is #metabrainz and #musicbrainz in the irc.freenode.net 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 | Introduction |
|---|---|---|---|
| Freso (@MusicBrainz, @BookBrainz (org admin) | Freso | UTC+0100 | Official MetaBrainz Community Manager (yes, that's his actual job), all-round MetaBrainz knowledge |
| reosarevok (@MusicBrainz (org admin) | reosarevok | UTC+0200 | Master of Style and overall MusicBrainz guy; has the 2nd most number of applied edits to MusicBrainz of all time! |
| Roman (@MusicBrainz (org admin) | Gentlecat | UTC+0100 | One of the primary developers of CritiqueBrainz, AcousticBrainz, and the MetaBrainz and ListenBrainz websites in addition to being one of the official (ie., paid) MusicBrainz developers. |
| Michael (@MusicBrainz (org admin) | bitmap | UTC-0600 | Senior/lead developer of MusicBrainz; official MusicBrainz developer. |
| Wieland "Mineo" Hoffmann (@MusicBrainz | Mineo | UTC+0100 | Developer of everything that even remotely looks like Python, but mostly Picard. |
| d4rkie/ Mihai (@MusicBrainz | Nyanko-sensei / D4RK-PH0ENiX | UTC+0900 | Occasional editor, mainly editing Japanese artists. |
| David Saunders (@MusicBrainz | drsaunders | UTC-0500 | MusicBrainz editor with the very most accepted edits of all time! Will mostly be mentoring tasks related to MusicBrainz editing. |
| sampsyo (@MusicBrainz | sampsyo | UTC-0800 | Author and primary developer of beets and will mostly mentor tasks related to this. |
| Alex / caller#6 (@MusicBrainz | CallerNo6 | PST (UTC-0800)) | Occasional editor, sometimes involved in Style and documentation. |
| Ben / LordSputnik (@BookBrainz, @MusicBrainz | LordSputnik | UTC+0000 | Lead developer of BookBrainz, with experience of Node.js, Python, beets and mutagen. Started out editing MusicBrainz. |
| Sean / Leftmost (@BookBrainz, @MusicBrainz | Leftmost | UTC-0700 | Also lead developer of BookBrainz, contributing developer for MusicBrainz. |
Note:Mentors are humans who eventually leave their laptops to sleep, work, study... Also they might be in different timezones than you. It could take your mentor(s) up to 36 hours to receive a review of the work that 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(Only for Mentors):Please feel Free to add your task suggestions on http://wiki.musicbrainz.org/Google_Code-in/Task_suggestions
