Search results

==User documentation== ===For the web interface===

.... The library supports Windows, Linux and Mac OS X, with packages released for the RedHat and Debian distributions. If you are looking for a complete, usable program to run, please try out [[Picard]].

...rt Archive Library (libcoverart), is a development library geared towards developers who wish to add Cover Art capabilities to their applications. The library s == Documentation ==

...ses keeps MusicBrainz running and covers the paychecks of paid MusicBrainz developers. The [[MusicBrainz Database]] is split into two components for licensing purposes.

...rbis.com/ Ogg Vorbis] files. There is currently no documentation available for this library. If you would like use this library to generate TRM IDs, pleas

BookBrainz (https://bookbrainz.org/) does not have much documentation, and what exists is outdated. * Auto-generated developer documentation https://doclets.io/bookbrainz/bookbrainz-site/master

: Our C/C++ development library geared towards developers who wish to add cover art capabilities to their applications. : Our C/C++ development library geared towards developers who wish to add MusicBrainz lookup capabilities to their applications.

===Documentation & Style=== * [[:Category:Style]] -- For pages describing, proposing, or discussing the style guidelines.

===Picard Developer Documentation Improvements=== ...ugin-api/ basic documentation] regarding the development of plugin modules for MusicBrainz Picard; however, it is somewhat sparse in content. The objecti

...and should not be used in new development. See [[Web Service|WebService]] for more details. ...ish to create MusicBrainz enabled tagging applications. If you are looking for a complete, usable program to run, please try out these:

This page is intended for translators of CritiqueBrainz, and for people interested in the state of its internationalization. For a general introduction about translation platform, projects, and languages,

<!-- Add some links to how-tos and help and documentation stuff once we have updated them --> ...ne who can answer your questions, but with them being a common hangout for developers, [[Editor#Auto-editors|auto-editors]] and other active users, the chances a

However, much of the user-focused documentation is outdated and will need updating and improving. ===New set of core documentation for website users===

API documentation can be created from the source code using [http://epydoc.sf.net epydoc] and ...can be asked on the MusicBrainz [[Mailing_List#Developers.27_Mailing_List|developers mailing list]].

...om/metabrainz/musicbrainz-server. For help in using Git, see our [[Git|Git documentation]]. Our developers are primarily based in North America and Europe. The easiest way to get in

This page collects documents useful for Developers. # [[/ws/js|/ws/js webservice documentation]]

* [[:Category:Development]] -- For pages about MusicBrainz features and implementation. This one is getting hu ...ls which are not only about style (which is covered by) but also new ideas for further developments and other stuff.

[http://developers.google.com/open-source/gci/ Google Code-in] is a contest to introduce pre-u ...google.com/open-source/gci/timeline timeline]). MetaBrainz is partcipating for the first time.

....com/open-source/gci/timeline full timeline]). MetaBrainz is participating for the second time. == General instructions for GCI students ==

* The documentation (you're reading part of it!). ==Documentation==