Google Code-in/2017/Task suggestions

From MusicBrainz Wiki
< Google Code-in‎ | 2017
Revision as of 16:24, 21 September 2017 by Caroline-g (talk | contribs) (Created page with "Various small-ish thing that may be good for Google Code-in. Please feel free to add stuff to this page. Take a look at the three links below for inspiration about what kind o...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Various small-ish thing that may be good for Google Code-in. Please feel free to add stuff to this page. Take a look at the three links below for inspiration about what kind of things are eligible for being GCI tasks. "You can contribute without being a coder!" "Tasks", GCI FAQ entry Example tasks from previous GCI's MetaBrainz' tasks in GCI 2016 Note: Please mark in parentheses which of the categories the task belongs to (multiple can be assigned): coding (CODE); documentation/training (D/T); quality assurance (QA); user interface (UI); or outreach/research (O/R) Contents [hide] 1 General 2 MusicBrainz 2.1 Wiki / Docs (D/T) 3 AcousticBrainz 4 MusicBrainz Picard 5 CritiqueBrainz 6 ListenBrainz 7 Cover Art Archive 8 BookBrainz 9 3rd party projects 9.1 beets General[edit]

MusicBrainz[edit] Wiki / Docs (D/T)[edit] AcousticBrainz[edit] MusicBrainz Picard[edit] CritiqueBrainz[edit] ListenBrainz[edit] Cover Art Archive[edit] BookBrainz[edit] 3rd party projects[edit] beets[edit]