Difference between revisions of "Google Code-in/2019"
(Copy of 2018 page)
Revision as of 16:53, 14 October 2019
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 2018 contest runs from October 23, 2018 to December 12, 2018 (see the full timeline). MetaBrainz will hopefully be participating for the fourth 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
- Design: 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.
|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, @BookBrainz)||reosarevok||UTC+0200||Yes||Style/support leader at MusicBrainz, occasional code monkey, 1.5 million edits.|
|Monkey (Nicolas Pelletier if you must) (@BookBrainz, @GitHub)||Mr_Monkey||UTC+0100||Yes||I'm the new BookBrainz project lead and MetaBrainz design helper, and first time GCI mentor.|
|iliekcomputers (Param Singh) (@ListenBrainz, @GitHub)||iliekcomputers||UTC+0530||No||I write code for AcousticBrainz, ListenBrainz and CritiqueBrainz.|
|Chhavi (Chhavi Shrivastava)||chhavi_||UTC+0530||No||All things design: interfaces, t-shirts and stickers.|
|rsh7 (Rashi Sah) (@AcousticBrainz, @Github, (@MusicBrainz)||rsh7||UTC+0530||No||I have been working on AcousticBrainz & I'm a Google Summer of Code 2018 Student.|
|CatQuest, the Endeavouring Cat! (@MusicBrainz, @BookBrainz)||CatQuest, CatCat, KassOtsimine or ZaphodBeeblebrox||UTC+0200||No||Instrument Inserter at MusicBrainz, BB α&β tester, member for 14 years, knows about all kinds of weird stuff.|
|rdswift (Bob Swift) (@MusicBrainz, @ListenBrainz, @Github)||rdswift||UTC-0700||No||Retired engineering manager, some Picard and script programming, first time GCI mentor.|
|Wizzup (Merlijn Boris Wolf Wajer)||Wizzup||UTC+0100||No||Whipper developer, will mentor tasks related to whipper|
|Ben Ockmore (@MusicBrainz, @BookBrainz, @GitHub)||LordSputnik||UTC||No||BookBrainz lead developer for the last 4 years, prior to that, a MusicBrainz editor for 3 years. In the real world, I make silicon designs for processors and SoCs.|
|Leo Verto (@MusicBrainz, @BookBrainz, @Github)||Leo_Verto||UTC+0100||No||I occasionally write code, maintain BrainzBot, and built SpamBrainz for GSOC 2018.|
|Shivam Tripathi (@MusicBrainz, @BookBrainz, @GitHub)||bukwurm||UTC+0530||No||GSoC 2018 @ BookBrainz|
|Suyash Garg (@MusicBrainz, @Github)||ferbncode||UTC+0200||No||I occasionally write code for CritiqueBrainz & AcousticBrainz, GSoC 2017@CritiqueBrainz|
|Major Lurker (Andrew C) (@MusicBrainz)||MajorLurker||UTC+1100||No||MusicBrainz editor. Will be mentoring tasks related to MusicBrainz editing.|
|Philipp Wolfer (outsidecontext) (@MusicBrainz, @Github)||outsidecontext||UTC+0100||No||Picard developer. Will be mentoring tasks related to MusicBrainz Picard.|
If you're interested 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.
- 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