Universal Music in the UK just launched their Artist Gateway, a site to showcase their artists and to provide lots of detail about their artists. Universal is using MusicBrainz IDs and data throughout their system to give their site the proper structure and links to elsewhere on the net. To launch it, Universal put out a slick video, complete with a plug for MusicBrainz:
This is a huge step for MusicBrainz — in the past the labels didn’t even acknowledge our existence and now they are using our data.
Thanks James Cowdery & crew over at Universal in London!
A potential customer just nudged me about our use of now deprecated CC licenses and a deprecated Public Domain dedication. We should really address these issues and upgrade our data licenses. We are currently using the following licenses:
The move to the CC license version 3 allows us to use the latest and most robust version of the Creative Commons license. If you’d like lots more detail on what this change means, please read the CC version 3 license “brief” explanation.
The CC0 grant improves a number of aspects of our old Public Domain dedication, especially in jurisdictions outside the US. Our current dedication isn’t sufficient to renounce any copyright over the data in some countries. The CC0 grant is an improved version that maximizes the global coverage of our rejection of copyright for our data.
Summary in plain english: We’d like to move to updated, more robust licenses. We are not changing what data is available under which license, nor are we taking away any rights that end users already have.
If you have questions or comments, please post them here. If there are no objections to this change, I will make it effective with our May 15th release.
UPDATE: Fixed an incorrect link that Mike from the Creative Commons pointed out. Thanks Mike!
We’ve talked a bit about our upcoming schema change release, but we hadn’t nailed down the exact date of the release. Now that we’re tangibly close, we’ve settled on the May 15th as the actual release date.
As some of you may know, this summer through Google Summer of Code I’m working on internationalization of musicbrainz-server. As outlined in my proposal, I’m currently looking to find what I call “language liaisons”: folks willing to be the go-to person about a given language for me and other developers.
What’s expected of liaisons:
Willing to be pestered occasionally, by me or other developers, about language-specific concerns: when adding new features, and thus adding new strings, we’d like to be able to ensure nothing’s added that will need to be changed before it can be translated into a given language.
Willing to file bugs for strings already in the database that are untranslatable, should you find them.
Be on the musicbrainz-i18n mailing list; this will be the main venue for organization and communication about i18n issues.
Ideally, to be an active translator for your language – but this isn’t a requirement, because I’d like to get the widest global coverage I can; even if a language doesn’t currently have a translation, we don’t want to unintentionally sabotage future translators with untranslatable strings!
I’ll also be determining a (related) list of “target languages” for the summer, with the intention of releasing translation on musicbrainz.org with these languages at the end of the summer. I’ll consider for inclusion on this list languages that are both in active translation on Transifex and have language liaisons.
If you’re interested in being a language liaison, please contact me: ianmcorvidae (at) musicbrainz (dot) org, editor ianmcorvidae, or ianmcorvidae on IRC, and join the mailing list.