Looking for a contract programmer for C++/Python work

UPDATE: This position has been filled.

A soon-to-be partner of MusicBrainz is looking for an engineer for contract work. This company is looking for a person who has the following skills:

  1. Strong Python and C++ skills with experience in building applications on Windows, Linux and Mac.
  2. Open source programming experience
  3. Server programming skills a plus
  4. Solr and audio programming experience a plus
  5. Ability to be a self starter, handle task coordination via Skype and IRC.

The work would involve working with MusicBrainz and the partner company. This contract would be full time for 2-5 months, depending on the workload which isn’t very clear yet. After that the contract would taper off to 10-20 hours per week on an ongoing basis. Depending on how main portion of the contract goes, the company may decide to give more hours to the contractor on new projects. The pay for this position is still being determined, but its safe to assume that it would be a fair rate for an engineer based in the US. This engineer can be located anywhere, but the pay is likely to be appropriate for US rates. If you are interested in this position, please send your resume to helpwanted at musicbrainz dot org.

Please take the MusicBrainz Survey!

Jess Hemerly, who is has been studying MusicBrainz as part of a class at UC Berkeley, has devised a survey for MusicBrainz users to get a better understanding of who contributes to MusicBrainz and why. She says:

I’m a researcher at UC Berkeley’s School of Information and a MusicBrainz editor (agreatnotion). I’m interested in how and why people contribute to MusicBrainz and how it can be better. Your participation will help us learn more about you, our community, and how to sustain a successful peer-produced database. The survey takes about 15 minutes, and all personal information—like username and email—will remain confidential. My advisor and I will review and analyze the results and hope to share our analysis with the academic and open source communities. The results will also be made available to the MusicBrainz community.

Take the survey here. The survey will be open for two weeks, until July 23, 2010.

Thank you for participating!

MusicBrainz Pub Gathering in London on 16 June

I will be in London again soon and its been a while since we’ve gathered to have a pint. If you’re in or near London and feel like meeting up with other Brainerz, please keep the evening of June 16th open.

If anyone has any suggestions for a pub that is reasonably central, but not overly noisy, please make a comment in this blog post.

Thanks, and I look forward to seeing you!

Six Degrees of Black Sabbath

For many years I’ve espoused MusicBrainz should collect enough information that would allow us to track connections between disparate artists through a game of six degrees of separation. And now Paul Lamere from the EchoNest has done exactly this for Music Hack Day San Francisco.

Six degrees of Black Sabbath allows you to enter two artists and it will search the MusicBrainz advanced relationships to find a connection between your two artists. See Paul’s blog post for more details.

Very very cool to see interesting applications like this appear in the MusicBrainz ecosystem!

Thanks Paul!

Concert listings on MusicBrainz?

During the last summit we spoke about listing concerts on MusicBrainz artist pages. So far we’ve had three concert listing providers approach us about listing concerts on our artist pages.

I generally hate the idea of advertising and I find the idea of advertising on MusicBrainz as very distasteful. But, being alerted to a concert in your area while browsing MusicBrainz seems like a very valuable addition to our site, especially if people are willing to provide the data for us for free!

So, I have two questions for the general MusicBrainz community:

  1. How do you feel about concert listings on MusicBrainz?
  2. Should we make the concert data providers pay for us showing their concert information? Since three companies have already approached us, it seems that we have leeway to ask for payment for this service. (This then would allow us to pay for some of the programmers who slave over making MB better for everyone).

Regardless of payment or not, we would rotate providers while showing listings to give every provider a fair number of impressions for their concert listings.

Please post your comments below!

LyricWiki and MusicBrainz integration!

LyricWiki and MusicBrainz are two community-powered sites about music which share some of the same passionate users. LyricWiki contains song lyrics and MusicBrainz contains metadata (detailed info) about music.

As of today, the two projects are going to be able to work together better than ever. Now that LyricWiki has obtained licensing, MusicBrainz can now link to song lyrics without worrying about legal issues. LyricWiki has given explicit permission to MusicBrainz to do so and MusicBrainz has added LyricWiki links (as an AR type) to their standard.

Linking from LyricWiki to MusicBrainzLyricWiki to MusicBrainz

To link to an artist, track, or release on MusicBrainz, put “musicbrainz= [UUID]” into the footer (ArtistFooter, AlbumFooter, or SongFooter) template. For [UUID], put in the MusicBrainzIdentifier. This has been available for quite a while, but hopefully there will be many more links now that we’re working more closely.

Linking from MusicBrainz to LyricWikiMusicBrainz to LyricWiki

To link a release or a track to LyricWiki, copy the LyricWiki album or track URL and then navigate to the proper release or track page in MusicBrainz. Be sure to be logged in and then click on “Relate to URL” link. Follow the instructions on the next page to add the LyricWiki URL to MusicBrainz.

This is an exciting opportunity for the two projects to be more closely linked together. We’re looking forward to it!

– Sean Colombo & Robert Kaye

mb_server is now hosted on Git

Today we are officially marking the transition of mb_server (that’s the code name for the MusicBrainz Server – the website) from Subversion to Git. This is now hosted at git.musicbrainz.org, and the “musicbrainz-server/core.git” repository contains the stable and unstable development branches (named master and next, respectively).

If you are just interested in setting up MusicBrainz locally, and not interested in development, the same instructions apply as before – use the latest RELEASE branch from Subversion. The git changes should only be of interest to those who were running the “trunk” branch from Subversion, and wish to test or contribute to the upcoming NGS server.

For more information about Git & MusicBrainz, see the Git wiki page

Privacy policy page re-written for clarity, policy remains unchanged

Navap undertook a re-write of our privacy policy page to make the page more consistent and better organized. However, the actual policy did not change — just the wording/formatting of the page has changed.

Please take a look at the diff of the changes and the new page.

(This post is mostly only for full disclosure — seeing Facebook being shredded for its new policy is making me overly cautious right now.)

MusicBrainz Summit 10 Wrapup

We’ve just finished our 10th MusicBrainz Summit, this time held in Nürnberg, Germany. It was a great success, with a number of participants and a lot of discussion! This time, we’ve managed to note all the discussions. So, if you missed the summit and want to catch up on what we talked about, head over to our wiki page with the summit notes, which contains a summary of just about everything we mentioned.

Thanks to everyone who came, and bring on the next summit!