Looking for short term contract software engineer

MusixMatch would like to have a feature (or two) added to NGS, but I’m dedicated to not piling on more work for the MusicBrainz engineering team. MusixMatch has agreed to pay for the development of these features via paid software engineer and then submit the patch for inclusion into NGS.

If you’re a software engineer and you have experience using Perl and Postgres and are available immediately to hack on some new features to NGS, please send mail to helpwanted at musicbrainz dot org.

Announcing MusicBrainz Server NGS Beta 3: Now live on test!

I’m sorry to say that we’re running a bit behind in bringing you MusicBrainz NGS Beta 3, but we’ve finally managed it!

I am, however, proud to say that we’ve made incredible progress in the last few weeks. Not only are Warp and Acid2 rounding out our features nicely, but with Nikki and Navap backing us up we’ve found/fixed a ton of problems and made countless improvements to the look of the new site. While at times it seems that we’re working on Duke Nukem NGS that seems to never get finished, it is days like today that make me very happy with what we are going to deliver when NGS ships. We’re making sure that the software we deliver at the end of this massive process is solid and will make our users happy. In that sense I am very happy that our users and customers are giving us the time to finish this project properly.

Enough waxing poetic — now for the meaty details of this release! Take a look at the massive change log that shows all the issues we’ve tackled since beta 2. The beta 3 release is available for your testing pleasure on our test server. If you’ve not logged into the test server before, use your normal password from the MB site — the data on test is a little bit old so if your password doesn’t work, try using one that you’ve used a couple of months ago.

This release is solid enough for people to come in and have a serious play. Please come test your favorite features and if you find bugs, please report them to Jira, our bug tracking system. (click on Create Issue in the upper right hand corner). We’ve fixed a ton of bugs already and we’re not afraid to have you report new ones! Beta 3 adds more features and improves many other features, but it is still not feature complete. Our next release, Release Candidate 1 will be feature complete — I hope to set timeframe for this release within a couple of weeks.

And now for some quick notes on areas of NGS that we’ve been focusing on:

  • Edit system: The edit system is now looking stable and fairly complete, though it is still lacking batch operations, which were hoping to get in for beta 3. There is also support for migrating all pre-NGS edit types, though some have display issues. (we’ll be loading new data onto test soon and then we’ll re-run the edit migration script).
  • Web services: The backwards compatible web service (/ws/1) is feature complete up to cd stubs, but everything else should just work (please point tagger applications at test and see what happens!). The new web service (/ws/2) is feature complete except submitting CD Stubs, ISRCs and collections — please take a look at the specification for Web Service Version 2 and see if you can break it!
  • Release editor: The release editor in beta 3 has two major new features. First is the a recordings tab, which allows you to associate recordings with tracks. Second is a preview of your edits on the final tab.
  • CD Stubs: Browsing top CD Stubs and viewing CD Stubs is now working. Submitting/importing CD stubs is not complete yet.
  • Lists (formerly collections): Collections have become a more generic concept of Lists, which allows multiple lists of releases per user. (This was one of our GSoc projects).
  • RDFa: Artist and release pages now contain embedded RDFa! For more details, please see our wiki page for the RDFa feature.

Thank you to everyone who has worked on this release! Things have been a little stressful the past few days as we tried to push as many things out the door as possible, but the results have been quite worthwhile. Now it is time to relax a little before we start charging towards our Release Candidate 1 release. Thanks everyone!

UPDATE: I added a note about the RDFa support.

NGS Beta 3: Delayed

What would a deadline be without a delay? Sadly, we felt that we were not quite ready to unleash beta 3 today. Rather than unleashing software that isn’t ready, we’re opting to delay beta 3.

We’re taking a look at where we stand and we hope to be able to finish it for next week. I’ll post about an update hopefully tomorrow.

MusixMatch becomes our customer!

MusixMatch, a new lyrics start-up company in Bologna, Italy just signed up to be our latest customer!

MusixMatch aims to license lyrics from all over the world (and not just the usual US/western Europe suspects) and aims to make accessing and licensing lyrics much easier than it currently is. I spent three days in June with the whole MusixMatch team to figure out how MusicBrainz and MusixMatch can work together, and we found a number of interesting ways in which we can help each other.

MusixMatch needs to match lyric publisher data to music metadata like the data in MusicBrainz. This matching will enable MusixMatch to instantly license lyrics to anyone who speaks MBIDs or anyone who can match their data to our metadata. And MusicBrainz will benefit from this relationship by being able to show lyrics on MusicBrainz pages, which enriches MusicBrainz and takes us one step further on our road to being a comprehensive music encyclopedia.

However, it should be noted that MusicBrainz is not getting into the lyrics business. We will never store Lyrics in our database since those are copyrighted! We plan to fetch lyrics from the MusixMatch servers to display them on our site. MusixMatch, however, plans to offer our music metadata and lyrics in a package deal once we’ve matched our data and have lyric support on musicbrainz.org.

All of this lyrics work will come after we’ve shipped NGS — until NGS we will not adapt any new features! We are really keeping our focus on delivering NGS as soon as we’re happy with its stability.

Track level Advanced Relationships for NGS

As you may know, in our Next Generation Schema release we are including support for musical Works. Our definition of a Work is a musical composition that will at some point be performed and possibly recorded, in which case it will become a Recording. In the current MusicBrainz implementation we do not have the concept of a Work and a lot of the Advanced Relationships (ARs) we have are muddled between the concept of a Work or a Recording.

This left us with the tricky task of reviewing all track level ARs and prying apart which ARs should be moved to Works and which ones to Recording. Or both! To accomplish this task, Brianfreud had compiled a list of open issues, which Ian McEwen has adopted and nutured. Today we convened an IRC meeting with Nikki, Pete Marsh from the BBC, Ian and myself. If you’re interested in how we reached the decisions we did, please take a look at the chatlog.

Our decisions have been captured in this wiki page — please take a look at it and see if we’ve missed anything or if there is anything you disagree with. If we do not hear any feedback on this topic, we will change our NGS data conversion script to convert the data as decided in this page.

Thanks to Ian, Pete and Nikki for your help in this meeting! And big thanks also go to Murdos for all of your help in steering me towards getting all Works related issues on to the table!

Please welcome our new Style Leader: Nikki

The MusicBrainz Style Leader has a really hard job — this position requires people to to have a thick skin, a deep understanding of MusicBrainz and the patience of a saint. Its a really challenging job! And because of this, people burn out fast and generally abandon their jobs after a while. This has been the pattern for many years for us and its been very frustrating. And now its has happened again: Brian, the Style Leader up til today, has not been responding to me. I’ve not heard anything from him in weeks.

In an effort to try and break out of this cycle, I am going start a new experiment: Make the Style Leader a paid position.

While we have some money in the bank, its not massive amounts of money and the pay for this position reflects just that. Its not a whole lot of money, but I am hoping its enough money to offset the pain of being the Style Leader and will keep the Style Leader engaged over a longer period. With that in mind, I am proud to announce that Nikki will be our next Style Leader and our first paid Style Leader.

Nikki has been tasked to ensure that the style process moves along and is properly documented. Her goal is to drive consensus among the brainerz who participate in the important Style process and to keep proposals on track. Once a proposal’s RFC/RFV periods are up, its Nikki’s job to ensure that the proposal is acted upon by the appropriate people. She should also help to keep the style process evolving as the MusicBrainz style needs evolve.

Thank you for all your hard work Brian! I look forward to working with you more closely Nikki!

BTW: Warp will still be involved in helping Nikki lead the style process, but his focus is on NGS for the time being. We’re very much dedicated to staying focused on delivering NGS as soon as we can.