Development / Introduction

This page has not been reviewed by our documentation team (more info).

MusicBrainz is made up of, and works with, several different components: the MusicBrainz Server, MusicBrainz Database, web service (and related client libraries), and lastly third party applications/services. Bug tracking is done centrally at http://tickets.musicbrainz.org/.

Our development timeline records major releases and developer summits.

MusicBrainz Server

The MusicBrainz Server is a GPLv2 licensed open source project. It's written primarily in Perl and makes use of Catalyst, Moose, and Template Toolkit. Development on the server was started in 2000 and has had many contributors over the years.

The source code is maintained using Git and is available at https://github.com/metabrainz/musicbrainz-server. For help in using Git, see our Git documentation.

MusicBrainz Picard

MusicBrainz Picard is a GPLv2 or later licensed open source project written in Python. Development of Picard in it's current form started in 2007 and it's predecessor has been around since 2003.

The Picard source code is available at https://github.com/musicbrainz/picard.

Developer community

Development team

Our developers are primarily based in North America and Europe. The easiest way to get in touch with them is via IRC in #metabrainz on irc.freenode.net.

Third-party developers

We are proud to have a third-party development community that builds applications and services that utilize or build upon the data that we provide. Most of these third-party projects use one our client libraries to query our web service, others set up their own database.

Google Summer of Code