Search results

(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]]) ...nt to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some

(see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]]) === Use Solr search server===

...available, [[Style|style guidelines]] are changed or are added to, or new server features are implemented. ...cated to the Open Source software development model, and thus the [[Server|server]] and client libraries are available under the [https://www.gnu.org/copylef

(see also: [[Development/Summer_of_Code/Getting_started|GSoC - Getting started]]) ...to work on AcousticBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some

The list of open tasks is kept on our [[Bug Tracker]], and on [[MusicBrainz Development]], and they change quite frequently. === MusicBrainz Server Developer ===

(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]]) ...nt to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some

<small>[[Development]] > Subversion Repository </small> The [[MusicBrainz Server]] is currently the only project that has made the transition; the source co

...ith the feature. It's now merged into master, and will be part of the next server release. ...nt, as it won't be possible to test these features against a live database server.

...nt to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some * Install the server on your computer or use the Vagrant setup scripts to build a virtual machin

=== Development === ...in May 2011 after more than five years of planning and two years of active development!

(see also: [[Development/Summer_of_Code/Getting_started|GSoC - Getting started]]) ...to work on AcousticBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some

(see also: [[Development/Summer_of_Code/Getting_started|GSoC - Getting started]]) ...to work on AcousticBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some

...Schema]] (NGS). NGS would prove to be our number one task in 2010, with no server releases happening at all because of our focus on NGS. ...m in the process of writing NGS. From Nov 2009 to Feb 2010 the MusicBrainz Server codebase went from ~224,000 lines of code down to ~72,000 (the lowest since

This page is intended for translators of [[MusicBrainz Server]] and [[MusicBrainz Database]]’s semi-static content, and people interest * MusicBrainz Server/Database translation: Use the [https://community.metabrainz.org/tags/c/musi

(see also: [[Development/Summer_of_Code/Getting_started|GSoC - Getting started]]) ...to work on AcousticBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some

(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]]) ...nt to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some

...pecific collaboration artist credit is credited to (similar to the current server's collaboration artist pages). ...rather see proposals that extend the Picard tagger and help along with its development.

# and finally builds searchable documents and sends these to the Solr search server. === Searching from MusicBrainz mirror without local Solr server ===

* "Artist was last updated X days ago" display in the server. ...the label associated with the release to be updated. However, our database server buckled under the load to constantly update all of this information so we w

...to 2009 before seeing benefit from this work. Consequently we had only one server update in all of 2008, but we're expecting to have about 3 major releases t | Development