Google Code-in/2015/Task suggestions: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(→‎General: Add categories.)
(Clarify that it's possible to have multiple categories on a task.)
Line 5: Line 5:
* [https://developers.google.com/open-source/gci/resources/example-tasks Example tasks from previous GCI's]
* [https://developers.google.com/open-source/gci/resources/example-tasks Example tasks from previous GCI's]


{{Note|Please denote in parentheses which of the categories the task belongs to: coding (CODE); documentation/training (D/T); quality assurance (QA); user interface (UI); or outreach/research (O/R)}}
{{Note|Please denote 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 ==
== General ==
; Create GCI Student landing page (D/R)
; Create GCI Student landing page (D/R)


; QA tasks in all projects (QA)
; QA tasks in all projects (QA; pos. D/R)
: "As a new user, try to do X and let us know what you found confusing or too complicated".
: "As a new user, try to do X and let us know what you found confusing or too complicated".



Revision as of 20:28, 10 November 2015

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 denote 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

Create GCI Student landing page (D/R)
QA tasks in all projects (QA; pos. D/R)
"As a new user, try to do X and let us know what you found confusing or too complicated".

MusicBrainz

Make a (screencast) video explaining how to do X
X = add release, add artist, add work, edit release, ...
jira:MBS-8623
Will probably need User:Bitmap or someone to help the student find out where the fix is supposed to be at. #Perl
Icon-related tickets (designing/displaying)
Some of these might involve two different tasks, one to design the icon and one to implement it (in some cases the latter might be a bit too tricky but the former still useful).
  • jira:MBS-8000 - Improve interface icons for better support of higher pixel density displays
  • jira:MBS-4644 - Indicate which releases have CAA art in listings
  • jira:MBS-3491 - Indicators for collection items
  • jira:MBS-8625 - Add data quality icons
  • jira:MBS-6869 - Show video flag when displaying work recordings
  • jira:MBS-6898 - Show video flag when displaying performances
  • jira:MBS-7070 - Missing icon (small version) for area, place and work
  • jira:MBS-2421 - Small icon near recording / work / release / artist / ... names to distinguish them (depends on 7070 and ideally on the following three)
  • jira:MBS-8626 - Add an icon for instruments
  • jira:MBS-8627 - Add an icon for events
  • jira:MBS-8628 - Add an icon for areas
  • jira:MBS-1352 - Different icon for Unknown/Person/Group on Artist pages
Sidebar icon updating

MusicBrainz Picard

Assorted tickets
https://gist.github.com/mineo/0ddf2d3dbb7a05ae8391
jira:PICARD-717

CritiqueBrainz

  • jira:CB-192 - Add link to CoverArtArchive on /artist and /release-group pages
  • jira:CB-188 - Translation of "CritiqueBrainz is a repository for..." missing
  • jira:CB-186 - Showing placeholder cover art image for events
  • jira:CB-184 - No good way to tell which entity type review is associated with
  • jira:CB-179 - Hidden reviews shouldn't be included in public data dumps
  • jira:CB-172 - "Notice! Please sign in to access this page" looks weird
  • jira:CB-171 - Mapping page fails to load if Spotify doesn't return info about an album
  • jira:CB-163 - Add info about compiling styling into installation instructions
  • jira:CB-160 - Add a note that will warn users that drafts are not private
  • jira:CB-154 - Document data dump importing process
  • jira:CB-146 - Add embedded player into review editor
  • jira:CB-134 - Show more information about Spotify albums on search page for matching
  • jira:CB-128 - Web API documentation should have usage examples
  • jira:CB-123 - Display review language
  • jira:CB-117 - Use "identicon" Gravatar instead of "mystery-man" for users without email address
  • jira:CB-114 - Make review classes less confusing
  • jira:CB-111 - Make language selector more visible

ListenBrainz

  • jira:LB-85 - Username in the profile URL should be case insensitive
  • jira:LB-35 - Write API documentation

Cover Art Archive

jira:CAA-79
Finish https://github.com/metabrainz/coverart_redirect/pull/14
*Very* small! #Python

BookBrainz