https://wiki.musicbrainz.org/api.php?action=feedcontributions&user=Armalcolite&feedformat=atomMusicBrainz Wiki - User contributions [en]2024-03-29T11:23:40ZUser contributionsMediaWiki 1.39.4https://wiki.musicbrainz.org/index.php?title=Google_Code-in/2016&diff=71202Google Code-in/20162016-11-13T20:31:50Z<p>Armalcolite: /* Mentors */</p>
<hr />
<div>[https://codein.withgoogle.com/ 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. <br />
Check [http://codein.withgoogle.com/tasks/?sp-organization=5413855668731904 MetaBrainz's list of tasks] in Google Code-in. The Google Code-in 2016 contest runs from November 28, 2016 to January 18, 2017 (see the [https://developers.google.com/open-source/gci/timeline full timeline]). MetaBrainz is participating for the second time.<br />
<br />
== General instructions for GCI students ==<br />
<br />
'''Tasks are divided into the following categories:'''<br />
*Code: Tasks related to writing or refactoring code<br />
*Documentation/Training: Tasks related to creating/editing documents and helping others learn more<br />
*Outreach/research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions<br />
*Quality Assurance: Tasks related to testing and ensuring code is of high quality<br />
*User Interface: Tasks related to user experience research or user interface design and interaction<br />
<br />
'''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. <br />
<br />
'''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.<br />
<br />
== Communications ==<br />
<br />
All communications should happen in the public and publicly logged [[Communication/IRC|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.<br />
<br />
== Mentors ==<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
!Name<br />
!IRC Nick<br />
!Timezone<br />
!Org. admin<br />
!Introduction<br />
|-<br />
|[[User:Freso|Freso (Frederik S. Olesen)]] ([[Editor:Freso|@MusicBrainz]], [[BBEditor:23|@BookBrainz]])<br />
|Freso<br />
|UTC+0100<br />
|Yes<br />
|Official MetaBrainz Community Manager (yes, that's his actual job), all-round MetaBrainz knowledge<br />
|-<br />
|[[User:Reosarevok|reosarevok]] ([[Editor:reosarevok|@MusicBrainz]])<br />
|reosarevok <br />
|UTC+0200<br />
|Yes<br />
|Master of [[Style]] and overall MusicBrainz guy; has the no. 1 number of applied edits to MusicBrainz of all time!<br />
|-<br />
|[[User:Gentlecat|Roman Tsukanov]] ([[Editor:Gentlecat|@MusicBrainz]])<br />
|Gentlecat <br />
|UTC+0100<br />
|Yes<br />
|One of the primary developers of CritiqueBrainz, AcousticBrainz, and the MetaBrainz and ListenBrainz websites in addition to being one of the official (ie., paid) MusicBrainz developers.<br />
|-<br />
|[[User:D4rkie|Mihai "d4rkie" Spinei]] ([[Editor:D4RK-PH0ENiX|@MusicBrainz]])<br />
|Nyanko-sensei / D4RK-PH0ENiX <br />
|UTC+0900<br />
|No<br />
|Occasional editor, mainly editing Japanese artists. <br />
|-<br />
|[[User:asampson|sampsyo]] ([https://musicbrainz.org/user/Adrian%20Sampson @MusicBrainz])<br />
|sampsyo <br />
|UTC-0800<br />
|Yes<br />
|Author and primary developer of [http://beets.radbox.org/ beets] and will mostly mentor tasks related to this.<br />
|-<br />
|[[User:LordSputnik|Ben Ockmore]] ([[BBEditor:4|@BookBrainz]], [[Editor:LordSputnik|@MusicBrainz]])<br />
|LordSputnik <br />
|UTC+0000<br />
|Yes<br />
|Lead developer of BookBrainz, with experience of Node.js, Python, beets and mutagen. Started out editing MusicBrainz.<br />
|-<br />
|[[User:Leftmostcat|Sean Burke]] ([[BBEditor:2|@BookBrainz]], [https://musicbrainz.org/user/Leftmost%20Cat @MusicBrainz])<br />
|Leftmost <br />
|UTC-0700<br />
|Yes<br />
|Also lead developer of BookBrainz, contributing developer for MusicBrainz.<br />
|-<br />
|[[User:Caroline-g|Caroline Gschwend]] ([[Editor:caroline-g|@MusicBrainz]])<br />
|gcilou<br />
|UTC-0500<br />
|No<br />
|MetaBrainz Grand Prize Winner of Google Code-in 2015.<br />
|-<br />
|Ohm Patel ([[Editor:opatel99|@MusicBrainz]])<br />
|opatel99<br />
|UTC-0500<br />
|No<br />
|MetaBrainz Grand Prize Winner of Google Code-in 2015.<br />
|-<br />
|Pinkesh Badjatiya ([[Editor:armalcolite|@MusicBrainz]])<br />
|armalcolite<br />
|UTC+0530<br />
|No<br />
|Google Summer Of Code 2016 participant<br />
|}<br />
<br />
{{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.}}<br />
<br />
{{note|Feel free to [[Google Code-in/2016/Task suggestions|suggest additional tasks]].}}<br />
<br />
== Subpages ==<br />
<br />
{{Special:Prefixindex/Google Code-in/}}</div>Armalcolitehttps://wiki.musicbrainz.org/index.php?title=Google_Code-in/2015/Task_suggestions&diff=71103Google Code-in/2015/Task suggestions2016-10-20T17:57:38Z<p>Armalcolite: /* ListenBrainz */</p>
<hr />
<div>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.<br />
<br />
* [https://developers.google.com/open-source/gci/resources/getting-started#you_can_contribute_without_being_a_coder "You can contribute without being a coder!"]<br />
* [https://developers.google.com/open-source/gci/faq#tasks "Tasks", GCI FAQ entry]<br />
* [https://developers.google.com/open-source/gci/resources/example-tasks Example tasks from previous GCI's]<br />
<br />
{{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)}}<br />
<br />
== General ==<br />
; Create GCI Student landing page (D/T)<br />
<br />
; QA tasks in all projects (QA; pos. O/R)<br />
: "As a new user, try to do X and let us know what you found confusing or too complicated".<br />
<br />
; Give a presentation to your class about {Meta,Music,Book,Listen,Acoustic,Critique}Brainz (O/R)<br />
: Either about the collection of projects, or about a specific project.<br />
<br />
; Make an infographic explaining how the various *Brainz are connected/related (O/R)<br />
<br />
; Organise an edit sprint (O/R)<br />
<br />
; Make a poster for use when organising possible edit sprints (O/R)<br />
<br />
; Update (outdated) wikipages<br />
<br />
== MusicBrainz ==<br />
<br />
===Wiki / Docs (D/T)===<br />
*[[jira:MBS-6516]] MusicBrainz Programming Guide<br />
*[[jira:MBS-5307]] Web Service (ws/2) Documentation<br />
*[[jira:MBS-8659]] Wikidocs - incorporate wiki categories (D/T; CODE)<br />
*How to create reports<br />
*How to create a ticket in the bug tracker<br />
<br />
;Create a glossary template (wikipedia has some good ones)<br />
<br />
; Make a (screencast) video explaining how to do X (D/T; O/R)<br />
: X = add release, add artist, add work, edit release, ...<br />
<br />
; <s>Create a user with as complete information as possible, report any oddities (QA; O/R?; UI?; beginner)</s><br />
: Fill out at last location, languages, and bio. Preferably also the other information.<br />
: Oddities could include: bad translations, errors, something is non-intuitive, ...<br />
<br />
<br />
<br />
===Icon-related tickets (designing/displaying) (UI; CODE)===<br />
: 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).<br />
* '''[[jira:MBS-8000]]''' - Improve interface icons for better support of higher pixel density displays (UI)<br />
* '''[[jira:MBS-4644]]''' - Indicate which releases have CAA art in listings (UI; CODE)<br />
* '''[[jira:MBS-3491]]''' - Indicators for collection items (UI; CODE)<br />
* <s>'''[[jira:MBS-8625]]''' - Add data quality icons (UI; CODE)</s> (added design only so far)<br />
* '''[[jira:MBS-6869]]''' - Show video flag when displaying work recordings (UI; CODE)<br />
* '''[[jira:MBS-6898]]''' - Show video flag when displaying performances (UI; CODE)<br />
* <s>'''[[jira:MBS-7070]]''' - Missing icon (small version) for area, place and work (UI; CODE)</s><br />
* '''[[jira:MBS-2421]]''' - Small icon near recording / work / release / artist / ... names to distinguish them (depends on 7070 and ideally on the following three) (UI; CODE)<br />
* <s>'''[[jira:MBS-8626]]''' - Add an icon for instruments (UI; CODE)</s><br />
* <s>'''[[jira:MBS-8627]]''' - Add an icon for events (UI; CODE)</s><br />
* <s>'''[[jira:MBS-8628]]''' - Add an icon for areas (UI; CODE)</s><br />
* <s>'''[[jira:MBS-1352]]''' - Different icon for Unknown/Person/Group on Artist pages (UI; CODE)</s><br />
<br />
; Sidebar icon updating<br />
* <s>'''[[jira:MBS-8565]]''' - Update the Discogs logo used in the sidebar (UI; CODE)</s><br />
* <s>'''[[jira:MBS-8574]]''' - Update the Google+ logo used in the sidebar (UI; CODE)</s><br />
<br />
== MusicBrainz Picard ==<br />
<br />
; Make a (screencast) video explaining how to do X (D/T; O/R)<br />
: X = add release, add artist, add work, edit release, ...<br />
<br />
; [[jira:PICARD-22]] (CODE; UI)<br />
: Link to Picard Scripting page under 'File Naming'<br />
<br />
; [[jira:PICARD-24]] (UI; pos. CODE)<br />
: Red/Green indication icons difficult to read for colour blind users<br />
<br />
; [[jira:PICARD-114]] (CODE; UI)<br />
: Link to documention for file naming in preferences<br />
<br />
; [[jira:PICARD-226]] (CODE; poss. UI)<br />
: Automatic clustering<br />
<br />
; [[jira:PICARD-692]] (CODE; UI)<br />
: "Play File" button should be renamed to "Open in Player"<br />
<br />
; [[jira:PICARD-717]] (CODE; beginner)<br />
: Picard default name files script refinement<br />
<br />
; [[jira:PICARD-756]] (CODE; UI)<br />
: MusicBrainz/AcoustID entities should be hyperlinked in Picard<br />
<br />
== CritiqueBrainz ==<br />
<br />
; Add and publish review for your favourite album and note any issues (D/T; O/R; QA?)<br />
: Non-unique task. Split up in multiple tasks?<br />
<br />
* <s>'''[[jira:CB-192]]''' - Add link to CoverArtArchive on /artist and /release-group pages (CODE; UI)</s><br />
* <s>'''[[jira:CB-188]]''' - Translation of "CritiqueBrainz is a repository for..." missing (CODE; QA)</s><br />
* <s>'''[[jira:CB-186]]''' - Showing placeholder cover art image for events (UI; CODE)</s><br />
* <s>'''[[jira:CB-184]]''' - No good way to tell which entity type review is associated with (UI; CODE)</s><br />
* <s>'''[[jira:CB-179]]''' - Hidden reviews shouldn't be included in public data dumps (CODE; QA)</s><br />
* <s>'''[[jira:CB-172]]''' - "Notice! Please sign in to access this page" looks weird (UI; CODE)</s><br />
* <s>'''[[jira:CB-171]]''' - Mapping page fails to load if Spotify doesn't return info about an album (CODE; QA)</s><br />
* <s>'''[[jira:CB-163]]''' - Add info about compiling styling into installation instructions (D/T)</s><br />
* <s>'''[[jira:CB-160]]''' - Add a note that will warn users that drafts are not private (UI; CODE)</s><br />
* <s>'''[[jira:CB-146]]''' - Add embedded player into review editor (UI; CODE)</s><br />
* <s>'''[[jira:CB-134]]''' - Show more information about Spotify albums on search page for matching (UI; CODE)</s><br />
* <s>'''[[jira:CB-128]]''' - Web API documentation should have usage examples (D/T)</s><br />
* <s>'''[[jira:CB-123]]''' - Display review language (UI; CODE)</s><br />
* '''[[jira:CB-117]]''' - Use "identicon" Gravatar instead of "mystery-man" for users without email address (UI?; CODE?)<br />
* <s>'''[[jira:CB-114]]''' - Make review classes less confusing (D/T?; UI?; CODE?)</s><br />
* <s>'''[[jira:CB-111]]''' - Make language selector more visible (UI; CODE)</s><br />
<br />
== ListenBrainz ==<br />
<br />
; Import your Last.FM scrobble history and note any issues and glitches (O/R; QA?)<br />
<br />
* '''[[jira:LB-85]]''' - Username in the profile URL should be case insensitive (CODE; QA)<br />
* '''[[jira:LB-35]]''' - Write API documentation (D/T)<br />
* '''[[jira:LB-102]]''' - Improve the SELECT database query (CODE)<br />
* Use audacious and scrobble the currently playing song and note any issues/glitches and report them if needed. (CODE; QA)<br />
* Add function docstrings explaining the function usage (QA?).<br />
* Create a video on how to setup ListenBrainz and use it to scrobble listens.<br />
* Create a list of audio players that can be used(can be tweaked) to scrobble listens to listenbrainz (Just like audacious). (O/R)<br />
<br />
== Cover Art Archive ==<br />
<br />
; [[jira:CAA-79]] (CODE; beginner)<br />
: Finish https://github.com/metabrainz/coverart_redirect/pull/14<br />
: *Very* small! #Python #Git<br />
<br />
== BookBrainz ==<br />
* <strike>'''[[jira:BB-52]]''' - Improve button layout (U, C)</strike><br />
* <strike>'''[[jira:BB-101]]''' - Alias adding should have a button to guess sortname (C)</strike><br />
* <strike>'''[[jira:BB-87]]''' - Support for deprecated relationships (C)</strike><br />
* <strike>'''[[jira:BB-134]]''' - Dynamic default alias implementation (C, U)</strike><br />
* <strike>'''[[jira:BB-135]]''' - Create Calibre plugin to pull metadata by BBID (R, C)</strike><br />
* <strike>'''[[jira:BB-136]]''' - Create Calibre plugin to search BookBrainz with existing/user-input metadata (R, C)</strike><br />
* <strike>'''[[jira:BB-137]]''' - Integrate Bootswatch Cosmo UI theme with site (R, U, C)</strike><br />
* <strike>'''[[jira:BB-138]]''' - Create alias style guidelines (D, R)</strike><br />
* Tests<br />
* Material UI<br />
* Reactification<br />
* User scripts<br />
<br />
== 3rd party projects ==<br />
<br />
=== [http://beets.radbox.org/ beets] ===<br />
<br />
; https://github.com/sampsyo/beets/issues/1629 (CODE)<br />
: Add an AcousticBrainz plugin, part 1 (easy): Retrieve AB information based on a recording MBID.<br />
<br />
; https://github.com/sampsyo/beets/issues/1629 (CODE)<br />
: Add an AcousticBrainz plugin, part 2 (medium): Perform AB extraction and submission (like abzsubmit).<br />
<br />
; https://github.com/sampsyo/beets/issues/1719 (CODE)<br />
: Add a new ListenBrainz plugin to fetch play data.<br />
<br />
; https://github.com/sampsyo/beets/issues/1547 (CODE)<br />
: Fetch a large batch of new MusicBrainz data by refactoring the way beets stores source data to make it more flexible.<br />
<br />
; https://github.com/sampsyo/beets/issues/1234 (CODE)<br />
: Tolerate MusicBrainz recording ID changes when updating metadata.<br />
<br />
; https://github.com/sampsyo/beets/issues/1089 https://github.com/sampsyo/beets/issues/1210 (CODE)<br />
: Ignore video and silence tracks identified by MusicBrainz when searching for missing tracks.<br />
<br />
; https://github.com/sampsyo/beets/issues/654 (CODE)<br />
: Use MusicBrainz "pseudo-releases" to get transliterated metadata.<br />
<br />
; https://github.com/sampsyo/beets/issues/216 (CODE)<br />
: Use MusicBrainz OAuth instead of storing username and password in the config file.<br />
<br />
; https://github.com/sampsyo/beets/issues/406 (CODE)<br />
: Fetch and store the musicbrainz_releasetrackid in beets.<br />
<br />
Document the workflow for submitting your carefully-crafted beets metadata to MusicBrainz.<br />
(D/T)<br />
<br />
Write a post for the beets blog about how to "give back" by finding music in your beets library that MusicBrainz doesn't have yet and submitting new releases. (And the same for submitting cover art that you have but the Cover Art Archive doesn't.)<br />
(O/R)<br />
<br />
Try importing your entire music library using beets and keep a log of what it got right, what it got wrong, and what was missing from MusicBrainz altogether.<br />
(QA)</div>Armalcolite