Monthly Archives: December 2016

New MusicBrainz Virtual Machine released

We’ve finally released a new MusicBrainz virtual machine! This new version has become a lot more automated and is much easier to create and deploy. Hopefully we will be doing monthly releases of the VM from here on out.

lot of things have changed for this new release. If you have used the VM before, you MUST read the instructions again. Before filing a bug or asking us a question, please re-read the documentation first!

Ready to jump in? Read the instructions.

Server update, 2016-12-19

This release features code from GCI student dpmittal, who fixed four of the tickets below under our mentorship. One of those tickets was for displaying the excellent artist icons that former GCI student (and current mentor) gcilou created. Those icons are displayed to the left of the name at the top of artist pages (examples: person, group, choir, orchestra, character, other). Nice work, gcilou and dpmittal! We also have various fixes and improvements thanks to chirlu and Zastai, listed below.

The git tag is v-2016-12-19.

Sub-task

  • [MBS-4159] – Vimeo relationship under the External links section

Bug

  • [MBS-7009] – Exception if replication type is slave but no data in replication_control
  • [MBS-8268] – Ratings (stars) display does not update on its own
  • [MBS-9117] – CD Stub track count not serialized correctly

New Feature

  • [MBS-8359] – Add “Guess Case” function for Event names

Task

  • [MBS-8870] – Add Setlist.fm links to the sidebar

Improvement

  • [MBS-1352] – Different icon for Unknown/Person/Group on Artist pages
  • [MBS-8542] – Blacklist Jaikoz from making barcode edits

Making ticket votes public

The MetaBrainz ticket tracker (which, incidentally, received a long-needed upgrade recently – thanks, Gentlecat!) is an important tool for all of our projects. It collects all kinds of bug reports, feature requests and other tasks to be done and makes sure none are forgotten.

One of its auxiliary features is the possibility for users to vote for a ticket, to indicate which tickets they consider particularly important. (There are only upvotes; you can’t vote against a ticket.) This may factor in when MetaBrainz employees decide on which tickets to tackle next, although there are other factors as well such as the complexity and the impact of a particular issue.

In the past, who voted for which tickets has been private, mostly because that is the default setting in JIRA, the ticket tracker software used. Only administrators can see the list of voters for a ticket; regular users just see the number of votes.

Now, we have decided to change that: In the future, all logged-in users will be able to see who voted for a ticket. This should not be sensitive information; whoever expressed their support for a ticket by commenting on it instead of (or in addition to) voting already was in the public eye. Still, it is a policy change. We’ve therefore decided to wait two weeks before implementing the new privileges, in order to give everybody the chance to remove any votes that they don’t want to be known with. The ticket tracker provides a list of all tickets that you have voted for.

Server update, 2016-12-05

No major changes, but the “Infer track durations from associated recordings” option in the release editor has been removed for being circular and unsound, because recording durations themselves are automatically inferred from tracks. Thanks again to chirlu and yvanz for their code contributions. The git tag is v-2016-12-05.

Bug

  • [MBS-9102] – Age calculation attempted when there is not enough data
  • [MBS-9136] – “Tracks with sequence issues” report is broken
  • [MBS-9138] – Unnecessary double attempt at getting a Commons image
  • [MBS-9140] – NewHost: Name of locale with territory does not replace locale code in UI language selector
  • [MBS-9142] – Artist-Artist relationship editing dialog does not show up in French

Improvement

  • [MBS-7654] – Remove “Infer track durations from associated recordings” option

Google is awesome: How should we spend $5000?

The Google Open Source Programs office is amazing!

In the past few years Google has sponsored our summit where we gather a pile of MusicBrainzers into one room and talk shop (and a bit of play) for a whole weekend. But, due to extenuating circumstances and our move to NewHost, we opted for a much smaller and lower key developer gathering in Barcelona. As a result we didn’t spend much money and I opted to not pester Google to support our summit as they have in the years past.

Then yesterday the lovely Cat Allman from OSPO send us a PO for $5000 and a stern reminder to send an invoice soon. After explaining the situation to Cat, she still felt it was appropriate to collect the money and to “use the money as best serves the project.” 

Wow, thank you!

The question I have, for all of our readers, contributors, editors, hackers and advocates: How do you think we should spend $5000 to best serve MusicBrainz and its sister projects?

I’ll leave it wide open to everyone to chime in — feel free to put suggest anything reasonable and meaningful in the comments. Please do the skip the “send it to me!” type comments. 🙂

Finally, I want to thank Google for its continued support of our projects. Through its annual support of $40,000, Summer of Code, Code-In, the paid data license for its Knowledge Graph and the support of our summit, Google is the biggest supporter of the MetaBrainz Foundation. By far: Google has donated more than $366,000!

THANK YOU GOOGLE. Your support really helps us along!