Help

Where to ask and discuss what

MusicBrainz has a big and busy community, with a somewhat wide range of tools to communicate.

Finding out the appropriate channel depends mainly on what you want.

I'm not too sure about that edit I made...

Write EditNotes! And obviously, answer questions addressed to you from voters on your edits.

EditNotes are one of the best place to learn and get answers, as most voters will usually provide opinions and links to the relevant parts of the documentation, or even help you in sorting out edits.

Usually, you will get an answer on an EditNote in a matter of days (that still heavily depends on how popular the artist you're editing is, and if there are voters who regularly provide input on your edits).

I just need an answer, NOW!

Well, can you spare five minutes and search the documentation ? Especially the?

It didn't help! And I still need help NOW!

Then your best shot is the IRC channel.

Be aware, though, that like all IRC channels, you'll obviously get an answer from the people who are hanging there at the moment you drop in. Some of them really are experts (including the project lead and main developers), others are just experts in telling jokes about mooses and choco (which sure is fine also :-) )

I have a somewhat generic question, and on IRC, you know, they just tell funny jokes about Mooses and Choco...

Assuming you went through the documentation already without finding your answer, you may certainly try either the MusicBrainzForum or the UsersMailingList, depending on your preference.

Usually, you'll get an answer in less than a day (and possibly a bit less jokes).

My question is pretty specific, actually

Our MailingLists (and so the MusicBrainzForum) are split into different topics (developers, style, etc), and you will probably find the appropriate one for your question.

Also, if your question pertain to something that is not really clear in the documentation, you are strongly encouraged to just edit the relevant wiki page and ask it there. That way is certainly a better choice for the long term, as your question not only will be answered but the documentation will benefit from it by being updated to clarify what was not in the first place.

I found a bug!

Then you may report it! Check our BugTracker (be sure to verify your bug is not already reported).

I found a problem in the documentation, and I think I can fix it

Just go ahead and edit the page on the MusicBrainzWiki. A few recommendations , though:

• please create a WikiAccount so your edits are signed (this is not the same as your editor MusicbrainzAccount)
• if the page you wanna edit is part of the official editor documentation, you definitely should not randomly change the meaning of it (especially the StyleGuidelines). Such a change should be discussed first (see below)
• just as with any Wiki, we have some code of conduct rules - obviously you shouldn't just remove content because it doesn't please you, or alter other people questions, etc...

I have this idea to propose about a style improvement

Our favorite process to do so works roughly as follow:

• taste the waters, especially if you're new: try to see what other people think about "the question" you are trying to solve, and dig a bit on the wiki (or the MailingLists archives) to check if a similar proposal was not suggested earlier
• when done, create a new wiki page that describes your style proposal (you may ask for help from a more experienced WikiZen if you need)
• post a request for comments to the StyleMailingList, and see what's the reaction
• you may also open-up a ticket in the BugTracker (that helps us in keeping a vision of our history)
• your request for comments will eventually become a request for veto and will eventually become reality!

More details about all that in the StyleCouncil page.

I have this new idea for a super-new-feature...

... but that involves additional code development, right? :-)

Whether your idea will be implemented or not pretty much sums-up to the question: "is one of the developers interested in implementing it?".

While obviously the easiest way to have it actually implemented is to contribute the code for it yourself (if you have such skills), even non-developers are encouraged in providing feedback and new ideas on future developments.

To do so, usually:

• get yourself familiar with the way the project will evolve (check the)
• create a wiki page describing your proposal
• possibly look for feedback from other users on the MailingLists
• hook-up with a developer!