Difference between revisions of "Google Code-in/2018"

From MusicBrainz Wiki
Jump to navigationJump to search
(→‎General instructions for GCI students: Updating task type names/descriptions from https://developers.google.com/open-source/gci/faq#tasks)
Line 5: Line 5:
   
 
'''Tasks are divided into the following categories:'''
  
'''Tasks are divided into the following categories:'''
−
*Code: Tasks related to writing or refactoring code
 +
* Code: Tasks related to writing or refactoring code
−
*Documentation/Training: Tasks related to creating/editing documents and helping others learn more
 +
* 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
 +
* 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
 +
* 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
 +
* 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.
 
'''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.

Revision as of 09:16, 17 September 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 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.

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

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.
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 No Style/support leader at MusicBrainz, occasional code monkey, 1.5 million edits.
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 Yes 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.
Monkey (Nicolas Pelletier if you must) (@BookBrainz, @GitHub) Mr_Monkey UTC+0200 Yes I'm the new BookBrainz project lead and MetaBrainz design helper, and first time GCI mentor.

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.

Note: Feel free to suggest additional tasks.

Subpages

Retrieved from "https://wiki.musicbrainz.org/index.php?title=Google_Code-in/2018&oldid=72924"