Google Code-in/2015: Difference between revisions
m (adding link, removing "PST" link from my timezone) |
m (Point task link to 2015 archive of it.) |
||
(5 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
[http://developers.google.com/open-source/gci/ 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. |
[http://developers.google.com/open-source/gci/ 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/archive/2015/organization/5644885180809216/task/ 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 [https://developers.google.com/open-source/gci/timeline timeline]). MetaBrainz is partcipating for the first time. |
||
⚫ | |||
⚫ | |||
'''Tasks are divided into the following categories:''' |
'''Tasks are divided into the following categories:''' |
||
Line 12: | Line 11: | ||
*User Interface: Tasks related to user experience research or user interface design and interaction |
*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. |
'''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. |
||
⚫ | '''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 |
||
== Communications == |
== Communications == |
||
Line 26: | Line 26: | ||
!IRC Nick |
!IRC Nick |
||
!Timezone |
!Timezone |
||
!Org. admin |
|||
!Introduction |
!Introduction |
||
|- |
|- |
||
|[[User:Freso|Freso]] ([[Editor:Freso|@MusicBrainz]], [[BBEditor:23|@BookBrainz]] |
|[[User:Freso|Freso (Frederik S. Olesen)]] ([[Editor:Freso|@MusicBrainz]], [[BBEditor:23|@BookBrainz]]) |
||
|Freso |
|Freso |
||
|UTC+0100 |
|UTC+0100 |
||
|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:Reosarevok|reosarevok]] ([[Editor:reosarevok|@MusicBrainz]] |
|[[User:Reosarevok|reosarevok]] ([[Editor:reosarevok|@MusicBrainz]]) |
||
|reosarevok |
|reosarevok |
||
|UTC+0200 |
|UTC+0200 |
||
|Yes |
|||
|Master of [[Style]] and overall MusicBrainz guy; has the 2nd most number of applied edits to MusicBrainz of all time! |
|Master of [[Style]] and overall MusicBrainz guy; has the 2nd most number of applied edits to MusicBrainz of all time! |
||
|- |
|- |
||
|[[User:Gentlecat|Roman]] ([[Editor:Gentlecat|@MusicBrainz]] |
|[[User:Gentlecat|Roman Tsukanov]] ([[Editor:Gentlecat|@MusicBrainz]]) |
||
|Gentlecat |
|Gentlecat |
||
|UTC+0100 |
|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. |
|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. |
||
|- |
|- |
||
|[[User:Bitmap|Michael]] ([[Editor:Bitmap|@MusicBrainz]] |
|[[User:Bitmap|Michael Wiencek]] ([[Editor:Bitmap|@MusicBrainz]]) |
||
|bitmap |
|bitmap |
||
|UTC-0600 |
|UTC-0600 |
||
|Yes |
|||
|Senior/lead developer of MusicBrainz; official MusicBrainz developer. |
|Senior/lead developer of MusicBrainz; official MusicBrainz developer. |
||
|- |
|- |
||
|[[User:Mineo|Wieland "Mineo" Hoffmann]] ([[Editor:Mineo|@MusicBrainz]] |
|[[User:Mineo|Wieland "Mineo" Hoffmann]] ([[Editor:Mineo|@MusicBrainz]]) |
||
|Mineo |
|Mineo |
||
|UTC+0100 |
|UTC+0100 |
||
|No |
|||
|Developer of everything that even remotely looks like Python, but mostly Picard. |
|Developer of everything that even remotely looks like Python, but mostly Picard. |
||
|- |
|- |
||
|[[User:D4rkie|d4rkie |
|[[User:D4rkie|Mihai "d4rkie" Spinei]] ([[Editor:D4RK-PH0ENiX|@MusicBrainz]]) |
||
|Nyanko-sensei / D4RK-PH0ENiX |
|Nyanko-sensei / D4RK-PH0ENiX |
||
|UTC+0900 |
|UTC+0900 |
||
|No |
|||
|Occasional editor, mainly editing Japanese artists. |
|Occasional editor, mainly editing Japanese artists. |
||
|- |
|- |
||
|[[User:Drsaunde|David Saunders]] ([[Editor:drsaunde|@MusicBrainz]] |
|[[User:Drsaunde|David Saunders]] ([[Editor:drsaunde|@MusicBrainz]]) |
||
|drsaunders |
|drsaunders |
||
|UTC-0500 |
|UTC-0500 |
||
|No |
|||
|MusicBrainz editor with the very most accepted edits of all time! Will mostly be mentoring tasks related to MusicBrainz editing. |
|MusicBrainz editor with the very most accepted edits of all time! Will mostly be mentoring tasks related to MusicBrainz editing. |
||
|- |
|- |
||
|[[User:asampson|sampsyo]] ([https://musicbrainz.org/user/Adrian%20Sampson @MusicBrainz] |
|[[User:asampson|sampsyo]] ([https://musicbrainz.org/user/Adrian%20Sampson @MusicBrainz]) |
||
|sampsyo |
|sampsyo |
||
|UTC-0800 |
|UTC-0800 |
||
|Yes |
|||
|Author and primary developer of [http://beets.radbox.org/ beets] and will mostly mentor tasks related to this. |
|Author and primary developer of [http://beets.radbox.org/ beets] and will mostly mentor tasks related to this. |
||
|- |
|- |
||
|[[User:caller_number_six|Alex / caller#6]] ([https://musicbrainz.org/user/caller%236 @MusicBrainz] |
|[[User:caller_number_six|Alex / caller#6]] ([https://musicbrainz.org/user/caller%236 @MusicBrainz]) |
||
|CallerNo6 |
|CallerNo6 |
||
|UTC-0800 |
|UTC-0800 |
||
|No |
|||
|Occasional editor, sometimes involved in [[Style]] and [[MusicBrainz_Documentation|documentation]]. |
|Occasional editor, sometimes involved in [[Style]] and [[MusicBrainz_Documentation|documentation]]. |
||
|- |
|- |
||
|[[User:LordSputnik|Ben |
|[[User:LordSputnik|Ben Ockmore]] ([[BBEditor:4|@BookBrainz]], [[Editor:LordSputnik|@MusicBrainz]]) |
||
|LordSputnik |
|LordSputnik |
||
|UTC+0000 |
|UTC+0000 |
||
|Yes |
|||
|Lead developer of BookBrainz, with experience of Node.js, Python, beets and mutagen. Started out editing MusicBrainz. |
|Lead developer of BookBrainz, with experience of Node.js, Python, beets and mutagen. Started out editing MusicBrainz. |
||
|- |
|- |
||
|[[User:Leftmostcat|Sean |
|[[User:Leftmostcat|Sean Burke]] ([[BBEditor:2|@BookBrainz]], [https://musicbrainz.org/user/Leftmost%20Cat @MusicBrainz]) |
||
|Leftmost |
|Leftmost |
||
|UTC-0700 |
|UTC-0700 |
||
|Yes |
|||
|Also lead developer of BookBrainz, contributing developer for MusicBrainz. |
|Also lead developer of BookBrainz, contributing developer for MusicBrainz. |
||
|} |
|} |
||
{{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/Task suggestions|suggest additional tasks]].}} |
|||
'''Note(Only for Mentors)''':Please feel Free to add your task suggestions on http://wiki.musicbrainz.org/Google_Code-in/Task_suggestions |
|||
== Subpages == |
== Subpages == |
Latest revision as of 14:15, 25 October 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 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 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 2nd most 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. |
Michael Wiencek (@MusicBrainz) | bitmap | UTC-0600 | Yes | Senior/lead developer of MusicBrainz; official MusicBrainz developer. |
Wieland "Mineo" Hoffmann (@MusicBrainz) | Mineo | UTC+0100 | No | Developer of everything that even remotely looks like Python, but mostly Picard. |
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 very 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. |
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