Google Code-in/2016: Difference between revisions
(→Mentors: Add myself) |
(Update link for GCI 2016 MetaBrainz tasks.) |
||
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. |
||
Check [ |
Check [https://codein.withgoogle.com/tasks/?sp-organization=4794680462016512 MetaBrainz's list of tasks] in Google Code-in. The Google Code-in 2016 contest runs from November 28, 2016 to January 18, 2017 (see the [https://developers.google.com/open-source/gci/timeline full timeline]). MetaBrainz is participating for the second time. |
||
== General instructions for GCI students == |
== General instructions for GCI students == |
Revision as of 18:07, 28 November 2016
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 2016 contest runs from November 28, 2016 to January 18, 2017 (see the full timeline). MetaBrainz is participating for the second 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 |
reosarevok (@MusicBrainz) | reosarevok | UTC+0200 | Yes | Master of Style and overall MusicBrainz guy; has the no. 1 number of applied edits to MusicBrainz of all time! |
Roman Tsukanov (@MusicBrainz) | Gentlecat | UTC+0100 | Yes | 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. |
Mihai "d4rkie" Spinei (@MusicBrainz) | Nyanko-sensei / D4RK-PH0ENiX | UTC+0900 | No | Occasional editor, mainly editing Japanese artists. |
David Saunders (@MusicBrainz) | drsaunders | UTC-0500 | No | MusicBrainz editor with the 2nd most accepted edits of all time! Will mostly be mentoring tasks related to MusicBrainz editing. |
sampsyo (@MusicBrainz) | sampsyo | UTC-0800 | Yes | Author and primary developer of beets and will mostly mentor tasks related to this. |
Alex / caller#6 (@MusicBrainz) | CallerNo6 | UTC-0800 | No | Occasional editor, sometimes involved in Style and documentation. |
Ben Ockmore (@BookBrainz, @MusicBrainz) | LordSputnik | UTC+0000 | Yes | Lead developer of BookBrainz, with experience of Node.js, Python, beets and mutagen. Started out editing MusicBrainz. |
Sean Burke (@BookBrainz, @MusicBrainz) | Leftmost | UTC-0700 | Yes | Also lead developer of BookBrainz, contributing developer for MusicBrainz. |
Caroline Gschwend (@MusicBrainz) | gcilou | UTC-0500 | No | MetaBrainz Grand Prize Winner of Google Code-in 2015. |
Ohm Patel (@MusicBrainz) | opatel99 | UTC-0500 | No | MetaBrainz Grand Prize Winner of Google Code-in 2015. |
Pinkesh Badjatiya (@MusicBrainz) | armalcolite | UTC+0530 | No | Google Summer Of Code 2016 participant |
Yvanz (@MusicBrainz) | yvanz | UTC+0100 | No | Occasional editor, translator to French, and contributing developer for MusicBrainz. |
Subpages
- Google Code-in/2015
- Google Code-in/2015/Task suggestions
- Google Code-in/2016
- Google Code-in/2016/Task suggestions
- Google Code-in/2017
- Google Code-in/2017/Task suggestions
- Google Code-in/2018
- Google Code-in/2018/Task suggestions
- Google Code-in/2019
- Google Code-in/Commonly used abbreviations
- Google Code-in/Elements of a CritiqueBrainz Review
- Google Code-in/Making videos
- Google Code-in/Mentoring
- Google Code-in/MusicBrainz editing
- Google Code-in/Releases not in MusicBrainz
- Google Code-in/Wiki Editing