MusicBrainz Summit/13: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
No edit summary
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Summary ==
== Summary ==


MusicBrainz Summit 13 will happen between the 20th and 23rd September, 2013 at Wikimedia Germany in Berlin.
MusicBrainz Summit 13 occurred on the 21st and 22nd of September, 2013 at Wikimedia Germany in Berlin.


'''Quote of the summit:''' "Can you please toss me the broccoli?"
=== Schedule ===


==Sponsors==
People planning to attend should aim to arrive in time for dinner on the 20th (Friday), though it seems that people will arrive mid-day. Plan to return home on the 23rd (Monday), or as late as possible on Sunday if you need to leave earlier.
A big thank you to Google and Spotify for sponsoring the 2013 summit, and to Wikimedia Deutschland for hosting and providing good internet!


== Summit attendees ==
We'll meet all day Saturday and Sunday at Wikimedia Germany at 10:00 -- please see the meal section for details on when group meals will happen.
Special guests:
* Lydia Pintscher from Wikimedia / Wikidata
* Anders Arpteg from Spotify


MusicBrainz community:
=== Meals ===
* CatCat
* fractalizator
* Freso
* ianmcorvidae
* ijabz
* JonnyJD
* kepstin
* LordSputnik
* Mineo
* navap
* nikki
* ocharles
* reosarevok
* ruaok
* warp


== Agenda ==
Meals will be provided for: Breakfast and lunch with be crowd-sourced from the local [http://goo.gl/maps/9OT4F NP-Markt]. We'll send some people to go to buy food for us to eat for breakfast and lunch. We'll at the Wikimedia offices. Detailed information on dinners follows below:

''Friday dinner''

When: 19:00<br/>
Where: [http://www.zsazsaburger.de/ ZsaZsa Burger], Motzstrasse 28 near U-Bahn Nollendorfplatz.<br/>
Notes: We have a reservation for up to 22 people and will be seated in their outdoor tent. They can provide blankets for anyone who needs one -- be prepared to dress a little warmer

''Saturday dinner''

When: 18:30<br/>
Where: [http://www.maxundmoritzberlin.de/ Max & Moritz], Oranienstrasse 162.<br/>
Notes: We must order from their [https://www.dropbox.com/s/2a6rubnnqdzmvrm/Max%20%26%20Mortiz%20Group%20Menu%20-%20German.pdf group menu]. We need to mail them our order around lunch time on Saturday in an effort from them to serve all of us at the same time.


''Sunday dinner''

We'll play this one by ear. Ruaok will lead an expedition to eat at Mustafas, which entails a long wait that is paired with beers form a shop next to Mustafas. This is a quintessential Berlin experience!

If you'd like something less authentic, we'll organize another group of people to go someplace else.

=== Lodging ===

We've rented a flat that has space for 10-12 people at [https://www.airbnb.com/rooms/729062 Weimarische Straße 15] ([http://www.openstreetmap.org/?mlat=52.47844&mlon=13.32423&way=4442078#map=17/52.47844/13.32423 OSM]). We have the flat from Friday 2pm to Monday 11am. If you'd like to stay at the flat, please add yourself to this list:

[[User:RobertKaye|ruaok]], [[User:Ianmcorvidae|ianmcorvidae]], [[User:Nikki|nikki]], [[User:CatCat|CatCat]], [[User:Kepstin|kepstin]], [[User:Mineo|Mineo]], [[User:Reosarevok|reosarevok]], [[User:LordSputnik|LordSputnik]], [[User:Warp|warp]], [[User:PavanChander|navap]], [[User:Freso|Freso]], [[User:OliverCharles|ocharles]]

The flat is '''full'''. If you plan to attend you will need to find other lodgings!

== People confirmed to be attending ==

'''NOTE: We have a limit of 20 people who can attend, based on available capacity at Wikimedia Germany.'''

(times are for Friday/Monday except where otherwise noted)
{| class="wikitable"
{| class="wikitable"
! colspan=2 | Saturday
|-
|-
|11 - 12
! rowspan=2 | !!colspan="2"| Arriving !! colspan="2"| Leaving !! rowspan="2"|Notes
|
Introductions
<br>Setting the agenda
<br>State of the MB
<br>Spotify introduction (Anders Arpteg)
|-
|-
|12 - 1pm
! Time || Details || Time || Details
|
Geordi introduction
<br>External data matching
|-
|-
|1 - 1:30
| [[User:JonnyJD|JonnyJD]] || colspan=5 | (lives in Berlin (Köpenick), I'm basically free Friday to Monday)
|Break
|-
|-
|1:30 - 1:45
| [[User:Fractalizator|fractalizator]] || colspan=5 | (lives in Berlin (Schöneberg))
|Spotify ingestion process
|-
|-
|1:45 - 2:15
| [[User:Hrglgrmpf|hrglgrmpf]] || colspan=5 | (lives in Berlin, can only attend on Friday evening for dinner)
|NES Overview
|-
|-
|2:30 - 2:45
| [[User:Nikki|nikki]] || rowspan=2 | 06:38 || rowspan=2 | DB CNL457 || rowspan=2 | 13:48 || rowspan=2 | DB ICE556 || rowspan=2 | via Berlin Hbf
|Improving UX
|-
|-
|2:45 - 3
| [[User:Ianmcorvidae|ianmcorvidae]]
|Guiding new users (edit visibility, voting, subscriptions, etc.)
|-
|-
|3 - 3:20
| [[User:Reosarevok|reosarevok]] || 10:15 || Air Baltic BT211 || 10:40 || Air Baltic BT212 || via TXL
|Break
|-
|-
|3:20 - 3:30
| [[User:PavanChander|navap]] || 11:15 || Brussels Airlines 2581 || 06:40 || Brussels Airlines 2592 || via TXL
|Artist/label art
|-
|-
|3:30 - 4
| [[User:Kepstin|kepstin]] || rowspan=2 | 11:30 || rowspan=2 | British Airways BA0982 || 11:00 || British Airways BA0991 || via TXL
|
Scrobbling
<br>Acoustic data
|-
|-
|4 - 4:20
| [[User:OliverCharles|ocharles]] || 12:20 || British Airways 983 || via TXL
|Voting
|-
|-
|4:20 - 4:40
| [[User:LordSputnik|LordSputnik]] || 11:35 || EZY5409 || 21:05 || EZY5416 || via SXF
|Break
|-
|-
|4:40 - 5:30
| [[User:RobertKaye|ruaok]] || 12:55 || Lufthansa 168 || 18:40 || Swiss 971 || via TXL
|Genres
|}

{| class="wikitable"
! colspan="2" | Sunday
|-
|-
|10:30 - 10:40
| [[User:Mineo|Mineo]] || 13:32 || DB IC2355 || 12:26 || DB IC2356 || via Berlin Hbf
|Agenda revision
|-
|-
|10:40 - 11
| [[User:ijabz|ijabz]] || 16:20 || EZY6237 || 16:50 || EZY6238 || via SXF
|i18n
|-
|-
|11 - 11:20
| [[User:CatCat|CatCat]] || 20:45 || Ryanair FR8903 || 21:10 (Sun.) || Ryanair FR8904 || via SXF
|Promotion ideas
|-
|-
|11:20 - 11:40
| [[User:Freso|Freso]] || 22:25 || EZY4558 || 07:15 || EZY4553 || via SXF
|DiscIDs
|-
|-
|11:40 - 12:10
| [[User:Warp|warp]] || 22:45 || EZY4568 || 19:35 (Sun.) || EZY4567 || via SXF
|Break
|-
|-
|12:10 - 12:30
| Anders Arpteg (Spotify) || colspan=5 | TBD
|Home page redesign
|-
|12:30 - 12:50
|Series
|-
|12:50 - 1:00
|Elephant IDs
|-
|1 - 2
|Lunch
|-
|2 - 2:05
|Classical
|-
|2:05 - 2:15
|WavePlot
|-
|2:15 - 2:30
|MusicBrainz Audio Player
|-
|2:30 - 5
|
NES & UX breakout sessions
<br>Socializing
|}
|}


== People who might attend ==
* [[User:KRSCuan|KRSCuan]] if my schedule allows
* [[User:Dupuy|Dupuy]] Although I've not been active in MBz for quite some time, I am now living in Berlin, and would love to attend if there's space. We have a large apartment in Wilmersdorf and I might be able to provide accommodations for some participants.
* [https://musicbrainz.org/user/Noobie/ noobie] I'm living in Berlin and will probably pop in for a beer in the evening ( if the weather allows in the park or whatever plans there are for the evening :) )
== Agenda ==


== Discussion notes ==
Saturday 21 September:

=== Saturday ===

==== State of the MB====
*MB is still hosted in California; hosting on autopilot, “when it dies, it dies”. Basic support from hosting folks to keep things running.
*Long term plans are to eventually move hosting away from California
*Online music monetization
**Zoe Keating is an example of an artist making real money online and she publishes her revenue statements
**Artists/labels are using YouTube as a monetization strategy (https://docs.google.com/spreadsheet/ccc?key=0AkasqHkVRM1OdEJFUnhyNFFkZjVSUWxhWGl1dE9lQXc)
**Would be nice to leverage YouTube to build better label relationships

==== Geordi ====
*Development led by Ian
*Geordi is a third party dataset ingester
*Data mappings are created per third party dataset
*Data is then made available at https://geordi.musicbrainz.org for users to complete the ingestion

==== Spotify====
*Spotify uses data from official label sources as well as third party sources
*They would like to explore a (better) relationship with MusicBrainz data
*They would like to have the “perfect music for every moment”


====MusicBottle / User friendliness====
* Genres
*MusicBottle - Freso hasn’t had time to work on it lately, so on hold for now
* DiscIDs
* Viewer-friendly site: [[MusicBottle]], [http://mbjs.kepstin.ca/ mbjs]
*kepstin has been working on an alternative front end http://mbjs.kepstin.ca/. Source code repository at: https://github.com/kepstin/mbjs
* Sub-entities


====Video ====
Sunday 22 September:
*Checkbox to be added to recordings marking them as video as a “stopgap” minimum measure
*Intent is to add a relationship from these “video” recordings to a third party video database


====NES (New Edit System) Overview====
* (add more here)
*Development led by Ollie
*NES introduces a new edit system comprised of a front end that submits to a backend editable web service
*NES will allow bundling multiple edits together (but not unbundling, at least initially)
*Breakout session on Sunday


====Improving UX====
At some point, with no assigned day (yet):
*The intent is not to dumb the site down, but to add improvements to the existing UX
*Proposal: “Fix bits that stick out”
**Locate individual editing features that behave strangely, or don’t “do the right thing” by default, and perform minimal fixes.
*Proposal: “Multiple modes”
**An analogy: with scanning software, you often have a “Simple” mode which lets you scan with some common settings, and “Advanced mode”, where you can specify descreening, colour curves, etc.
*Proposal: “Better defaults and default-hidden advanced features”
**Instead of full modes, just reorder things so simple/important stuff first and possibly hide features that many users might not need (with a preference to always show them)


====Guiding new users====
* Box Sets
*Proposal: Create a music dashboard that lists new users that need help
* Beginner-Friendliness
*Proposal: Create multiple subscription lists
* Promotion
**Having multiple lists narrows the scope of each list and makes it easier to digest
* More visiblility for/work on NES?/NES update
* Videos
* Internationalization (i18n) (including multi-lingual wiki)
* Classical Support
* Official Cross-Platform Awesome MusicBrainz Player
* WavePlot Scanning + Tagging
* How to make voting a less tedious experience and get more people to do it!
* Making Relationships easier to use, add and edit
* Master and Performance Entities (+ relationship inheritance?)
* Geordi update
* mb-style reform
* Homepage Design
* Site Target Audience (analytics?)


====Artist/label art====
See also: [https://docs.google.com/document/d/1wVADHHlKHZr1eQnkpyZrUGVd1NZNJNXZRrqWrzszXGM/ Google Doc with previous unresolved summit topics] (LordSputnik's -- not editable by others)
*Now that CAA has been a success, intent is to expand and also cover artist and label images
*Proposal: Use a whitelist of CC-licensed websites and start displaying the art
**Whitelist: WikiMedia Commons, Flickr, and more
**For Flickr and other API-enabled websites, ModBot will add a comment with the license and where it comes from


====Scrobbling====
== Important things to not forget, but that will be forgotten anyway ==
*Proposal: Set up a scrobbling server under the MetaBrainz umbrella
*The initial API would be last.fm compatible
*Over the long term the intent is to improve the API and build support for it directly into third party apps (eg. players) to increase user base


====Acoustic data====
* Napkins
*Essentia does cool shit! The proposal is to collect data output from it and make it available to whoever wants to use it for recommendation, etc.
*UPF can run it on the research dataset put out by the internet archive as some seed data, and it could potentially be integrated with a tool like Picard/Jaikoz, similar to how AcoustID collection works.
*WavePlot already does similar things and might constitute a starting point for a database of such data


====Voting====
== Public Transportation in Berlin ==
*Intent is to increase the voting being performed in the database
=== From Tegel Airport (TXL) ===
*Previously (~6 years ago) we had an iframe at the top of the page, this resulted in a lot of ‘no’ votes and was seen as an annoyance
Tegel in the north west is the more central of the airports (zone B). There are no train connections, so you will need to take a bus to the city centre. The bus route TXL runs every 6-7 minutes to Berlin Hauptbahnhof and takes about 22 minutes. The bus route X9 runs every 10 minutes to Zoologischer Garten and takes about 20 minutes.
*Proposal: Remove ‘Yes’ votes
*Proposal: Display relevant edit information to improve voting workflow
*Proposal: Add ability to save custom searches


====Genres====
=== From Schönefeld Airport (SXL) ===
*2012 discussion summary:
Schönefeld in the south east is just outside Berlin (zone C). There are two direct train routes to Berlin Hauptbahnhof, the RE7 running hourly at 23 minutes past the hour and the RB14 running hourly around 48 minutes past the hour. Both take about 28 minutes to reach the Hauptbahnhof. There are also buses and S-Bahn trains running more frequently, but they do not connect directly with the Hauptbahnhof and the journey takes about twice as long.
*#Multi level list of genres
*#*Soundunwound solution: “main”, “quite”, “hints of”
*#*2 levels: “main genre”, “sub genre(s)”
*#Flat list of genres
*#*Fixed list to choose from
*#*Free form with autocompletion
*#Genre graph
*Ben’s “genre entity” proposal
**Genres are entered by users as freeform, auto-completed tags
**After reaching a certain threshold, the tag is converted into a “genre entity”
**Displayed genres are comprised of both the tags and genre entities
**Converting a genre tag into a genre entity allows it to have relationships, and a genre entity would have fields for id3/itunes/(spotify?) genre mappings
**Tags can be manually promoted to entities with a vote
**Genre entities can be merged. The title of the merge source becomes a search hint for the merge target
**This would allow things like “Pop-Rock” and “poprock” to be merged and typing either of these as tags would result in the same genre entity being applied to the entity.
*No conclusion here. It might be good to do some genres meetings, because this is a feature we should have and it would be good to have a better plan/timeframe for implementing it.


=== Tickets ===
=== Sunday ===
Tickets for zones A and B cover the whole city area including Tegel Airport, but '''not''' Schönefeld Airport.
A single ticket costs €2.60 and you can travel on the S+U-Bahn trains, RE/RB trains, trams and buses for 2 hours in one direction. A short trip ticket is €1.50 and you can go 3 S+U-Bahn stations or 6 bus stops (without changing buses). A day ticket costs €6.70.


====Internationalization====
For travelling to/from Schönefeld, you need a ticket which includes zone C. A single ticket for zones A+B+C costs €3.20. A day ticket costs €7.20.
*Discussion point: whether to enable translation support on the main site
**Proposal: Enable all languages that are on beta on main
**Proposal: Enable just one language to start
*Discussion held on whether to enable other languages even though all the documentation is all in English
*Consensus reached that waiting for the all the documentation to be translated into other language(s) is not going to work
*Consensus reached that we enable just German (most Germans speak English) and then go from there
*Can we look into translating the wiki? Wikimedia DE has had good experience with Extension:Translate. The documentation team would also like this.


====Promotion ideas====
=== Other information ===
*First impression for new users is lacking (home page needs work)
There is a [http://images.vbb.de/assets/downloads/file/14479.PDF map with the main trains] (S-Bahn + U-Bahn). You can search for [http://fahrinfo.vbb.de/bin/query.exe/en times and routes].
*Developer awareness can be raised by promoting MB-aware apps such as those created as a part of Music Hack Day
*Build a promotion-oriented community of users to coordinate promotional releases (reddit posts, social media, etc.), collaborate via a new mailing list
*A possible Summer of Code project is to create a visually pleasing statistics page similar to VGMdb


====DiscIDs====
Some of the main trains also run (quite frequently) [http://www.bvg.de/index.php/de/binaries/asset/download/21113/file/1-1 in the night]. To other places you can get with night busses (starting with N). If you feel lost, try to find out where you are and call a taxi at +4930202020.
*Different ideas discussed:
**DiscIDs prevent a few useful edge cases like pre-gap tracks and correct tracklists for certain VideoCDs.
**But they’re also used a lot by rippers/taggers, so we cannot just get rid of them.
*Decision reached that we look at our DiscID usage statistics and then revisit this topic
*There is a follow-up in [[User:JonnyJD/DiscID]] with details.


====Home page redesign ideas====
For the trains, you should buy your tickets up front at the station from the ticket machine and then stamp it to validate it in one of the stamping devices (which will probably be next to the ticket machines). On buses you can also buy tickets when entering. Tickets are only checked randomly and not when entering stations or trains (you are supposed to show your ticket when entering a bus).
*short desc/tagline
**"an open music encyclopedia"?
*divide people into categories in as few words as possible.
**general users / people who want to tag
**artists / labels
**devs
*show coverart
*show “recent activity” in an activity steam
*very basic stats
*highlight search bar?


====Series====
[http://en.wikivoyage.org/wiki/Berlin Wikivoyage] has a relatively well-populated page on Berlin as well, though much of the information duplicates the above.
*Consensus that everyone wants series support
**New entity should be created with
***Title
***Sub entities (see proposals below)
***Relationships to labels, artists
***Dates derived from contents
***Ordering of sub entities is optional
*Consensus split on what can be put into a series
**Proposal: Just release groups
**Proposal: Either release groups or releases, but not both at the same time
**Proposal: One of the above AND recordings (podcasts being captured via stand alone recordings)
*Motion carried to prototype and test the workability of a series entity that contains just release groups


=== TL;DR ===
====Elephant IDs====
* aka adding track IDs into music files
*Motion carried to add the MusicBrainz Track ID into a tag called "musicbrainz_releasetrackid"


====Classical====
Use [http://www.bvg.de/index.php/en/index.html BVG.de (English version)] to plan you route. Locations like "Tegel Airport" are also supported.
*Consensus reached that classical discussion requires a separate summit
*Further discussion tabled


====WavePlot====
Don't trust [https://maps.google.com/ Google Maps]! It supports only S-Bahn and regional trains, and most of the time says "take a taxi, take a train, take a taxi".
*Development on WavePlot led by Ben
*WavePlot is a system for making images of audio files and extracting data from then.
*Future work will be improving integration with existing tools and adding features.


====MusicBrainz Audio Player====
''Update'': Google Maps should also work starting from the 3rd of September.
*Consensus reached that the optimal audio player is the MusicBrainz website itself
*Proposal is to further develop keptsin’s MBJS and then integrate either a third party streaming service, a web based player, or a desktop player
*Consensus reached that an optimal player also needs to be accessible/usable entirely offline.

Latest revision as of 19:19, 1 June 2014

Summary

MusicBrainz Summit 13 occurred on the 21st and 22nd of September, 2013 at Wikimedia Germany in Berlin.

Quote of the summit: "Can you please toss me the broccoli?"

Sponsors

A big thank you to Google and Spotify for sponsoring the 2013 summit, and to Wikimedia Deutschland for hosting and providing good internet!

Summit attendees

Special guests:

  • Lydia Pintscher from Wikimedia / Wikidata
  • Anders Arpteg from Spotify

MusicBrainz community:

  • CatCat
  • fractalizator
  • Freso
  • ianmcorvidae
  • ijabz
  • JonnyJD
  • kepstin
  • LordSputnik
  • Mineo
  • navap
  • nikki
  • ocharles
  • reosarevok
  • ruaok
  • warp

Agenda

Saturday
11 - 12

Introductions
Setting the agenda
State of the MB
Spotify introduction (Anders Arpteg)

12 - 1pm

Geordi introduction
External data matching

1 - 1:30 Break
1:30 - 1:45 Spotify ingestion process
1:45 - 2:15 NES Overview
2:30 - 2:45 Improving UX
2:45 - 3 Guiding new users (edit visibility, voting, subscriptions, etc.)
3 - 3:20 Break
3:20 - 3:30 Artist/label art
3:30 - 4

Scrobbling
Acoustic data

4 - 4:20 Voting
4:20 - 4:40 Break
4:40 - 5:30 Genres
Sunday
10:30 - 10:40 Agenda revision
10:40 - 11 i18n
11 - 11:20 Promotion ideas
11:20 - 11:40 DiscIDs
11:40 - 12:10 Break
12:10 - 12:30 Home page redesign
12:30 - 12:50 Series
12:50 - 1:00 Elephant IDs
1 - 2 Lunch
2 - 2:05 Classical
2:05 - 2:15 WavePlot
2:15 - 2:30 MusicBrainz Audio Player
2:30 - 5

NES & UX breakout sessions
Socializing


Discussion notes

Saturday

State of the MB

  • MB is still hosted in California; hosting on autopilot, “when it dies, it dies”. Basic support from hosting folks to keep things running.
  • Long term plans are to eventually move hosting away from California
  • Online music monetization

Geordi

  • Development led by Ian
  • Geordi is a third party dataset ingester
  • Data mappings are created per third party dataset
  • Data is then made available at https://geordi.musicbrainz.org for users to complete the ingestion

Spotify

  • Spotify uses data from official label sources as well as third party sources
  • They would like to explore a (better) relationship with MusicBrainz data
  • They would like to have the “perfect music for every moment”

MusicBottle / User friendliness

Video

  • Checkbox to be added to recordings marking them as video as a “stopgap” minimum measure
  • Intent is to add a relationship from these “video” recordings to a third party video database

NES (New Edit System) Overview

  • Development led by Ollie
  • NES introduces a new edit system comprised of a front end that submits to a backend editable web service
  • NES will allow bundling multiple edits together (but not unbundling, at least initially)
  • Breakout session on Sunday

Improving UX

  • The intent is not to dumb the site down, but to add improvements to the existing UX
  • Proposal: “Fix bits that stick out”
    • Locate individual editing features that behave strangely, or don’t “do the right thing” by default, and perform minimal fixes.
  • Proposal: “Multiple modes”
    • An analogy: with scanning software, you often have a “Simple” mode which lets you scan with some common settings, and “Advanced mode”, where you can specify descreening, colour curves, etc.
  • Proposal: “Better defaults and default-hidden advanced features”
    • Instead of full modes, just reorder things so simple/important stuff first and possibly hide features that many users might not need (with a preference to always show them)

Guiding new users

  • Proposal: Create a music dashboard that lists new users that need help
  • Proposal: Create multiple subscription lists
    • Having multiple lists narrows the scope of each list and makes it easier to digest

Artist/label art

  • Now that CAA has been a success, intent is to expand and also cover artist and label images
  • Proposal: Use a whitelist of CC-licensed websites and start displaying the art
    • Whitelist: WikiMedia Commons, Flickr, and more
    • For Flickr and other API-enabled websites, ModBot will add a comment with the license and where it comes from

Scrobbling

  • Proposal: Set up a scrobbling server under the MetaBrainz umbrella
  • The initial API would be last.fm compatible
  • Over the long term the intent is to improve the API and build support for it directly into third party apps (eg. players) to increase user base

Acoustic data

  • Essentia does cool shit! The proposal is to collect data output from it and make it available to whoever wants to use it for recommendation, etc.
  • UPF can run it on the research dataset put out by the internet archive as some seed data, and it could potentially be integrated with a tool like Picard/Jaikoz, similar to how AcoustID collection works.
  • WavePlot already does similar things and might constitute a starting point for a database of such data

Voting

  • Intent is to increase the voting being performed in the database
  • Previously (~6 years ago) we had an iframe at the top of the page, this resulted in a lot of ‘no’ votes and was seen as an annoyance
  • Proposal: Remove ‘Yes’ votes
  • Proposal: Display relevant edit information to improve voting workflow
  • Proposal: Add ability to save custom searches

Genres

  • 2012 discussion summary:
    1. Multi level list of genres
      • Soundunwound solution: “main”, “quite”, “hints of”
      • 2 levels: “main genre”, “sub genre(s)”
    2. Flat list of genres
      • Fixed list to choose from
      • Free form with autocompletion
    3. Genre graph
  • Ben’s “genre entity” proposal
    • Genres are entered by users as freeform, auto-completed tags
    • After reaching a certain threshold, the tag is converted into a “genre entity”
    • Displayed genres are comprised of both the tags and genre entities
    • Converting a genre tag into a genre entity allows it to have relationships, and a genre entity would have fields for id3/itunes/(spotify?) genre mappings
    • Tags can be manually promoted to entities with a vote
    • Genre entities can be merged. The title of the merge source becomes a search hint for the merge target
    • This would allow things like “Pop-Rock” and “poprock” to be merged and typing either of these as tags would result in the same genre entity being applied to the entity.
  • No conclusion here. It might be good to do some genres meetings, because this is a feature we should have and it would be good to have a better plan/timeframe for implementing it.

Sunday

Internationalization

  • Discussion point: whether to enable translation support on the main site
    • Proposal: Enable all languages that are on beta on main
    • Proposal: Enable just one language to start
  • Discussion held on whether to enable other languages even though all the documentation is all in English
  • Consensus reached that waiting for the all the documentation to be translated into other language(s) is not going to work
  • Consensus reached that we enable just German (most Germans speak English) and then go from there
  • Can we look into translating the wiki? Wikimedia DE has had good experience with Extension:Translate. The documentation team would also like this.

Promotion ideas

  • First impression for new users is lacking (home page needs work)
  • Developer awareness can be raised by promoting MB-aware apps such as those created as a part of Music Hack Day
  • Build a promotion-oriented community of users to coordinate promotional releases (reddit posts, social media, etc.), collaborate via a new mailing list
  • A possible Summer of Code project is to create a visually pleasing statistics page similar to VGMdb

DiscIDs

  • Different ideas discussed:
    • DiscIDs prevent a few useful edge cases like pre-gap tracks and correct tracklists for certain VideoCDs.
    • But they’re also used a lot by rippers/taggers, so we cannot just get rid of them.
  • Decision reached that we look at our DiscID usage statistics and then revisit this topic
  • There is a follow-up in User:JonnyJD/DiscID with details.

Home page redesign ideas

  • short desc/tagline
    • "an open music encyclopedia"?
  • divide people into categories in as few words as possible.
    • general users / people who want to tag
    • artists / labels
    • devs
  • show coverart
  • show “recent activity” in an activity steam
  • very basic stats
  • highlight search bar?

Series

  • Consensus that everyone wants series support
    • New entity should be created with
      • Title
      • Sub entities (see proposals below)
      • Relationships to labels, artists
      • Dates derived from contents
      • Ordering of sub entities is optional
  • Consensus split on what can be put into a series
    • Proposal: Just release groups
    • Proposal: Either release groups or releases, but not both at the same time
    • Proposal: One of the above AND recordings (podcasts being captured via stand alone recordings)
  • Motion carried to prototype and test the workability of a series entity that contains just release groups

Elephant IDs

  • aka adding track IDs into music files
  • Motion carried to add the MusicBrainz Track ID into a tag called "musicbrainz_releasetrackid"

Classical

  • Consensus reached that classical discussion requires a separate summit
  • Further discussion tabled

WavePlot

  • Development on WavePlot led by Ben
  • WavePlot is a system for making images of audio files and extracting data from then.
  • Future work will be improving integration with existing tools and adding features.

MusicBrainz Audio Player

  • Consensus reached that the optimal audio player is the MusicBrainz website itself
  • Proposal is to further develop keptsin’s MBJS and then integrate either a third party streaming service, a web based player, or a desktop player
  • Consensus reached that an optimal player also needs to be accessible/usable entirely offline.