Google Code-in/2017/Task suggestions

From MusicBrainz Wiki
Jump to navigationJump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

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.


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)

General

MusicBrainz

Wiki / Docs (D/T)

AcousticBrainz

MusicBrainz Picard

CritiqueBrainz

ListenBrainz

  • Import your listens from Last.FM if you have a Last.FM account and note any issues if you find them. (O/R)
  • Use the Simple Last.FM Scrobbler Android App to submit listens to LB for a few hours. (O/R)
  • jira:LB-212: Show the MetaBrainz logo instead of the MusicBrainz logo on the LB website footer. (UI / CODE)
  • jira:LB-213: Add some usage examples to the LB API documentation. (D/T)
  • jira:LB-148: Write tests for the API Compat feature of LB. (CODE / QA)
  • jira:LB-83: Add a list of LB compatible players (with instructions on how to use them) to the LB website. (D/T)
  • jira:LB-85: Make usernames in LB case-insensitive. (CODE)

Cover Art Archive

BookBrainz

3rd party projects

beets

whipper