Google Code-in/2017: Difference between revisions
No edit summary |
mNo edit summary |
||
(16 intermediate revisions by 8 users not shown) | |||
Line 38: | Line 38: | ||
|gcilou |
|gcilou |
||
|UTC-0600 |
|UTC-0600 |
||
| |
|Yes |
||
|Google Code-in 2015 Winner from MetaBrainz |
|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]]) |
|[[User:LordSputnik|Ben Ockmore]] ([[Editor:LordSputnik|@MusicBrainz]], [[BBEditor:4|@BookBrainz]]) |
||
|LordSputnik |
|LordSputnik |
||
|UTC+0000 |
|UTC+0000 |
||
| |
|Yes |
||
|BookBrainz Lead Developer. GCI mentor for 2015, 2016. Also knows MusicBrainz. |
|BookBrainz Lead Developer. GCI mentor for 2015, 2016. Also knows MusicBrainz. |
||
|- |
|- |
||
Line 50: | Line 50: | ||
|Leftmost |
|Leftmost |
||
|UTC-0700 |
|UTC-0700 |
||
| |
|No |
||
|BookBrainz lead, ne'er-do-well, once wrote some Perl for MusicBrainz |
|BookBrainz lead, ne'er-do-well, once wrote some Perl for MusicBrainz |
||
|- |
|- |
||
|[[User:CatCat|CatQuest, the Endeavouring Cat!]] ([[Editor:CatCat|@MusicBrainz]], [[BBEditor:16|@BookBrainz]]) |
|[[User:CatCat|CatQuest, the Endeavouring Cat!]] ([[Editor:CatCat|@MusicBrainz]], [[BBEditor:16|@BookBrainz]]) |
||
|CatQuest |
|CatQuest or ZaphodBeeblebrox |
||
|UTC+0200 (always DST) |
|UTC+0200 (always DST) |
||
| |
|No |
||
|Instrument Inserter at musicbrainz, member for 13 years, knows about all kinds of weird stuff. |
|Instrument Inserter at musicbrainz, member for 13 years, knows about all kinds of weird stuff. |
||
|- |
|- |
||
Line 62: | Line 62: | ||
|reosarevok |
|reosarevok |
||
|UTC+0200 |
|UTC+0200 |
||
| |
|No |
||
|Style leader at MusicBrainz, occasional code monkey, 1.5 million edits. |
|Style leader at MusicBrainz, occasional code monkey, 1.5 million edits. |
||
|- |
|- |
||
Line 69: | Line 69: | ||
|UTC+0100 |
|UTC+0100 |
||
|No |
|No |
||
|Whipper developer, will mentor tasks related to whipper |
|[https://github.com/JoeLametta/whipper Whipper] developer, will mentor tasks related to whipper |
||
|- |
|- |
||
|[https://github.com/samj1912 samj1912 (Sambhav Kothari)] |
|[https://github.com/samj1912 samj1912 (Sambhav Kothari)] |
||
Line 81: | Line 81: | ||
|UTC-0400 |
|UTC-0400 |
||
|No |
|No |
||
|Maintainer of beets. |
|Maintainer of [http://beets.io/ beets]. |
||
|- |
|- |
||
|[[User:iliekcomputers|Param Singh (iliekcomputers) (@ListenBrainz |
|[[User:iliekcomputers|Param Singh (iliekcomputers)]] ([https://listenbrainz.org/user/iliekcomputers @ListenBrainz]) |
||
|iliekcomputers |
|iliekcomputers |
||
|UTC+0530 |
|UTC+0530 |
||
|No |
|No |
||
| |
|2017 Google Summer of Code student working on ListenBrainz (and MessyBrainz and other projects). |
||
|- |
|- |
||
|[[User:ferbncode|ferbncode (@CritiqueBrainz |
|[[User:ferbncode|ferbncode]] ([https://critiquebrainz.org/user/bab9d7f9-0b0a-4483-8225-909b94c8a939 @CritiqueBrainz]) |
||
|ferbncode |
|ferbncode |
||
|UTC+0530 |
|UTC+0530 |
||
|No |
|No |
||
| |
|2017 Google Summer of Code student working on CritiqueBrainz. Loves MetaBrainz. |
||
|- |
|- |
||
|[[User:Yvanz|yvanzo]] ([https://github.com/yvanzo @GitHub], [[Editor:yvanzo|@MusicBrainz]]) |
|[[User:Yvanz|yvanzo]] ([https://github.com/yvanzo @GitHub], [[Editor:yvanzo|@MusicBrainz]]) |
||
Line 99: | Line 99: | ||
|UTC+0100 |
|UTC+0100 |
||
|No |
|No |
||
|Software Engineer at MetaBrainz, |
|Software Engineer at MetaBrainz, Co-Maintainer of MusicBrainz Server. |
||
|- |
|- |
||
|[[User:Leo Verto|Leo Verto]] ([[Editor: |
|[[User:Leo Verto|Leo Verto]] ([[Editor:Leo Verto|@MusicBrainz]], [[BBEditor:3|@BookBrainz]]) |
||
|Leo_Verto |
|Leo_Verto |
||
|UTC+ |
|UTC+0100 |
||
|No |
|No |
||
|BookBrainz, SpamBrainz and lots of other stuff. |
|BookBrainz, SpamBrainz and lots of other stuff. |
||
|- |
|- |
||
|[[User: |
|[[User:Arthelon|arthelon (Daniel Hsing)]] ([https://github.com/arthelon @GitHub], [[BBEditor:403|@BookBrainz]]) |
||
|arthelon |
|||
|zas |
|||
|UTC+ |
|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 |
|No |
||
|MusicBrainz editor. Will be mentoring tasks related to MusicBrainz editing. |
|||
|System Administrator at MetaBrainz, Maintainer of Picard and few importers. |
|||
|} |
|||
If you're interesting in being a mentor for the MetaBrainz organisation and you're already [[How to Contribute|an active community member]], contact [[User:Freso|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|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.}} |
Latest revision as of 18:28, 15 March 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 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.
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 |
Caroline Gschwend (@MusicBrainz) | gcilou | UTC-0600 | Yes | Google Code-in 2015 Winner from MetaBrainz, general MetaBrainz knowledge, UX and graphic design, community outreach |
Ben Ockmore (@MusicBrainz, @BookBrainz) | LordSputnik | UTC+0000 | Yes | BookBrainz Lead Developer. GCI mentor for 2015, 2016. Also knows MusicBrainz. |
Sean Burke (@MusicBrainz, @BookBrainz) | Leftmost | UTC-0700 | No | BookBrainz lead, ne'er-do-well, once wrote some Perl for MusicBrainz |
CatQuest, the Endeavouring Cat! (@MusicBrainz, @BookBrainz) | CatQuest or ZaphodBeeblebrox | UTC+0200 (always DST) | No | Instrument Inserter at musicbrainz, member for 13 years, knows about all kinds of weird stuff. |
reosarevok (@MusicBrainz, @BookBrainz) | reosarevok | UTC+0200 | No | 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 | 2017 Google Summer of Code student working on ListenBrainz (and MessyBrainz and other projects). |
ferbncode (@CritiqueBrainz) | ferbncode | UTC+0530 | No | 2017 Google Summer of Code student working on CritiqueBrainz. Loves MetaBrainz. |
yvanzo (@GitHub, @MusicBrainz) | yvanzo | UTC+0100 | No | Software Engineer at MetaBrainz, Co-Maintainer of MusicBrainz Server. |
Leo Verto (@MusicBrainz, @BookBrainz) | Leo_Verto | UTC+0100 | No | BookBrainz, SpamBrainz and lots of other stuff. |
arthelon (Daniel Hsing) (@GitHub, @BookBrainz) | arthelon | UTC+0800 | No | 2016 Google Code-in Winner. Full-stack JavaScript developer. |
anshuman73 (Anshuman Agarwal) (@GitHub) | anshuman73 | UTC+0530 | No | Google Code-In 2016 Grand Prize Winner |
Justin W. Flory (@GitHub, @MusicBrainz, @ListenBrainz) | jwf | UTC-0500 | No | ListenBrainz contributor, MusicBrainz metadata contributor, documentation lover. |
Major Lurker (Andrew C) (@MusicBrainz) | MajorLurker | UTC+1100 | No | MusicBrainz editor. Will be mentoring tasks related to MusicBrainz editing. |
David Saunders (@MusicBrainz) | drsaunders | UTC-0500 | No | MusicBrainz editor. Will be mentoring tasks related to MusicBrainz editing. |
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.
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