https://wiki.musicbrainz.org/api.php?action=feedcontributions&user=Dupuy&feedformat=atom
MusicBrainz Wiki - User contributions [en]
2024-03-28T16:17:45Z
User contributions
MediaWiki 1.39.4
https://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/13&diff=64457
MusicBrainz Summit/13
2013-09-20T11:10:29Z
<p>Dupuy: /* TL;DR */ Google Maps is actually useful now</p>
<hr />
<div>== Summary ==<br />
<br />
MusicBrainz Summit 13 will happen between the 20th and 23rd September, 2013 at Wikimedia Germany in Berlin.<br />
<br />
=== Schedule ===<br />
<br />
People planning to attend should aim to arrive in time for dinner on the 20th (Friday), though it seems that people will arrive mid-day. Plan to return home on the 23rd (Monday), or as late as possible on Sunday if you need to leave earlier.<br />
<br />
We'll meet all day Saturday and Sunday at Wikimedia Germany at 10:00 -- please see the meal section for details on when group meals will happen.<br />
<br />
=== Meals ===<br />
<br />
Meals will be provided for: Breakfast and lunch with be crowd-sourced from the local [http://goo.gl/maps/9OT4F NP-Markt]. We'll send some people to go to buy food for us to eat for breakfast and lunch. We'll at the Wikimedia offices. Detailed information on dinners follows below:<br />
<br />
''Friday dinner''<br />
<br />
When: 19:00<br/><br />
Where: [http://www.zsazsaburger.de/ ZsaZsa Burger], Motzstrasse 28 near U-Bahn Nollendorfplatz.<br/><br />
Notes: We have a reservation for up to 22 people and will be seated in their outdoor tent. They can provide blankets for anyone who needs one -- be prepared to dress a little warmer<br />
<br />
''Saturday dinner''<br />
<br />
When: 18:30<br/><br />
Where: [http://www.maxundmoritzberlin.de/ Max & Moritz], Oranienstrasse 162.<br/><br />
Notes: We must order from their [https://www.dropbox.com/s/2a6rubnnqdzmvrm/Max%20%26%20Mortiz%20Group%20Menu%20-%20German.pdf group menu]. We need to mail them our order around lunch time on Saturday in an effort from them to serve all of us at the same time.<br />
<br />
''Sunday dinner''<br />
<br />
We'll play this one by ear. Ruaok will lead an expedition to eat at Mustafas, which entails a long wait that is paired with beers from a shop next to Mustafas. This is a quintessential Berlin experience! <br />
<br />
If you'd like something less authentic, we'll organize another group of people to go someplace else.<br />
<br />
=== Lodging ===<br />
<br />
We've rented a flat that has space for 10-12 people at [https://www.airbnb.com/rooms/729062 Weimarische Straße 15] ([http://www.openstreetmap.org/?mlat=52.47844&mlon=13.32423&way=4442078#map=17/52.47844/13.32423 OSM]). We have the flat from Friday 2pm to Monday 11am. If you'd like to stay at the flat, please add yourself to this list:<br />
<br />
[[User:RobertKaye|ruaok]], [[User:Ianmcorvidae|ianmcorvidae]], [[User:Nikki|nikki]], [[User:CatCat|CatCat]], [[User:Kepstin|kepstin]], [[User:Mineo|Mineo]], [[User:Reosarevok|reosarevok]], [[User:LordSputnik|LordSputnik]], [[User:Warp|warp]], [[User:PavanChander|navap]], [[User:Freso|Freso]], [[User:OliverCharles|ocharles]]<br />
<br />
The flat is '''full'''. If you plan to attend you will need to find other lodgings!<br />
<br />
== People confirmed to be attending ==<br />
<br />
'''NOTE: We have a limit of 20 people who can attend, based on available capacity at Wikimedia Germany.'''<br />
<br />
(times are for Friday/Monday except where otherwise noted)<br />
{| class="wikitable"<br />
|-<br />
! rowspan=2 | !!colspan="2"| Arriving !! colspan="2"| Leaving !! rowspan="2"|Notes<br />
|-<br />
! Time || Details || Time || Details<br />
|-<br />
| [[User:JonnyJD|JonnyJD]] || colspan=5 | (lives in Berlin (Köpenick), I'm basically free Friday to Monday)<br />
|-<br />
| [[User:Fractalizator|fractalizator]] || colspan=5 | (lives in Berlin (Schöneberg))<br />
|-<br />
| [[User:Hrglgrmpf|hrglgrmpf]] || colspan=5 | (lives in Berlin, can only attend on Friday evening for dinner)<br />
|-<br />
| [[User:Nikki|nikki]] || rowspan=2 | 06:38 || rowspan=2 | DB CNL457 || rowspan=2 | 13:48 || rowspan=2 | DB ICE556 || rowspan=2 | via Berlin Hbf<br />
|-<br />
| [[User:Ianmcorvidae|ianmcorvidae]]<br />
|-<br />
| [[User:Reosarevok|reosarevok]] || 10:15 || Air Baltic BT211 || 10:40 || Air Baltic BT212 || via TXL<br />
|-<br />
| [[User:PavanChander|navap]] || 11:15 || Brussels Airlines 2581 || 06:40 || Brussels Airlines 2592 || via TXL<br />
|-<br />
| [[User:Kepstin|kepstin]] || rowspan=2 | 11:30 || rowspan=2 | British Airways BA0982 || 11:00 || British Airways BA0991 || via TXL<br />
|-<br />
| [[User:OliverCharles|ocharles]] || 12:20 || British Airways 983 || via TXL<br />
|-<br />
| [[User:LordSputnik|LordSputnik]] || 11:35 || EZY5409 || 21:05 || EZY5416 || via SXF<br />
|-<br />
| [[User:RobertKaye|ruaok]] || 12:55 || Lufthansa 168 || 18:40 || Swiss 971 || via TXL<br />
|-<br />
| [[User:Mineo|Mineo]] || 13:32 || DB IC2355 || 12:26 || DB IC2356 || via Berlin Hbf<br />
|-<br />
| [[User:ijabz|ijabz]] || 16:20 || EZY6237 || 16:50 || EZY6238 || via SXF<br />
|-<br />
| [[User:CatCat|CatCat]] || 20:45 || Ryanair FR8903 || 21:10 (Sun.) || Ryanair FR8904 || via SXF<br />
|-<br />
| [[User:Freso|Freso]] || 22:25 || EZY4558 || 07:15 || EZY4553 || via SXF<br />
|-<br />
| [[User:Warp|warp]] || 22:45 || EZY4568 || 19:35 (Sun.) || EZY4567 || via SXF<br />
|-<br />
| Anders Arpteg (Spotify) || colspan=5 | TBD<br />
|}<br />
<br />
== People who might attend ==<br />
* [[User:KRSCuan|KRSCuan]] if my schedule allows<br />
* [[User:Dupuy|Dupuy]] Although I've not been active in MBz for quite some time, I am now living in Berlin, and would love to attend if there's space. We have a large apartment in Wilmersdorf and I might be able to provide accommodations for some participants.<br />
* [https://musicbrainz.org/user/Noobie/ noobie] I'm living in Berlin and will probably pop in for a beer in the evening ( if the weather allows in the park or whatever plans there are for the evening :) )<br />
== Agenda ==<br />
<br />
Saturday 21 September:<br />
<br />
* Genres<br />
* DiscIDs<br />
* Viewer-friendly site: [[MusicBottle]], [http://mbjs.kepstin.ca/ mbjs]<br />
* Sub-entities<br />
<br />
Sunday 22 September:<br />
<br />
* (add more here)<br />
<br />
At some point, with no assigned day (yet):<br />
<br />
* Box Sets<br />
* Beginner-Friendliness<br />
* Promotion<br />
* More visiblility for/work on NES?/NES update<br />
* Videos<br />
* Internationalization (i18n) (including multi-lingual wiki)<br />
* Classical Support<br />
* Official Cross-Platform Awesome MusicBrainz Player<br />
* WavePlot Scanning + Tagging<br />
* How to make voting a less tedious experience and get more people to do it!<br />
* Making Relationships easier to use, add and edit<br />
* Master and Performance Entities (+ relationship inheritance?)<br />
* Geordi update<br />
* mb-style reform<br />
* Homepage Design<br />
* Site Target Audience (analytics?)<br />
<br />
See also: [https://docs.google.com/document/d/1wVADHHlKHZr1eQnkpyZrUGVd1NZNJNXZRrqWrzszXGM/ Google Doc with previous unresolved summit topics] (LordSputnik's -- not editable by others)<br />
<br />
== Important things to not forget, but that will be forgotten anyway ==<br />
<br />
* Napkins<br />
<br />
== Public Transportation in Berlin ==<br />
=== From Tegel Airport (TXL) ===<br />
Tegel in the north west is the more central of the airports (zone B). There are no train connections, so you will need to take a bus to the city centre. The bus route TXL runs every 6-7 minutes to Berlin Hauptbahnhof and takes about 22 minutes. The bus route X9 runs every 10 minutes to Zoologischer Garten and takes about 20 minutes.<br />
<br />
=== From Schönefeld Airport (SXL) ===<br />
Schönefeld in the south east is just outside Berlin (zone C). There are two direct train routes to Berlin Hauptbahnhof, the RE7 running hourly at 23 minutes past the hour and the RB14 running hourly around 48 minutes past the hour. Both take about 28 minutes to reach the Hauptbahnhof. There are also buses and S-Bahn trains running more frequently, but they do not connect directly with the Hauptbahnhof and the journey takes about twice as long.<br />
<br />
=== Tickets ===<br />
Tickets for zones A and B cover the whole city area including Tegel Airport, but '''not''' Schönefeld Airport.<br />
A single ticket costs €2.60 and you can travel on the S+U-Bahn trains, RE/RB trains, trams and buses for 2 hours in one direction. A short trip ticket is €1.50 and you can go 3 S+U-Bahn stations or 6 bus stops (without changing buses). A day ticket costs €6.70.<br />
<br />
For travelling to/from Schönefeld, you need a ticket which includes zone C. A single ticket for zones A+B+C costs €3.20. A day ticket costs €7.20.<br />
<br />
=== Other information ===<br />
There is a [http://images.vbb.de/assets/downloads/file/14479.PDF map with the main trains] (S-Bahn + U-Bahn). You can search for [http://fahrinfo.vbb.de/bin/query.exe/en times and routes]. <br />
<br />
Some of the main trains also run (quite frequently) [http://www.bvg.de/index.php/de/binaries/asset/download/21113/file/1-1 in the night]. To other places you can get with night busses (starting with N). If you feel lost, try to find out where you are and call a taxi at +4930202020.<br />
<br />
For the trains, you should buy your tickets up front at the station from the ticket machine and then stamp it to validate it in one of the stamping devices (which will probably be next to the ticket machines). On buses you can also buy tickets when entering. Tickets are only checked randomly and not when entering stations or trains (you are supposed to show your ticket when entering a bus).<br />
<br />
[http://en.wikivoyage.org/wiki/Berlin Wikivoyage] has a relatively well-populated page on Berlin as well, though much of the information duplicates the above.<br />
<br />
=== TL;DR ===<br />
<br />
Use [http://www.bvg.de/index.php/en/index.html BVG.de (English version)] to plan your route. Locations like "Tegel Airport" are also supported. If you have an iPhone/iPad/iPod, [https://itunes.apple.com/de/app/fahrinfo-berlin/id284971745?mt=8 Fahrinfo] is the best free app for transit route planning.<br />
<br />
[https://maps.google.com/ Google Maps] now supports (BVG) U-Bahn and buses, as well as S-Bahn and regional trains (but be wary of routes via regional RE/RB as those trains often run late).</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/13&diff=64456
MusicBrainz Summit/13
2013-09-20T10:57:14Z
<p>Dupuy: /* Meals */ typo</p>
<hr />
<div>== Summary ==<br />
<br />
MusicBrainz Summit 13 will happen between the 20th and 23rd September, 2013 at Wikimedia Germany in Berlin.<br />
<br />
=== Schedule ===<br />
<br />
People planning to attend should aim to arrive in time for dinner on the 20th (Friday), though it seems that people will arrive mid-day. Plan to return home on the 23rd (Monday), or as late as possible on Sunday if you need to leave earlier.<br />
<br />
We'll meet all day Saturday and Sunday at Wikimedia Germany at 10:00 -- please see the meal section for details on when group meals will happen.<br />
<br />
=== Meals ===<br />
<br />
Meals will be provided for: Breakfast and lunch with be crowd-sourced from the local [http://goo.gl/maps/9OT4F NP-Markt]. We'll send some people to go to buy food for us to eat for breakfast and lunch. We'll at the Wikimedia offices. Detailed information on dinners follows below:<br />
<br />
''Friday dinner''<br />
<br />
When: 19:00<br/><br />
Where: [http://www.zsazsaburger.de/ ZsaZsa Burger], Motzstrasse 28 near U-Bahn Nollendorfplatz.<br/><br />
Notes: We have a reservation for up to 22 people and will be seated in their outdoor tent. They can provide blankets for anyone who needs one -- be prepared to dress a little warmer<br />
<br />
''Saturday dinner''<br />
<br />
When: 18:30<br/><br />
Where: [http://www.maxundmoritzberlin.de/ Max & Moritz], Oranienstrasse 162.<br/><br />
Notes: We must order from their [https://www.dropbox.com/s/2a6rubnnqdzmvrm/Max%20%26%20Mortiz%20Group%20Menu%20-%20German.pdf group menu]. We need to mail them our order around lunch time on Saturday in an effort from them to serve all of us at the same time.<br />
<br />
''Sunday dinner''<br />
<br />
We'll play this one by ear. Ruaok will lead an expedition to eat at Mustafas, which entails a long wait that is paired with beers from a shop next to Mustafas. This is a quintessential Berlin experience! <br />
<br />
If you'd like something less authentic, we'll organize another group of people to go someplace else.<br />
<br />
=== Lodging ===<br />
<br />
We've rented a flat that has space for 10-12 people at [https://www.airbnb.com/rooms/729062 Weimarische Straße 15] ([http://www.openstreetmap.org/?mlat=52.47844&mlon=13.32423&way=4442078#map=17/52.47844/13.32423 OSM]). We have the flat from Friday 2pm to Monday 11am. If you'd like to stay at the flat, please add yourself to this list:<br />
<br />
[[User:RobertKaye|ruaok]], [[User:Ianmcorvidae|ianmcorvidae]], [[User:Nikki|nikki]], [[User:CatCat|CatCat]], [[User:Kepstin|kepstin]], [[User:Mineo|Mineo]], [[User:Reosarevok|reosarevok]], [[User:LordSputnik|LordSputnik]], [[User:Warp|warp]], [[User:PavanChander|navap]], [[User:Freso|Freso]], [[User:OliverCharles|ocharles]]<br />
<br />
The flat is '''full'''. If you plan to attend you will need to find other lodgings!<br />
<br />
== People confirmed to be attending ==<br />
<br />
'''NOTE: We have a limit of 20 people who can attend, based on available capacity at Wikimedia Germany.'''<br />
<br />
(times are for Friday/Monday except where otherwise noted)<br />
{| class="wikitable"<br />
|-<br />
! rowspan=2 | !!colspan="2"| Arriving !! colspan="2"| Leaving !! rowspan="2"|Notes<br />
|-<br />
! Time || Details || Time || Details<br />
|-<br />
| [[User:JonnyJD|JonnyJD]] || colspan=5 | (lives in Berlin (Köpenick), I'm basically free Friday to Monday)<br />
|-<br />
| [[User:Fractalizator|fractalizator]] || colspan=5 | (lives in Berlin (Schöneberg))<br />
|-<br />
| [[User:Hrglgrmpf|hrglgrmpf]] || colspan=5 | (lives in Berlin, can only attend on Friday evening for dinner)<br />
|-<br />
| [[User:Nikki|nikki]] || rowspan=2 | 06:38 || rowspan=2 | DB CNL457 || rowspan=2 | 13:48 || rowspan=2 | DB ICE556 || rowspan=2 | via Berlin Hbf<br />
|-<br />
| [[User:Ianmcorvidae|ianmcorvidae]]<br />
|-<br />
| [[User:Reosarevok|reosarevok]] || 10:15 || Air Baltic BT211 || 10:40 || Air Baltic BT212 || via TXL<br />
|-<br />
| [[User:PavanChander|navap]] || 11:15 || Brussels Airlines 2581 || 06:40 || Brussels Airlines 2592 || via TXL<br />
|-<br />
| [[User:Kepstin|kepstin]] || rowspan=2 | 11:30 || rowspan=2 | British Airways BA0982 || 11:00 || British Airways BA0991 || via TXL<br />
|-<br />
| [[User:OliverCharles|ocharles]] || 12:20 || British Airways 983 || via TXL<br />
|-<br />
| [[User:LordSputnik|LordSputnik]] || 11:35 || EZY5409 || 21:05 || EZY5416 || via SXF<br />
|-<br />
| [[User:RobertKaye|ruaok]] || 12:55 || Lufthansa 168 || 18:40 || Swiss 971 || via TXL<br />
|-<br />
| [[User:Mineo|Mineo]] || 13:32 || DB IC2355 || 12:26 || DB IC2356 || via Berlin Hbf<br />
|-<br />
| [[User:ijabz|ijabz]] || 16:20 || EZY6237 || 16:50 || EZY6238 || via SXF<br />
|-<br />
| [[User:CatCat|CatCat]] || 20:45 || Ryanair FR8903 || 21:10 (Sun.) || Ryanair FR8904 || via SXF<br />
|-<br />
| [[User:Freso|Freso]] || 22:25 || EZY4558 || 07:15 || EZY4553 || via SXF<br />
|-<br />
| [[User:Warp|warp]] || 22:45 || EZY4568 || 19:35 (Sun.) || EZY4567 || via SXF<br />
|-<br />
| Anders Arpteg (Spotify) || colspan=5 | TBD<br />
|}<br />
<br />
== People who might attend ==<br />
* [[User:KRSCuan|KRSCuan]] if my schedule allows<br />
* [[User:Dupuy|Dupuy]] Although I've not been active in MBz for quite some time, I am now living in Berlin, and would love to attend if there's space. We have a large apartment in Wilmersdorf and I might be able to provide accommodations for some participants.<br />
* [https://musicbrainz.org/user/Noobie/ noobie] I'm living in Berlin and will probably pop in for a beer in the evening ( if the weather allows in the park or whatever plans there are for the evening :) )<br />
== Agenda ==<br />
<br />
Saturday 21 September:<br />
<br />
* Genres<br />
* DiscIDs<br />
* Viewer-friendly site: [[MusicBottle]], [http://mbjs.kepstin.ca/ mbjs]<br />
* Sub-entities<br />
<br />
Sunday 22 September:<br />
<br />
* (add more here)<br />
<br />
At some point, with no assigned day (yet):<br />
<br />
* Box Sets<br />
* Beginner-Friendliness<br />
* Promotion<br />
* More visiblility for/work on NES?/NES update<br />
* Videos<br />
* Internationalization (i18n) (including multi-lingual wiki)<br />
* Classical Support<br />
* Official Cross-Platform Awesome MusicBrainz Player<br />
* WavePlot Scanning + Tagging<br />
* How to make voting a less tedious experience and get more people to do it!<br />
* Making Relationships easier to use, add and edit<br />
* Master and Performance Entities (+ relationship inheritance?)<br />
* Geordi update<br />
* mb-style reform<br />
* Homepage Design<br />
* Site Target Audience (analytics?)<br />
<br />
See also: [https://docs.google.com/document/d/1wVADHHlKHZr1eQnkpyZrUGVd1NZNJNXZRrqWrzszXGM/ Google Doc with previous unresolved summit topics] (LordSputnik's -- not editable by others)<br />
<br />
== Important things to not forget, but that will be forgotten anyway ==<br />
<br />
* Napkins<br />
<br />
== Public Transportation in Berlin ==<br />
=== From Tegel Airport (TXL) ===<br />
Tegel in the north west is the more central of the airports (zone B). There are no train connections, so you will need to take a bus to the city centre. The bus route TXL runs every 6-7 minutes to Berlin Hauptbahnhof and takes about 22 minutes. The bus route X9 runs every 10 minutes to Zoologischer Garten and takes about 20 minutes.<br />
<br />
=== From Schönefeld Airport (SXL) ===<br />
Schönefeld in the south east is just outside Berlin (zone C). There are two direct train routes to Berlin Hauptbahnhof, the RE7 running hourly at 23 minutes past the hour and the RB14 running hourly around 48 minutes past the hour. Both take about 28 minutes to reach the Hauptbahnhof. There are also buses and S-Bahn trains running more frequently, but they do not connect directly with the Hauptbahnhof and the journey takes about twice as long.<br />
<br />
=== Tickets ===<br />
Tickets for zones A and B cover the whole city area including Tegel Airport, but '''not''' Schönefeld Airport.<br />
A single ticket costs €2.60 and you can travel on the S+U-Bahn trains, RE/RB trains, trams and buses for 2 hours in one direction. A short trip ticket is €1.50 and you can go 3 S+U-Bahn stations or 6 bus stops (without changing buses). A day ticket costs €6.70.<br />
<br />
For travelling to/from Schönefeld, you need a ticket which includes zone C. A single ticket for zones A+B+C costs €3.20. A day ticket costs €7.20.<br />
<br />
=== Other information ===<br />
There is a [http://images.vbb.de/assets/downloads/file/14479.PDF map with the main trains] (S-Bahn + U-Bahn). You can search for [http://fahrinfo.vbb.de/bin/query.exe/en times and routes]. <br />
<br />
Some of the main trains also run (quite frequently) [http://www.bvg.de/index.php/de/binaries/asset/download/21113/file/1-1 in the night]. To other places you can get with night busses (starting with N). If you feel lost, try to find out where you are and call a taxi at +4930202020.<br />
<br />
For the trains, you should buy your tickets up front at the station from the ticket machine and then stamp it to validate it in one of the stamping devices (which will probably be next to the ticket machines). On buses you can also buy tickets when entering. Tickets are only checked randomly and not when entering stations or trains (you are supposed to show your ticket when entering a bus).<br />
<br />
[http://en.wikivoyage.org/wiki/Berlin Wikivoyage] has a relatively well-populated page on Berlin as well, though much of the information duplicates the above.<br />
<br />
=== TL;DR ===<br />
<br />
Use [http://www.bvg.de/index.php/en/index.html BVG.de (English version)] to plan you route. Locations like "Tegel Airport" are also supported.<br />
<br />
Don't trust [https://maps.google.com/ Google Maps]! It supports only S-Bahn and regional trains, and most of the time says "take a taxi, take a train, take a taxi".<br />
<br />
''Update'': Google Maps should also work starting from the 3rd of September.</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=MusicBrainz_Summit/13&diff=64071
MusicBrainz Summit/13
2013-08-06T23:48:36Z
<p>Dupuy: /* People who might attend */ added Dupuy</p>
<hr />
<div>== Summary ==<br />
<br />
MusicBrainz Summit 13 will happen between the 20th and 23rd September, 2013 at Wikimedia Germany in Berlin.<br />
<br />
=== Tentative Schedule ===<br />
<br />
People planning to attend should aim to arrive in time for dinner on the 20th (Friday), though it seems that people will arrive mid-day. We'll meet all day Saturday and Sunday at Wikimedia Germany. Plan to return home on the 23rd (Monday), or as late as possible on Sunday if you need to leave earlier.<br />
<br />
=== Meals ===<br />
<br />
Meals will be provided for: Breakfast and lunch with be crowd-sourced from a local supermarket. Dinner will be at local establishments. More details will be posted here as we get closer to the event.<br />
<br />
=== Lodging ===<br />
<br />
We'll arrange and pay for lodging for community members again. Please stay tuned as this has not been arranged yet.<br />
<br />
== People confirmed to be attending ==<br />
<br />
'''NOTE: We have a limit of 20 people who can attend, based on available capacity at Wikimedia Germany.'''<br />
<br />
(times are for Friday/Monday except where otherwise noted)<br />
{| class="wikitable"<br />
|-<br />
! rowspan=2 | !!colspan="2"| Arriving !! colspan="2"| Leaving !! rowspan="2"|Notes<br />
|-<br />
! Time || Details || Time || Details<br />
|-<br />
| [[User:JonnyJD|JonnyJD]] || colspan=5 | (lives in Berlin (Köpenick), I'm basically free Friday to Monday)<br />
|-<br />
| [[User:Fractalizator|fractalizator]] || colspan=5 | (lives in Berlin (Schöneberg))<br />
|-<br />
| [[User:Nikki|nikki]] || rowspan=2 | 04:26 || rowspan=2 | DB CNL457 || rowspan=2 | 13:48 || rowspan=2 | DB ICE556 || rowspan=2 | via Berlin Hbf<br />
|-<br />
| [[User:Ianmcorvidae|ianmcorvidae]]<br />
|-<br />
| [[User:Reosarevok|reosarevok]] || 10:15 || Air Baltic BT211 || 10:40 || Air Baltic BT212 || via TXL<br />
|-<br />
| [[User:RobertKaye|ruaok]] || 12:55 || Lufthansa 168 || 18:40 || Swiss 971 || via TXL<br />
|-<br />
| [[User:Mineo|Mineo]] || 13:32 || DB IC2355 || 12:26 || DB IC2356 || via Berlin Hbf<br />
|-<br />
| [[User:CatCat|CatCat]] || 20:45 || Ryanair FR8903 || 21:15 (Sun.) || Ryanair FR8904 || via SXF<br />
|-<br />
| [[User:LukasLalinsky|luks]] || colspan=5 | (arrives by car, not decided on the exact time yet)<br />
|-<br />
| (corporate sponsor #1) || || || || ||<br />
|-<br />
| (corporate sponsor #2) || || || || ||<br />
|-<br />
| (corporate sponsor #3) || || || || ||<br />
|}<br />
<br />
== People who might attend ==<br />
* [[User:Freso|Freso]] (would like to go, but can't pay for (air)fare)<br />
* [[User:Ianweller|ianweller]] (would like to go, but can't pay for airfare)<br />
* [[navap]]<br />
* [http://kloeri.livejournal.com/ kloeri]<br />
* [[User:Wizzcat|Wizzcat]]<br />
* [[User:Leftmostcat|Leftmost]]<br />
* [[User:Kepstin|kepstin]] will do his best to be there.<br />
* [[User:OliverCharles|ocharles]]<br />
* [[User:ijabz|ijabz]]<br />
* [[User:KRSCuan|KRSCuan]] if my schedule allows<br />
* [[User:LordSputnik|LordSputnik]] if I can get time off work :)<br />
* [[User:Dupuy|Dupuy]] Although I've not been active in MBz for quite some time, I am now living in Berlin, and would love to attend if there's space. We have a large apartment in Wilmersdorf and I might be able to provide accommodations for some participants.<br />
<br />
== Agenda ==<br />
<br />
Saturday 21 September:<br />
<br />
* Genres<br />
* DiscIDs<br />
* [[MusicBottle]]<br />
<br />
Sunday 22 September:<br />
<br />
* (add more here)<br />
<br />
== Important things to not forget, but that will be forgotten anyway ==<br />
<br />
* Napkins<br />
<br />
== Public Transportation in Berlin ==<br />
<br />
Tegel Airport (TXL) is the more central one and in the north west. You can take a bus to train stations from there.<br />
Schönefeld (SXL) is just outside Berlin (SE) and you probably want to take the bus to Rudow (and underground train afterwards), but you can also take an express train to the city.<br />
If you have heard of Berlin Brandenburg International Airport (BER) that was supposed to open last year.. it still isn't. It would be close to SXL otherwise.<br />
<br />
There is a [http://images.vbb.de/assets/downloads/file/14479.PDF map with the main trains] (S-Bahn + U-Bahn). You can search for [http://fahrinfo.vbb.de/bin/query.exe/en times and routes]. The normal ticket costs 2,60 € and is for the parts A+B which is the whole city area, but without Schönefeld (SXF) Airport. You can then go with S+U Bahn, bus and tram for 2 hours. A short trip ticket is 1,50 € and you can go 3 train stations or 6 bus stations without changing trains. Day ticket is 6,70 €.<br />
<br />
Some of the main trains also run (quite frequently) [http://www.bvg.de/index.php/de/binaries/asset/download/21113/file/1-1 in the night]. To other places you can get with night busses (starting with N). If you feel lost, try to find out where you are and call a taxi at +4930202020.<br />
<br />
You are supposed to buy your tickets up front at the stations from ticket machines, but at buses you can also buy them when entering. Tickets are only checked randomly and not when entering stations or trains (you are supposed to show your ticket when entering a bus).</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Auto-Editor_Election&diff=49512
Auto-Editor Election
2011-11-08T20:46:11Z
<p>Dupuy: enhancements, corrections, writing style improvements</p>
<hr />
<div>Elections for users to become [[Auto-Editor|auto-editors]] take place on the [http://musicbrainz.org/user/election/ main server] (although at the moment they are still held on the [http://musicbrainz.org/user/election/ "classic" server]). Election results are available for anyone to review, however, you must be an auto-editor to vote on an election.<br />
<br />
When viewing details of an open (ongoing) election, generally only the list of auto-editors who have voted is provided . For closed elections, a vote tally of total yes and no votes are provided (for open elections, the proposer and seconders can also see the vote tally, as they are ineligible to vote).<br />
<br />
Individual users' votes are always hidden (you ''can'' see your own vote, if any, and if the election is still open, change it). The election details go back as far as mid-2004, when the informal elections then held on the [[Mailing_List#Users.27_Mailing_List|musicbrainz-users mailing list]] were replaced with an automated version.<br />
<br />
==Becoming an auto-editor==<br />
<br />
In order to become an auto-editor, you must first be nominated by an auto-editor, seconded by two other auto-editors, and then have your nomination accepted by a majority of the remaining auto-editors voting Yes or No.<br />
<br />
There are no hard and fast prerequisite criteria that must be met before a user is "worthy" of being nominated, and while each situation may differ, the following are some general guidelines to keep in mind.<br />
<br />
Auto-editors should have:<br />
* experience with the various editing aspects of the site<br />
* a clear grasp of the [[Style Guidelines]]<br />
* a willingness to help and support other users<br />
* the ability to take an objective point of view regarding the data they edit<br />
* a reasonably significant volume of current activity<br />
<br />
== Rules/Regulations/Formalities ==<br />
<br />
# Any auto-editor can nominate any user to become an auto-editor candidate. <br />
# Up to two other auto-editors may second the candidate within a week from nomination.<br />
# As soon as two seconds are made, the election is open for one week for other auto-editors to vote.<br />
# The candidate is accepted if a simple majority (more than half) of non-abstaining auto-editors vote Yes.<br />
# Otherwise the candidate is declined, but may be re-nominated in the future.<br />
<br />
Any auto-editor who nominates or seconds a candidate cannot vote in the election itself. <br />
<br />
== Process ==<br />
<br />
# If you have a potential candidate for auto-editor status, first, do some more research: was this user nominated previously? How long has the user been active, and are they still active?<br />
# Before nominating a user, you should check that the user is willing to be nominated. Many are, but some feel they are not ready, and others are not comfortable being discussed and voted on.<br />
# To start a new election, click on "Nominate for auto-editor" on the profile page of the candidate. (This currently just sends an e-mail to the nominee - see point 2; at the moment you must nominate the user on the classic site.)<br />
# While it is not strictly required, it is strongly recommended that the proposer send an email to the [[Mailing_List#Auto-Editors_Mailing_List|auto-editors mailing list]] to personally announce the nomination and give others a brief introduction to the candidate and why they should be elected.<br />
# Up to two other auto-editors may second the nomination by going to the candidate's [http://www.musicbrainz.org/user/election/ election page] and clicking the "Second" button.<br />
# If two seconds are not made within a week, the election is automatically canceled.<br />
# If seconded twice, the election is then open for voting for a week. Auto-editors can vote by going to the candidate's [http://www.musicbrainz.org/user/election/ election page]. Possible choices are "Yes", "No", and "Abstain". A simple majority (not including abstentions or non-voters) is required to pass the election.<br />
# At any time while the election is open, the original proposer can cancel the election, closing it to further votes, and leaving the nominee as a normal user.<br />
<br />
There is some historical precedent for proposers to cancel elections that are close or controversial, in the interests of creating consensus; however this is not required. It is good form for the proposer (or seconders) to notify other auto-editors on the mailing list if the election is a close one, although they should not provide the actual tally (remember that other auto-editors cannot see the vote tally while the election is open)<br />
<br />
'''Note:''' All the above actions can only be performed by a current auto-editor.<br />
<br />
== Communication ==<br />
<br />
The [[Mailing_List#Auto-Editors_Mailing_List|auto-editors mailing list]], like all of MusicBrainz' mailing lists, is a publicly readable list and is used to discuss nominations, as well as the election process and other issues related to auto-editors activities. Only auto-editors can post to this list.<br />
<br />
Additionally, any candidate who is accepted as an auto-editor will be automatically subscribed to that mailing list; this is a mandatory subscription for all auto-editors.<br />
<br />
[[Category:Documentation]] [[Category:WikiDocs Page]] [[Category:To Be Reviewed]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Editor&diff=49490
Editor
2011-11-08T19:39:23Z
<p>Dupuy: link to main server, not test, for current autoeditor list</p>
<hr />
<div>An editor (previously called moderator) is user who contributes to MusicBrainz by entering [[Edit|edits]] into the [[MusicBrainz Database|database]]. All editors are expected to follow the MusicBrainz [[Code of Conduct]].<br />
<br />
Some editors have special privileges which are discussed below. A list of these editors is available on the [http://musicbrainz.org/privileged server].<br />
<br />
==Auto-editors==<br />
<br />
Auto-editors are trusted users who have been given "auto-editor" privileges. These privileges allow them to make select edits that are automatically approved without going through the normal [[How Voting Works|voting process]], as well as the ability to instantly approve other users' edits.<br />
<br />
===Obligations of an auto-editor===<br />
<br />
:"''With great power comes great responsibility''" - Uncle Ben (of Spider Man fame)<br />
<br />
While auto-editors can be thought of as having more "power" than other users, they should always align themselves to the [[Code Of Conduct|Code of Conduct]]. Furthermore, they should be able to look beyond their nose and take an objective point of view regarding the data they edit. Being familiar with the various editing aspects of the site is important, as well as having a clear grasp of the [[Style Guidelines|style guidelines]].<br />
<br />
Additionally, while it is good to be an expert in certain areas of the database (e.g. certain musical genres or specific artists), every auto-editor should be comfortable enough with the basic editing fundamentals that they are able to edit outside their realm of expertise.<br />
<br />
===Becoming an auto-editor===<br />
<br />
In order to become an auto-editor, you must first be nominated by an existing auto-editor and then have your nomination put to a vote. See [[Auto-Editor Election|auto-editor election]] for more information.<br />
<br />
[[Category:Terminology]] [[Category:WikiDocs Page]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Artist_Alias&diff=45413
Artist Alias
2011-05-19T19:14:39Z
<p>Dupuy: /* Description */ ticket 820 has been closed</p>
<hr />
<div>{{DocumentationHeader|Artist|Terminology}}<br />
<br />
==Description==<br />
<br />
While the name "aliases" may be an example of [[Bad Terminology]], and these could perhaps better be called "variant names" or "search hints", artist aliases are very useful. They are primarily used to guide selection of artists for releases and tracks, but can also be used to provide [[Internationalization]] of artist names, by creating aliases for particular locales.<br />
<br />
[[MusicBrainz]] supports both explicit and implicit [[Artist Search]]es, which consider both [[Artist Name]]s and artist aliases (but '''not''' [[Artist Sort Name]]s). Explicit searches can be made through both the [[Quick Search]] and [[Advanced Search]] forms, but implicit ones are much more common. Any time that you specify an artist name, e.g. in an [[Add Release Edit]], [[Move Release Edit]], or [[Merge Artists Edit]] or similar [[Edit Type]]s, the name you provide is used to retrieve a list of candidate (matching) artists; you can select one of these, retry the search with another name, or create a new artist.<br />
<br />
==Limitations==<br />
<br />
Currently, aliases are required to be unique, i.e. a given alias can only be associated to one artist. [[Ticket:780|Ticket 780]] suggests allowing duplicate artist aliases, until then it can be worked around by adding (parenthetical) text to the alias.<br />
<br />
==When NOT to use aliases==<br />
<br />
You should '''not''' use aliases for [[Performance Name]]s (where an individual or group have multiple "projects" under whose different names they release different musical works). Instead, these should be added as separate artists, and linked together using [[Performance Name Relationship Type]]. Note that this is not like what Discogs does!<br />
<br />
==When to use aliases==<br />
<br />
There are many other cases where use of aliases ''is'' appropriate:<br />
# '''Misspellings''':<br />
#* These are the most common, and function as a simplistic automatic spelling corrector, e.g. ''Led Zepplin'' = Led Zeppelin<br />
# '''Variants''':<br />
#* An artist may use several similar names interchangeably without making a distinction, from release to release, e.g. ''Hootie and the Blowfish'' = Hootie & the Blowfish; ''Monty Python's Flying Circus'' = Monty Python<br />
# '''Numbers''':<br />
#* Even if the artist prefers spelled out or numerical form, they may or may not be spelled out by users, e.g. ''The 3 Tenors'' = The Three Tenors<br />
# '''Stylized Names''':<br />
#* Many artists feel a need to spell their names with strange spacing, odd characters and punctuation, etc., e.g. ''NSync'' = 'N Sync<br />
# '''Missing Titles''':<br />
#* Artists add or drop titles, monikers and/or articles from their names, e.g. ''The Sex Pistols'' = Sex Pistols; ''Tiësto'' = DJ Tiësto; ''Cheb Khaled'' = Khaled<br />
# '''Acronyms''':<br />
#* Artists with long and unwieldy names are often better known by their acronyms, and may use them on their release covers, e.g. ''B.D.P.'' = ''BDP'' = Boogie Down Productions<br />
# '''Initials''':<br />
#* Overlaps somewhat with acronyms, but there are sometimes middle initials not generally used in the artist's name, e.g. ''J.S. Bach'' = Johann Sebastian Bach<br />
# '''Incomplete Names''':<br />
#* When credited as "Strauss", it's usually Johan Strauss II and not Richard or one of the others that is intended, e.g. ''Strauss'' = Johan Strauss II<br />
# '''Lead Performers''':<br />
#* Sting is a member of The Police - it is not a collaboration, and the band does not officially include his name in theirs, however compilations often list featured members explicitly by name in this way, e.g. ''Sting & The Police'' = The Police<br />
# '''Misencodings''':<br />
#* Artist names entered in FreeDB using non-UTF-8 encodings; these are somewhat like typos, but in non-Unicode locales, these may in fact be more accurate than an automatic conversion from UTF-8, e.g. ''©PªNÛ'' = Jay Chou (''note hidden soft-hyphen after N in misencoding'')<br />
# '''Localization''':<br />
#* While English-speakers are used to "Tchaikovsky", he is known elsewhere in the world by different spellings, e.g. ''Piotr Ilitch Tchaïkovski'' = Pyotr Ilyich Tchaikovsky<br />
# '''Transliterations''':<br />
#* There are often several ways to transliterate non-Roman characters according to different standards, e.g. ''Jay Chow'' = Jay Chou<br />
# '''"Translated" Names''':<br />
#* Many Asian artists have "English" names in addition to their given "Chinese" or "Japanese" etc. names - in some cases, the artists prefer the English name even in non-English text, e.g. ''Chou Jie Lun'' = Jay Chou<br />
# '''Legal Changes''':<br />
#* Artists are often forced to change their names for legal reasons, sometimes only in part of the world, e.g. ''Yaz'' = Yazoo. See [[edit:1439666|edit 1439666]] for the best (worst?) example. Please consult [[Same Artist With Different Names]] for more information about how to handle such cases, both for individuals and for groups.<br />
<br />
{{ArtistFooter}}<br />
<br />
{{DocumentationFooter|1.0|dmppanda}}<br />
<br />
[[Category:To Be Reviewed]] [[Category:Terminology]] [[Category:Artist]] [[Category:WikiDocs Page]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Style_Council/History&diff=44524
History:Style Council/History
2011-05-13T19:08:44Z
<p>Dupuy: /* Delegate System */ typo</p>
<hr />
<div>=History of the Style Coucil=<br />
''or''<br />
=How the (Old) Style Council did not work=<br />
<br />
The [[Style Council|StyleCouncil]] has a long history of reforms which have led to the current practice, which is documented on the [[Style Council|StyleCouncil]] page. This history is kept here, because it offers some lessons about how things do not work in the [[MusicBrainz]] community. <br />
<br />
==The Style Dudes==<br />
In the past, we had a single Style Dude. This worked very well. The '''Style Dude''' was the the person who oversaw questions of "style," defined as pretty much anything to do with how the data about music is presented and stored in the database. Typical issues are the correct way to capitalize titles, how information about featured artists should be presented, and so forth. <br />
<br />
[[MusicBrainz]] had two Style Dudes, the first being [[User:NeilCafferkey|NeilCafferkey]], who held the job from somewhere in 2001 until [[User:TarragonAllen|TarragonAllen]] took over in 2004. Tarragon resigned in 2005 and it became clear that the job of style dude had grown beyond the job of one person. <br />
<br />
'''Now there is a [[Style Council|StyleCouncil]], which has taken over the role of the Style Dude''' and eliminated the need for a gender-neutral version of the position (Style Dudette, anyone?). <br />
<br />
After a period of slight anarchy concerning the [[Featuring Artist Style Alternative|FeaturingArtistStyleAlternative]], Tarragon temporarlily became Style Dude again from 11/2005 to 01/2006. <br />
<br />
Beginning in January 2006, the [[Style Council|StyleCouncil]] has two 'dudey' positions: a secretary and an Elder.<br />
<br />
==First Formalized Style Council==<br />
<br />
The following section describes the members and their roles in the first Style Council. This has not worked well, mostly because the distribution of roles was not really applicable in practice (is this correct?): <br />
<br />
===Members of the Style Council===<br />
<br />
(a.k.a. [[Style Moderator|StyleModerator]]<code><nowiki></nowiki></code>s) <br />
<br />
====Secretaries (''Ministers of Style'')====<br />
<br />
* [[User:JohnCarter|JohnCarter]] <br />
* [[User:RjMunro|RjMunro]] <br />
* [[User:Dupuy|Dupuy]] <br />
<br />
====Editors====<br />
<br />
* [[User:ClutchEr2|ClutchEr2]] <br />
* [[User:DJKC|DJKC]] <br />
* [[User:Gecks|Gecks]] <br />
* [[User:Keschte|Keschte]] <br />
* [[Mcymd]] <br />
* [[User:MichelleW|MichelleW]] <br />
* [[User:Nikki|Nikki]] <br />
* [[User:Steinbdj|Steinbdj]] <br />
* [[User:WolfSong|WolfSong]] <br />
<br />
''editor-without-portfolio'' (ombudsman) <br />
* [[User:DonRedman|DonRedman]] <br />
<br />
====Emeriti====<br />
<br />
* [[User:TarragonAllen|TarragonAllen]] <br />
* [[User:NeilCafferkey|NeilCafferkey]] <br />
<br />
===Areas of specialization===<br />
<br />
# [[Metadata|MetaData]] -- [[User:Dupuy|Dupuy]] <br />
## [[Advanced Relationship Type|AdvancedRelationshipType]]<code><nowiki></nowiki></code>s (basic advanced relationships) -- [[User:WolfSong|WolfSong]] / [[User:Gecks|Gecks]] <br />
## [[Advanced Relationship Attribute|AdvancedRelationshipAttribute]]<code><nowiki></nowiki></code>s (instruments, etc.) -- [[Mcymd]] <br />
## [[Advanced Relationship Usage|AdvancedRelationshipUsage]] (what to represent with advanced relationships, what to omit) -- [[User:JohnCarter|JohnCarter]] <br />
## [[Other Meta Data|OtherMetaData]] ([[Extra Title Information Style|ExtraTitleInformation]], artist comments, annotations) -- [[User:RjMunro|RjMunro]] <br />
<br />
# [[Data Presentation|DataPresentation]] -- [[User:RjMunro|RjMunro]] <br />
## [[Formatting Style|FormattingStyle]] ([[Capitalization Standard|CapitalizationStandard]], punctuation, etc.) -- [[User:Keschte|Keschte]] <br />
## [[Internationalization|InterNationalization]] (language stuff) -- [[User:Nikki|Nikki]] / [[User:Dupuy|Dupuy]] <br />
## [[Non Musical Style|NonMusicalStyle]] (data cds tracks, silence, etc.) <br />
## [[Special Case Style|SpecialCaseStyle]] ([[Various Artists|VariousArtists]] releases, [[Special Purpose Artist|SpecialPurposeArtist]]<code><nowiki></nowiki></code>s) -- MichelleW <br />
<br />
# [[Genre Style|GenreStyle]] -- [[User:JohnCarter|JohnCarter]] <br />
## [[Classical Style Guide|ClassicalStyleGuide]] (orchestral & classical music) -- [[User:ClutchEr2|ClutchEr2]] / [[User:WolfSong|WolfSong]] <br />
## [[Soundtrack Style|SoundtrackStyle]] (musicals, anime, & movie soundtracks) -- [[User:Steinbdj|Steinbdj]] <br />
## [[Electronic Style|ElectronicStyle]] (electronica, DJ & fan remixes, mash-ups, etc.) -- [[User:Gecks|Gecks]] <br />
## [[Asian Style|AsianStyle]] (J-pop, K-pop, C-pop, etc.) -- [[User:DJKC|DJKC]] <br />
<br />
==Delegate System==<br />
<br />
Then (when?) the strict distribution of roles was abolished in favor of a system in which people would become delegates for a specific [[Style Issue|StyleIssue]] on a case by case basis. This did not work well, mostly because the delegates were not really motivated to work hard on issues that someone else had reported. <br />
<br />
The Delegate system was never really fixed. But there was general consensus about more or less these points: <br />
# The Style Council will have a '''leader'''. This leader will act as a benevolent dictator and ''make decisions'', but should not do any of the actual work involved with the issues discussed. <br />
# The Council will consist of members, who agree to become '''delegates''' for a specific [[Style Issue|StyleIssue]]. Once a person has become a delegate, she/he is responsible for the progress of this issue according to the process described in [[How To Solve A Style Issue|HowToSolveAStyleIssue]]. That means that a delegate is responsible to ''do the actual work'', if nobody else does it. Delegates should be assigned to [[Style Issue|StyleIssue]]<code><nowiki></nowiki></code>s in a rotating fashion to avoid burnout. <br />
# All subscribers to the [[Style Mailing List|StyleMailingList]] form an '''interested public''' and take part in discussions about [[Style Guideline|StyleGuideline]]<code><nowiki></nowiki></code>s. <br />
# Each [[Style Issue|StyleIssue]] has a person who raised it. This '''proposer''' also has some responsibilities; see below. <br />
<br />
The roles of these three people are distributed like this: <br />
<br />
====The Proposer's Job is to====<br />
<br />
* Open the issue in the [[Bug Tracker|BugTracker]] and start a thread about it on the [[Style Mailing List|StyleMailingList]]. <br />
* If the proposal is a complex one, create a [[Wiki Page|WikiPage]] describing the initial issue. <br />
* Collaborate with the delegate on summaries etc. <br />
* In some tough cases it might be necessary or at least helpful to summarize the finally proposed change and make sure it addresses all objections raised on the [[Style Mailing List|StyleMailingList]]. <br />
<br />
====The Leader's Job is to====<br />
<br />
* Make sure that an issue is assigned to a delegate who then has the responsibility to do the ''work'' involved with it. The leader her/himself should never do the actual work, to prevent burnout as we experienced it with the Style Dudes. <br />
* Check that all important aspects of the issue have been touched <br />
** impact on existing data, including edge cases and Various Artists albums (an often forgotten problem area). <br />
** conflicts with other style rules. <br />
** editor time required to implement the change. <br />
** developer time required to implement the change (if any), keeping in mind that developer time is limited and we wish to avoid wasting their time if at all possible. <br />
** impact on paying clients. <br />
** can the change be automated? <br />
<br />
* Make a decision. This can be just a statement, that apparently consensus has been reached or that the outcome of a vote is positive/negative. It can be a final and dictatorial decision. <br />
<br />
====The Delegate's Job is to====<br />
<br />
* Acompany any documentation in the wiki in a way that makes sure that a neutral description of the issue is available during discussion. This means that they must be prepared to write such a summary, should no one else do that. <br />
* Write up a final version of the proposed change on the wiki. <br />
* When a decision has been reached, blog about the proposed change (ot should this be done by the leader?) <br />
* Finally, make sure the change is implemented. Agian this means to be prepared to edit the wiki or the AR definition or to collaborate with developers.<br />
<br />
==Approval Mechanism==<br />
<br />
When it became clear, that nobody was willing to do all this work if they had not "an itch" that scratched them, the job of fixing a [[Style Issue|StyleIssue]] was laid upon the person requesting the fix. As a means of quality assurance a [[Style Secretary|StyleSecretary]] was appointed. His job was to require certain formalisms that should prevent bad changes to the [[Style Guideline|StyleGuideline]]<code><nowiki></nowiki></code>s to come through. <br />
<br />
This system did not work well at all. Everything was pushed to the secretary and he became the bottleneck of the whole process: <br />
# You need a formal approval from the secretary before you change anything official. <br />
# If you are unhappy with a decision of the Secretary, publicly call upon the Elder. Similarly, if no consensus can be reached, the Secretary calls upon the Elder <br />
# If you want an approval from the Secretary do this: <br />
#* Make sure there is an [http://bugs.musicbrainz.org/report/8 Active Ticket for the Style Issue] in the [[Bug Tracker|BugTracker]]. <br />
#* Let the Style Council reach consensus. <br />
#* Make sure the requirements on the [[Checklist For Style Changes|ChecklistForStyleChanges]] are met. <br />
#* Send a mail to the [[Style Mailing List|StyleMailingList]] that summarizes the points above and asks for an OK by the Secretary. <br />
<ul><li style="list-style-type:none">This could even be more complicated: <br />
#* * Create a "request for approval" ticket in the [[Bug Tracker|BugTracker]]. <br />
#* * Refer to the bug or improvement that you want to fix and <br />
#* * link to a page or mail that exactly describes the fix and goes through the [[Checklist For Style Changes|ChecklistForStyleChanges]]. <br />
#* * Assign the ticket to you and accept it. <br />
<br />
</ul>The secretary will wait 24 hours for a veto. If nothing happens he will close the ticket as "fixed". That means you have the approval. If he closes it as "wontfix", your request has been rejected. <br />
<br />
<ul><li style="list-style-type:none">The Secretary should give you an OK and maybe a date to apply the change. If no consensus could be reached or somebody objects, the Elder has to jump in and make a decision. <br />
</ul><br />
<br />
===How to Make a Change===<br />
<br />
If you want to make a change, keep in mind that this means you will have to do all this: <br />
* Make the change (e.g. to the [[Advanced Relationship Type|AdvancedRelationshipType]] tree) yourself, or collaborate jointly with the developers. <br />
* Document the changes on the wiki. <br />
* Blog about the change and/or notify people on the [[Users Mailing List|UsersMailingList]] <br />
<br />
There is an old page that describes [[How To Propose New Guidelines|HowToProposeNewGuidelines]], but this needs to be updated. <br />
<br />
==Conclusions==<br />
<br />
These experiences have led to some important lessons. <br />
* First, the current process of the [[Style Council|StyleCouncil]] (documented on that page), which has its quirks, is relatively slow but works astonishingly well. <br />
* Second, a very fundamental rule for "organizational development" in the [[MusicBrainz]] community: <br />
<ul><li style="list-style-type:none">'''Rules follow practice''' <br />
</ul>This means, that we establish a practice by improvising and discussing it first and then, when it seems to work, we write up the rules, not the other way around. <br />
<br />
= The New Style Council = <br />
<br />
==Changing of the guard, August 2008==<br />
<br />
Through August 2008, the role of ''secretary'' was to be the elder's right hand. He does the non-controversial daily work, but cannot make actual rulings. This was a rotating position filled by [[User:DonRedman|DonRedman]], who wanted to step off in April 2006 (per [[Style Council|StyleCouncil]] at the time). By 2008, [[User:DonRedman|DonRedman]] wasn't able to be very active in style issues. <br />
<br />
On June 2008, [[User:RobertKaye|RobertKaye]] put out a call for a new style leader. "The style guideline process has been stuck in neutral for quite some time and I was hoping that Panda could take over this role from Don Redman (who had been swallowed up by real life quite some time ago), but real life is about to swallow Panda for the foreseeable future. Thus, I start the search for a new leader of the Style Council once again." [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2008-June/006987.html (mb-style) Looking for a new style leader], [http://blog.musicbrainz.org/?p=332 (blog) Looking for a new style leader!]. <br />
<br />
Some discussion continued on [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2008-July/007002.html mb-style in July 2008]. Two posts which pointed to the current [[Style Council|StyleCouncil]] thinking were [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2008-July/007011.html RobertKaye's message of Fri Jul 11 06:42:33 UTC 2008] and [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2008-July/007025.html JimDeLaHunt's message of Fri Jul 25 07:01:37 UTC 2008]. <br />
<br />
On Aug 4 2008, [[User:RobertKaye|RobertKaye]] announced [[User:JimDeLaHunt|JimDeLaHunt]] as the new style leader.[http://blog.musicbrainz.org/?p=339 (blog) Jim DeLaHunt is our new style leader!], [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2008-August/007047.html mb-style thread]. <br />
<br />
==Changing of the guard, June 2009==<br />
<br />
Sadly, JimDeLaHunt stepped down on May 4th, leaving MusicBrainz without a style leader again. <br />
<br />
On Jun 10 2009, [[User:RobertKaye|RobertKaye]] appointed [[User:BrianSchweitzer|BrianFreud]] and [[User:kuno|kuno]] as style leaders ([http://chatlogs.musicbrainz.org/2009/2009-06/2009-06-10.html#T20-44-43-776298 irc log]).<br />
<br />
==Changing of the guard, August 2010==<br />
<br />
On August 13 2010, [[User:RobertKaye|RobertKaye]] appointed [[User:Nikki|nikki]] as the [http://blog.musicbrainz.org/?p=629 new Style Leader] to replace [[User:BrianFreud|BrianFreud]]. <br />
<br />
[[Category:Philosophy]] [[Category:History]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:FreeDB_Gateway&diff=30547
History:FreeDB Gateway
2009-06-04T20:45:09Z
<p>Dupuy: /* Application instructions */ add KDE system settings</p>
<hr />
<div>The MusicBrainz to FreeDB gateway ('''mb2freedb''') is a service that allows [[FreeDB]] clients to access MusicBrainz data through the [http://ftp.freedb.org/pub/freedb/misc/freedb_CDDB_protcoldoc.zip FreeDB protocol].<br />
<br />
==How to Access It==<br />
<br />
The mb2freedb gateway is setup at the Oregon State University Open Source Lab and can be accessed using the following settings:<br />
<br />
<pre><br />
host freedb.musicbrainz.org<br />
via http<br />
port 80<br />
path /~cddb/cddb.cgi<br />
</pre><br />
<br />
It should be just a matter of changing the host and possibly the path, as the other settings are standard for most applications.<br />
<br />
===Application instructions===<br />
<br />
* Exact Audio Copy (EAC): To access the "FreeDB / Database Options" page either press F12 or click the toolbar button EAC and scroll down to "FreeDB / Database Options". On the FreeDB Tab you will see the entry "FreeDB server". Enter "<code><nowiki>http://freedb.musicbrainz.org:80/~cddb/cddb.cgi</nowiki></code>" and click OK. That's it! (If you use version 0.95, see [http://blog.musicbrainz.org/?p=311 additional instructions]).<br />
* MediaMonkey: Navigate to Tools >> Options.. then General >> Network (Proxy & FreeDB). Set the protocol to "HTTP" and host to "freedb.musicbrainz.org". User name and domain remain optional. If you receive ''socket 11004'' errors, ensure that MediaMonkey has access out either your Windows or 3rd party firewall.<br />
* KDE: To set the CDDB preferences used by various KDE applications, open System Settings, select the Advanced tab, and double click on CDDB Retrieval. Make sure that you have checked Enable MusicBrainz lookup so that MusicBrainz is used directly if possible; then set the Freedb server to freedb.musicbrainz.org (the other settings default values are fine).<br />
<br />
==Limitations==<br />
<br />
* Because the gateway is running on a mirror server, any changes made on the main MusicBrainz site will take time to propagate, normally this is no more than a hour after the edit has been applied, but occasionally it can take longer.<br />
* CDs with data tracks such as videos are supported, but will return one less track than normally expected from FreeDB. This might cause a problem with some clients.<br />
* The genre will always be set to ''Unknown''.<br />
* The year is always set to the first one on the matching database entry. As re-releases with the same track listing are always combined with the original, the year returned might not match that of the disc in hand.<br />
* Data is always returned in UTF-8 to cater for extended character sets. For most albums, this isn't a problem. But, for full compatibility a FreeDB client that supports protocol version 6 is required. If the characters look garbled in your FreeDB enabled application, this is probably the reason why.<br />
* Obviously only albums on MusicBrainz with [[Disc ID]]s attached will return matches!<br />
** If the album you want to check doesn't have your disc ID attached, follow the process on [[How To Add Disc IDs]] to add it.<br />
<br />
==Bug Reporting/Questions==<br />
<br />
Our [[Bug Tracker]] has a component for mb2freedb, please report all problems there, including as much detail as possible:<br />
* Problem seen<br />
* Software and version<br />
* The release url, eg: [http://musicbrainz.org/release/b84ee12a-09ef-421b-82de-0441a926375b.html http://musicbrainz.org/release/b84ee12a-09ef-421b-82de-0441a926375b.html]<br />
* The FreeDB ID if you have it<br />
* Your IP address if you know it<br />
* approximate date/time, preferably in GMT/UTC so the logs can be checked.<br />
<br />
If you want to play with the source code, it's here: [http://bugs.musicbrainz.org/browser/mb2freedb/trunk/ http://bugs.musicbrainz.org/browser/mb2freedb/trunk/]<br />
<br />
{{WikiDocsPageMonitoredBy|murdos}}<br />
[[Category:To Be Reviewed]] [[Category:Products]] [[Category:WikiDocs Page]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=User:Dupuy/OfficialBio&diff=18161
User:Dupuy/OfficialBio
2008-04-21T16:07:33Z
<p>Dupuy: no longer subscribed to thousands of artists (Imported from MoinMoin)</p>
<hr />
<div>=Alexander Dupuy=<br />
<br />
{| border="1"<br />
|-<br />
| [[Image:05_shirtlogo_web3.gif]] || '''Alexander Dupuy''' [ MB: [http://musicbrainz.org/show/user/?username=dupuy dupuy] | IRC: dupuy | Wiki: [[User:Dupuy|Dupuy]] | Last.fm: - | [http://yourweb Web] ] <br />
|-<br />
| Alex organized the MusicBrainz [[Style Council|StyleCouncil]], responsible for editing the style guidelines used by moderators when entering and updating the data in MusicBrainz. He led an effort to correct the many foreign language entries that were [[Misencoding FAQ|misencoded]], and largely as a result is one of our [http://musicbrainz.org/topmods.html top editors]. Although there is no official top-20 list for this, for a while, Alex was the moderator with the [http://musicbrainz.org/user/subscriptions.html?user=38240 most subscribed artists] (> 2100) (the vast majority being [[International Artists|InternationalArtists]]). <br />
|-<br />
| Having worked for many years as a researcher in networks at [http://www1.cs.columbia.edu/ Columbia University] (his e-mail address there is over 20 years old), Alex has spent most of the last decade as a network programmer at a number of start-ups in the [http://wfmu.org/ WFMU] listening area (a.k.a. New York City), except for a few years living in the [http://www.stetson.edu/~rsitler/TodosSantos/ Guatemalan town of Todos Santos]. Despite his programming background, Alex has somehow managed to avoid writing a single line of code for MusicBrainz in any of the innumerable hours he has spent working on MusicBrainz projects. <br />
|-<br />
| Alex is interested in all kinds of music from around the world, and his hobbies include linguistics and internationalization. He has studied Spanish, French, Portuguese, German, Japanese, Arabic, Turkish and Mam Maya; and is somewhat fluent in the first three, but can only puzzle out bits in the rest. <br />
|}<br />
<br />
[[Category:Bio]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Folksonomy_Tagging&diff=7658
History:Folksonomy Tagging
2007-09-25T22:26:19Z
<p>Dupuy: fix link (Imported from MoinMoin)</p>
<hr />
<div><br />
Follksonomy Tagging is a new feature which is currently being develloped (Sept 2007). Users will be able to add "tags" to [[MusicBrainz]] entities like on [http://last.fm last.fm] or [http://del.icio.us del.icio.us]. <br />
<br />
See the release notes at [[Server Release Notes/200709 XX|ServerReleaseNotes/200709XX]] for current status of this feature. <br />
<br />
----<br />
<br />
<br />
<br />
==Some Musings about Tagging==<br />
<br />
These are some thoughts about tagging, started by [[User:DonRedman|DonRedman]]. I put them here, because I do not have the time to keep up with a [[Mailing List|MailingList]] discussion. So read it ans enhance it, or let it rot :-) <br />
<br />
IMHO there are a few things MB should do, if you want tagst to work: <br />
<br />
First, make tags '''navigable'''. Display them nicely and unobstrusively on the entity pages (no separate page!), so that people can browse through MB by clicking on tags, artists, albums, etc. A small tag cloud on each artist page should do the trick. If a user is logged in, show her both her own tags and everybody's tags. I believe you can copy a lot from last.fm's layout here. <br />
<br />
The most important thing is to make tags usable. Tagging only works if it creates an information ecology. [[MusicBrainz]] is only one half of the ecology. The other half is the user at home. So what would people use tags for ''at home'' and ''egoistically for themselves''? <br />
* '''Sorting music:''' To enable people sorting their music according to their own or everybody's tags, the [[Picard Tagger|PicardTagger]] (the old one or [[Picard Qt|PicardQt]]) should be able to fetch my tags and rename/move files according to the tag. The difficulty is to determine which one of the tags to use. Maybe a user could select a primary tag for each entity. If the lists of tags you store are order sensitive that this could just be the first entry. <br />
* '''Tagging music:''' I mean tagging as in ID3 tags. That will probably turn out to be a major chalenge. How can you store MB folksonomy tags in music files in a way that is ''usable''? <br />
<ul><li style="list-style-type:none">In this case usable means that the major music players (Winamp, iTunes, foobar, and yes ideally Microsoft Media Player. Don't know about Linux) should be able to read the tags. I have no idea about their special/proprietary tagging schemes, but they should all be supported. Probably by plugins to Picard. <br />
</ul><br />
* It turns out that there might be a very simple standard, that ''all'' players support and which could make folksonomy tags really useful: '''Playlists'''. <br />
<ul><li style="list-style-type:none">Imagine a small app that crawls all my music files, reads the MBIDs, fetches either my tags or everybody's tags for these files and builds playlists from them. This way I could listen to all my 'chilly' music (using the player of my choice on any system). Most importantly this would create a dynamic information ecology in which users add tags to MB, download them with the appp, use them, correct them or add more, etc. This dynamics would give MB tons of RFEs, Bug reports and most importantly ''tags''. I know that there are many pitfalls on the way to such an ecology. One of them might be bandwith. But hey, MB can make this a subscriber feature (sorry we cannot alow more than x requests per minute unless you pay for your bandwidth). I mean, last.fm makes me pay 30 Euros per year for a similar feature, and my tags are not free. 'My tags'on last.fm are ''theirs''. <br />
</ul><br />
<br />
I think you get the idea. I am not set on the playist idea. But I seriously believe that folksonomy tagging will only lift off if you provide some kind of usable feature on the side of the user at home and enable a feedback loop from MB to the user and back. -- [[User:DonRedman|DonRedman]] 12:35, 23 September 2007 (UTC) (Please feel free to correct, expand, edit this text as boldly as you like, :-) rather than making it an unreadable dicussion.) <br />
<br />
==Using folksonomy tags for personal collections/wishlists==<br />
<br />
Something that just occurred to me while replying to a random request for help, is that we could use the folksonomy tagging support to implement the often-requested "I have this album" / "I want this album" feature. <br />
<br />
There's no need to have voting and whatever on the contents of my personal collection and wishlist - while the current (still-in-beta) interface for the folksonomy tags isn't ideal for this, I think the back-end database support is. And we can use the forthcoming support right away, with some simple conventions. <br />
<br />
If you have a release, tag it with "owned-<modname>" (e.g. I would use "owned-dupuy"); if you want it, use "wanted-<modname>" instead. <br />
<br />
Once there's some search capability for tags, you should be able to search your collection and wishlist. You can (sort-of) do this already with the current (still-in-beta) interface by using the [http://test.musicbrainz.org/show/tag/?tag=owned-dupuy http://test.musicbrainz.org/show/tag/?tag=owned-dupuy] URL interface (is there a way to add this to the search things on the left sidebar?). <br />
<br />
If this seems to be popular, the next next server release could treat these "collection tags" specially: <br />
* adding buttons ("I have this", "I want this") to release page that add the corresponding tag <br />
* filtering these tags from the standard tags view and displaying them separately <br />
* preventing moderator "luser" from adding "owned-otheruser" and mapping user-entered "owned" and "wanted" to "wanted-luser" automatically <br />
* maybe using a namespace-reserved character (like ':') for collection tags, e.g. "owned:dupuy" to simplify this special treatment (we'd want to mass-convert the database if this is done) <br />
<br />
[[User:Dupuy|@alex]] 23:00, 25 September 2007 (UTC) <br />
[[Category:To Be Reviewed]] [[Category:Development]] [[Category:Advanced Relationships]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Folksonomy_Tagging&diff=7659
History:Folksonomy Tagging
2007-09-25T21:00:41Z
<p>Dupuy: added note on using folksonomy tags for collections (Imported from MoinMoin)</p>
<hr />
<div><br />
Follksonomy Tagging is a new feature which is currently being develloped (Sept 2007). Users will be able to add "tags" to [[MusicBrainz]] entities like on [http://last.fm last.fm] or [http://del.icio.us del.icio.us]. <br />
<br />
See the release notes at [[Server Release Notes/200709 XX|ServerReleaseNotes/200709XX]] for current status of this feature. <br />
<br />
----<br />
<br />
<br />
<br />
==Some Musings about Tagging==<br />
<br />
These are some thoughts about tagging, started by [[User:DonRedman|DonRedman]]. I put them here, because I do not have the time to keep up with a [[Mailing List|MailingList]] discussion. So read it ans enhance it, or let it rot :-) <br />
<br />
IMHO there are a few things MB should do, if you want tagst to work: <br />
<br />
First, make tags '''navigable'''. Display them nicely and unobstrusively on the entity pages (no separate page!), so that people can browse through MB by clicking on tags, artists, albums, etc. A small tag cloud on each artist page should do the trick. If a user is logged in, show her both her own tags and everybody's tags. I believe you can copy a lot from last.fm's layout here. <br />
<br />
The most important thing is to make tags usable. Tagging only works if it creates an information ecology. [[MusicBrainz]] is only one half of the ecology. The other half is the user at home. So what would people use tags for ''at home'' and ''egoistically for themselves''? <br />
* '''Sorting music:''' To enable people sorting their music according to their own or everybody's tags, the [[Picard Tagger|PicardTagger]] (the old one or [[Picard Qt|PicardQt]]) should be able to fetch my tags and rename/move files according to the tag. The difficulty is to determine which one of the tags to use. Maybe a user could select a primary tag for each entity. If the lists of tags you store are order sensitive that this could just be the first entry. <br />
* '''Tagging music:''' I mean tagging as in ID3 tags. That will probably turn out to be a major chalenge. How can you store MB folksonomy tags in music files in a way that is ''usable''? <br />
<ul><li style="list-style-type:none">In this case usable means that the major music players (Winamp, iTunes, foobar, and yes ideally Microsoft Media Player. Don't know about Linux) should be able to read the tags. I have no idea about their special/proprietary tagging schemes, but they should all be supported. Probably by plugins to Picard. <br />
</ul><br />
* It turns out that there might be a very simple standard, that ''all'' players support and which could make folksonomy tags really useful: '''Playlists'''. <br />
<ul><li style="list-style-type:none">Imagine a small app that crawls all my music files, reads the MBIDs, fetches either my tags or everybody's tags for these files and builds playlists from them. This way I could listen to all my 'chilly' music (using the player of my choice on any system). Most importantly this would create a dynamic information ecology in which users add tags to MB, download them with the appp, use them, correct them or add more, etc. This dynamics would give MB tons of RFEs, Bug reports and most importantly ''tags''. I know that there are many pitfalls on the way to such an ecology. One of them might be bandwith. But hey, MB can make this a subscriber feature (sorry we cannot alow more than x requests per minute unless you pay for your bandwidth). I mean, last.fm makes me pay 30 Euros per year for a similar feature, and my tags are not free. 'My tags'on last.fm are ''theirs''. <br />
</ul><br />
<br />
I think you get the idea. I am not set on the playist idea. But I seriously believe that folksonomy tagging will only lift off if you provide some kind of usable feature on the side of the user at home and enable a feedback loop from MB to the user and back. -- [[User:DonRedman|DonRedman]] 12:35, 23 September 2007 (UTC) (Please feel free to correct, expand, edit this text as boldly as you like, :-) rather than making it an unreadable dicussion.) <br />
<br />
==Using folksonomy tags for personal collections/wishlists==<br />
<br />
Something that just occurred to me while replying to a random request for help, is that we could use the folksonomy tagging support to implement the often-requested "I have this album" / "I want this album" feature. <br />
<br />
There's no need to have voting and whatever on the contents of my personal collection and wishlist - while the current (still-in-beta) interface for the folksonomy tags isn't ideal for this, I think the back-end database support is. And we can use the forthcoming support right away, with some simple conventions. <br />
<br />
If you have a release, tag it with "owned-<modname>" (e.g. I would use "owned-dupuy"); if you want it, use "wanted-<modname>" instead. <br />
<br />
Once there's some search capability for tags, you should be able to search your collection and wishlist. You can (sort-of) do this already with the current (still-in-beta) interface by using the [http://test.musicbrainz.org/show/?tag=owned-dupuy http://test.musicbrainz.org/show/?tag=owned-dupuy] URL interface (is there a way to add this to the search things on the left sidebar?). <br />
<br />
If this seems to be popular, the next next server release could treat these "collection tags" specially: <br />
* adding buttons ("I have this", "I want this") to release page that add the corresponding tag <br />
* filtering these tags from the standard tags view and displaying them separately <br />
* preventing moderator "luser" from adding "owned-otheruser" and mapping user-entered "owned" and "wanted" to "wanted-luser" automatically <br />
* maybe using a namespace-reserved character (like ':') for collection tags, e.g. "owned:dupuy" to simplify this special treatment (we'd want to mass-convert the database if this is done) <br />
<br />
[[User:Dupuy|@alex]] 23:00, 25 September 2007 (UTC) <br />
[[Category:To Be Reviewed]] [[Category:Development]] [[Category:Advanced Relationships]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Server_Release_Notes/20071014&diff=26273
History:Server Release Notes/20071014
2007-09-25T20:47:07Z
<p>Dupuy: spelling (Imported from MoinMoin)</p>
<hr />
<div>=Changelog for the 2007-10-07 Server Release=<br />
<br />
List of new features and bug-fixes in the 2007-10-07 server release. Please help us test these changes/features on our [http://test.musicbrainz.org test server]. <br />
<br />
==New Folksonomy "Tagging" Feature==<br />
<br />
This release will include support for [[Folksonomy Tagging|FolksonomyTagging]] for artists, labels, releases and tracks. Each of these entities now has a "Tag" link associated where the user can enter their own tags for an entity and each entity will then have a tag cloud that lets users view the tags most applied to a given entity. Given that applying these tags is highly subjective, these tag additions will ''not'' be subject to peer review via the edit voting system. Each person applies tags to entities (others can't see which tags a specific user has applied) and the system then aggregates all the tags for a collective view of all the tags applied to an entity. For instance, see the [http://test.musicbrainz.org/show/artist/tags.html?id=65 tags applied to artist Portishead]. <br />
<br />
Right now the UI still needs some refinements and we're keen to get your input on it: <br />
* Is the tagging feature too buried? Right now you need to click on the "Tags" link before you see the tags for an artist and can tag the artist yourself. <br />
* How does the [http://test.musicbrainz.org/show/tag/?tag=down-tempo tag display] feature look? Any feedback there? <br />
<br />
Tags are comma separated and only alphanumeric (word) characters, '-' and <space> are allowed for making tags. You can apply as many tags as you want in one operation on the web site. <br />
<br />
The [[XML Web Service|XMLWebService]] API has been extended to support tag submission. To apply tags for a given entity, do an HTTP POST to a URL formatted like this: <br />
<ul><li style="list-style-type:none">[http://test.musicbrainz.org/ws/1/tag/?id=8f6bd1e4-fbe1-4f50-aa9b-94c450ec0f11&entity=artist&type=xml&tags=waga,poly,klepto http://test.musicbrainz.org/ws/1/tag/?id=8f6bd1e4-fbe1-4f50-aa9b-94c450ec0f11&entity=artist&type=xml&tags=waga,poly,klepto] <br />
</ul><br />
<br />
This will apply the tags 'waga', 'poly' and 'klepto' to artist Portishead and overwrite any tags you may have applied previously. This will require an HTTP authorization with your editor name and password. This can be done via the command line and the wget program like so: <br />
<ul><li style="list-style-type:none">wget --user=<editor name> --password=<password> --post-data=id=8f6bd1e4-fbe1-4f50-aa9b-94c450ec0f11\&entity=artist\&type=xml\&tags=foo,bar,baz [http://test.musicbrainz.org/ws/1/tag http://test.musicbrainz.org/ws/1/tag] <br />
</ul><br />
<br />
This is MusicBrainz' first foray into subjective metadata and its bound to ruffle some (more) feathers in the community. At this point in time this new tagging feature is a test project. If it turns out that this test fails for some reason and we can't fix it, we will remove this feature at a later point in time. <br />
<br />
If you have feedback for this new feature, please enter a bug report or enhancement request in our [http://bugs.musicbrainz.org/newticket bug tracker]. <br />
<br />
==New Features==<br />
<br />
* Allow [[Subscribe To Editor|subscribing to editors]]. <br />
* Allow editing of AR end-points (i.e. moving AR from one entity to another). <br />
* New page for artist to track and release relationships: the link is titled "''Appears on''" on artist page. <br />
* Add ARs to multiple tracks on a release (#[[Ticket:2292|2292]]) <br />
* PUID reports. (#[[Ticket:1917|1917]]) <br />
* PureVolume url AR type detection. (#[[Ticket:2724|2724]]) <br />
* Custom release sorting on the label page. <br />
* "Cover art" url AR type detection. <br />
* After creating an AR, redirect to the 'current' entity, instead of the first one. (#[[Ticket:2722|2722]]) <br />
* Automatically remove spaces and hyphens from barcodes. (#[[Ticket:2635|2635]]) <br />
* Improve conditions.html overview. (#[[Ticket:2715|2715]]) <br />
* Guess Case: Convert "blank" to "[silence]". (#[[Ticket:2103|2103]]) <br />
* Guess Case: Convert "Ver." to "version". (#[[Ticket:2001|2001]]) <br />
* [[JavaScript]] version of "Change Direction" for [[Edit Relationship Edit|EditRelationshipEdit]]. (#[[Ticket:2837|2837]]) <br />
* Make non-[[WikiDocs Page|WikiDocsPage]]<code><nowiki></nowiki></code>s look like normal [[WikiDocs Page|WikiDocsPage]]<code><nowiki></nowiki></code>s. (#[[Ticket:1962|1962]]) <br />
* Edit note pop-up and text field are too small. (#[[Ticket:2441|2441]]) <br />
* [http://musicbrainz.org/edit/wikitransclusion/transclusion.html Wiki Transclusion Table] is now viewable by non-[[Transclusion Editor|TransclusionEditor]]<code><nowiki></nowiki></code>s. (#[[Ticket:2988|2988]]) <br />
* JavaScript versions of 'Show full lists'/'Show reduced lists' buttons on edit language/script page. <br />
* A comment field for cancelling edits. (#[[Ticket:2737|2737]]) <br />
* Don't compact ARs on the track page. (#[[Ticket:2799|2799]]) <br />
* Automatically change format of Discogs URLs. (#[[Ticket:2938|2938]]) <br />
* Display of pending edits on DiscIDs on release details page. (#[[Ticket:2823|2823]]) <br />
* Allow edit notes to identify [[WikiDocs Page|WikiDocsPage]] links using the following syntax: <code><nowiki>"[SomeWikiDocPage]"</nowiki></code> or <code><nowiki>"doc:SomeWikiDocPage"</nowiki></code>. See [[Edit Note Syntax|EditNoteSyntax]]. (#[[Ticket:3014|3014]]) <br />
* Paginated subscriptions. (#[[Ticket:2428|2428]]) <br />
* "Keep Editing" action now remembers edit notes. (#[[Ticket:3020|3020]]) <br />
* [http://bugs.musicbrainz.org/query?status=closed&milestone=Server+2007-10-07&type=enhancement&order=priority complete list of fixed enhancements] <br />
<br />
==Fixed Bugs==<br />
<br />
* Don't double HTML-encode values in hidden inputs. (#[[Ticket:2726|2726]]) <br />
* Removed broken links to (non-existant) TRM reports. <br />
* Add release preview page shouldn't display data quality. (#[[Ticket:2654|2654]]) <br />
* Duplicate error message for inc parameter. (#[[Ticket:2692|2692]]) <br />
* Guess Case: Fixed hanlding of 'pres' and 'presents' in artist names. (#[[Ticket:2215|2215]]) <br />
* Guess Case: "orchestral" [[Extra Title Information|ExtraTitleInformation]] shouldn't be capitalized. (#[[Ticket:2759|2759]]) <br />
* Guess Case: Don't convert '3 In' (with a space) to '3"'. (#[[Ticket:2191|2191]]) <br />
* Guess Case: Expand Volume (Vol.) and Part (Pt.) numbers with subtitles. (#[[Ticket:2805|2805]]) <br />
* Wrong wording in private message copy (when using the option "Send me a copy to my e-mail address"). (#[[Ticket:2826|2826]]) <br />
* Annotation history: show edits link broken. (#[[Ticket:2835|2835]]) <br />
* Tagger links on artist view are malformed. (#[[Ticket:2819|2819]]) <br />
* HTML error on front page. (#[[Ticket:2796|2796]]) <br />
* Country of label isnt retained when editing label. (#[[Ticket:2794|2794]]) <br />
* Broken link to annotation history on the release page. (#[[Ticket:2832|2832]]) <br />
* Check for label ARs in the artist cleanup script. (#[[Ticket:2814|2814]]) <br />
* Error in handling track length edits. (#[[Ticket:2887|2887]]) <br />
* Display [[Transclusion Editor|TransclusionEditor]] privilege on editor profile. (#[[Ticket:3000|3000]]) <br />
* Drop of some products pages already migrated to [[WikiDocs]]. (#[[Ticket:2928|2928]]) <br />
* Prevent cat # from wrapping in label view. (#[[Ticket:2725|2725]]) <br />
* Fixed the 'Back to form' button while selecting a label. (#[[Ticket:2736|2736]]) <br />
* Fixed counts of hidden ARs. (#[[Ticket:2035|2035]], #[[Ticket:1464|1464]]) <br />
* Display rounded track durations. <br />
* [http://bugs.musicbrainz.org/query?status=closed&milestone=Server+2007-10-07&type=bug&order=priority complete list of fixed bugs] <br />
<br />
==Search Changes==<br />
<br />
* Only bug fixes have been applied to the search system. See the [http://bugs.musicbrainz.org/query?status=closed&component=MusicBrainz+Server+Search&milestone=Server+2007-10-07&order=priority list of closed search bugs] for details. <br />
<br />
==Web Service Changes==<br />
<br />
* See Tagging description <br />
<br />
==Schema Changes==<br />
<br />
For the exact details on how the schema is going to change for this release, please examine these files: <br />
* [http://bugs.musicbrainz.org/browser/mb_server/trunk/admin/sql/updates/20070622-1.sql http://bugs.musicbrainz.org/browser/mb_server/trunk/admin/sql/updates/20070622-1.sql] <br />
* [http://bugs.musicbrainz.org/browser/mb_server/trunk/admin/sql/updates/20070719-1.sql http://bugs.musicbrainz.org/browser/mb_server/trunk/admin/sql/updates/20070719-1.sql] <br />
* [http://bugs.musicbrainz.org/browser/mb_server/trunk/admin/sql/updates/20070813-1.sql http://bugs.musicbrainz.org/browser/mb_server/trunk/admin/sql/updates/20070813-1.sql] <br />
* [http://bugs.musicbrainz.org/browser/mb_server/trunk/admin/sql/updates/20070921-1.sql http://bugs.musicbrainz.org/browser/mb_server/trunk/admin/sql/updates/20070921-1.sql] <br />
<br />
These files will be combined into one update script before we start the server release process. <br />
<br />
===20070622===<br />
<br />
This update file creates the necessary tables for the [[Folksonomy Tagging|FolksonomyTagging]] feature. It also creates an optional vertical database where the raw data for the tags can live on a seperate database server. This update file only creates new tables, it does not change existing tables. <br />
<br />
===20070719===<br />
<br />
This update file creates new tables for the editor subscription feature. It does not change existing tables. <br />
<br />
===20070813===<br />
<br />
This file adds one column to the cdtoc table for a possible future feature, but this new column is currently unused. <br />
<br />
(Lukas, please describe the rest of the changes in this file) <br />
<br />
===20070921===<br />
<br />
This file fixes PUID counts in the albummeta table and changes the type of the [[Prev Value|PrevValue]] in the moderation_open and moderation_closed tables from VARCHAR(255) to TEXT. <br />
<br />
==Detailed bug list==<br />
<br />
For a complete history of the bugs fixed for this release: <br />
* [http://bugs.musicbrainz.org/milestone/Server%202007-10-07 Milestone in the bug tracker] <br />
<br />
For a more detailed (but incomplete) Changelog: <br />
* [http://bugs.musicbrainz.org/browser/mb_server/trunk/CHANGES Changelog in Subversion] <br />
<br />
==Discussion==<br />
<br />
===Tags===<br />
<br />
I guess it will be possible for 3rd party program to request (XML & Co I guess) the tags of an entity; will it be possible to request the tags set by one user for this entity ? --[[User:MLL|MLL]] <br />
<ul><li style="list-style-type:none">Yes, e.g. [http://test.musicbrainz.org/ws/1/tag/?id=8f6bd1e4-fbe1-4f50-aa9b-94c450ec0f11&entity=artist&type=xml http://test.musicbrainz.org/ws/1/tag/?id=8f6bd1e4-fbe1-4f50-aa9b-94c450ec0f11&entity=artist&type=xml] -- [[User:LukasLalinsky|LukasLalinsky]] 12:30, 25 August 2007 (UTC) <br />
<ul><li style="list-style-type:none">Example not very talkative - returns empty xml. --[[User:MLL|MLL]] <br />
<ul><li style="list-style-type:none">That's probably because *you* have not defined any tags for [[Artist:8f6bd1e4-fbe1-4f50-aa9b-94c450ec0f11|this artist]]. I wonder however which URL should be used if you want *all* tags defined for an artist, not only yours. -- [[User:murdos|murdos]] 15:25, 25 August 2007 (UTC) <br />
<ul><li style="list-style-type:none">You're right, thanks. --[[User:MLL|MLL]] <br />
</ul>Global tags are included in the main WS queries - e.g. [http://test.musicbrainz.org/ws/1/artist/8f6bd1e4-fbe1-4f50-aa9b-94c450ec0f11?type=xml&inc=tags http://test.musicbrainz.org/ws/1/artist/8f6bd1e4-fbe1-4f50-aa9b-94c450ec0f11?type=xml&inc=tags] -- [[User:LukasLalinsky|LukasLalinsky]] 20:33, 25 August 2007 (UTC) <br />
</ul><br />
</ul><br />
</ul><br />
<br />
I think the tags should be seeable from the entity page if we want people to use / edit them. And the "Tag this artist" link is not easy to spot when there is a big soup of tags. --[[User:MLL|MLL]] <br />
<br />
The [http://test.musicbrainz.org/show/tag/?tag=down-tempo tag display] feature looks fine to me. Nice to have all entities (albums / artists etc in one place). --[[User:MLL|MLL]] <br />
<br />
''Tags are comma separated and only alphanumberic (word) characters, '-' and <space> are allowed for making tags.'' - I think this should be indicated when on clicks on the "Tag this artist" link. --[[User:MLL|MLL]] <br />
<ul><li style="list-style-type:none">You can add any tags right now, for example ones with Chinese characters. Why should a Chinese user who wants to tag something as being related to 周杰倫 have to use the Englishified "Jay Chou"? I think this is good and I don't think that tags should be limited to 7-bit ascii or anything like that. I hope that the policy isn't implemented technically or as a guideline. --[[User:foolip|foolip]] <br />
</ul><br />
<br />
[[Category:To Be Reviewed]] [[Category:Server]] [[Category:Development]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=User:BrianSchweitzer/Proposal/Soundtrack_Style&diff=23024
User:BrianSchweitzer/Proposal/Soundtrack Style
2007-09-19T20:58:23Z
<p>Dupuy: comments on latest debates (Imported from MoinMoin)</p>
<hr />
<div><ul><li style="list-style-type:none">[[Image:Alert.png]] '''''Status:''' This is a [[Proposed Style Guideline|ProposedStyleGuideline]], it is not official and shouldn't be used as such. See [[Official Style Guideline|OfficialStyleGuideline]] and [[Classical Style Guide|ClassicalStyleGuide]] for now.'' <br />
</ul><br />
<br />
These [[Proposed Style Guideline|ProposedStyleGuideline]]s apply to soundtracks for: <br />
* Movies <br />
* Television Shows <br />
* Video Games <br />
* Theatrical Productions <br />
<br />
==Basic Guidelines==<br />
<br />
* A separate style guide already exists for [[Soundtrack Title Style|SoundtrackTitleStyle]]. In summary, the title is the title of the movie, musical, or video game. Additional information is only added if necessary to distinguish between multiple soundtracks. <br />
* For music written for the soundtrack, '''Artist''' should contain the composer, not the performer. <br />
** Where performer information is available, it should be indicated using [[Advanced Relationships|AdvancedRelationships]]. ''Such music is often referred to as the "score" - especially if it is instrumental.'' <br />
<br />
* For music from other sources used in a soundtrack, '''Artist''' should be handled according as it would for any compilation. Thus: <br />
** For pre-existing classical music used on soundtracks, Artist should contain the composer in accordance with the [[Classical Style Guide|ClassicalStyleGuide]]. <br />
** For pre-existing non-classical music, Artist should contain the performers. <br />
*** '''Exception''': For "tribute" soundtracks where all the music was previously composed by the same songwriter, see, e.g., [http://www.musicbrainz.org/showalbum.html?albumid=339952 De-Lovely] or [http://www.musicbrainz.org/showalbum.html?albumid=92712 Movin' Out], the artist should contain the songwriter and the performers should be credited using [[Advanced Relationships|AdvancedRelationships]]. <br />
<br />
* All releases to which these guidelines apply should be given the [[Release Attribute|ReleaseAttribute]] "Soundtrack." <br />
<br />
==Discussion==<br />
<br />
* How should we handle cases such as [http://musicbrainz.org/artist/eca1f8ea-52af-4e33-959a-12a59e12adab.html The Simpsons] and [http://musicbrainz.org/showartist.html?artistid=1362 South Park], would these go under the category of "Music written for the soundtrack" and be listed under the name of the compsosers (assuming they can be found)? This is especially curious for the Simpsons, who have releases of original material as well as soundtracks for the show. Should [http://musicbrainz.org/album/cdcd30d8-9edd-4a3b-b82a-db7f662b1657.html Go Simpsonic with the Simpsons] be placed under the composer's name and be separated from [http://musicbrainz.org/artist/eca1f8ea-52af-4e33-959a-12a59e12adab.html The Simpsons Sing The Blues] (despite the fact that they're concidered as being from the same artist), or should all the Simpsons releases be changed, for consistancy, including the non-soundtrack releases? ''I think that one of the basic things we need to do is say "what is a soundtrack." There's a basic operational definition in the existing style guidelines, but it needs to be clarified with respect to follow-on and related releases like the ones you mention, as well as compilations of music from several works (these last are compilations, not soundtracks). This gets particularly hairy for some of the anime stuff. There was also some recent discussion of "fictional artists" like the Blues Brothers, which may be relevant here.'' ''Another issue that we need to think about is composer vs. composer&lyricist as primary artist, especially for musicals. There are many cases (e.g. Lerner and Loewe, Rodgers and Hammerstein, Rodgers and Hart) where the composer and lyricist worked together as partners, no different from a musical group where some members sing and others play drums. In these cases, I think that making the primary artist be the composer alone is not what people want or expect. I know that there are [[AudioScrobbler]] users who insist on the primacy of the composer, but in cases such as these well known partnerships, I think that a separate artist for the partnership is the correct approach.'' [[User:Dupuy|@alex]] <br />
* In the light of SG5 and the track artist stuff should we still store the entire score under the name of the composer - even when there are hit songs from a film that are performed by a different artist: [http://musicbrainz.org/showalbum.html?albumid=105954 http://musicbrainz.org/showalbum.html?albumid=105954] Should John Barry or a-ha be the track artist on title track? <br />
<br />
Having been working with Disney a week or more long. I see serious difficulties with this proposal. Classical is classical. It is handled as it is and I don't feel I have any grasp whatsoever to make a thought about it. However, Disney is "soundtrack" and therefore handled as a soundtrack. The problems with this is Disney songs are often times utlized on various other Various artists releases all over the place. Perhaps I am reading this wrong. But, pre-existing doesn't seem to fit here. More like, these songs were on a Disney soundtrack first, therefore the "opposite" stands. If they are on a compilation after that, they should then all be changed to the composer. We are playing Salmon, swimming up river. For every time we fix one "Alan Menken" there are another five disc's released with A Whole New World, or Circle of Life, or whatever next popular song comes out on a various hit album. Currently, even after Disney is down from 100+ albums to less than 50 There are at least 50 various artists albums with "A Whole New World" on them, and approximately 20 correctly attributed songs. This is just one song I am speaking about. I haven't yet to do a count on Circle of Life, or the other vastly popular songs from the vastly prolific Disney studios. I think Soundtrack should be handled a lot differently. I proposed a change, to attempt to embrace soundtrack and performance artist all in one lump, this at least wouldn't be quite as apparent that this was a broken situation. As of yet I have not seen any true feedback on that proposal. I would ask for a little research to be put into this, or to consider it. I have suggestions, I will take the time with Disney, but there has to be some end in sight, or once more, I am sure not only will Disney never be done, it will constantly be an eyesore to those that are perfectionists. [[User:Nyght|Nyght]] <br />
<br />
Personally, I'm of the opinion that most of SoundtrackStyle should just go away. The only time most people look for the composer in a soundtrack is if the soundtrack is instrumental, and in many of those cases the composer is already defined as the [[Primary Artist|PrimaryArtist]] by other style guides. [[Sailor Leo|SailorLeo]] <br />
<ul><li style="list-style-type:none">Totally disagree. That may be your main reason, but far and away it's not a universal reason why people would want composer info for a soundtrack. Also, many soundtracks, that composition may contain vocals, and even when it doesn't, for instrumental tracks, it's debatable in many cases that it could be considered "classical", and thus no style guides would otherwise apply. -- [[Brian Schweitzer|BrianSchweitzer]] 01:26, 06 August 2007 (UTC) <br />
<ul><li style="list-style-type:none">I'm with "[[Sailor Leo|SailorLeo]]" on this. The guideline says "For music written for the soundtrack, '''Artist''' should contain the composer, not the performer", but no reason is given. *Why* is the composer more important than the performer when it comes to soundtracks, as opposed to pop albums? When someone buys "The Wizard of Oz OST", they are buying it for Judy Garland, not Harold Arlen and his co-writers. Same goes with Julie Andrews singing "The Sound of Music" or "My Fair Lady". In my opinion, soundtracks don't need a specific style at all. They generally aren't classical albums, so the Artist for tracks should be the performer. Soundtracks should generally continue to be listed as [[Various Artist|VariousArtist]] releases, with the bulk of the MBz information coming directly from record sleeves. Where the only info for performer is "Original Cast", then I would allow that composers or their orchestras could be listed, but I would argue that an encyclopaedia of music releases should primarily mirror the records people own, and not be the preserve of people who delight in changing standard data into something esoteric and unfriendly. Each day, correct artists are having their performances nullified by over-zealous auto-editors that don't seem to know the difference between a guideline, a rule, and common sense. --[[Arty Smokes|ArtySmokes]] <br />
<ul><li style="list-style-type:none">I've posted comments on [http://www.nabble.com/The-Hills-are-Alive-with...-%28The-Great-Soundtrack-Debate%29-tf4479014s2885.html#a12783669 the mailing list], don't really want to repeat them here again, although I will note that whether people buy soundtracks for Judy Garland or Julie Andrews, the fact remains that they only perform '''some''' of the songs on those albums, while the composers were responsible for all of them. One problem I see is that there are a lot of overlapping genres that fall in the general category of soundtracks. Thinking that splitting this (and [[Soundtrack Title Style|SoundtrackTitleStyle]]) up would help, I created [[Musical Soundtrack Style|MusicalSoundtrackStyle]] and [[Game Soundtrack Style|GameSoundtrackStyle]] as trials. I'm not sure this is quite the right approach, though, as it leads to a lot of duplication. However, I think it does lead to simpler guidelines than trying to come up with one that handles all the different types (scores, anime/games, musicals, TV/films) with the same set of guidelines. [[User:Dupuy|@alex]] <br />
</ul><br />
</ul><br />
</ul><br />
<br />
[[Category:To Be Reviewed]] [[Category:Proposed Style]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Style/Specific_types_of_releases/Theatre&diff=16898
Style/Specific types of releases/Theatre
2007-09-19T20:33:35Z
<p>Dupuy: (Imported from MoinMoin)</p>
<hr />
<div>[[Image:Alert.png]] '''''Status:''' This is a [[Proposed Style Guideline|ProposedStyleGuideline]], it is not official and shouldn't be used as such. See [[Soundtrack Style|SoundtrackStyle]].'' <br />
<br />
These [[Proposed Style Guideline|ProposedStyleGuideline]]<code><nowiki></nowiki></code>s apply to soundtracks for musical theater or films. These are works where songs are performed by the actors as part of the work (but not operas, which are covered by [[Classical Style Guide|ClassicalStyleGuide]] and [[Opera Track Style|OperaTrackStyle]], nor live (non-theatrical) performances by musical groups). <br />
<br />
==Basic Guidelines==<br />
<br />
* '''The [[Release Artist|ReleaseArtist]] should be the composer''', not the performer(s). <br />
** Where performer information is available, it should be indicated using [[Advanced Relationships|AdvancedRelationships]]. <br />
*** Except in the case of [[Fictitious Artist|FictitiousArtist]]<code><nowiki></nowiki></code>s, the actual performers should be used, not the characters <br />
<br />
* '''The [[Release Title|ReleaseTitle]] is just the title of the musical'''. The title should '''exclude secondary information''' such as "Original Soundtrack", "Music from," etc. '''except that''' <br />
** Performance cast (with year) may be used '''if required to distinguish the release from other versions of the soundtrack''', for example [http://musicbrainz.org/release/5cdde27c-1b6e-4883-998c-6b4d743b9321.html Carousel (1956 Film Cast)]. <br />
<br />
* The [[Release Attribute|ReleaseAttribute]] should be '''Soundtrack'''. <br />
<br />
==Examples==<br />
<br />
==Discussion==<br />
<br />
In cases where the composer and lyricist collaborated on a number of musicals, and are generally well-known, it would probably make sense to use a collaboration artist (e.g. "Rogers & Hart") rather than the composer alone. [[User:Dupuy|@alex]] <br />
<br />
[[Opera Track Style|OperaTrackStyle]] has a way to represent character information for songs. Would it be appropriate to include such information in track titles for musical soundtracks? [[User:Dupuy|@alex]] <br />
<br />
[[Category:To Be Reviewed]] [[Category:Proposed Style]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Game_Soundtrack_Style&diff=16604
Game Soundtrack Style
2007-09-19T20:27:05Z
<p>Dupuy: (Imported from MoinMoin)</p>
<hr />
<div>[[Image:Alert.png]] '''''Status:''' This is a [[Proposed Style Guideline|ProposedStyleGuideline]], it is not official and shouldn't be used as such. See [[Soundtrack Style|SoundtrackStyle]].'' <br />
<br />
These [[Proposed Style Guideline|ProposedStyleGuideline]]<code><nowiki></nowiki></code>s apply to soundtracks for computer or console games, including related musical releases. <br />
<br />
==Basic Guidelines==<br />
<br />
* '''The [[Release Artist|ReleaseArtist]] should be the composer''', not the performer(s). In the case of actual game CDs where neither is known, the company that developed the game may be used instead. <br />
** Where performer information is available, it should be indicated using [[Advanced Relationships|AdvancedRelationships]]. <br />
** In cases where popular music available on other releases is used in the soundtrack, the performer should be the [[Artist]] for those tracks. <br />
<br />
* '''The [[Release Title|ReleaseTitle]] should be the same as the game''' unless it has a distinctly different title. The title should '''exclude secondary information''' such as "Original Soundtrack," "Music from," "Inspired by," or "OST", etc. '''except when''' <br />
** it '''is clearly part of the title''' of the soundtrack '''''and''''' <br />
** it '''is required to distinguish the release from other variations of the soundtrack.''' <br />
When "O.S.T." or similar abbreviations are to be retained in titles, the preference is to expand abbreviations to their full wording to avoid ambiguity and to help with translation efforts at a later time. Secondary information that is to be excluded will mostly look like a sub-title as per [[Subtitle Style|SubTitleStyle]]. "Soundtrack" is a single word, and should never be spelt out as "Sound Track" without good reason. For example, the OST of FFVII is called "Final Fantasy VII: Original Sound Track" whereas the OST of FFVIII is called "Final Fantasy VIII: Original Soundtrack", as clearly indicated on the packaging. <br />
* The [[Release Attribute|ReleaseAttribute]] for actual game CDs which have both data and audio tracks should be '''Other'''; for all others, including game rips, it should be '''Soundtrack'''. <br />
* The [[Release Status|ReleaseStatus]] for game rips should ''not'' be '''Official''' - they may or may not be '''Bootleg'''. <br />
<br />
==Examples==<br />
<br />
==Discussion==<br />
<br />
The guidelines above are a starting point; there was a lot of discussion about release attributes, titles and extra title information on the [[Mailing List|MailingList]] and I honestly don't remember how it was left. [[User:Dupuy|@alex]] <br />
<br />
[[Category:To Be Reviewed]] [[Category:Proposed Style]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Game_Soundtrack_Style&diff=16605
Game Soundtrack Style
2007-09-19T20:07:21Z
<p>Dupuy: breakout of SoundtrackStyle (Imported from MoinMoin)</p>
<hr />
<div>[[Image:Alert.png]] '''''Status:''' This is a [[Proposed Style Guideline|ProposedStyleGuideline]], it is not official and shouldn't be used as such. See [[Soundtrack Style|SoundtrackStyle]].'' <br />
<br />
These [[Proposed Style Guideline|ProposedStyleGuideline]]<code><nowiki></nowiki></code>s apply to soundtracks for computer or console games, including related musical releases. <br />
<br />
==Basic Guidelines==<br />
<br />
* '''The [[Release Artist|ReleaseArtist]] should be the composer''', not the performer(s). In the case of actual game CDs where neither is known, the company that developed the game may be used instead. <br />
** Where performer information is available, it should be indicated using [[Advanced Relationships|AdvancedRelationships]]. <br />
** In cases where popular music available on other releases is used in the soundtrack, the performer should be the [[Artist]] for those tracks. <br />
<br />
* '''The [[Release Title|ReleaseTitle]] should be the same as the game''' unless it has a distinctly different title. The title should '''exclude secondary information''' such as "Original Soundtrack", "Music from or Inspired by" or "OST", etc, '''except when''' <br />
** it '''is clearly part of the title''' of the soundtrack '''''and''''' <br />
** it '''is required to distinguish the release from other variations of the soundtrack.''' <br />
When "O.S.T." or similar abbreviations are to be retained in titles, the preference is to expand abbreviations to their full wording to avoid ambiguity and to help with translation efforts at a later time. Secondary information that is to be excluded will mostly look like a sub-title as per [[Subtitle Style|SubTitleStyle]]. "Soundtrack" is a single word, and should never be spelt out as "Sound Track" without good reason. For example, the OST of FFVII is called "Final Fantasy VII: Original Sound Track" whereas the OST of FFVIII is called "Final Fantasy VIII: Original Soundtrack", as clearly indicated on the packaging. <br />
* The [[Release Attribute|ReleaseAttribute]] for actual game CDs which have both data and audio tracks should be '''Other'''; for all others, including game rips, it should be '''Soundtrack'''. <br />
* The [[Release Status|ReleaseStatus]] for game rips should ''not'' be '''Official''' - they may or may not be '''Bootleg'''. <br />
<br />
==Examples==<br />
<br />
==Discussion==<br />
<br />
The guidelines above are a starting point; there was a lot of discussion about release attributes, titles and extra title information on the [[Mailing List|MailingList]] and I honestly don't remember how it was left. [[User:Dupuy|@alex]] <br />
<br />
[[Category:To Be Reviewed]] [[Category:Proposed Style]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Style/Specific_types_of_releases/Theatre&diff=16899
Style/Specific types of releases/Theatre
2007-09-19T19:23:23Z
<p>Dupuy: breakout of SoundtrackStyle (Imported from MoinMoin)</p>
<hr />
<div>[[Image:Alert.png]] '''''Status:''' This is a [[Proposed Style Guideline|ProposedStyleGuideline]], it is not official and shouldn't be used as such. See [[Soundtrack Style|SoundtrackStyle]].'' <br />
<br />
These [[Proposed Style Guideline|ProposedStyleGuideline]]<code><nowiki></nowiki></code>s apply to soundtracks for musical theater or films. These are works where songs are performed by the actors as part of the work (but not operas, which are covered by [[Classical Style Guide|ClassicalStyleGuide]] and [[Opera Track Style|OperaTrackStyle]], nor live (non-theatrical) performances by musical groups). <br />
<br />
==Basic Guidelines==<br />
<br />
* The [[Release Artist|ReleaseArtist]] should be the composer, not the performer(s). <br />
** Where performer information is available, it should be indicated using [[Advanced Relationships|AdvancedRelationships]]. <br />
*** Except in the case of [[Fictitious Artist|FictitiousArtist]]<code><nowiki></nowiki></code>s, the actual performers should be used, not the characters <br />
<br />
* The [[Release Title|ReleaseTitle]] is just the title of the musical. Additional information is only added if necessary to distinguish between multiple soundtracks, and should contain the performance cast name, e.g. "Carousel (Original Broadway Cast)" <br />
* The [[Release Attribute|ReleaseAttribute]] should be '''Soundtrack'''. <br />
<br />
==Examples==<br />
<br />
==Discussion==<br />
<br />
In cases where the composer and lyricist collaborated on a number of musicals, and are generally well-known, it would probably make sense to use a collaboration artist (e.g. "Rogers & Hart") rather than the composer alone. [[User:Dupuy|@alex]] <br />
<br />
[[Opera Track Style|OperaTrackStyle]] has a way to represent character information for songs. Would it be appropriate to include such information in track titles for musical soundtracks? [[User:Dupuy|@alex]] <br />
<br />
[[Category:To Be Reviewed]] [[Category:Proposed Style]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Relationship_Editor&diff=21802
Relationship Editor
2007-08-24T19:32:05Z
<p>Dupuy: response to Brian's comment + deletion of obsolete parts of my comments (Imported from MoinMoin)</p>
<hr />
<div>=Relationship Editors=<br />
<br />
RelationshipEditor<code><nowiki></nowiki></code>s are users of [[MusicBrainz]] who have the permission to change [[Advanced Relationship Type|AdvancedRelationshipType]]<code><nowiki></nowiki></code>s and [[Advanced Relationship Attribute|AdvancedRelationshipAttribute]]<code><nowiki></nowiki></code>s and to add new ones. <br />
<br />
The ideal process to get such a change done is: <br />
# propose the change on the [[Users Mailing List|UsersMailingList]] <br />
# If you get some positive feedback, <br />
## For an existing type add the proposal to the discussion section of the existing relationship type page. <br />
## For a new type write a full proposal on a page named like this SomethingRelationshipType. <br />
<br />
# Propose the change to the [[Style Mailing List|StyleMailingList]]. If you get consensus there, the change will be implemented. <br />
<br />
Current RelationshipEditor<code><nowiki></nowiki></code>s are: <br />
* [[User:Dupuy|AlexanderDupuy]] (dupuy) <br />
* [[User:DaveEvans|DaveEvans]] (djce) <br />
* [[User:DonRedman|DonRedman]] (donredman) <br />
* [[User:LukasLalinsky|LukasLalinsky]] (lukz) <br />
* [[User:mo|mo]] (mo) <br />
* [[User:RobertKaye|RobertKaye]] (rob) <br />
* [[User:WolfSong|WolfSong]] (wolfsong) <br />
<br />
----<br />
<br />
<br />
==Discussion==<br />
<br />
Perhaps the term [[Relationship Type Editor|RelationshipTypeEditor]] (although there are also relationship ''attributes'') might be better than this one? [[User:Dupuy|@alex]] <br />
<ul><li style="list-style-type:none">Yes you are right, [[Relationship Type Editor|RelationshipTypeEditor]] would be more correct. If you want to fix this, go ahead. I for myself think that RelationshipEditor is ok enough. --[[User:DonRedman|DonRedman]] <br />
</ul><br />
<br />
"Editor" would tend to imply that the RelationshipEditor<code><nowiki></nowiki></code>s are the proposers of change, in the way we use the term "Editor" elsewhere. Based on the above description, where the general population proposes changes/additions, and the RelationshipEditor<code><nowiki></nowiki></code>s then eventually become the ones to implement such changes, perhaps "[[Relationship Edit Implementor|RelationshipEditImplementor]]" would be more correct? -- [[Brian Schweitzer|BrianSchweitzer]] 03:58, 17 August 2007 (UTC) <br />
<ul><li style="list-style-type:none">Well, as these are a subset (or subclass) of Editors, and by analogy with [[Auto-Editor|AutoEditor]]<code><nowiki></nowiki></code>s (and the more recent [[Transclusion Editor|TransclusionEditor]]<code><nowiki></nowiki></code>s), I now feel the term is fine as it is. [[User:Dupuy|@alex]] <br />
</ul><br />
<br />
[[Category:To Be Reviewed]] [[Category:Terminology]] [[Category:Advanced Relationships]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=User:Kuno/CurrentProposals&diff=9694
User:Kuno/CurrentProposals
2007-08-21T19:48:31Z
<p>Dupuy: compliments and suggestion (Imported from MoinMoin)</p>
<hr />
<div>=Current Proposals=<br />
<br />
This page is an attempt to list all 'current' or 'active' [[Proposals|proposals]]. Often, proposals do reach some sort of consensus, but are never followed up on, the goal of this page is to keep track of those proposals so they are not forgotten, and can be revisited at the appropriate time. <br />
<br />
Formal RFCs on the [[Style Mailing List|StyleMailingList]] are tracked here. Other proposals found in the wiki have also been added. It looks like the RFC/RFV process is also in use on the [[Users Mailing List|UsersMailingList]] -- these still need to be added. <br />
<br />
Disclaimer: this is not an automated list, but I will try to keep it up to date. If you think some information is out of date or incorrect, notify me (warp on irc, or [mailto:kuno@frob.nl kuno@frob.nl]) and I will look into it (or, change it yourself, this is a wiki :). <br />
{| border="1"<br />
|-<br />
| '''Summary''' || '''Date''' || '''Full Proposal''' || '''RFV''' || '''Current Status''' || '''[[Idea Champion|IdeaChampion]]''' || '''Developer''' <br />
|-<br />
| RFC: Improving Subscription Emails || 2007-08-20 || [http://lists.musicbrainz.org/pipermail/musicbrainz-users/2007-August/016577.html post] [http://wiki.musicbrainz.org/AaronCooper/UpdatingSubscriptionMails wiki] || - || open to discussion || [[User:AaronCooper|AaronCooper]] || - <br />
|-<br />
| RFC: change video game data cdroms from soundtrack to other || 2007-08-15 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-August/005107.html post] [http://forums.musicbrainz.org/viewtopic.php?pid=2661 forum] || - || [[User:kuno/CurrentProposals#kuno01|discussion died]] || [[User:kuno|kuno]] || - <br />
|-<br />
| RFV: new vocal type - "rap" || 2007-08-15 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-August/005103.html post] || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-August/005122.html post] || [[User:kuno/CurrentProposals#luks03|consensus]] || [[User:LukasLalinsky|LukasLalinsky]] || - <br />
|-<br />
| RFC: [[Classical Release Language|ClassicalReleaseLanguage]] || 2007-07-24 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-July/005068.html post] [[Classical Release Language|wiki]] || - || [[User:kuno/CurrentProposals#aaron03|no support]] || [[User:AaronCooper|AaronCooper]] || - <br />
|-<br />
| RFC: Classical works for multiple instruments || 2007-06-29 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-June/005043.html post] || - || [[User:kuno/CurrentProposals#aaron02|no support]] || [[User:AaronCooper|AaronCooper]] || - <br />
|-<br />
| RFC: Change Default Data Quality || 2007-06-19 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-June/004983.html post] [[Change Default Data Quality Proposal|wiki]] || - || [[User:kuno/CurrentProposals#brianfr01|no consensus]] || [[User:BrianFreud|BrianFreud]] || - <br />
|-<br />
| RFC: Adding {instrument} and {vocals} to 'Recorded By' AR || 2007-05-21 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004916.html post] || - || [[User:kuno/CurrentProposals#gecks02|discussion died]] || [[User:Gecks|Gecks]] || - <br />
|-<br />
| RFC: "changed name to" AR || 2007-05-07 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004800.html post] || - || [[User:kuno/CurrentProposals#bogdan03|discussion died]] || [[User:Bogdanb|Bogdanb]] || - <br />
|-<br />
| RFC: Reissue Produced By" and "Compilation Produced By || 2007-05-06 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004796.html post] || - || [[User:kuno/CurrentProposals#gecks01|no discussion]] || [[User:Gecks|Gecks]] || - <br />
|-<br />
| RFC: performance dates and locations || 2007-05-03 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004759.html post] [[Performances And Recordings Proposal|wiki]] [[Location Proposal|wiki]] [[Ticket:2371|trac]] || - || [[User:kuno/CurrentProposals#bogdan02|discussion died]] || [[User:Bogdanb|Bogdanb]] || - <br />
|-<br />
| RFC: instrument-related AR changes || 2007-05-03 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004758.html post] || - || [[User:kuno/CurrentProposals#bogdan01|no discussion]] || [[User:Bogdanb|Bogdanb]] || - <br />
|-<br />
| RFC: Conductor AR Changes || 2007-05-03 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004743.html post] || - || [[User:kuno/CurrentProposals#luks02|discussion died]] || [[User:LukasLalinsky|LukasLalinsky]] || - <br />
|-<br />
| RFV: "has a blog at" AR || 2007-05-01 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004725.html post] || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004741.html post] || [[User:kuno/CurrentProposals#luks01|no veto]] || [[User:LukasLalinsky|LukasLalinsky]] || - <br />
|-<br />
| RFC: IMDb AR change || 2007-05-01 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004721.html post] || - || [[User:kuno/CurrentProposals#kilu01|no discussion]] || [[User:Kilu|Kilu]] || - <br />
|-<br />
| RFC: Bad Terminology: bootleg || 2007-04-24 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-April/004694.html post] || - || [[User:kuno/CurrentProposals#panda01|consensus?]] || [[User:dmppanda|dmppanda]] || - <br />
|-<br />
| RFC: New Release Status: "Upcoming" || 2007-04-14 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-April/004667.html post] || - || [[User:kuno/CurrentProposals#aaron01|consensus]] || [[User:AaronCooper|AaronCooper]] || - <br />
|-<br />
| x (disc 1) & x (disc 2), vs x & x (bonus disc) || 2006-05-03 || [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2006-May/002527.html post] [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2006-September/003684.html revisit] [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004921.html revisit] || - || [[User:kuno/CurrentProposals#gecks03|needs work?]] || [[User:Gecks|Gecks]] || - <br />
|-<br />
| ?: Add Advanced Relationship Qualifiers || 2006-07-25 || [[Advanced Relationships Free Text Qualifiers|wiki]] [[Ticket:1142|trac]] || - || ? || [[User:Gecks|Gecks]] || - <br />
|-<br />
| ?: Add Class "Artist Type" || 2006-07-04 || [[Artist Type Project|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Add Data Class "Location" || 2006-05-02 || [[Location Proposal|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Add Data Fields "Performances and Recordings" || 2007-05-02 || [[Performances And Recordings Proposal|wiki]] || - || ? || [[User:Bogdanb|Bogdanb]] || - <br />
|-<br />
| ?: Add Relationship Type "Narrator" || 2005-08-06 || [[Narrator Relationship Type|wiki]] [[Performance Restructuring Proposal|wiki]] || - || ? || [[User:azertus|azertus]] || - <br />
|-<br />
| ?: Add Relationship Type "Reader" || 2006-03-07 || [[Reader Relationship Type|wiki]] [[Performance Restructuring Proposal|wiki]] || - || ? || [[User:Shepard|Shepard]] || - <br />
|-<br />
| ?: Add Relationship Type "Speaker" || 2006-03-07 || [[Speaker Relationship Type|wiki]] [[Performance Restructuring Proposal|wiki]] || - || ? || [[User:Shepard|Shepard]] || - <br />
|-<br />
| ?: Add Relationship Type "Writer" || 2006-05-02 || [[Writer Relationship Type|wiki]] [[Performance Restructuring Proposal|wiki]] || - || ? || [[User:Gecks|Gecks]] || - <br />
|-<br />
| ?: Adding Sub-Types to Band Members || 2005-08-22 || [[New Voting Proposal|wiki]] || - || ? || [[User:Shepard|Shepard]] || - <br />
|-<br />
| ?: Advanced Vocal Tree || 2006-08-30 || [[Advanced Vocal Tree|wiki]] [[Ticket:1140|trac]] || - || ? || [[User:Shepard|Shepard]]? [[User:mo|mo]]? || - <br />
|-<br />
| ?: Album Rework Proposal || 2005-10-23 || [[Album Rework|wiki]] || - || ? || [[User:Shepard|Shepard]] || - <br />
|-<br />
| ?: Artist Role Inheritance Proposal || predates 2005-07-23 || [[Artist Role Inheritance|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Capitalization Standard Hebrew || 2005-09-15 || [[Capitalization Standard Hebrew|wiki]] || - || ? || [[User:dseomn|dseomn]] || - <br />
|-<br />
| ?: Capitalization Standard Turkish || 2006-06-12 || [[Capitalization Standard Turkish|wiki]] || - || ? || [[User:hakan|hakan]] || - <br />
|-<br />
| ?: Capitalization Standard Yiddish || 2005-09-21 || [[Capitalization Standard Yiddish|wiki]] || - || ? || [[User:dseomn|dseomn]] || - <br />
|-<br />
| ?: Change Voting System || 2006-04-11 || [[New Voting Proposal|wiki]] || - || ? || [[User:Gecks|Gecks]] || - <br />
|-<br />
| ?: Disentangle Interfaces from Schema || 2005-11-13 || [[Disentangle Interfaces From Schema|wiki]] || - || ? || [[User:DonRedman|DonRedman]] || - <br />
|-<br />
| ?: Extend Artist Relationship Category "ArtistNames" || predates 2005-07-23 || [[Linking Different Artist Names|wiki]] || - || ? || [[User:MatthewExon|MatthewExon]] || - <br />
|-<br />
| ?: Extend Relationship Type "OGLA" || predates 2005-07-23 || [http://wiki.musicbrainz.org/OLGARelationshipType wiki] || - || ? || ? || - <br />
|-<br />
| ?: Extend Release Relationship Category "cover art" || 2007-05-01 || [[Miscellaneous Production Relationship Type/Artwork|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Hello Project Style || 2005-12-23 || [[Hello Project Style|wiki]] || - || ? || [[User:DJKC|DJKC]] || - <br />
|-<br />
| ?: Instrumental Style || 2005-04-19 || [[Instrumental Style|wiki]] || - || ? || [[User:WolfSong|WolfSong]] || - <br />
|-<br />
| ?: Live Bootleg Style || 2006-01-23 || [[Live Bootleg Style|wiki]] || - || ? || [[User:Fuchs|Fuchs]] || - <br />
|-<br />
| ?: Live Track Style || predates 2005-07-23 || [[Live Track Style|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Medley Style || predates 2005-07-23 || [[Medley Style|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: New Proposal Process || 2007-03-01 || [[Proposal Process Suggestion|wiki]] [http://forums.musicbrainz.org/viewtopic.php?id=70 forum] || - || ? || [[User:Kerensky97|Kerensky97]]? || - <br />
|-<br />
| ?: Performance Name Style || predates 2005-07-23 || [[Performance Name Style|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Record Label as Artist proposal || 2006-05-19 || [[Record Label As Artist|wiki]] || - || ? || [[User:Nyght|Nyght]] || - <br />
|-<br />
| ?: Release Artist Style || 2006-04-20 || [[Release Artist Style|wiki]] || - || ? || [[User:Keschte|Keschte]] || - <br />
|-<br />
| ?: Release Country Style || predates 2005-07-23 || [[Release Country Style|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Release Event Style || 2006-04-20 || [[Release Event Style|wiki]] || - || ? || [[User:Keschte|Keschte]] || - <br />
|-<br />
| ?: Release Event Style || 2006-04-20 || [[Release Event Style|wiki]] || - || ? || [[User:Keschte|Keschte]] || - <br />
|-<br />
| ?: Release Title Style || 2005-11-22 || [[Release Title|wiki]] || - || ? || [[User:Zout|Zout]] || - <br />
|-<br />
| ?: Restructure Release Types || 2005-08-11 / 2007-01-04 || [[Release Type Restructuring Proposal|wiki]][[Talk:Release Type Restructuring| discussion]] || - || ? || [[User:mo|mo]] || - <br />
|-<br />
| ?: Revised Audio Book Style || predates 2005-07-23 || [[AudioBook Style|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Revised Classical Style Guide || predates 2005-07-23 || [[Classical Style Guide|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Revised Extra Title Information Style || 2006-04-21 || [[Clarify Extra Title Information|wiki]] || - || ? || [[User:Zout|Zout]]? || - <br />
|-<br />
| ?: Revised Soundtrack Style || predates 2005-07-23 || [[Soundtrack Style|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Revised Soundtrack Title Style || predates 2005-07-23 || [[Soundtrack Title Style|wiki]] || - || ? || ? || - <br />
|-<br />
| ?: Track Title Style || 2005-11-22 || [[Track Title|wiki]] || - || ? || [[User:Zout|Zout]] || - <br />
|-<br />
| ?: Untitled Release Style || 2006-07-25 || [[Untitled Release Style|wiki]] || - || ? || [[User:Bogdanb|Bogdanb]] || - <br />
|-<br />
| ?: Use Composers as Release Artists for Tributes || 2007-05-16 || [[Proposals/Composers As Release Artists For Tributes|wiki]] || - || ? || [[User:AaronCooper|AaronCooper]] || - <br />
|}<br />
<br />
<span id="kuno01"></span> <br />
==RFC: change video game data cdroms from soundtrack to other==<br />
<br />
Discussion has probably died out, needs to be summarized. <br />
<br />
<span id="luks03"></span> <br />
==RFC: new vocal type - "rap"==<br />
<br />
consensus, waiting for RFV. <br />
<br />
<span id="aaron03"></span> <br />
==RFC: ClassicalReleaseLanguage==<br />
<br />
Out of the people who voiced their opinion on this proposal, Alex Dupuy doesn't see the need for it and Olivier is not in favour. I assume this proposal has been abandoned due to lack of support. <br />
<br />
<span id="aaron02"></span> <br />
==RFC: Classical works for multiple instruments==<br />
<br />
Only three people participated in the discussion, with no clear support for the proposal. I expect the author has abandoned the proposal, but please correct me if I am wrong --kuno. <br />
<br />
<span id="brianfr01"></span> <br />
==RFC: Change Default Data Quality==<br />
<br />
No consensus was reached on the actual proposal in its original form. However, a lot of valuable suggestions were made by various people, the proposal should probably be rewritten to take those suggestions into account and resubmitted as an RFC. <br />
<br />
(IMO, [[User:DonRedman|DonRedman]] has an insightful [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-July/005067.html post on the proposal]. --kuno). <br />
<br />
<span id="gecks02"></span> <br />
==RFC: Adding {instrument} and {vocals} to 'Recorded By' AR==<br />
<br />
Discussion died, no clear consensus reached as far as i can see. No summary of the discussion. <br />
<br />
<span id="bogdan03"></span> <br />
==RFC: "changed name to" AR==<br />
<br />
In general, people seemed to be in favour of this proposal -- but concerned that the AR will be abused to split up artists which wouldn't be split up without the AR. The discussion died out, wasn't summarized or otherwise followed up later. <br />
<br />
<span id="gecks01"></span> <br />
==RFC: Reissue Produced By" and "Compilation Produced By==<br />
<br />
No discussion took place. No further action was taken. <br />
<br />
<span id="bogdan02"></span> <br />
==RFC: performance dates and locations==<br />
<br />
Discussion has died on the [[Mailing List|MailingList]] and died or slowed down on the wiki pages. I don't see a clear consensus yet on the implementation details. <br />
<br />
<span id="bogdan01"></span> <br />
==RFC: instrument-related AR changes==<br />
<br />
No discussion took place. No further action was taken. <br />
<br />
<span id="luks02"></span> <br />
==RFC: Conductor AR Changes==<br />
<br />
Discussion died. There seem to be no objections to the proposal, however the discussion was not summarized nor do I see an RFV for the proposal. <br />
<br />
<span id="luks01"></span> <br />
==RFV: "has a blog at" AR==<br />
<br />
No vetoes on the RFV, but not implemented yet afaics. <br />
<br />
<span id="kilu01"></span> <br />
==RFC: IMDb AR change==<br />
<br />
No discussion took place. No further action was taken. <br />
<br />
<span id="panda01"></span> <br />
==RFC: Bad Terminology: bootleg==<br />
<br />
Apparently enough consensus was reached to prepare the wiki for changes: [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004841.html http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004841.html] , but looking at the history, no actual changes were made. <br />
<br />
<span id="aaron01"></span> <br />
==RFC: New Release Status: "Upcoming"==<br />
<br />
Consensus reached according to [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004726.html http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004726.html] , see also [http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004840.html http://lists.musicbrainz.org/pipermail/musicbrainz-style/2007-May/004840.html] . No further work seems to have been done on this after the initial consensus was reached. <br />
<br />
Related activity: [[Not Yet Released Releases|NotYetReleasedReleases]] <br />
<br />
Also, I ''think'' the issue of upcoming releases was also discussed on the style mailinglist within the context of Data Quality (setting upcoming releases to low data quality), but cannot find the thread right now --kuno. <br />
<br />
<span id="gecks03"></span> <br />
==x (disc 1) & x (disc 2), vs x & x (bonus disc)==<br />
<br />
The proposed changes to [[Bonus Disc|BonusDisc]] were first discussed and written in may 2006, amended in september 2006, and a call for further discussion in may 2007 (with no responses). Some issues raised in the september discussion and on the wiki page haven't been addressed by the proposal. <br />
<br />
===Comments===<br />
<br />
This is a great page. But why under your personal page? You should put all this stuff in [[Current Work|CurrentWork]] (you can move the ancient cruft on that page out of the way). [[User:Dupuy|@alex]] <br />
[[Category:Proposal]] [[Category:Development]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Future_Of_Music_Summit_Ad&diff=14540
History:Future Of Music Summit Ad
2007-08-10T16:00:44Z
<p>Dupuy: comment (Imported from MoinMoin)</p>
<hr />
<div>=Future of Music Summit Ad=<br />
<br />
With increased support from Google we have a little money to start making noise about MusicBrainz. In order to target musicians and hard-core music fans we're going to sponsor the [http://www.futureofmusic.org/events/summit07 Future of Music Coalitions Policy Summit] on September 17 & 18. The sponsorship gives us exposure on the Future of Music web site and signage at the event (including tall banners hung on both sides of the stage). The banners on the stage are key, because the audience's eyes are drawn to them. Finally we also have a half page ad in the conference brochure -- this ad measures 4.5 inches by 3.625 inches. The goal of this page is to decide what we should put into that ad. <br />
<br />
The target audience at the summit include: musicians, music fans, entrepreneurs and policy makers. MusicBrainz has something to offer for three of the targeted audiences. When it comes to Policymakers, they should really focus on impeaching Bush, so we don't care about them. <br />
<br />
What should our ad say? How can we draw in the three target audiences? Remember that we shouldn't have too much text -- no one is going to read a chunky blob of text. We'll need to keep it simple and straight to the point. I'm going to paste my first attempt for an ad below. If you have suggestions/fixes or other comments, please leave them below. If you have a totally different suggestion from mine, please add yours and leave my (and other's suggestions intact). -- [[User:RobertKaye|RobertKaye]] <br />
<br />
==Mayhem's Draft==<br />
<br />
[ MusicBrainz Logo ] <br />
<br />
We’re building the comprehensive music encyclopedia with the help of fans and musicians everywhere. <br />
<br />
Musicians, please come and let us know about your music. Tell us what you’ve released, who contributed to your work and let fans find your music. <br />
<br />
Fans, please help us make MusicBrainz better by contributing your knowledge about your favorite music and use our tools to clean up your digital music collection. <br />
<br />
Entrepreneurs, use our music metadata to power your music project. <br />
<br />
Come to [http://musicbrainz.org http://musicbrainz.org] to find out more. The MetaBrainz Foundation, a 501.c.3 non-profit run by music fanatics operates the MusicBrainz project. <br />
<br />
==Comments==<br />
<br />
* I like your opening sentence, but I think the next few sentences aren't very cohesive. They seem to divide the roles of our targets, but I think we should be bringing them together to a collective goal. Here's what I've added, just a rushed attempt as I've got to get back to studying: "We’re building a comprehensive music encyclopedia with the help of fans and musicians everywhere! [[MusicBrainz]] provides extensive details about your favourite artists that can be used to power your music application or to turn your MP3 collection into a repository of useful information!" -[[User:AaronCooper|AaronCooper]] <br />
* I think the way that [[MusicBrainz]] isn't just a discography listing but it ties all the discographies together with the AR's is what really defines it from similar things like gracenote. Also that it's created and contributed to by the community like wiki. Emphasizing both will make is sound different and better than all the music discographies sites already out there. The contribution part in the message covers part of that, but it should say more about how it ties all different music for people to see. - Kerensky97 <br />
* I'm not sure about the wording of the advert, but Aaron's suggestion is closer to the concise ''marketing speak'' that you really need. As for the banners at the side of the stage, one should read "IMPEACH" and the other "BUSH". ;) --[[Arty Smokes|ArtySmokes]] <br />
* Okay, a serious suggestion. Since MBz means different things to different people, and is evolving constantly, I think you need something very short that entices people to check it out. You don't need to explain it's an encyclopaedia (that would instantly put off some people) or mention tagging or ARs. Just go for something really simple like "Is Your Favourite Music On Musicbrainz? You have the power to put it there." --[[Arty Smokes|ArtySmokes]] <br />
* It might be useful to have a special welcoming page as the URL (not just [http://musicbrainz.org/ http://musicbrainz.org/] but perhaps [http://musicbrainz.org/fms http://musicbrainz.org/fms]) you can use it to track response to this campaign, and to have some additional text explaining (or linking to) MB philosophy, futures, sample queries, discographies, etc. [[User:Dupuy|@alex]] <br />
<br />
[[Category:To Be Reviewed]] [[Category:Discussion]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Series_Migration&diff=7835
Series Migration
2007-06-11T18:13:51Z
<p>Dupuy: add Hello Recording Club "series" (Imported from MoinMoin)</p>
<hr />
<div>==Series==<br />
<br />
# [[Series/20th Century Masters|20th Century Masters]] <br />
# [[Series/Absolute|Absolute]] <br />
# [[Series/Back To Mine|Back To Mine]] <br />
# [[Series/DJ Kicks|DJKicks]] <br />
# [[Series/Dream Dance|Dream Dance]] <br />
# [[Series/Fetenhits|Fetenhits]] <br />
# [[Series/Global Underground|Global Underground]] <br />
# [[Series/Hello Recording Club|Series/HelloRecordingClub]] <br />
# [[Series/Hitdossier|Hitdossier]] <br />
# [[Series/Hitzone|Hitzone]] <br />
# [[Series/Indie20|Indie20]] <br />
# [[Series/Knuffelrock|Knuffelrock]] <br />
# [[Series/Kuschelrock|Kuschelrock]] <br />
# [[Series/Late Night Tales|Late Night Tales]] <br />
# [[Series/Ministry Of Sound|Ministry of Sound]] <br />
# [[Series/Mixmag|Mixmag]] <br />
# [[Series/MTV Unplugged|MTVUnplugged]] <br />
# [[Series/Now Thats What I Call Music|Now That's What I Call Music! ]] <br />
# [[Series/Putumayo|Putumayo]] <br />
# [[Series/Skitz Mix|SkitzMix]] <br />
# [[Series/Trojan Box Set|Trojan Box Set]] <br />
# [[Series/X Mix|XMix]] <br />
# [[Series/YTMND Soundtrack|YTMND Soundtrack]] <br />
<br />
==Usage==<br />
<br />
To be put in the [[Release Annotation|ReleaseAnnotation]] of each corresponding release in the series: <br />
<br />
<pre>'''[http://wiki.musicbrainz.org/Series/<SeriesName>]'''<br />
</pre><br />
<br />
For example: <br />
<br />
<pre>'''[http://wiki.musicbrainz.org/Series/DreamDance]'''<br />
</pre><br />
<br />
Shows as: '''[http://wiki.musicbrainz.org/Series/DreamDance http://wiki.musicbrainz.org/Series/DreamDance]''' <br />
<br />
==Criteria==<br />
<br />
A ''series''... <br />
* must have at least 10 releases. <br />
<br />
==Other Sources==<br />
<br />
There's a very comprehensive (German) [http://www.musiksampler.de/ site about sampler series in Germany]. <br />
<br />
==Discussion==<br />
<br />
Great idea! would it be wrong for me to add my [http://musicbrainz.org/label/85ac8cad-c035-48dc-b896-cffc91b4785e.html (Sounds Direct) Rock] compilation? there is also the 'Heavy 100' collection which is related. (I haven't added that yet). what do you think? ~[[User:mo|mo]] <br />
<ul><li style="list-style-type:none">Yes, that's what it's here for. --[[User:chancey|chancey]] <br />
</ul><br />
<br />
I believe there should be a criteria, something simple like a minimum of 5 discs? --[[User:chancey|chancey]] <br />
<ul><li style="list-style-type:none">See Criteria --[[User:chancey|chancey]] <br />
</ul><br />
<br />
I've added Hello Recording Club - this was a bit different in that it was all original recordings, and had an associated label. Also, some of the monthly discs did in fact have titles apart from the series (although most just had the artist name). [[User:Dupuy|@alex]] <br />
<br />
[[Category:To Be Reviewed]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=User:OliverCharles&diff=24829
User:OliverCharles
2007-05-03T17:11:18Z
<p>Dupuy: add link to renamed DeprecatedStaticPages (Imported from MoinMoin)</p>
<hr />
<div>Hi! <br />
<br />
My name is Oliver Charles and I've been interested in [[MusicBrainz]] since the start of 2006. Around April 2007 I'd entered about 600 edits into the database, and decided to start also taking in intrest in the development in MB. On this page you can find out some of the stuff I've done (until I become a major contributor and there's too much to list. Hey, I can wish!) <br />
<br />
==Contributions==<br />
<br />
* '''[[python-musicbrainz2|PythonMusicBrainz2]] Label Support''': A few days after label support was added, I wrote a fairly large patch to add label support to [[python-musicbrainz2|PythonMusicBrainz2]]. <br />
* '''PicardQT Cover Artwork Plugin''': I rewrote the amazon cover art plugin to use [[Cover Art Link|CoverArtLink]] relations, and degrade gracefully through different types of album artwork. <br />
* '''[[Mix Engineer Alias|MixEngineerAlias]]''': A mini database of alias that mix engineers write on the runout etchings of vinyl. <br />
<br />
==Current Projects==<br />
<br />
* '''Drum & Bass Cleanup''': One of the first major uses of [[MusicBrainz]] for me was to tag all my vinyl as I ripped it. Now that all the ripping is complete, I've learnt more about [[MusicBrainz]], and a lot of the data was lacking in some aspects (mainly relationships). Now I'm going through my collection, making sure every release has as much information attached as possible. <br />
<br />
==Future Projects==<br />
<br />
Stuff I plan to do in the future, but haven't yet got round to doing (as I have current projects that take priority) include: <br />
* '''Hacking on [[MusicBrainz Server|MusicBrainzServer]]''': I'd like to start contributing code as I love programming... just gotta take the leap in and get started! <br />
* '''Funkadelic Cleanup''': Shouldn't take much, I just plan to go through and make sure it is all as clean as it can be (inspired by [[User:BrianFreud|BrianFreud]]'s Nirvana effort). <br />
** [http://www.duke.edu/~tmc/motherpage/albums_funkadelic http://www.duke.edu/~tmc/motherpage/albums_funkadelic] <br />
<br />
* '''High Contrast cleanup''': It's not very bad at the moment, but it could certainly be better. <br />
<br />
==Hacking==<br />
<br />
I'm new to hacking on [[MusicBrainz Server|MusicBrainzServer]], so I'm doing so simple tasks at the moment: <br />
* '''XHTML Cleanup''': The pages are pretty good since the XHTML 1.1 transition, but they are still lacking. They are also using a lot of semantic elements for layout (hell, the whole site is based in tables!). Here's the status at the moment: <br />
** ''Validation'': The first step is to make sure every page validates in validators. [http://htmlhelp.com/cgi-bin/validate.cgi http://htmlhelp.com/cgi-bin/validate.cgi] is being used as the validator. <br />
** ''Semantic Elements'': Changing elements for semantic equivilents to help text-to-speech translators, screen readers and mobile devices parse the website better. <br />
** ''CSS Cleanup'': Clean the CSS of redundent definitions, make sure it is valid, and make sure the above new elements are styled correctly. <br />
** ''Re-validate'': Make sure it still validates! <br />
(If you know of or find static server content that has migrated to [[WikiDocs]] and thus doesn't need to be XHTML, please add them to the list at [[Deprecated Static Pages|DeprecatedStaticPages]]). <br />
<br />
==Talking to me==<br />
<br />
I can be reached on IRC most of the time - aCiD2 is my alias, and I'm often in the [[MusicBrainz]] channel. <br />
<br />
{{lang en-native}}</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Capitalization_Standard/Japanese_Releases_Clarification&diff=22173
Capitalization Standard/Japanese Releases Clarification
2007-05-03T16:13:05Z
<p>Dupuy: (Imported from MoinMoin)</p>
<hr />
<div>=Capitalization Standard Exception for Japanese Releases=<br />
<br />
<ul><li style="list-style-type:none">'''Status:''' This page outlines an exception to the capitalization rules for the '''English''' language when it appears on some Japanese releases. This is a [[Proposed Style Guideline|ProposedStyleGuideline]]. <br />
</ul><br />
<br />
==In English==<br />
<br />
For Japanese releases by Japanese artists, copy the track titles exactly as they are on the cover. This ignores [[Capitalization Standard English|CapitalizationStandardEnglish]]. <br />
<br />
==Rationale==<br />
<br />
This exception arises because of the [[Style Principle|StylePrinciple]]s: both [[Artist Intent|ArtistIntent]] and [[Consistent Original Data|ConsistentOriginalData]] take priority over the [[Capitalization Standard|CapitalizationStandard]]s. <br />
<br />
For Western artists capitalization is not usually considered part of the title. They often use eccentric capitalization on covers, but revert to standardized capitalization and punctuation in discographies and on re-releases of the songs. <br />
<br />
In contrast, Japanese artists have a tendency to choose track titles and punctuation for aesthetic reasons, and tend to be very consistent about it once a track is titled. These Japanese entries, will intentionally retain the eccentricities across multiple issues, on all entries on their website (and often label websites), and on compilation issues. <br />
<br />
==To Do==<br />
<br />
* Insert a couple of good examples, here. Something from the Escaflowne soundtracks or Gits:SAC maybe, that have been edited a million times and are about as accurate as we'll ever manage) <br />
* I don't think we need this in Japanese, do we? <br />
* Figure out if we need to mention other languages than English and Japanese. <br />
<br />
[[Category:To Be Reviewed]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Miscellaneous_Production_Relationship_Type/Artwork_Proposal&diff=19093
History:Miscellaneous Production Relationship Type/Artwork Proposal
2007-05-03T15:46:35Z
<p>Dupuy: notes on attributes and re-parenting existing ARs (Imported from MoinMoin)</p>
<hr />
<div>==Cover art-related Relationships proposal==<br />
<br />
I propose a few enhancements to the general "covert art" category; the current three relationships are (in my experience) not very pliable to what's actually on many covers (i.e., on the covers I've seen). <br />
<br />
First, I suggest to group all such roles under a general "artwork" category. (Or class, I don't know which is the preferred term.) <br />
<br />
Below is a list of roles that should be in the category. The list contains the previously existing relationships (I assume they were added for good reasons), and a few more that I encountered on covers. Anyone who has encountered others should add them here. The list is hierarchical, I believe that's possible, right? <br />
* '''artist''' or '''URL''' ''provided art direction on'' '''release''' or '''track''' <br />
* '''release''' or '''track''' ''has art direction by'' '''artist''' or '''URL''' <br />
* '''artist''' or '''URL''' ''provided design for'' '''release''' or '''track''' <br />
* '''release''' or '''track''' ''has design by'' '''artist''' or '''URL''' (this is broken from "art design / illustration", I don't see why they should be together.) <br />
** '''artist''' or '''URL''' ''provided graphic design on'' '''release''' or '''track''' <br />
** '''release''' or '''track''' ''has graphic design by'' '''artist''' or '''URL''' <br />
** '''artist''' or '''URL''' ''provided executive design on'' '''release''' or '''track''' <br />
** '''release''' or '''track''' ''has executive design by'' '''artist''' or '''URL''' <br />
** '''artist''' or '''URL''' ''provided layout for'' '''release''' or '''track''' <br />
** '''release''' or '''track''' ''has layout by'' '''artist''' or '''URL''' <br />
<br />
* '''artist''' or '''URL''' ''provided artwork for'' '''release''' or '''track''' <br />
* '''release''' or '''track''' ''has artwork by'' '''artist''' or '''URL''' <br />
** '''artist''' or '''URL''' ''provided cover art for'' '''release''' or '''track''' <br />
** '''release''' or '''track''' ''has cover art by'' '''artist''' or '''URL''' <br />
** '''artist''' or '''URL''' ''provided illustration for'' '''release''' or '''track''' <br />
** '''release''' or '''track''' ''has illustration by'' '''artist''' or '''URL''' (this is broken from "art design / illustration", I don't see why they should be together.) <br />
** '''artist''' or '''URL''' ''provided photography for'' '''release''' or '''track''' <br />
** '''release''' or '''track''' ''has photography by'' '''artist''' or '''URL''' <br />
** '''artist''' or '''URL''' ''provided front cover painting for'' '''release''' or '''track''' <br />
** '''release''' or '''track''' ''has front cover painting by'' '''artist''' or '''URL''' <br />
<ul><li style="list-style-type:none">I've actually seen this on a release [[release:36cbbb31-c6eb-4452-b072-d495f4faa309|wiki:release:36cbbb31-c6eb-4452-b072-d495f4faa309]]; other similar albums (where the same artist created painted artwork from the cover) had only "cover art by". I don't see any harm adding "painting" -- it's the same with photography and illustration -- but if we multiply this for any back/front cover, booklet, etc., this could become huge. See the "Domains" proposal below. <br />
</ul><br />
<br />
* '''artist''' or '''URL''' ''provided typography for'' '''release''' or '''track''' <br />
* '''release''' or '''track''' ''has typography by'' '''artist''' or '''URL''' <br />
* '''artist''' or '''URL''' ''provided cover/artwork concept for'' '''release''' or '''track''' <br />
* '''release''' or '''track''' ''has cover/artwork concept by'' '''artist''' or '''URL''' <br />
<ul><li style="list-style-type:none">I don't know if it's worth it to differentiate these two, but I'm wary of another "art design/illustration" problem, so it may be a good idea to separate them. <br />
</ul><br />
<br />
==Discussion==<br />
<br />
If you're not certain about adding something to the list above, or you need to discuss anything else about this proposal, discuss the item in this section. <br />
<br />
====Recording unfulfilling ARs====<br />
<br />
While you wait on the above to be added, please feel free to use [[User:FrederikSOlesen/SubOptimalCredits|FrederikSOlesen/SubOptimalCredits]] to records ARs that aren't able to be fulfilled with current list. -- [[User:FrederikSOlesen|FrederikSOlesen]] 09:56, 02 May 2007 (UTC) <br />
<br />
====Breaking the current "art design/illustration" relationship====<br />
<br />
I recommend breaking this relationship in two, as the two are not very closely-related (they're even in different subtrees of the hierarchy above) and this seems confusing. The only problem is what to do with the ARs that already use this relationship. I see only a few possibilities, but they don't seem very satisfactory, so maybe someone can suggest something better: <br />
* Just delete them. Of course, that looses data. <br />
* (1) Add the new relationships, and leave the old one in a "deprecated" state where it can't be added to new releases. (2) Then auto-add an edit note to all edits that added such relationships, asking the moderator to re-do the edit with the new AR types. (3 - optional) After a while, send a note to subscribers of the artists that still have such ARs asking them to change them. (4) Make a list of still-existing ARs, if there are not lots maybe we can do a "clean-up week" where volunteers can clean up some more. (5) Finally, drop whatever's left :( <br />
* The "lazy" version: just leave the old version together with the new ones. (And maybe "deprecate" it, so it's not used anymore.) Note that this problem with existing data occurs not only when breaking an existing AR, but also if an existing AR is "reparented" in the hierarchy (unless Robert or somebody goes and whacks the underlying DB tables with some SQL magic) since there is no way to re-parent entries now - they have to be deleted and re-added. [[User:Dupuy|@alex]] <br />
<br />
====Domains of artwork contribution====<br />
<br />
It was noted on the mailing list and above that sometimes credits mention "cover art" (or "cover photography", presumably more) but sometimes just "artwork" (or "photography" etc.). <br />
<br />
It might be a good idea to add only the functional roles (i.e. "photography", "concept", "artwork", "typography") under the general "artwork AR" category, and have checkboxes for specific areas: "cover", "booklet", "disc", "data track". I have only encountered "cover art" and [generic] "artwork" types, but conceivably there may be more, especially with all the special-deluxe-limited-edition-picture-vinyl-with-extra-bonus-tracks-plus-poster-and-decoder-ring releases that are coming out these days. -- [[User:Bogdanb|Bogdanb]] <br />
<br />
===Use more attributes===<br />
<br />
There are ''way'' too many different AR types above. Using an {artwork} attribute for cover/booklet/disc makes a lot of sense - I tried it on the test server. Things like executive design are also better dealt with as an attribute (if at all). But there are still too many functional roles: "art direction", "design", "layout", "concept", "photography", "illustration", "typography". Maybe the photography/illustration/typography thing could be an attribute? And the difference between "art direction" and "concept" seems blurry, as also for "design" and "layout". Remember, this is '''Music'''Brainz - chopping hairs about the visual artwork is a bit of a reach for this database [[User:Dupuy|@alex]] <br />
<br />
[[Category:To Be Reviewed]] [[Category:Proposed Advanced Relationship Type]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Release/Country&diff=6649
Release/Country
2007-04-02T14:58:29Z
<p>Dupuy: notes and four-letter 3166-3 codes in comments (Imported from MoinMoin)</p>
<hr />
<div><br />
This field is a part of [[Release Event|ReleaseEvent]] and describes the country in which an album was released. The list includes countries from [[WikiPedia:ISO_3166-1|ISO 3166-1]], some important historical countries from [[WikiPedia:ISO_3166-3|ISO 3166-3]], and special purpose entries ''[Worldwide]'', ''Europe'', and ''[Unknown Country]''. The codes listed in the first column are 3166-1 codes; for historical countries and special purpose entries, reserved codes are used (and marked in ''italics'') rather than the four-character 3166-3 codes. <br />
{| border="1"<br />
|-<br />
| '''ISO Code''' || '''Name''' || '''Additional Info''' <br />
|-<br />
| AF || Afghanistan || <br />
|-<br />
| AX || Åland Islands || ''not in the list yet'' <br />
|-<br />
| AL || Albania || <br />
|-<br />
| DZ || Algeria || <br />
|-<br />
| AS || American Samoa || <br />
|-<br />
| AD || Andorra || <br />
|-<br />
| AO || Angola || <br />
|-<br />
| AI || Anguilla || <br />
|-<br />
| AQ || Antarctica || <br />
|-<br />
| AG || Antigua and Barbuda || <br />
|-<br />
| AR || Argentina || <br />
|-<br />
| AM || Armenia || <br />
|-<br />
| AW || Aruba || <br />
|-<br />
| AU || Australia || <br />
|-<br />
| AT || Austria || <br />
|-<br />
| AZ || Azerbaijan || <br />
|-<br />
| BS || Bahamas || <br />
|-<br />
| BH || Bahrain || <br />
|-<br />
| BD || Bangladesh || <br />
|-<br />
| BB || Barbados || <br />
|-<br />
| BY || Belarus || <br />
|-<br />
| BE || Belgium || <br />
|-<br />
| BZ || Belize || <br />
|-<br />
| BJ || Benin || <br />
|-<br />
| BM || Bermuda || <br />
|-<br />
| BT || Bhutan || <br />
|-<br />
| BO || Bolivia || <br />
|-<br />
| BA || Bosnia and Herzegovina || <br />
|-<br />
| BW || Botswana || <br />
|-<br />
| BV || Bouvet Island || <br />
|-<br />
| BR || Brazil || <br />
|-<br />
| IO || British Indian Ocean Territory || <br />
|-<br />
| BN || Brunei Darussalam || <br />
|-<br />
| BG || Bulgaria || <br />
|-<br />
| BF || Burkina Faso || <br />
|-<br />
| BI || Burundi || <br />
|-<br />
| KH || Cambodia || <br />
|-<br />
| CM || Cameroon || <br />
|-<br />
| CA || Canada || <br />
|-<br />
| CV || Cape Verde || <br />
|-<br />
| KY || Cayman Islands || <br />
|-<br />
| CF || Central African Republic || <br />
|-<br />
| TD || Chad || <br />
|-<br />
| CL || Chile || <br />
|-<br />
| CN || China || <br />
|-<br />
| CX || Christmas Island || <br />
|-<br />
| CC || Cocos (Keeling) Islands || <br />
|-<br />
| CO || Colombia || <br />
|-<br />
| KM || Comoros || <br />
|-<br />
| CG || Congo || <br />
|-<br />
| CD || Congo, The Democratic Republic of the || <br />
|-<br />
| CK || Cook Islands || <br />
|-<br />
| CR || Costa Rica || <br />
|-<br />
| CI || Cote d'Ivoire || <br />
|-<br />
| HR || Croatia || <br />
|-<br />
| CU || Cuba || <br />
|-<br />
| CY || Cyprus || <br />
|-<br />
| ''XC'' || Czechoslovakia || Historical, October 1918 - January 1992 (3166-3 CSHH) <br />
|-<br />
| CZ || Czech Republic || <br />
|-<br />
| DK || Denmark || <br />
|-<br />
| DJ || Djibouti || <br />
|-<br />
| DM || Dominica || <br />
|-<br />
| DO || Dominican Republic || <br />
|-<br />
| ''XG'' || East Germany || Historical, 1949 - 1990 (3166-3 DDDE) <br />
|-<br />
| EC || Ecuador || <br />
|-<br />
| EG || Egypt || <br />
|-<br />
| SV || El Salvador || <br />
|-<br />
| GQ || Equatorial Guinea || <br />
|-<br />
| ER || Eritrea || <br />
|-<br />
| EE || Estonia || <br />
|-<br />
| ET || Ethiopia || <br />
|-<br />
| ''XE'' || Europe || for European releases where specific country unknown <br />
|-<br />
| FK || Falkland Islands (Malvinas) || <br />
|-<br />
| FO || Faroe Islands || <br />
|-<br />
| FJ || Fiji || <br />
|-<br />
| FI || Finland || <br />
|-<br />
| FR || France || <br />
|-<br />
| GF || French Guiana || <br />
|-<br />
| PF || French Polynesia || <br />
|-<br />
| TF || French Southern Territories || <br />
|-<br />
| GA || Gabon || <br />
|-<br />
| GM || Gambia || <br />
|-<br />
| GE || Georgia || <br />
|-<br />
| DE || Germany || <br />
|-<br />
| GH || Ghana || <br />
|-<br />
| GI || Gibraltar || <br />
|-<br />
| GR || Greece || <br />
|-<br />
| GL || Greenland || <br />
|-<br />
| GD || Grenada || <br />
|-<br />
| GP || Guadeloupe || <br />
|-<br />
| GU || Guam || <br />
|-<br />
| GT || Guatemala || <br />
|-<br />
| GG || Guernsey || ''not in the list yet'' <br />
|-<br />
| GN || Guinea || <br />
|-<br />
| GW || Guinea-Bissau || <br />
|-<br />
| GY || Guyana || <br />
|-<br />
| HT || Haiti || <br />
|-<br />
| HM || Heard and Mc Donald Islands || <br />
|-<br />
| HN || Honduras || <br />
|-<br />
| HK || Hong Kong || <br />
|-<br />
| HU || Hungary || <br />
|-<br />
| IS || Iceland || <br />
|-<br />
| IN || India || <br />
|-<br />
| ID || Indonesia || <br />
|-<br />
| IR || Iran (Islamic Republic of) || <br />
|-<br />
| IQ || Iraq || <br />
|-<br />
| IE || Ireland || <br />
|-<br />
| IM || Isle of Man || ''not in the list yet'' <br />
|-<br />
| IL || Israel || <br />
|-<br />
| IT || Italy || <br />
|-<br />
| JM || Jamaica || <br />
|-<br />
| JP || Japan || <br />
|-<br />
| JE || Jersey || ''not in the list yet'' <br />
|-<br />
| JO || Jordan || <br />
|-<br />
| KZ || Kazakhstan || <br />
|-<br />
| KE || Kenya || <br />
|-<br />
| KI || Kiribati || <br />
|-<br />
| KP || Korea (North), Democratic People's Republic of || <br />
|-<br />
| KR || Korea (South), Republic of || <br />
|-<br />
| KW || Kuwait || <br />
|-<br />
| KG || Kyrgyzstan || <br />
|-<br />
| LA || Lao People's Democratic Republic || <br />
|-<br />
| LV || Latvia || <br />
|-<br />
| LB || Lebanon || <br />
|-<br />
| LS || Lesotho || <br />
|-<br />
| LR || Liberia || <br />
|-<br />
| LY || Libyan Arab Jamahiriya || <br />
|-<br />
| LI || Liechtenstein || <br />
|-<br />
| LT || Lithuania || <br />
|-<br />
| LU || Luxembourg || <br />
|-<br />
| MO || Macau || <br />
|-<br />
| MK || Macedonia, The Former Yugoslav Republic of || <br />
|-<br />
| MG || Madagascar || <br />
|-<br />
| MW || Malawi || <br />
|-<br />
| MY || Malaysia || <br />
|-<br />
| MV || Maldives || <br />
|-<br />
| ML || Mali || <br />
|-<br />
| MT || Malta || <br />
|-<br />
| MH || Marshall Islands || <br />
|-<br />
| MQ || Martinique || <br />
|-<br />
| MR || Mauritania || <br />
|-<br />
| MU || Mauritius || <br />
|-<br />
| YT || Mayotte || <br />
|-<br />
| MX || Mexico || <br />
|-<br />
| FM || Micronesia, Federated States of || <br />
|-<br />
| MD || Moldova, Republic of || <br />
|-<br />
| MC || Monaco || <br />
|-<br />
| MN || Mongolia || <br />
|-<br />
| ME || Montenegro || ''not in the list yet'' <br />
|-<br />
| MS || Montserrat || <br />
|-<br />
| MA || Morocco || <br />
|-<br />
| MZ || Mozambique || <br />
|-<br />
| MM || Myanmar || <br />
|-<br />
| NA || Namibia || <br />
|-<br />
| NR || Nauru || <br />
|-<br />
| NP || Nepal || <br />
|-<br />
| NL || Netherlands || <br />
|-<br />
| AN || Netherlands Antilles || <br />
|-<br />
| NC || New Caledonia || <br />
|-<br />
| NZ || New Zealand || <br />
|-<br />
| NI || Nicaragua || <br />
|-<br />
| NE || Niger || <br />
|-<br />
| NG || Nigeria || <br />
|-<br />
| NU || Niue || <br />
|-<br />
| NF || Norfolk Island || <br />
|-<br />
| MP || Northern Mariana Islands || <br />
|-<br />
| NO || Norway || <br />
|-<br />
| OM || Oman || <br />
|-<br />
| PK || Pakistan || <br />
|-<br />
| PW || Palau || <br />
|-<br />
| PS || Palestinian Territory || ''not in the list yet'' <br />
|-<br />
| PA || Panama || <br />
|-<br />
| PG || Papua New Guinea || <br />
|-<br />
| PY || Paraguay || <br />
|-<br />
| PE || Peru || <br />
|-<br />
| PH || Philippines || <br />
|-<br />
| PN || Pitcairn || <br />
|-<br />
| PL || Poland || <br />
|-<br />
| PT || Portugal || <br />
|-<br />
| PR || Puerto Rico || <br />
|-<br />
| QA || Qatar || <br />
|-<br />
| RE || Reunion || <br />
|-<br />
| RO || Romania || <br />
|-<br />
| RU || Russian Federation || <br />
|-<br />
| RW || Rwanda || <br />
|-<br />
| SH || St. Helena || ''should be renamed to Saint Helena'' <br />
|-<br />
| KN || Saint Kitts and Nevis || <br />
|-<br />
| LC || Saint Lucia || <br />
|-<br />
| PM || St. Pierre and Miquelon || ''should be renamed to Saint Pierre and Miquelon'' <br />
|-<br />
| VC || Saint Vincent and The Grenadines || <br />
|-<br />
| WS || Samoa || <br />
|-<br />
| SM || San Marino || <br />
|-<br />
| ST || Sao Tome and Principe || <br />
|-<br />
| SA || Saudi Arabia || <br />
|-<br />
| SN || Senegal || <br />
|-<br />
| RS || Serbia || ''not in the list yet'' <br />
|-<br />
| ''CS'' || Serbia and Montenegro || Historical, February 2003 - June 2006 (3166-3 CSXX) <br />
|-<br />
| SC || Seychelles || <br />
|-<br />
| SL || Sierra Leone || <br />
|-<br />
| SG || Singapore || <br />
|-<br />
| SK || Slovakia || <br />
|-<br />
| SI || Slovenia || <br />
|-<br />
| SB || Solomon Islands || <br />
|-<br />
| SO || Somalia || <br />
|-<br />
| ZA || South Africa || <br />
|-<br />
| GS || South Georgia and the South Sandwich Islands || ''not in the list yet'' <br />
|-<br />
| ''SU'' || Soviet Union || Historical, 1922 - 1991 (3166-3 SUHH)<br />
|-<br />
| ES || Spain || <br />
|-<br />
| LK || Sri Lanka || <br />
|-<br />
| SD || Sudan || <br />
|-<br />
| SR || Suriname || <br />
|-<br />
| SJ || Svalbard and Jan Mayen Islands || ''rename to Svalbard and Jan Mayen'' <br />
|-<br />
| SZ || Swaziland || <br />
|-<br />
| SE || Sweden || <br />
|-<br />
| CH || Switzerland || <br />
|-<br />
| SY || Syrian Arab Republic || <br />
|-<br />
| TW || Taiwan || <br />
|-<br />
| TJ || Tajikistan || <br />
|-<br />
| TZ || Tanzania, United Republic of || <br />
|-<br />
| TH || Thailand || <br />
|-<br />
| TL || East Timor || ''should be renamed to Timor-Leste'' <br />
|-<br />
| TG || Togo || <br />
|-<br />
| TK || Tokelau || <br />
|-<br />
| TO || Tonga || <br />
|-<br />
| TT || Trinidad and Tobago || <br />
|-<br />
| TN || Tunisia || <br />
|-<br />
| TR || Turkey || <br />
|-<br />
| TM || Turkmenistan || <br />
|-<br />
| TC || Turks and Caicos Islands || <br />
|-<br />
| TV || Tuvalu || <br />
|-<br />
| UG || Uganda || <br />
|-<br />
| UA || Ukraine || <br />
|-<br />
| AE || United Arab Emirates || <br />
|-<br />
| GB || United Kingdom || <br />
|-<br />
| US || United States || <br />
|-<br />
| UM || United States Minor Outlying Islands || <br />
|-<br />
| ''XU'' || [Unknown Country] || <br />
|-<br />
| UY || Uruguay || <br />
|-<br />
| UZ || Uzbekistan || <br />
|-<br />
| VU || Vanuatu || <br />
|-<br />
| VA || Vatican City State (Holy See) || <br />
|-<br />
| VE || Venezuela || <br />
|-<br />
| VN || Viet Nam || <br />
|-<br />
| VG || Virgin Islands (British) || <br />
|-<br />
| VI || Virgin Islands (U.S.) || <br />
|-<br />
| WF || Wallis and Futuna Islands || <br />
|-<br />
| EH || Western Sahara || <br />
|-<br />
| ''XW'' || [Worldwide] || <br />
|-<br />
| YE || Yemen || <br />
|-<br />
| ''YU'' || Yugoslavia || Historical, 1918 - 1992 (3166-3 YUCS) <br />
|-<br />
| ZM || Zambia || <br />
|-<br />
| ZW || Zimbabwe || <br />
|}<br />
<br />
[[Category:To Be Reviewed]] [[Category:Terminology]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Style/Specific_types_of_releases/Opera&diff=6989
History:Style/Specific types of releases/Opera
2007-03-20T21:38:13Z
<p>Dupuy: I support the "Second possibility" (with character [part] information at end) (Imported from MoinMoin)</p>
<hr />
<div>=Development of Style for Opera Tracks=<br />
<br />
<ul><li style="list-style-type:none">{i} '''Purpose:''' ''This page is for the evolution of the new style guide we would like to use for tracks from operas.'' <br />
</ul><br />
<br />
It starts as my synthesis of the mails from the thread Opera Track Style. Following [[User:DonRedman|DonRedman]]'s suggestion, this page is going to evolve (by including digests of what was said on the mailing list, and by direct editing) until we reach a stable enough consensus to try it for real. In Don's proposed system, there are three stages: <br />
* development (current) during which we discuss without editing any real data. <br />
* testing (as soon as we are ready) where we test the proposed style on real data. <br />
* validation (when we are happy with the testing) which means the results of this page become part of the official Style Guides. <br />
<br />
==Tentative Conclusion==<br />
<br />
It seems that after all discussions three possible styles remain: <br />
# [[Opera Name|OperaName]], [[Opus Number|OpusNumber]]: [[Act Number|ActNumber]][, [[Scene Number|SceneNumber]]]. ([[Performance Type|PerformanceType]]: Characters) "Name of the song" <br />
# [[Opera Name|OperaName]], [[Opus Number|OpusNumber]]: [[Act Number|ActNumber]][, [[Scene Number|SceneNumber]]]. [[Performance Type|PerformanceType]] "Name of the song" (Characters) <br />
# [[Opera Name|OperaName]], [[Opus Number|OpusNumber]]: [[Act Number|ActNumber]][, [[Scene Number|SceneNumber]]]. [[Performance Type|PerformanceType]] (Characters) "Name of the song" <br />
<br />
Details follow further down the page. <br />
<br />
===Tests===<br />
<br />
I did a test with [http://musicbrainz.org/show/release/?releaseid=551121 http://musicbrainz.org/show/release/?releaseid=551121] see edits [http://musicbrainz.org/mod/search/results.html?moderator_type=3&moderator_id=189467&orderby=asc&minid=6583620&maxid=6583635 http://musicbrainz.org/mod/search/results.html?moderator_type=3&moderator_id=189467&orderby=asc&minid=6583620&maxid=6583635] -- [[User:davitof|davitof]] 2007-03-17 <br />
<br />
Second test, same release but different style here: [http://test.musicbrainz.org/mod/search/results.html?moderator_id=189467&moderator_type=4&orderby=asc http://test.musicbrainz.org/mod/search/results.html?moderator_id=189467&moderator_type=4&orderby=asc] -- [[User:davitof|davitof]] 2007-03-18 <br />
<br />
===First possibility===<br />
<br />
====OperaName[, OpusNumber]: Act XX[, Scene XX]. [([PerformanceType: ][Character1, Character2, ...])] "Name of the song"====<br />
<br />
<ul><li style="list-style-type:none">supporters: <br />
</ul><br />
<br />
Simple Examples: Full details including catalog number, performance type, and character names: <br />
* Don Giovanni, Op. 500: Act I, Scene III. (Duettino: Don Giovanni, Zerlina) "La ci darem la mano" <br />
<br />
Somewhere in the middle: <br />
* Don Giovanni, Op. 500: Act I, Scene III. (Don Giovanni, Zerlina) "La ci darem la mano" <br />
* Don Giovanni, Op. 500: Act I, Scene III. (Duettino) "La ci darem la mano" <br />
* Don Giovanni, Op. 500: Act I, Scene III. "La ci darem la mano" <br />
* Don Giovanni: Act I, Scene III. (Duettino: Don Giovanni, Zerlina) "La ci darem la mano" <br />
* Don Giovanni: Act I, Scene III. (Don Giovanni, Zerlina) "La ci darem la mano" <br />
* Don Giovanni: Act I, Scene III. (Duettino) "La ci darem la mano" <br />
<br />
Bare essentials, without catalog number, performance type, or character names: <br />
* Don Giovanni: Act I, Scene III. "La ci darem la mano" <br />
<br />
Special case: the Prelude or instrumental parts: <br />
* Don Giovanni: Act III. Prelude <br />
* Don Giovanni: Act III, Scene II. An Instrumental Part <br />
<br />
Complex Examples: Another part in the same scene: <br />
* Don Giovanni: Act IV, Scene II. "La ci darem la mano" - "Another song in the same scene" <br />
* Don Giovanni: Act IV, Scene II. An Instrumental Part - "La ci darem la mano" <br />
<br />
Another part in a different scene: <br />
* Don Giovanni: Act III, Scene I. "La ci darem la mano" / Act III, Scene II. "Another song in a different scene" <br />
* Don Giovanni: Act III, Scene I. "La ci darem la mano" / Act III, Scene II. An Instrumental Part in a Different Scene <br />
<ul><li style="list-style-type:none">Note: I think Act XX is essential here since there is no colon after "Act III" - I don't think it follows logically that everything after it is "within" Act III <br />
</ul><br />
<br />
Another part in a different act: <br />
* Don Giovanni: Act II, Scene III. "La ci darem la mano" / Act III, Scene I. "Another song in a different act" <br />
* Don Giovanni: Act II, Scene III. "La ci darem la mano" / Act III. Prelude <br />
<br />
===Second possibility===<br />
<br />
====OperaName[, Catalog ###]: Act XX[, Scene XX]. [PerformanceType] "Name of the song" [(Character1, Character2, ...)]====<br />
<br />
<ul><li style="list-style-type:none">Supporters: joseba Robert Kiessling, [[User:DonRedman|DonRedman]], [[User:Dupuy|@alex]] <br />
Don Giovanni, Op. 500: Act I, Scene III. Duettino "La ci darem la mano" (Don Giovanni, Zerlina) <br />
</ul><br />
<br />
This to me looks more in line with other CSG uses, it has the least important information last and it's not even theoretically ambiguous in case [[Performance Type|PerformanceType]] or Character is omitted. <br />
<br />
We should also add [, No. XX] to allow for linear song/part numbering where applicable. <br />
<br />
Lastly, I am a believer in "consistency rules". So we should at the same time test and propose this for similarly structured works (cantatas, oratorios, masses, ...). -- Robert Kiessling <br />
<ul><li style="list-style-type:none">Agreed! -- [http://wiki.musicbrainz.org/AaronCooper cooperaa] <br />
</ul><br />
<br />
===Third possibility===<br />
<br />
====OperaName[, OpusNumber]: Act XX[, Scene XX]. [PerformanceType] [(Character1, Character2, ...)] "Name of the song"====<br />
<br />
<ul><li style="list-style-type:none">Supporters: leivhe, [[User:davitof|davitof]], [http://wiki.musicbrainz.org/AaronCooper cooperaa] <br />
Don Giovanni, Op. 500: Act I, Scene III. Duettino (Don Giovanni, Zerlina) "La ci darem la mano" <br />
</ul><br />
<br />
----<br />
<br />
<br />
==The whole Discussion==<br />
<br />
The remainder of this page discusses the different options and their pros and cons. The page is sprinkled with the names of users to indicate what position these users seemed to agree with. I hope I guessed your MB names correctly. Please move your names around if you change your mind or if I have misunderstood your position. The idea of course is to try to extract the options which most users like. I would like to try here something slightly different from a voting system, that is you may choose more than one option for each issue. I understand the urge to argument your choices, but please don't forget to add your names after the corresponding choices. <br />
<br />
I identified four main issues in the thread: order, numbering system, punctuation and quotes. <br />
<br />
==Order==<br />
<br />
===1: the order I originally suggested===<br />
<br />
* 1 - Opera name <br />
* ( - No catalogue number) <br />
* ( - No movement number) <br />
* 2 - Act number <br />
* 3 - Scene number <br />
* 4 - Type (optional) <br />
* 5 - First words of the scene <br />
* 6 - Part (optional) <br />
<br />
Example (don't look at the punctuation): ''Don Giovanni, Act I, Scene 3, Duettino, "Là ci darem la mano" (Don Giovanni, Zerlina)'' <br />
<br />
===2: leivhe's order===<br />
<br />
(cooperaa, leivhe) <br />
* 1 - Opera name <br />
* 2 - catalogue number (optional) <br />
* ( - No movement number) <br />
* 3 - Act number <br />
* 4 - Scene number <br />
* 5 - Type (optional) <br />
* 6 - Part (optional) <br />
* 7 - First words of the scene <br />
<br />
Example (don't look at the punctuation): ''Don Giovanni, Act I, Scene 3, Duettino (Don Giovanni, Zerlina), "Là ci darem la mano"'' <br />
<ul><li style="list-style-type:none">In the second case, are we running the risk of too-long common prefixes? Take the example of "first <n> characters are used for the filename" where it's quite likely that there are cases where (1) to (6) are the same. -- joseba, 2007-02-05 <br />
<ul><li style="list-style-type:none">Of course this will happen. But I believe we must not take this too much into account. This is a ripper/tagger problem. The MB database must strive towards exactness and usefulness. Anyhow, adding the catalogue number won't increase much the title length. But your question raises an interesting suggestion: we could move the type and part elements after the quotation, so that if the track name gets cut, it has better chances to stay meaningful. So here is the new suggestion: --[[User:davitof|davitof]] 2007-02-06 <br />
</ul><br />
</ul><br />
<br />
===3: joseba's order===<br />
<br />
This was suggested in an attempt to keep as many significant characters as possible in case of file name truncature. --[[User:davitof|davitof]] 2007-02-15 (davitof) <br />
* 1 - Opera name <br />
* 2 - catalogue number (optional) <br />
* ( - No movement number) <br />
* 3 - Act number <br />
* 4 - Scene number <br />
* 5 - First words of the scene <br />
* 6 - Type (optional) <br />
* 7 - Part (optional) Actually joseba prefers order (1) since it's most consistent with other classical styles where the type like "Rondo" clearly comes first --joseba, 2006-02-25 <br />
<br />
==Numbering system (act - scene)==<br />
<br />
* arabic - arabic (davitof, leivhe) (it seems we could both be persuaded to go to romans) <br />
<ul><li style="list-style-type:none">''Don Giovanni, Act 1, Scene 3, Duettino (Don Giovanni, Zerlina), "Là ci darem la mano"'' <br />
</ul><br />
* roman - arabic <br />
* roman - roman (cooperaa, cadalach) <br />
<ul><li style="list-style-type:none">''Don Giovanni, Act I, Scene III, Duettino (Don Giovanni, Zerlina), "Là cidarem la mano"'' <br />
</ul>At least, it seems we can refuse the roman-arabic mix! --[[User:davitof|davitof]] 2007-02-02 <br />
<ul><li style="list-style-type:none">Yes please, let's have simple rules! Like "'No.' followed by arabic, everything else roman". --joseba, 2006-02-05 <br />
</ul>Note that in this numbering scheme two tracks can have the same Part_number. [[Multi-Track Movement Style|MultiTrackMovementStyle]] was proposed in a different context to address that issue. Please refer to the next comment for further discussion. --joseba, 2007-02-25 See [[Classical Track Title Partnumber Style|ClassicalTrackTitlePartnumberStyle]] for a proposal that incorporates the above in a more general framework of part numbers. --joseba, 2006-02-25 <br />
<br />
==Punctuation==<br />
<br />
After <br />
* work title: Nobody suggested anything else than a colon. <br />
* act number: Nobody suggested anything else than a comma. <br />
* scene number: <br />
** comma <br />
** dot, by analogy with the general classical style. I think this is a good idea, since the scene type is closer to a movement indication. (cadalach, cooperaa, davitof, joseba) <br />
** colon (suggested by leivhe). <br />
<br />
* part type and parts: <br />
** nothing (davitof, leivhe) <br />
** colon (andrewski) <br />
** comma <br />
** dot (andrewski, cooperaa) <br />
<br />
Examples <br />
* comma comma <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3, Duettino (Don Giovanni, Zerlina), "Là ci darem la mano"'' <br />
</ul><br />
* comma colon <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3, Duettino (Don Giovanni, Zerlina): "Là ci darem la mano"'' <br />
</ul><br />
* comma none <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3, Duettino (Don Giovanni, Zerlina) "Là ci darem la mano"'' <br />
</ul><br />
* comma dot <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3, Duettino (Don Giovanni, Zerlina). "Là ci darem la mano"'' <br />
</ul><br />
* none brackets <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3 (Duettino: Don Giovanni, Zerlina) "Là ci darem la mano"'' <br />
</ul><br />
* dot brackets (cooperaa, davitof, leivhe) <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3. (Duettino: Don Giovanni, Zerlina) "Là ci darem la mano"'' <br />
</ul><br />
* dot brackets variant (joseba) <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3. Duettino (Don Giovanni, Zerlina) "Là ci darem la mano"'' <br />
</ul><br />
<br />
==Quotation: quotes or not==<br />
<br />
some users have suggested we could omit the quotes altogether. examples <br />
* comma comma <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3, Duettino (Don Giovanni, Zerlina), Là ci darem la mano'' <br />
</ul><br />
* comma colon <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3, Duettino (Don Giovanni, Zerlina): Là ci darem la mano'' <br />
</ul><br />
* comma none <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3, Duettino (Don Giovanni, Zerlina) Là ci darem la mano'' <br />
</ul><br />
* comma dot <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene 3, Duettino (Don Giovanni, Zerlina). Là ci darem la mano'' <br />
</ul><br />
<br />
We must remember that the parts may not be here at all, so that I feel that at least a separator is needed --[[User:davitof|davitof]] 2007-02-02 <br />
<br />
So, should it be <br />
* with quotes (davitof, Prodoc, cadalach) <br />
* without quotes (leivhe?) <br />
<br />
Personally I think it's better to use quotes to have a clearer distinction between what's information about a track (everything before it) and what could be considered an actual title -- [[User:Prodoc|Prodoc]] 20:21, 05 February 2007 (UTC) <br />
<br />
Sometimes quotes are needed, imo, and somtimes not. I'd suggest we use quotes when the "title" is a line from the libretto, but drop them when it's the name of an orchestral interlude. So '... Prelude' but '... "Là ci darem la mano"'. -- cadalach, 2006-02-06 <br />
<ul><li style="list-style-type:none">I agree. This makes me see that the title of this section wasn't specific enough. --[[User:davitof|davitof]] 2007-02-06 <br />
</ul><br />
<br />
==Optional information==<br />
<br />
I (cadalach) have created this new section to solicit opinions on what's been called the optional information. Here I mean, as in the above example, the "Duettino" and "Don Giovanni, Zerlina" information. Would it be sensible to treat this as just one piece of information? That is, either both are included or neither. I'd guess that it would be reasonable to say that if you knew (or cared about) one then you'd know the other too. <br />
<ul><li style="list-style-type:none">I don't think so. My release of Le Nozze de Figaro (Kleiber) only mentions the parts, not the part type. Although I can understand that someone would later add the parts, we can't expect the original editor to search for them when he enters the release first. We must remember that some voters insist that the releases must be almost perfect to get into MB, so the less requirements we put, the more new releases we will have. Of course this means we will have to correct and improve many of those after, but I don't think this is too high a price to pay. --[[User:davitof|davitof]] 2007-02-02 <br />
<ul><li style="list-style-type:none">Agree with davitof. --leivhe <br />
<ul><li style="list-style-type:none">Yes, also IMHO it should be stated very clearly that these are optional. We should guide how to use them but they should never become mandatory. Moreover they are redundant. When characters are present you can count out the kind of scene: 2 = duetto, 3 = trio, 4 = quartetto and so on. -- [[User:ClutchEr2|ClutchEr2]] <br />
</ul><br />
</ul><br />
</ul><br />
<br />
Ok, that's fine with me. -- cadalach, 2006-02-06 <br />
<br />
==Pending issue==<br />
<br />
(this can be decided separately IMO) (cooperaa), what should we do when several scenes are merged on the same track ([[Multiple Title Style|MultipleTitleStyle]]): <br />
<ul><li style="list-style-type:none">''Die Walküre: Act II. Prelude - Act II, Scene I. (Wotan) "Nun zäume dein Ross, reisige Maid!"'' ''Die Walküre: Act II. Prelude / Act II, Scene I. (Wotan) "Nun zäume dein Ross, reisige Maid!"'' ''Die Walküre: Act II. Prelude - Scene I. (Wotan) "Nun zäume dein Ross, reisige Maid!"'' ''Die Walküre: Act II. Prelude / Scene I. (Wotan) "Nun zäume dein Ross, reisige Maid!"'' ''Die Walküre: Act II. Prelude, Scene I. (Wotan) "Nun zäume dein Ross, reisige Maid!"'' <br />
</ul><br />
<br />
And what do we do when liner notes (non-scene-splitting) have more than one arias/recitatives for a track? Example: <br />
<ul><li style="list-style-type:none">''Croesus, Act II, Scene III: "Seht, wie Herr Elcius ist ein Politicus" (Elcius) / "Mein Kätchen ist ein Mädchen" (Bauernkinder) / "Ich solltes schier mein Unglück vergessen" (Elcius)'' [http://musicbrainz.org/track/7ab7b6c7-a5cf-48e0-beca-f3faa9f006ab.html http://musicbrainz.org/track/7ab7b6c7-a5cf-48e0-beca-f3faa9f006ab.html] <br />
<ul><li style="list-style-type:none">I believe that according to your own suggested order, your example should be: <br />
<ul><li style="list-style-type:none">''Croesus, Act II, Scene III: (Elcius) "Seht, wie Herr Elcius ist ein Politicus" / (Bauernkinder) "Mein Kätchen ist ein Mädchen" / (Elcius) "Ich solltes schier mein Unglück vergessen"'' --[[User:davitof|davitof]] 2007-02-02 <br />
</ul>Quite right (punctuation differs, but this was about multiple arias/recs in a track) --leivhe <br />
</ul><br />
</ul><br />
<br />
This is the track style I support most: --cooperaa (Feb 2) <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act I, Scene III. (Duettino: Don Giovanni, Zerlina) "La ci darem la mano"'' <br />
<ul><li style="list-style-type:none">Looks good, I could agree on this! :) I'd like to have Arabics though, but it's not essential. Also note that the quotes are not needed, as the formatting guarantees a colon or a dot or a bracket (or a slash, in the case of multiple-arias-in-one-track) in front of the name. How about removing the quotes? You'd get: --leivhe (Feb 3.) <br />
<ul><li style="list-style-type:none">''Don Giovanni: Act 1, Scene 3. (Duettino: Don Giovanni, Zerlina) La ci darem la mano'' <br />
</ul>How does that work for the Overture? Just ''Don Giovanni: Overture''? -- joseba, 2007-02-05 Note that if we do this, we should amend the cantata style, as it currently puts Aria/Duet/Rec. in front of the brackets. --leivhe (Feb 5.) <br />
<ul><li style="list-style-type:none">Looking at cantatas, would we expect to have the first line of the text in all cases, even for something like a recitative? -- joseba, 2007-02-05 <br />
</ul><br />
</ul><br />
</ul><br />
<br />
==Common practice==<br />
<br />
What I'm interested in, and what I'm missing on this page, is information about what's common practice in 'the real world' outside of [[MusicBrainz]]. If possible, we should stick to that as close as possible unless we come up with something significantly better. By doing this, more people than just us will have less trouble adapting to it. We might all have our personal preferences but e.g. which numbering system is most commonly used for acts and scenes? It would be good if we link to some resources or add examples to each issue just to have some form of reference. At this stage it's hard to make out personal preference and common practice -- [[User:Prodoc|Prodoc]] 20:23, 05 February 2007 (UTC) <br />
<ul><li style="list-style-type:none">I almost agree with you, but for a huge difference: I would replace the word "possible" with "desirable". But let's try: <br />
* Archiv, EMI and Erato: Type "quotation" (parts), <br />
* Decca: quotation parts <br />
* harmonia mundi: part type (parts) quotation <br />
What do other editors have? Are their releases for the above labels consistent? What about the other labels? -- [[User:davitof|davitof]] 2007-02-05 <br />
</ul><br />
<br />
==About the Third proposition==<br />
<br />
Although leivhe supported the first proposition, he said he would have preferred this one. I (once more) change my mind because this proposition stays clear even after removing the [[Part Type|PartType]] or the Characters. IMO it uses the best parts of the first two: regrouping [[Part Type|PartType]] and characters, staying clear even if some parts are not mentioned. I don't see any reason for putting the characters at the end. It isn't specially consistent with any other MB style I know of, and I have found widely differing styles on the actual CDs. So my order is Third, Second and last First (I feel cooperaa's suggestion to put the [[Part Type|PartType]] in lowercase is not solid enough, careless editors would make mistakes). -- [[User:davitof|davitof]] 2007-03-19 <br />
<br />
[[Category:To Be Reviewed]] [[Category:Proposed Style]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Musical_Terms_Translations&diff=10751
Musical Terms Translations
2006-11-30T02:23:02Z
<p>Dupuy: japanese, plus comment on scope (Imported from MoinMoin)</p>
<hr />
<div>This is an attempt at providing a translation of musical terms names in the most used languages to express them (in classical works at least, but feel free to add columns) (translations taken from Wikipedia's "other languages" section). Very useful when trying to be consistent, some sleeves are not (unappropriate use of movement type name, mix of different languages...). <br />
{| border="1"<br />
|-<br />
| '''english''' || '''french''' || '''german''' || '''italian''' || '''swedish''' || '''japanese'''<br />
|-<br />
| '''Classical'''<br />
|-<br />
| ''choral''<br />
|-<br />
| [http://en.wikipedia.org/wiki/Chorale Chorale] || choral || Chorale || corale || || コラール<br />
|-<br />
| [http://en.wikipedia.org/wiki/Aria Aria] || aria || Arie || aria || aria || アリア<br />
|-<br />
| [http://en.wikipedia.org/wiki/Recitative Recitative] || [http://fr.wikipedia.org/wiki/Récitatif récitatif] || Rezitativ || recitativo || || レチタティーヴォ<br />
|-<br />
| '''Non-classical'''<br />
|-<br />
| [http://en.wikipedia.org/wiki/Bridge_(music) Bridge] || pont || Zwischenspiel || || brygga || <br />
|-<br />
| ''To be completed...''<br />
|}<br />
<br />
'''Interesting links''' <br />
* [http://en.wikipedia.org/wiki/Category:Musical_terminology http://en.wikipedia.org/wiki/Category:Musical_terminology] <br />
* [http://en.wikipedia.org/wiki/Category:Musical_forms http://en.wikipedia.org/wiki/Category:Musical_forms] <br />
* [http://en.wikipedia.org/wiki/Category:Vocal_music http://en.wikipedia.org/wiki/Category:Vocal_music] <br />
<br />
'''Comments''' <br />
<br />
I removed recitativo from the french column because as the wikipedia page explains, recitativo is not french. --davitof <br />
<ul><li style="list-style-type:none">I agree that I've always seen récitatif in french. Yet, on french WP, récitatif redirects to recitativo and not the reverse; --MLL <br />
</ul><br />
<br />
We should mention the plurals (especially for german) --davitof <br />
<ul><li style="list-style-type:none">Agreed --MLL <br />
</ul><br />
<br />
We should better define the scope of this - there's no need to provide translations of all musical terminology - just those words that are common in album or track titles and thus may need to be entered in MB. [[User:Dupuy|@alex]] <br />
<br />
[[Category:To Be Reviewed]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Klingon_Artists&diff=22556
Klingon Artists
2006-11-19T23:24:11Z
<p>Dupuy: (Imported from MoinMoin)</p>
<hr />
<div>=Artists with Klingon Names or Works with Titles in Klingon=<br />
<br />
The following is a partial list of [[International Artists|InternationalArtists]] whose names are Klingon or who have works with titles in Klingon. If you can read and write Klingon, please consider adding these artists to your [[Artist Subscription|ArtistSubscription]]<code><nowiki></nowiki></code>s so that you can be notified when there are additions or changes to their discographies, and you can check them for errors. If you know of other Klingon artists not listed here, please add them. <br />
<br />
----<br />
<br />
<br />
* [http://musicbrainz.org/artist/b4542a0c-95fb-467f-8724-101dd7efc453.html Marc Okrand] <br />
* [http://musicbrainz.org/artist/f6bf9642-2373-4e1f-a432-e898a70cbb33.html Bianca Maria Gerlich (K'Vacor)] <br />
* [http://musicbrainz.org/artist/85312ab2-4300-4226-9ab2-71fe11eb1c8c.html Stovokor] <br />
<br />
==Discussion==<br />
<br />
While there are of course no real Klingons, there ''is'' a real (if artificial) Klingon language (tlhIngan Hol), as legitimate as Esperanto or other artificial languages, if perhaps not as widely used. There's a good [http://en.wikipedia.org/wiki/Klingon_language Wikipedia article] about Klingon. [http://musicbrainz.org/artist/b4542a0c-95fb-467f-8724-101dd7efc453.html Marc Okrand] is the inventor of the Klingon language, so if anyone could be said to be a native speaker, it would be him. However, he only has two [[Spoken Word|SpokenWord]] releases that attempt to teach some of the language. (Note that these are entered in the database as ''English/Latin'' since that's the language the titles are in.) <br />
<br />
There are two known artists who have released music in Klingon. The Portland death-metal band [http://musicbrainz.org/artist/85312ab2-4300-4226-9ab2-71fe11eb1c8c.html Stovokor] has two songs on the [http://musicbrainz.org/release/20a8b281-3e81-4b5a-a3eb-8e43765f8856.html Trekkies 2 soundtrack], as well as a demo EP [http://musicbrainz.org/release/810729b7-c10f-42ea-85c0-8f535d20e67c.html Metal of Honor] (with the same two songs). However, although they sing in Klingon, their song titles are in English. <br />
<br />
[http://musicbrainz.org/artist/f6bf9642-2373-4e1f-a432-e898a70cbb33.html Bianca Maria Gerlich] ("Klingon" name: K'Vacor [although tlhIngan Hol has neither 'k' nor 'c') has a CD (probably a CD-R) with a Klingon song - a [http://musicbrainz.org/release/97a407b8-00ac-4171-888d-1fd74f9bf790.html single with Italian and Klingon versions] of Puccini's aria "Un bel di vedremo" from Madame Butterfly. (Thanks to [[User:mo|mo]] for finding this on FreeDB). Unfortunately, it's entered as <code><nowiki>[Multiple languages]</nowiki></code> since only one track title is in Klingon. [[User:Dupuy|@alex]] <br />
<br />
''That album is indeed in Klingon, but I don't know the language well enough to recompose the correct Klingon script characters (or, for that matter, whether the Unicode Consortium has officially added it yet or not. Last I checked it was still on the Extension list, along with Elvish).'' -Sailorleo <br />
<ul><li style="list-style-type:none">As noted in the Wikipedia article, there are several non-Latin scripts for Klingon, the most popular (if that word could actually be used) is the [http://en.wikipedia.org/wiki/Klingon_language#KLI_pIqaD KLI pIqaD]. However, this was rejected by Unicode for official inclusion, and exists only in a private use space for now. As such, and given that few (if any) systems include fonts for Klingon, it's unlikely we'll see Klingon script entries. Even if one were entered, there's no ISO 15924 code for tlhIngan pIqaD, and thus no possibility to specify it. [[User:Dupuy|@alex]] <br />
</ul><br />
<br />
[[Category:To Be Reviewed]] [[Category:Metadata]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=International_Artists&diff=12433
International Artists
2006-11-19T22:11:53Z
<p>Dupuy: add ElvishArtists (there is one, apparently) (Imported from MoinMoin)</p>
<hr />
<div>=Artists in Many Languages from All Over the World=<br />
<br />
[[MusicBrainz]] has listings for artists who perform in many languages from all over the world. Some of them are listed here. Eventually, it should be possible to record the native language and home country of an artist in the [[MusicBrainz]] database itself, and these pages will become redundant. <br />
<br />
Of particular note for [[Internationalization|InterNationalization]] are artists whose names and titles of works are in non-Latin alphabets. <br />
* [[Afrikaans Artists|AfrikaansArtists]] (Afrikaans) <br />
* [[Albanian Artists|AlbanianArtists]] (Shqip) <br />
* [[Arabic Artists|ArabicArtists]] (العرب) <br />
* [[Basque Artists|BasqueArtists]] (Euskara) <br />
* [[Belarusian Artists|BelarusianArtists]] (Беларуская) <br />
* [[Breton Artists|BretonArtists]] (Brezhoneg) <br />
* [[Bulgarian Artists|BulgarianArtists]] (Български) <br />
* [[Catalan Artists|CatalanArtists]] (Català) <br />
* [[Chinese Artists|ChineseArtists]] (中文: 繁體 / 简体) <br />
* [[Croatian Artists|CroatianArtists]] (Hrvatski) <br />
* [[Czech Artists|CzechArtists]] (Česká) <br />
* [[Danish Artists|DanishArtists]] (Dansk) <br />
* [[Dutch Artists|DutchArtists]] (Nederlands) <br />
* [[Esperanto Artists|EsperantoArtists]] (Esperanto) <br />
* [[Estonian Artists|EstonianArtists]] (Eesti) <br />
* [[Elvish Artists|ElvishArtists]] (Quenya & Sindarin) <br />
* [[Faroese Artists|FaroeseArtists]] (Føroyskt) <br />
* [[Finnish Artists|FinnishArtists]] (Suomi) <br />
* [[French Artists|FrenchArtists]] (Français) <br />
* [[German Artists|GermanArtists]] (Deutsch) <br />
* [[Greek Artists|GreekArtists]] (Ελληνικά) <br />
* [[Hawaiian Artists|HawaiianArtists]] ('Ōlelo Hawai'i) <br />
* [[Hebrew Artists|HebrewArtists]] (עברית) <br />
* [[Hindi Artists|HindiArtists]] (हिन्दी) <br />
* [[Hungarian Artists|HungarianArtists]] (Magyar) <br />
* [[Icelandic Artists|IcelandicArtists]] (Íslenska) <br />
* [[Indonesian Artists|IndonesianArtists]] (Bahasa Indonesia) <br />
* [[Irish Artists|IrishArtists]] (Gaeilge) <br />
* [[Italian Artists|ItalianArtists]] (Italiano) <br />
* [[Japanese Artists|JapaneseArtists]] (日本語) <br />
* [[Javanese Artists|JavaneseArtists]] (Basa Jawi) <br />
* [[Kannada Artists|KannadaArtists]] (ಕನ್ನಡ) <br />
* [[Klingon Artists|KlingonArtists]] (tlhIngan Hol) <br />
* [[Korean Artists|KoreanArtists]] (한국어) <br />
* [[Latin Artists|LatinArtists]] (Latin) <br />
* [[Latvian Artists|LatvianArtists]] (Latviešu) <br />
* [[Lingala Artists|LingalaArtists]] (Lingala) <br />
* [[Lithuanian Artists|LithuanianArtists]] (Lietuvių) <br />
* [[Malay Artists|MalayArtists]] (Bahasa Melayu) <br />
* [[Maori Artists|MaoriArtists]] (Te Reo Māori) <br />
* [[Norwegian Artists|NorwegianArtists]] (Norsk) <br />
* [[Persian Artists|PersianArtists]] (فارسی) <br />
* [[Polish Artists|PolishArtists]] (Polski) <br />
* [[Portuguese Artists|PortugueseArtists]] (Português) <br />
* [[Romanian Artists|RomanianArtists]] (Română) <br />
* [[Russian Artists|RussianArtists]] (Русский) <br />
* [[Sami Artists|SamiArtists]] (Sámi) <br />
* [[Scottish Artists|ScottishArtists]] (Gàidhlig) <br />
* [[Serbian Artists|SerbianArtists]] (Српски) <br />
* [[Slovak Artists|SlovakArtists]] (Slovenčina) <br />
* [[Slovenian Artists|SlovenianArtists]] (Slovenščina) <br />
* [[Spanish Artists|SpanishArtists]] (Español) <br />
* [[Sundanese Artists|SundaneseArtists]] (Basa Sunda) <br />
* [[Swahili Artists|SwahiliArtists]] (Kiswahili) <br />
* [[Swedish Artists|SwedishArtists]] (Svenska) <br />
* [[Tagalog Artists|TagalogArtists]] (Tagalog) <br />
* [[Tamil Artists|TamilArtists]] (தமிழ்) <br />
* [[Thai Artists|ThaiArtists]] (ไทย) <br />
* [[Turkish Artists|TurkishArtists]] (Türkçe) <br />
* [[Ukrainian Artists|UkrainianArtists]] (Українська) <br />
* [[Urdu Artists|UrduArtists]] (اردو) <br />
* [[Vietnamese Artists|VietnameseArtists]] (Tiếng Việt) <br />
* [[Welsh Artists|WelshArtists]] (Cymraeg) <br />
<br />
==Other Resources==<br />
<br />
The [http://en.wikipedia.org/wiki/Category:Musical_groups_by_nationality Wikipedia list of Musical Groups by Nationality] is useful for non-English artists; please remember, however, that these pages are organized by [[Language Code|language]] not by [[Country Code|nation]]. <br />
<br />
If you are working to update any of these entries, there are [[Online Translator|OnlineTranslator]]s that may be helpful; some even provide transliteration, which is especially useful for [[Artist Name|ArtistName]]s. <br />
<br />
If you know of any artist that sould be listed under one of these, but you do not know ''which'' you might want to try to [[Tell Similar Languages Apart|TellSimilarLanguagesApart]] <br />
<br />
[[Category:To Be Reviewed]] [[Category:Metadata]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Klingon_Artists&diff=22557
Klingon Artists
2006-11-19T21:13:15Z
<p>Dupuy: note on ISO 15924 (Imported from MoinMoin)</p>
<hr />
<div>=Artists with Klingon Names or Works with Titles in Klingon=<br />
<br />
The following is a partial list of [[International Artists|InternationalArtists]] whose names are Klingon or who have works with titles in Klingon. If you can read and write Klingon, please consider adding these artists to your [[Artist Subscription|ArtistSubscription]]s so that you can be notified when there are additions or changes to their discographies, and you can check them for errors. If you know of other Klingon artists not listed here, please add them. <br />
<br />
----<br />
<br />
<br />
* [http://musicbrainz.org/artist/b4542a0c-95fb-467f-8724-101dd7efc453.html Marc Okrand] <br />
* [http://musicbrainz.org/artist/f6bf9642-2373-4e1f-a432-e898a70cbb33.html Bianca Maria Gerlich (K'Vacor)] <br />
* [http://musicbrainz.org/artist/85312ab2-4300-4226-9ab2-71fe11eb1c8c.html Stovokor] <br />
<br />
==Discussion==<br />
<br />
While there are of course no real Klingons, there ''is'' a real (if artificial) Klingon language (tlhIngan Hol), as legitimate as Esperanto or other artificial languages, if perhaps not as widely used. There's a good [http://en.wikipedia.org/wiki/Klingon_language Wikipedia article] about Klingon. [http://musicbrainz.org/artist/b4542a0c-95fb-467f-8724-101dd7efc453.html Marc Okrand] is the inventor of the Klingon language, so if anyone could be said to be a native speaker, it would be him. However, he only has two [[Spoken Word|SpokenWord]] releases that attempt to teach some of the language. (Note that these are entered in the database as ''English/Latin'' since that's the language the titles are in.) <br />
<br />
There are two known artists who have released music in Klingon. The Portland death-metal band [http://musicbrainz.org/artist/85312ab2-4300-4226-9ab2-71fe11eb1c8c.html Stovokor] has two songs on the [http://musicbrainz.org/release/20a8b281-3e81-4b5a-a3eb-8e43765f8856.html Trekkies 2 soundtrack], as well as a demo EP [http://musicbrainz.org/release/810729b7-c10f-42ea-85c0-8f535d20e67c.html Metal of Honor] (with the same two songs). However, although they sing in Klingon, their song titles are in English. <br />
<br />
[http://musicbrainz.org/artist/f6bf9642-2373-4e1f-a432-e898a70cbb33.html Bianca Maria Gerlich] ("Klingon" name: K'Vacor [although tlhIngan Hol has neither 'k' nor 'c') has a CD (probably a CD-R) with a Klingon song - a [http://musicbrainz.org/release/97a407b8-00ac-4171-888d-1fd74f9bf790.html single with Italian and Klingon versions] of Puccini's aria "Un bel di vedremo" from Madame Butterfly. (Thanks to [[User:mo|mo]] for finding this on FreeDB). Unfortunately, it's entered as <code><nowiki>[Multiple languages]</nowiki></code> since only one track title is in Klingon. [[User:Dupuy|@alex]] <br />
<br />
''That album is indeed in Klingon, but I don't know the language well enough to recompose the correct Klingon script characters (or, for that matter, whether the Unicode Consortium has officially added it yet or not. Last I checked it was still on the Extension list, along with Elvish).'' -Sailorleo <br />
<ul><li style="list-style-type:none">As noted in the Wikipedia article, there are several non-Latin scripts for Klingon, the most popular (if that word could actually be used) is the [http://en.wikipedia.org/wiki/Klingon_language#KLI_pIqaD KLI pIqaD]. However, this was rejected by Unicode for official inclusion, and exists only in a private use space for now. As such, and given that few (if any) systems include fonts for Klingon, it's unlikely we'll see Klingon script entries. Even if one were entered, there's no ISO 15924 code for tlhIngan pIqaD, and thus no possibility to specify it. [[User:Dupuy|@alex]] <br />
</ul><br />
<br />
[[Category:To Be Reviewed]] [[Category:Metadata]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Klingon_Artists&diff=22558
Klingon Artists
2006-11-19T19:46:37Z
<p>Dupuy: updated, with two new Klingon artists (Imported from MoinMoin)</p>
<hr />
<div>=Artists with Klingon Names or Works with Titles in Klingon=<br />
<br />
The following is a partial list of [[International Artists|InternationalArtists]] whose names are Klingon or who have works with titles in Klingon. If you can read and write Klingon, please consider adding these artists to your [[Artist Subscription|ArtistSubscription]]s so that you can be notified when there are additions or changes to their discographies, and you can check them for errors. If you know of other Klingon artists not listed here, please add them. <br />
<br />
----<br />
<br />
<br />
* [http://musicbrainz.org/artist/b4542a0c-95fb-467f-8724-101dd7efc453.html Marc Okrand] <br />
* [http://musicbrainz.org/artist/f6bf9642-2373-4e1f-a432-e898a70cbb33.html Bianca Maria Gerlich (K'Vacor)] <br />
* [http://musicbrainz.org/artist/85312ab2-4300-4226-9ab2-71fe11eb1c8c.html Stovokor] <br />
<br />
==Discussion==<br />
<br />
While there are of course no real Klingons, there ''is'' a real (if artificial) Klingon language (tlhIngan Hol), as legitimate as Esperanto or other artificial languages, if perhaps not as widely used. There's a good [http://en.wikipedia.org/wiki/Klingon_language Wikipedia article] about Klingon. [http://musicbrainz.org/artist/b4542a0c-95fb-467f-8724-101dd7efc453.html Marc Okrand] is the inventor of the Klingon language, so if anyone could be said to be a native speaker, it would be him. However, he only has two [[Spoken Word|SpokenWord]] releases that attempt to teach some of the language. (Note that these are entered in the database as ''English/Latin'' since that's the language the titles are in.) <br />
<br />
There are two known artists who have released music in Klingon. The Portland death-metal band [http://musicbrainz.org/artist/85312ab2-4300-4226-9ab2-71fe11eb1c8c.html Stovokor] has two songs on the [http://musicbrainz.org/release/20a8b281-3e81-4b5a-a3eb-8e43765f8856.html Trekkies 2 soundtrack], as well as a demo EP [http://musicbrainz.org/release/810729b7-c10f-42ea-85c0-8f535d20e67c.html Metal of Honor] (with the same two songs). However, although they sing in Klingon, their song titles are in English. <br />
<br />
[http://musicbrainz.org/artist/f6bf9642-2373-4e1f-a432-e898a70cbb33.html Bianca Maria Gerlich] ("Klingon" name: K'Vacor [although tlhIngan Hol has neither 'k' nor 'c') has a CD (probably a CD-R) with a Klingon song - a [http://musicbrainz.org/release/97a407b8-00ac-4171-888d-1fd74f9bf790.html single with Italian and Klingon versions] of Puccini's aria "Un bel di vedremo" from Madame Butterfly. (Thanks to [[User:mo|mo]] for finding this on FreeDB). Unfortunately, it's entered as <code><nowiki>[Multiple languages]</nowiki></code> since only one track title is in Klingon. [[User:Dupuy|@alex]] <br />
<br />
''That album is indeed in Klingon, but I don't know the language well enough to recompose the correct Klingon script characters (or, for that matter, whether the Unicode Consortium has officially added it yet or not. Last I checked it was still on the Extension list, along with Elvish).'' -Sailorleo <br />
<ul><li style="list-style-type:none">As noted in the Wikipedia article, there are several non-Latin scripts for Klingon, the most popular (if that word could actually be used) is the [http://en.wikipedia.org/wiki/Klingon_language#KLI_pIqaD KLI pIqaD]. However, this was rejected by Unicode for official inclusion, and exists only in a private use space for now. As such, and given that few (if any) systems include fonts for Klingon, it's unlikely we'll see Klingon script entries. [[User:Dupuy|@alex]] <br />
</ul><br />
<br />
[[Category:To Be Reviewed]] [[Category:Metadata]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Series/Mozart_Complete_Philips&diff=14508
Series/Mozart Complete Philips
2006-11-08T00:05:35Z
<p>Dupuy: suggest SeriesStyleGuideline, note on post vs. wiki (Imported from MoinMoin)</p>
<hr />
<div>This is just a space to organize and keep track of Mozart's "Complete Mozart Edition" series. There are a total of 45 volumes with multiple discs per volume. The volumes were originally released by Philips starting on 1990-10-12 and it appears that two volumes were released each month thereafter. <br />
<br />
If you see a release on [http://musicbrainz.org/artist/b972f589-fb0e-474e-b64a-803b0364fa75.html Wolfgang Amadeus Mozart]'s artist page that isn't documented here, please add a link so we can attempt to get this whole series entered into the database. I'm sure there are several more releases already in [[MusicBrainz]] that belong to the series, so make sure you search Mozart's page before you import/add the missing release. Searching for the volume number (i.e., "Volume 4:") works well, as does searching for the volume's subtitle (i.e., "Serenades and Divertimenti for Wind"). Also, some of these discs may be under the performer's artist page, so watch out for that! <br />
<br />
If you see a disc below that is not linked, see if you can find it in [[MusicBrainz]] and add a link to the release here. <br />
<br />
==Part I - Volumes 1-21==<br />
<br />
<ul><li style="list-style-type:none">(see [http://www.iclassics.com/productDetail?contentId=3254 iClassics]) <br />
</ul><br />
{| border="1"<br />
|-<br />
| '''[[Volume Number|VolumeNumber]]: [[Subtitle|SubTitle]]''' || '''Tracklisting''' || '''[[MusicBrainz]] Releases''' || '''Release Date'''<br />
|-<br />
| Volume 1: Early Symphonies || [http://www.iclassics.com/productDetail?contentId=479 iClassics] || [http://musicbrainz.org/release/20f926aa-43e6-4e13-932a-586fa1c280b3.html disc 1] [http://musicbrainz.org/release/e52335fb-e62b-4339-8da3-12129ee7651e.html disc 2] [http://musicbrainz.org/release/40508ea4-cc6d-4c08-8c0a-a1f5813cb77d.html disc 3] [http://musicbrainz.org/release/1a064fa8-dce2-40e3-b29a-43cc754d4111.html disc 4] [http://musicbrainz.org/release/8e5d2c2f-04eb-4568-942b-fb3a4e045562.html disc 5] [http://musicbrainz.org/release/39054db6-7ba9-4f32-85ed-a8d5c28f6bc2.html disc 6] || 1990-10-12<br />
|-<br />
| Volume 2: Symphonies || [http://www.iclassics.com/productDetail?contentId=351 iClassics] || [http://musicbrainz.org/release/22469726-2b29-4779-a0bd-7cc3186aa083.html disc 1] [http://musicbrainz.org/release/ee4f4ac6-4bfd-40a4-b2c8-b2fbc5f66367.html disc 2] [http://musicbrainz.org/release/1c497ae6-2558-45ab-b7d7-e7bd555cdd3a.html disc 3] [http://musicbrainz.org/release/3d9b2cd7-e35b-45c3-964e-ad553e67e3da.html disc 4] [http://musicbrainz.org/release/27deb4f6-e5f6-4d16-ac70-c948ec74c4e6.html disc 5] [http://musicbrainz.org/release/5596d094-d186-4abc-a64a-6071322c21bf.html disc 6] || 1990-10-12<br />
|-<br />
| Volume 3: Serenades for Orchestra || [http://www.iclassics.com/productDetail?contentId=890 iClassics] || [http://musicbrainz.org/release/2b16e8b6-0d8d-4069-9ba1-4b828ce22ec4.html disc 1] [http://musicbrainz.org/release/e3248e84-6868-4d25-91ea-3bf6ed4de398.html disc 2] [http://musicbrainz.org/release/3c4f5341-a845-4cb4-9ba0-708139b04dd1.html disc 3] [http://musicbrainz.org/release/1c8c4f31-c9a7-4fe6-8967-a12393ee0f84.html disc 4] [http://musicbrainz.org/release/2233254b-f3ff-45e8-98ca-041a36ab4031.html disc 5] [http://musicbrainz.org/release/54d2c964-bbad-45bf-9ea6-f03c7cbb191e.html disc 6] [http://musicbrainz.org/release/4d499d8c-1938-4549-bf09-3564c982b521.html disc 7] || 1990-11-10<br />
|-<br />
| Volume 4: Divertimenti || [http://www.iclassics.com/productDetail?contentId=716 iClassics] || [http://musicbrainz.org/release/af98b44a-2bd9-403b-ba67-3042b45f049e.html disc 1] [http://musicbrainz.org/release/ffdf7a17-d070-459e-889d-1bf26bc88d48.html disc 2] [http://musicbrainz.org/release/8528d426-e287-4706-8d1a-a157d369a2ad.html disc 3] [http://musicbrainz.org/release/56bf51cc-88c0-4812-9b95-73338fd7ef5a.html disc 4] [http://musicbrainz.org/release/6ebe7331-b17d-4969-a1de-22cb6c6eca57.html disc 5] || 1990-11-10<br />
|-<br />
| Volume 5: Serenades and Divertimenti for Wind || [http://www.iclassics.com/productDetail?contentId=882 iClassics] || [http://musicbrainz.org/release/019d0646-ff13-4a17-aee7-33996abdb551.html disc 1] [http://musicbrainz.org/release/6adc8c7c-24da-4e6f-9749-55e0e79294b8.html disc 2] [http://musicbrainz.org/release/876b6b99-3852-42d7-b3e9-9393f4e16036.html disc 3] [http://musicbrainz.org/release/18146173-c6c4-49c3-ba9c-5f7505487124.html disc 4] [http://musicbrainz.org/release/355d4f0b-89c4-4ac3-b84e-4628eb7ebc80.html disc 5] [http://musicbrainz.org/release/352eee7b-2ae0-497f-974c-b79cf1ecf586.html disc 6] || 1990-12-10<br />
|-<br />
| Volume 6: Dances and Marches || [http://www.iclassics.com/productDetail?contentId=2402 iClassics] || disc 1 disc 2 disc 3 disc 4 disc 5 disc 6 || 1990-12-10<br />
|-<br />
| Volume 7: Piano Concertos || [http://www.iclassics.com/productDetail?contentId=2050 iClassics] || [http://musicbrainz.org/release/576701d7-8d7e-4524-a80e-07f1b66d332e.html disc 1] [http://musicbrainz.org/release/53971795-3c83-42e2-8ee4-16ebb4b5e252.html disc 2] [http://musicbrainz.org/release/86248e8f-7337-42f3-9813-6c33286ab773.html disc 3] [http://musicbrainz.org/release/3516bc19-48ba-4f25-9fc2-40071b5ecb48.html disc 4] [http://musicbrainz.org/release/a38e5dea-545e-467b-b724-d8b550857e33.html disc 5] [http://musicbrainz.org/release/98dceb25-14d3-4142-b48a-03f57404abbd.html disc 6] [http://musicbrainz.org/release/cf6a1f7b-090c-4e90-ac47-892eb03841fb.html disc 7] disc 8 disc 9 disc 10 [http://musicbrainz.org/release/d0cb2574-e733-4285-a127-f8ad157f5a0e.html disc 11] [http://musicbrainz.org/release/d0be044a-204b-472b-b518-fbdc781b58dc.html disc 12] || 1991-01-18<br />
|-<br />
| Volume 8: Violin Concertos || [http://www.iclassics.com/productDetail?contentId=2666 iClassics] || disc 1 disc 2 disc 3 disc 4 || 1991-03-08<br />
|-<br />
| Volume 9: Wind Concertos || [http://www.iclassics.com/productDetail?contentId=1105 iClassics] || disc 1 disc 2 disc 3 disc 4 disc 5 || 1991-03-08<br />
|-<br />
| Volume 10: Quintets & Quartets, etc. || [http://www.iclassics.com/productDetail?contentId=419 iClassics] || disc 1 disc 2 disc 3 || 1991-03-08<br />
|-<br />
| Volume 11: String Quintets || [http://www.iclassics.com/productDetail?contentId=2717 iClassics] || [http://musicbrainz.org/release/507b0e90-82f8-4c40-ac97-e4d3915d7f19.html disc 1] [http://musicbrainz.org/release/5228ff70-7ed1-43f1-9aae-8d6ef17b8a8e.html disc 2] [http://musicbrainz.org/release/b9eb4bd7-d85c-4284-acff-8441087dbcaf.html disc 3] || 1991-03-08<br />
|-<br />
| Volume 12: String Quartets || [http://www.iclassics.com/productDetail?contentId=344 iClassics] || [http://musicbrainz.org/release/7bdf9a29-7732-43e4-8527-12b243eacdab.html disc 1] [http://musicbrainz.org/release/5cd10634-e0c7-4744-a04e-8676696b9659.html disc 2] [http://musicbrainz.org/release/54e0c001-03f3-4d4d-98c1-49950cad2a8c.html disc 3] [http://musicbrainz.org/release/a35002ad-826b-4390-ad25-d858a425c827.html disc 4] [http://musicbrainz.org/release/2f26dac8-52ea-4a9d-9213-9096ed657f55.html disc 5] [http://musicbrainz.org/release/ad91a763-eb65-4091-93a9-f9804ac2767f.html disc 6] [http://musicbrainz.org/release/fc3958ed-8d94-425c-91a2-9c3b64e15196.html disc 7] [http://musicbrainz.org/release/e69ecbce-ca6b-421e-bea2-a8d5f35b023d.html disc 8] || 1991-04-05<br />
|-<br />
| Volume 13: String Trios & Duos || [http://www.iclassics.com/productDetail?contentId=106 iClassics] || disc 1 disc 2 || 1991-04-05<br />
|-<br />
| Volume 14: Piano Quintet / Quartet / Trios || [http://www.iclassics.com/productDetail?contentId=2656 iClassics] || disc 1 disc 2 disc 3 disc 4 disc 5 || 1991-04-05<br />
|-<br />
| Volume 15: Violin Sonatas || [http://www.iclassics.com/productDetail?contentId=2438 iClassics] || disc 1 disc 2 disc 3 disc 4 disc 5 disc 6 disc 7 || 1991-05-10<br />
|-<br />
| Volume 16: Music for 2 Pianos / Piano Duets || [http://www.iclassics.com/productDetail?contentId=405 iClassics] || disc 1 disc 2 || 1991-05-10<br />
|-<br />
| Volume 17: Piano Sonatas || [http://www.iclassics.com/productDetail?contentId=2595 iClassics] || [http://musicbrainz.org/release/818b36a0-2018-4438-b21f-e71eca07843d.html disc 1] disc 2 [http://musicbrainz.org/release/19611203-7c6a-440d-bf4d-89d0e310ca3d.html disc 3] [http://musicbrainz.org/release/1c4edb11-6038-41fe-a13a-04a15ad74750.html disc 4] disc 5 || 1991-05-10<br />
|-<br />
| Volume 18: Piano Variations / Rondos || [http://www.iclassics.com/productDetail?contentId=893 iClassics] || disc 1 disc 2 disc 3 disc 4 disc 5 || 1991-06-14<br />
|-<br />
| Volume 19: Masses / Requiem || [http://www.iclassics.com/productDetail?contentId=2557 iClassics] || disc 1 disc 2 disc 3 disc 4 disc 5 disc 6 [http://musicbrainz.org/release/76429dfe-985d-408d-9910-668fce32f54d.html disc 7] [http://musicbrainz.org/release/8cabaafe-4cb8-48b4-abcb-939a43154457.html disc 8] disc 9 || 1991-06-14<br />
|-<br />
| Volume 20: Litanies, Vespers, etc. || [http://www.iclassics.com/productDetail?contentId=349 iClassics] || disc 1 disc 2 disc 3 disc 4 disc 5 || 1991-07-12<br />
|-<br />
| Volume 21: Organ Sonatas & Solos || [http://www.iclassics.com/productDetail?contentId=758 iClassics] || disc 1 disc 2 || 1991-07-12<br />
|}<br />
<br />
==Part II - Volumes 22-45==<br />
<br />
<ul><li style="list-style-type:none">(see [http://www.iclassics.com/productDetail?contentId=3256 iClassics]) <br />
</ul><br />
<br />
==Discussion==<br />
<br />
It might make sense to have a [[Series Style Guideline|SeriesStyleGuideline]] for this series, just to make it clear what the [[Classical Style Guide|ClassicalStyleGuide]] suggests for each volume and disc, and to suggest minor enhancements (e.g. since there are > 10 entries, perhaps it makes sense to name them Volume 01, Volume 02, etcetera, so that they sort correctly by title - or perhaps that's too ugly, and the release date provides the necessary sorting). Just a thought. [[User:Dupuy|@alex]] <br />
<br />
P.S. It's easier for 15 people to edit the wiki than to have them all post to the mailing list - if somebody is already editing a wiki page, you are warned, and it helps avoid duplication of effort (and noise on the mailing list). <br />
<br />
[[Category:To Be Reviewed]] [[Category:To Do List]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Great_Dispute&diff=7237
History:Great Dispute
2006-08-22T22:32:45Z
<p>Dupuy: reponse to DonRedman's comment on principle names (Imported from MoinMoin)</p>
<hr />
<div>=The Great Dispute=<br />
<br />
The dispute, which is still ongoing as of 2006-08-21. If the project survives this, it may be remembered as the Great Dispute. <br />
<br />
==Related Documents==<br />
<br />
''Currently a random collection of 'places' and events of the dispute.'' <br />
* The [[MusicBrainz Haiku|MusicBrainzHaiku]] gives the shortest possible summary. <br />
* On August 15th, 2006 Robert writes a blog post entitled [http://blog.musicbrainz.org/archives/2006/08/developer_chang.html Developer changes], in which he states that he will remove [[User:Keschte|Keschte]]'s developer privileges. <br />
<br />
==The IRC Chat==<br />
<br />
On August 21st, 2006, from 2100 to about 2330 GMT, there was an [[IRC]] discussion about this problem (see [http://chatlogs.musicbrainz.org/2006/2006-08/2006-08-21.html#T21-01-52-447060 chatlog]), which still managed to be less voluminous than the [[Users Mailing List|UsersMailingList]] discussion. <br />
<br />
During this discussion, the participants developed a list of the underlying problems that had led up to the dispute: <br />
# differences in coding and communications styles <br />
# lack of sufficient resources for developers (enough staging/testing servers, etc.) <br />
# lack of guidelines or rules of behavior for the development team (and community) <br />
# changes in MB as the community becomes larger, and more "businesslike" <br />
# failures or deficiencies in the communications forums (e.g. arguments in Trac tickets) <br />
# lack of clarity about the "final arbiter" of disputes <br />
# missing development guidelines/concept + master plan <br />
<br />
Generally, points 1 and 3 were felt to be the most significant, with 4, 5, and 6 also important. <br />
<br />
To address these problems, a number of of guiding principles for the [[MusicBrainz]] community were outlined; these should eventually have their own [[Wiki Pages|WikiPages]], once we come up with good [[Wiki Phrases|WikiPhrases]] for them (add your suggestions to the Discussion below): <br />
* Create an environment that encourages volunteers (developers and others) <br />
* Transparency in communications (public) and process (documented) <br />
* Seek mediators for conflicts, ideally, even before they occur <br />
* Distribute responsibility, by asking for help, and growing teams <br />
* Needs of the community as a whole come before the demands of any individual <br />
<br />
Although there wasn't time to discuss them in much detail, the [[User:Dupuy|moderator]] also came up with a list of various proposals (originally with two items numbered 3, and forgetting to include the last two items) that were suggested earlier on the mailing list, or which were mentioned in the IRC chat: <br />
# Agree on and document development process <br />
# Agree on and document conflict-resolution process <br />
# Codes of conduct for developers and others <br />
# Bug triage team for Trac <br />
# Changes to rollout process (selectable server versions? live-data testing?) <br />
# "Support groups" (like Wikipedia Esperanza, etc.) <br />
# Improvements to development resources (more testing/staging servers?) <br />
# Establishing web "forum(s?)" for better communication between developers/users <br />
# Enhance mb server to collect immediate feedback from users <br />
<br />
There is much that still needs to be done - some of these proposals must be made much more specific to be meaningful, and some of them are surely quite contentious (notably the first two or three). As a start, if you are interested in participating in one or more of these, please note your interest in the Discussion section below. As the mailing lists have been pretty swamped lately, it may be more effective to create wiki pages for each of these and to have the discussion there; please discuss the page names here before creating them (that will probably happen sometime later on Tuesday). <br />
<br />
==Discussion==<br />
<br />
===WikiNames===<br />
<br />
Okay, here are my ideas for names for the principles: [[Encourage Volunteers|EncourageVolunteers]], [[Participate Openly|ParticipateOpenly]], [[Seek Mediators|SeekMediators]], [[Distribute Responsibility|DistributeResponsibility]], and [[Put Community First|PutCommunityFirst]]. They can surely be improved (especially the second one, it's tough to capture in 2-3 words, especially since "open" and "transparent" are so abused as to have lost much meaning), and made more consistent, so please don't go and create them (yet). As for participation in the proposals, I'm afraid that moderating the IRC chat pretty much used up my available time - I will try to work on this and related wiki pages when I can, but that's probably all I can really commit to at the moment. [[User:Dupuy|@alex]] <br />
<br />
''Please add your thoughts here!'' <br />
<ul><li style="list-style-type:none">Alternatives for [[Participate Openly|ParticipateOpenly]]: What about if you have a problem or there is a good common practice, then go and [[Make It Public|MakeItPublic]]! I have not Idea how the "it" could be better qualified to include "I belive we have a serious problem there", but not "Look at what that idiot has been doing". Maybe that is too complex to be caputured in a wiki phrase. :-) --[[User:DonRedman|DonRedman]] ''I like [[Make It Public|MakeItPublic]], perhaps "publish" is the word to capture public communication and documentation. How about "[[Publish Problems|PublishProblems]]" and/or "[[Publish Solutions|PublishSolutions]]"? (I can't find one noun that captures both communications about problems and records of the solutions).'' [[User:Dupuy|@alex]] <br />
</ul><br />
<br />
===Support Groups===<br />
<br />
I would like to work on realising #6 - after reading all the Wikipedia links about it and in case [[User:DonRedman|DonRedman]] can help me with his expertise. :) I think it's important to find an expressive name for such a group like Wikipedia has with "Esperanza". Suggestions? :) -- [[User:Shepard|Shepard]] <br />
<br />
====Brainstorm for a Name====<br />
<br />
''(just add to the list, no negative comments)'' <br />
* Esperanza <br />
* [[Cup Of Hope|CupOfHope]] <br />
* [[Rent A Moose|RentAMoose]] - inspired by our [[MusicBrainz Slang|unofficial mascot]]; expresses that you "rent" a mediator/helper when you have problems; unfortunately not a working [[Wiki Name|WikiName]] :( <br />
* I would hope we could find a music-related name; a bit of searching turned up [http://en.wikipedia.org/wiki/Glee_club GleeClub], which I like quite a bit [[User:Dupuy|@alex]] <br />
<br />
While we're at it, we could probably use a name for the bug triage group as well; I thought of [[Piano Tuners|PianoTuners]] but it seems a bit of a stretch... <br />
<br />
[[Category:To Be Reviewed]] [[Category:Philosophy]] [[Category:History]] [[Category:Discussion]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Great_Dispute&diff=7238
History:Great Dispute
2006-08-22T22:25:33Z
<p>Dupuy: typo (Imported from MoinMoin)</p>
<hr />
<div>=The Great Dispute=<br />
<br />
The dispute, which is still ongoing as of 2006-08-21. If the project survives this, it may be remembered as the Great Dispute. <br />
<br />
==Related Documents==<br />
<br />
''Currently a random collection of 'places' and events of the dispute.'' <br />
* The [[MusicBrainz Haiku|MusicBrainzHaiku]] gives the shortest possible summary. <br />
* On August 15th, 2006 Robert writes a blog post entitled [http://blog.musicbrainz.org/archives/2006/08/developer_chang.html Developer changes], in which he states that he will remove [[User:Keschte|Keschte]]'s developer privileges. <br />
<br />
==The IRC Chat==<br />
<br />
On August 21st, 2006, from 2100 to about 2330 GMT, there was an [[IRC]] discussion about this problem (see [http://chatlogs.musicbrainz.org/2006/2006-08/2006-08-21.html#T21-01-52-447060 chatlog]), which still managed to be less voluminous than the [[Users Mailing List|UsersMailingList]] discussion. <br />
<br />
During this discussion, the participants developed a list of the underlying problems that had led up to the dispute: <br />
# differences in coding and communications styles <br />
# lack of sufficient resources for developers (enough staging/testing servers, etc.) <br />
# lack of guidelines or rules of behavior for the development team (and community) <br />
# changes in MB as the community becomes larger, and more "businesslike" <br />
# failures or deficiencies in the communications forums (e.g. arguments in Trac tickets) <br />
# lack of clarity about the "final arbiter" of disputes <br />
# missing development guidelines/concept + master plan <br />
<br />
Generally, points 1 and 3 were felt to be the most significant, with 4, 5, and 6 also important. <br />
<br />
To address these problems, a number of of guiding principles for the [[MusicBrainz]] community were outlined; these should eventually have their own [[Wiki Pages|WikiPages]], once we come up with good [[Wiki Phrases|WikiPhrases]] for them (add your suggestions to the Discussion below): <br />
* Create an environment that encourages volunteers (developers and others) <br />
* Transparency in communications (public) and process (documented) <br />
* Seek mediators for conflicts, ideally, even before they occur <br />
* Distribute responsibility, by asking for help, and growing teams <br />
* Needs of the community as a whole come before the demands of any individual <br />
<br />
Although there wasn't time to discuss them in much detail, the [[User:Dupuy|moderator]] also came up with a list of various proposals (originally with two items numbered 3, and forgetting to include the last two items) that were suggested earlier on the mailing list, or which were mentioned in the IRC chat: <br />
# Agree on and document development process <br />
# Agree on and document conflict-resolution process <br />
# Codes of conduct for developers and others <br />
# Bug triage team for Trac <br />
# Changes to rollout process (selectable server versions? live-data testing?) <br />
# "Support groups" (like Wikipedia Esperanza, etc.) <br />
# Improvements to development resources (more testing/staging servers?) <br />
# Establishing web "forum(s?)" for better communication between developers/users <br />
# Enhance mb server to collect immediate feedback from users <br />
<br />
There is much that still needs to be done - some of these proposals must be made much more specific to be meaningful, and some of them are surely quite contentious (notably the first two or three). As a start, if you are interested in participating in one or more of these, please note your interest in the Discussion section below. As the mailing lists have been pretty swamped lately, it may be more effective to create wiki pages for each of these and to have the discussion there; please discuss the page names here before creating them (that will probably happen sometime later on Tuesday). <br />
<br />
==Discussion==<br />
<br />
===WikiNames===<br />
<br />
Okay, here are my ideas for names for the principles: [[Encourage Volunteers|EncourageVolunteers]], [[Participate Openly|ParticipateOpenly]], [[Seek Mediators|SeekMediators]], [[Distribute Responsibility|DistributeResponsibility]], and [[Put Community First|PutCommunityFirst]]. They can surely be improved (especially the second one, it's tough to capture in 2-3 words, especially since "open" and "transparent" are so abused as to have lost much meaning), and made more consistent, so please don't go and create them (yet). As for participation in the proposals, I'm afraid that moderating the IRC chat pretty much used up my available time - I will try to work on this and related wiki pages when I can, but that's probably all I can really commit to at the moment. [[User:Dupuy|@alex]] <br />
<br />
''Please add your thoughts here!'' <br />
<ul><li style="list-style-type:none">Alternatives for [[Participate Openly|ParticipateOpenly]]: What about if you have a problem or there is a good common practice, then go and [[Make It Public|MakeItPublic]]! I have not Idea how the "it" could be better qualified to include "I belive we have a serious problem there", but not "Look at what that idiot has been doing". Maybe that is too complex to be caputured in a wiki phrase. :-) --[[User:DonRedman|DonRedman]] <br />
</ul><br />
<br />
===Support Groups===<br />
<br />
I would like to work on realising #6 - after reading all the Wikipedia links about it and in case [[User:DonRedman|DonRedman]] can help me with his expertise. :) I think it's important to find an expressive name for such a group like Wikipedia has with "Esperanza". Suggestions? :) -- [[User:Shepard|Shepard]] <br />
<br />
====Brainstorm for a Name====<br />
<br />
''(just add to the list, no negative comments)'' <br />
* Esperanza <br />
* [[Cup Of Hope|CupOfHope]] <br />
* [[Rent A Moose|RentAMoose]] - inspired by our [[MusicBrainz Slang|unofficial mascot]]; expresses that you "rent" a mediator/helper when you have problems; unfortunately not a working [[Wiki Name|WikiName]] :( <br />
* I would hope we could find a music-related name; a bit of searching turned up [http://en.wikipedia.org/wiki/Glee_club GleeClub], which I like quite a bit [[User:Dupuy|@alex]] <br />
<br />
While we're at it, we could probably use a name for the bug triage group as well; I thought of [[Piano Tuners|PianoTuners]] but it seems a bit of a stretch... <br />
<br />
[[Category:To Be Reviewed]] [[Category:Philosophy]] [[Category:History]] [[Category:Discussion]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Great_Dispute&diff=7239
History:Great Dispute
2006-08-22T22:24:17Z
<p>Dupuy: some more ideas for names (Imported from MoinMoin)</p>
<hr />
<div>=The Great Dispute=<br />
<br />
The dispute, which is still ongoing as of 2006-08-21. If the project survives this, it may be remembered as the Great Dispute. <br />
<br />
==Related Documents==<br />
<br />
''Currently a random collection of 'places' and events of the dispute.'' <br />
* The [[MusicBrainz Haiku|MusicBrainzHaiku]] gives the shortest possible summary. <br />
* On August 15th, 2006 Robert writes a blog post entitled [http://blog.musicbrainz.org/archives/2006/08/developer_chang.html Developer changes], in which he states that he will remove [[User:Keschte|Keschte]]'s developer privileges. <br />
<br />
==The IRC Chat==<br />
<br />
On August 21st, 2006, from 2100 to about 2330 GMT, there was an [[IRC]] discussion about this problem (see [http://chatlogs.musicbrainz.org/2006/2006-08/2006-08-21.html#T21-01-52-447060 chatlog]), which still managed to be less voluminous than the [[Users Mailing List|UsersMailingList]] discussion. <br />
<br />
During this discussion, the participants developed a list of the underlying problems that had led up to the dispute: <br />
# differences in coding and communications styles <br />
# lack of sufficient resources for developers (enough staging/testing servers, etc.) <br />
# lack of guidelines or rules of behavior for the development team (and community) <br />
# changes in MB as the community becomes larger, and more "businesslike" <br />
# failures or deficiencies in the communications forums (e.g. arguments in Trac tickets) <br />
# lack of clarity about the "final arbiter" of disputes <br />
# missing development guidelines/concept + master plan <br />
<br />
Generally, points 1 and 3 were felt to be the most significant, with 4, 5, and 6 also important. <br />
<br />
To address these problems, a number of of guiding principles for the [[MusicBrainz]] community were outlined; these should eventually have their own [[Wiki Pages|WikiPages]], once we come up with good [[Wiki Phrases|WikiPhrases]] for them (add your suggestions to the Discussion below): <br />
* Create an environment that encourages volunteers (developers and others) <br />
* Transparency in communications (public) and process (documented) <br />
* Seek mediators for conflicts, ideally, even before they occur <br />
* Distribute responsibility, by asking for help, and growing teams <br />
* Needs of the community as a whole come before the demands of any individual <br />
<br />
Although there wasn't time to discuss them in much detail, the [[User:Dupuy|moderator]] also came up with a list of various proposals (originally with two items numbered 3, and forgetting to include the last two items) that were suggested earlier on the mailing list, or which were mentioned in the IRC chat: <br />
# Agree on and document development process <br />
# Agree on and document conflict-resolution process <br />
# Codes of conduct for developers and others <br />
# Bug triage team for Trac <br />
# Changes to rollout process (selectable server versions? live-data testing?) <br />
# "Support groups" (like Wikipedia Esperanza, etc.) <br />
# Improvements to development resources (more testing/staging servers?) <br />
# Establishing web "forum(s?)" for better communication between developers/users <br />
# Enhance mb server to collect immediate feedback from users <br />
<br />
There is much that still needs to be done - some of these proposals must be made much more specific to be meaningful, and some of them are surely quite contentious (notably the first two or three). As a start, if you are interested in participating in one or more of these, please note your interest in the Discussion section below. As the mailing lists have been pretty swamped lately, it may be more effective to create wiki pages for each of these and to have the discussion there; please discuss the page names here before creating them (that will probably happen sometime later on Tuesday). <br />
<br />
==Discussion==<br />
<br />
===WikiNames===<br />
<br />
Okay, here are my ideas for names for the principles: [[Encourage Volunteers|EncourageVolunteers]], [[Participate Openly|ParticipateOpenly]], [[Seek Mediators|SeekMediators]], [[Distribute Responsibility|DistributeResponsibility]], and [[Put Community First|PutCommunityFirst]]. They can surely be improved (especially the second one, it's tough to capture in 2-3 words, especially since "open" and "transparent" are so abused as to have lost much meaning), and made more consistent, so please don't go and create them (yet). As for participation in the proposals, I'm afraid that moderating the IRC chat pretty much used up my available time - I will try to work on this and related wiki pages when I can, but that's probably all I can really commit to at the moment. [[User:Dupuy|@alex]] <br />
<br />
''Please add your thoughts here!'' <br />
<ul><li style="list-style-type:none">Alternatives for [[Participate Openly|ParticipateOpenly]]: What about if you have a problem or there is a good common practice, then go and [[Make It Public|MakeItPublic]]! I have not Idea how the "it" could be better qualified to include "I belive we have a serious problem there", but not "Look at what that idiot has been doing". Maybe that is too complex to be caputured in a wiki phrase. :-) --[[User:DonRedman|DonRedman]] <br />
</ul><br />
<br />
===Support Groups===<br />
<br />
I would like to work on realising #6 - after reading all the Wikipedia links about it and in case [[User:DonRedman|DonRedman]] can help me with his expertise. :) I think it's important to find an expressive name for such a group like Wikipedia has with "Esperanza". Suggestions? :) -- [[User:Shepard|Shepard]] <br />
<br />
====Brainstorm for a Name====<br />
<br />
''(just add to the list, no negative comments)'' <br />
* Esperanza <br />
* [[Cup Of Hope|CupOfHope]] <br />
* [[Rent A Moose|RentAMoose]] - inspired by our [[MusicBrainz Slang|unofficial mascot]]; expresses that you "rent" a mediator/helper when you have problems; unfortunately not a working [[Wiki Name|WikiName]] :( <br />
* I would hope we could find a music-related name; a bit of searching turned up [http://en.wikipedia.org/wiki/Glee_club GleeClub], which I like quite a bit [[[User:Dupuy|@alex]] <br />
<br />
While we're at it, we could probably use a name for the bug triage group as well; I thought of [[Piano Tuners|PianoTuners]] but it seems a bit of a stretch... <br />
<br />
[[Category:To Be Reviewed]] [[Category:Philosophy]] [[Category:History]] [[Category:Discussion]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Great_Dispute&diff=7242
History:Great Dispute
2006-08-22T15:43:21Z
<p>Dupuy: add discussion category tag (Imported from MoinMoin)</p>
<hr />
<div>=The Great Dispute=<br />
<br />
The dispute, which is still ongoing as of 2006-08-21. If the project survives this, it may be remembered as the Great Dispute. <br />
<br />
==Related Documents==<br />
<br />
''Currently a random collection of 'places' and events of the dispute.'' <br />
* The [[MusicBrainz Haiku|MusicBrainzHaiku]] gives the shortest possible summary. <br />
* On August 15th, 2006 Robert writes a blog post entitled [http://blog.musicbrainz.org/archives/2006/08/developer_chang.html Developer changes], in which he states that he will remove [[User:Keschte|Keschte]]'s developer privileges. <br />
<br />
==The IRC Chat==<br />
<br />
On August 21st, 2006, from 2100 to about 2330 GMT, there was an [[IRC]] discussion about this problem (see [http://chatlogs.musicbrainz.org/2006/2006-08/2006-08-21.html#T21-01-52-447060 chatlog]), which still managed to be less voluminous than the [[Users Mailing List|UsersMailingList]] discussion. <br />
<br />
During this discussion, the participants developed a list of the underlying problems that had led up to the dispute: <br />
# differences in coding and communications styles <br />
# lack of sufficient resources for developers (enough staging/testing servers, etc.) <br />
# lack of guidelines or rules of behavior for the development team (and community) <br />
# changes in MB as the community becomes larger, and more "businesslike" <br />
# failures or deficiencies in the communications forums (e.g. arguments in Trac tickets) <br />
# lack of clarity about the "final arbiter" of disputes <br />
# missing development guidelines/concept + master plan <br />
<br />
Generally, points 1 and 3 were felt to be the most significant, with 4, 5, and 6 also important. <br />
<br />
To address these problems, a number of of guiding principles for the [[MusicBrainz]] community were outlined; these should eventually have their own [[Wiki Pages|WikiPages]], once we come up with good [[Wiki Phrases|WikiPhrases]] for them (add your suggestions to the Discussion below): <br />
* Create an environment that encourages volunteers (developers and others) <br />
* Transparency in communications (public) and process (documented) <br />
* Seek mediators for conflicts, ideally, even before they occur <br />
* Distribute responsibility, by asking for help, and growing teams <br />
* Needs of the community as a whole come before the demands of any individual <br />
<br />
Although there wasn't time to discuss them in much detail, the [[User:Dupuy|moderator]] also came up with a list of various proposals (originally with two items numbered 3, and forgetting to include the last two items) that were suggested earlier on the mailing list, or which were mentioned in the IRC chat: <br />
# Agree on and document development process <br />
# Agree on and document conflict-resolution process <br />
# Codes of conduct for developers and others <br />
# Bug triage team for Trac <br />
# Changes to rollout process (selectable server versions? live-data testing?) <br />
# "Support groups" (like Wikipedia Esperanza, etc.) <br />
# Improvements to development resources (more testing/staging servers?) <br />
# Establishing web "forum(s?)" for better communication between developers/users <br />
# Enhance mb server to collect immediate feedback from users <br />
<br />
There is much that still needs to be done - some of these proposals must be made much more specific to be meaningful, and some of them are surely quite contentious (notably the first two or three). As a start, if you are interested in participating in one or more of these, please note your interest in the Discussion section below. As the mailing lists have been pretty swamped lately, it may be more effective to create wiki pages for each of these and to have the discussion there; please discuss the page names here before creating them (that will probably happen sometime later on Tuesday). <br />
<br />
==Discussion==<br />
<br />
Okay, here are my ideas for names for the principles: [[Encourage Volunteers|EncourageVolunteers]], [[Participate Openly|ParticipateOpenly]], [[Seek Mediators|SeekMediators]], [[Distribute Responsibility|DistributeResponsibility]], and [[Put Community First|PutCommunityFirst]]. They can surely be improved (especially the second one, it's tough to capture in 2-3 words, especially since "open" and "transparent" are so abused as to have lost much meaning), and made more consistent, so please don't go and create them (yet). As for participation in the proposals, I'm afraid that moderating the IRC chat pretty much used up my available time - I will try to work on this and related wiki pages when I can, but that's probably all I can really commit to at the moment. [[User:Dupuy|@alex]] <br />
<br />
''Please add your thoughts here!'' <br />
<br />
As for the proposals: I would like to work on realising #6 - after reading all the Wikipedia links about it and in case [[User:DonRedman|DonRedman]] can help me with his expertise. :) I think it's important to find a expressive name for such a group like Wikipedia has with "Esperanza". Suggestions? :) -- [[User:Shepard|Shepard]] 00:39, 22 August 2006 (UTC) <br />
<br />
[[Category:To Be Reviewed]] [[Category:Philosophy]] [[Category:History]] [[Category:Discussion]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Great_Dispute&diff=7243
History:Great Dispute
2006-08-22T15:34:14Z
<p>Dupuy: add two items to proposals (Imported from MoinMoin)</p>
<hr />
<div>=The Great Dispute=<br />
<br />
The dispute, which is still ongoing as of 2006-08-21. If the project survives this, it may be remembered as the Great Dispute. <br />
<br />
==Related Documents==<br />
<br />
''Currently a random collection of 'places' and events of the dispute.'' <br />
* The [[MusicBrainz Haiku|MusicBrainzHaiku]] gives the shortest possible summary. <br />
* On August 15th, 2006 Robert writes a blog post entitled [http://blog.musicbrainz.org/archives/2006/08/developer_chang.html Developer changes], in which he states that he will remove [[User:Keschte|Keschte]]'s developer privileges. <br />
<br />
==The IRC Chat==<br />
<br />
On August 21st, 2006, from 2100 to about 2330 GMT, there was an [[IRC]] discussion about this problem (see [http://chatlogs.musicbrainz.org/2006/2006-08/2006-08-21.html#T21-01-52-447060 chatlog]), which still managed to be less voluminous than the [[Users Mailing List|UsersMailingList]] discussion. <br />
<br />
During this discussion, the participants developed a list of the underlying problems that had led up to the dispute: <br />
# differences in coding and communications styles <br />
# lack of sufficient resources for developers (enough staging/testing servers, etc.) <br />
# lack of guidelines or rules of behavior for the development team (and community) <br />
# changes in MB as the community becomes larger, and more "businesslike" <br />
# failures or deficiencies in the communications forums (e.g. arguments in Trac tickets) <br />
# lack of clarity about the "final arbiter" of disputes <br />
# missing development guidelines/concept + master plan <br />
<br />
Generally, points 1 and 3 were felt to be the most significant, with 4, 5, and 6 also important. <br />
<br />
To address these problems, a number of of guiding principles for the [[MusicBrainz]] community were outlined; these should eventually have their own [[Wiki Pages|WikiPages]], once we come up with good [[Wiki Phrases|WikiPhrases]] for them (add your suggestions to the Discussion below): <br />
* Create an environment that encourages volunteers (developers and others) <br />
* Transparency in communications (public) and process (documented) <br />
* Seek mediators for conflicts, ideally, even before they occur <br />
* Distribute responsibility, by asking for help, and growing teams <br />
* Needs of the community as a whole come before the demands of any individual <br />
<br />
Although there wasn't time to discuss them in much detail, the [[User:Dupuy|moderator]] also came up with a list of various proposals (originally with two items numbered 3, and forgetting to include the last two items) that were suggested earlier on the mailing list, or which were mentioned in the IRC chat: <br />
# Agree on and document development process <br />
# Agree on and document conflict-resolution process <br />
# Codes of conduct for developers and others <br />
# Bug triage team for Trac <br />
# Changes to rollout process (selectable server versions? live-data testing?) <br />
# "Support groups" (like Wikipedia Esperanza, etc.) <br />
# Improvements to development resources (more testing/staging servers?) <br />
# Establishing web "forum(s?)" for better communication between developers/users <br />
# Enhance mb server to collect immediate feedback from users <br />
<br />
There is much that still needs to be done - some of these proposals must be made much more specific to be meaningful, and some of them are surely quite contentious (notably the first two or three). As a start, if you are interested in participating in one or more of these, please note your interest in the Discussion section below. As the mailing lists have been pretty swamped lately, it may be more effective to create wiki pages for each of these and to have the discussion there; please discuss the page names here before creating them (that will probably happen sometime later on Tuesday). <br />
<br />
==Discussion==<br />
<br />
Okay, here are my ideas for names for the principles: [[Encourage Volunteers|EncourageVolunteers]], [[Participate Openly|ParticipateOpenly]], [[Seek Mediators|SeekMediators]], [[Distribute Responsibility|DistributeResponsibility]], and [[Put Community First|PutCommunityFirst]]. They can surely be improved (especially the second one, it's tough to capture in 2-3 words, especially since "open" and "transparent" are so abused as to have lost much meaning), and made more consistent, so please don't go and create them (yet). As for participation in the proposals, I'm afraid that moderating the IRC chat pretty much used up my available time - I will try to work on this and related wiki pages when I can, but that's probably all I can really commit to at the moment. [[User:Dupuy|@alex]] <br />
<br />
''Please add your thoughts here!'' <br />
<br />
As for the proposals: I would like to work on realising #6 - after reading all the Wikipedia links about it and in case [[User:DonRedman|DonRedman]] can help me with his expertise. :) I think it's important to find a expressive name for such a group like Wikipedia has with "Esperanza". Suggestions? :) -- [[User:Shepard|Shepard]] 00:39, 22 August 2006 (UTC) <br />
<br />
[[Category:To Be Reviewed]] [[Category:Philosophy]] [[Category:History]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Great_Dispute&diff=7246
History:Great Dispute
2006-08-22T00:15:13Z
<p>Dupuy: summary of IRC discussion agenda and points (Imported from MoinMoin)</p>
<hr />
<div>=The Great Dispute=<br />
<br />
The dispute, which is still ongoing as of 2006-08-21. If the project survives this, it may be remembered as the Great Dispute. <br />
<br />
==Related Documents==<br />
<br />
''Currently a random collection of 'places' and events of the dispute.'' <br />
* The [[MusicBrainz Haiku|MusicBrainzHaiku]] gives the shortest possible summary. <br />
* On August 15th, 2006 Robert writes a blog post entitled [http://blog.musicbrainz.org/archives/2006/08/developer_chang.html Developer changes], in which he states that he will remove [[User:Keschte|Keschte]]'s developer privileges. <br />
<br />
==The IRC Chat==<br />
<br />
On August 21st, 2006, from 2100 to about 2330 GMT, there was an [[IRC]] discussion about this problem, which still managed to be less voluminous than the [[Users Mailing List|UsersMailingList]] discussion. <br />
<br />
During this discussion, the participants developed a list of the underlying problems that had led up to the dispute: <br />
# differences in coding and communications styles <br />
# lack of sufficient resources for developers (enough staging/testing servers, etc.) <br />
# lack of guidelines or rules of behavior for the development team (and community) <br />
# changes in MB as the community becomes larger, and more "businesslike" <br />
# failures or deficiencies in the communications forums (e.g. arguments in Trac tickets) <br />
# lack of clarity about the "final arbiter" of disputes <br />
# missing development guidelines/concept + master plan <br />
<br />
Generally, points 1 and 3 were felt to be the most significant, with 4, 5, and 6 also important. <br />
<br />
To address these problems, a number of of guiding principles for the [[MusicBrainz]] community were outlined; these should eventually have their own [[Wiki Pages|WikiPages]], once we come up with good [[Wiki Phrases|WikiPhrases]] for them (add your suggestions to the Discussion below): <br />
* Create an environment that encourages volunteers (developers and others) <br />
* Transparency in communications (public) and process (documented) <br />
* Seek mediators for conflicts, ideally, even before they occur <br />
* Distribute responsibility, by asking for help, and growing teams <br />
* Needs of the community as a whole come before the demands of any individual <br />
<br />
Although there wasn't time to discuss them in much detail, the [[User:Dupuy|moderator]] also came up with a list (originally with two items numbered 3) of various proposals that were suggested earlier on the mailing list, or which were mentioned in the IRC chat: <br />
# Agree on and document development process <br />
# Agree on and document conflict-resolution process <br />
# Codes of conduct for developers and others <br />
# Bug triage team for Trac <br />
# Changes to rollout process (selectable server versions? live-data testing?) <br />
# "Support groups" (like Wikipedia Esperanza, etc.) <br />
# Improvements to development resources (more testing/staging servers?) <br />
<br />
There is much that still needs to be done - some of these proposals must be made much more specific to be meaningful, and some of them are surely quite contentious (notably the first two or three). As a start, if you are interested in participating in one or more of these, please note your interest in the Discussion section below. As the mailing lists have been pretty swamped lately, it may be more effective to create wiki pages for each of these and to have the discussion there; please discuss the page names here before creating them (that will probably happen sometime later on Tuesday). <br />
<br />
==Discussion==<br />
<br />
Okay, here are my ideas for names for the principles: [[Encourage Volunteers|EncourageVolunteers]], [[Participate Openly|ParticipateOpenly]], [[Seek Mediators|SeekMediators]], [[Distribute Responsibility|DistributeResponsibility]], and [[Put Community First|PutCommunityFirst]]. They can surely be improved (especially the second one, it's tough to capture in 2-3 words, especially since "open" and "transparent" are so abused as to have lost much meaning), and made more consistent, so please don't go and create them (yet). As for participation in the proposals, I'm afraid that moderating the IRC chat pretty much used up my available time - I will try to work on this and related wiki pages when I can, but that's probably all I can really commit to at the moment. [[User:Dupuy|@alex]] <br />
<br />
''Please add your thoughts here!'' <br />
<br />
[[Category:To Be Reviewed]] [[Category:Philosophy]] [[Category:History]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Style/Language/Turkish&diff=11963
Style/Language/Turkish
2006-07-16T17:41:37Z
<p>Dupuy: add link to capitalization bug tracker item (Imported from MoinMoin)</p>
<hr />
<div>This page outlines the capitalization rules for the '''Turkish''' language. It forms part of the [[MusicBrainz]] [[Capitalization Standard|CapitalizationStandard]]. This is a [[Proposed Style Guideline|ProposedStyleGuideline]]. <br />
<br />
===Türkçe===<br />
<br />
Kitap, dergi, gazete ve sanat eserlerinin (tablo, heykel, müzik) her kelimesi büyük harfle başlar: Nutuk, Safahat, Kendi Gök Kubbemiz, Anadolu Notları, Sinekli Bakkal; Türk Dili, Türk Kültürü, Varlık; Resmî Gazete, Hürriyet, Milliyet, Türkiye, Yeni Yüzyıl, Yeni Asır; Saraydan Kız Kaçırma, Onuncu Yıl Marşı. <br />
<br />
UYARI: Özel ada dâhil olmayan gazete, dergi, tablo vb. sözler büyük harfle başlamaz: Milliyet gazetesi, Türk Dili dergisi, Halı Dokuyan Kızlar tablosu. <br />
<br />
UYARI: Büyük harflerin kullanıldığı yerlerde bulunan ve, ile, ya, veya, yahut, ki, da, de sözleriyle mı, mi, mu, mü soru eki küçük harfle yazılır: Mai ve Siyah, Suç ve Ceza, Leyla ile Mecnun, Turfanda mı, Turfa mı? Diyorlar ki, Dünyaya İkinci Geliş yahut Sır İçinde Esrar, Ya Devlet Başa ya Kuzgun Leşe, Ben de Yazdım. <br />
<br />
([http://www.tdk.gov.tr "Türk Dil Kurumu"]'nun sitesindeki [http://tdk.org.tr/yazim/kurallar.htm "yazım kuralları"] 14. maddeden alınmıştır) <br />
<br />
Türk alfabesinde 29 harf olduğunu lütfen unutmayalım: <br />
<br />
'''Büyük Harf:''' A B C Ç D E F G Ğ H I İ J K L M N O Ö P R S Ş T U Ü V Y Z <br />
<br />
'''Küçük Harf:''' a b c ç d e f g ğ h ı i j k l m n o ö p r s ş t u ü v y z <br />
<br />
Çoğu dilin aksine Türkçe'de "I" harfi "i" harfinin büyük karşılığı değildir. Music<code><nowiki></nowiki></code>Brainz sitesindeki programlar "i" harfini "I" harfi ile değiştirecektir ve bu [http://bugs.musicbrainz.org/ticket/1835 yanlıştır]. Lütfen bu konuda özel dikkat gösteriniz. <br />
<br />
===In English===<br />
<br />
Every words of book, magazine, newspaper and artistic production (painting, sculpture, music) titles are capitalized: Nutuk, Safahat, Kendi Gök Kubbemiz, Anadolu Notları, Sinekli Bakkal; Türk Dili, Türk Kültürü, Varlık; Resmi Gazete, Hürriyet, Milliyet, Türkiye, Yeni Yüzyıl, Yeni Asır; Saraydan Kız Kaçırma, Onuncu Yıl Marşı. <br />
<br />
WARNING: If the word is not part of the title it is not capitalized: Milliyet gazetesi, Türk Dili dergisi, Halı Dokuyan Kızlar tablosu. <br />
<br />
WARNING: If the title includes words such as 've', 'ile', 'ya', 'veya', 'yahut', 'ki', 'da', 'de', 'mı', 'mi', 'mu', 'mü' then these words are not capitalized: Mai ve Siyah, Suç ve Ceza, Leyla ile Mecnun, Turfanda mı, Turfa mı? Diyorlar ki, Dünyaya İkinci Geliş yahut Sır İçinde Esrar, Ya Devlet Başa ya Kuzgun Leşe, Ben de Yazdım, [http://musicbrainz.org/release/228484d0-7290-4a10-b4bf-cc22375d2496.html "Düğün ve Cenaze"], [http://musicbrainz.org/release/279cb527-da9c-4945-9e3b-e5e44aef005f.html "Şıkıdım (Hepsi Senin mi?)"], [http://musicbrainz.org/track/54a14a61-8f44-4a77-ab58-c1d6cbe911e1.html "Aşkları da Vururlar"], [http://musicbrainz.org/track/7e511499-d099-407f-94e2-b5f2b3bd6744.html "Kalbim Ege'de Kaldı"]. <br />
<br />
(Taken from 14th rule of ([http://www.tdk.gov.tr "Turkish Language Society"] [http://tdk.org.tr/yazim/kurallar.htm "writing guideline"]) <br />
<br />
Also it should be noted that there are 29 letters on Turkish alphabet: <br />
<br />
'''Capital:''' A B C Ç D E F G Ğ H I İ J K L M N O Ö P R S Ş T U Ü V Y Z <br />
<br />
'''Normal :''' a b c ç d e f g ğ h ı i j k l m n o ö p r s ş t u ü v y z <br />
<br />
It can be easily seen that, unlike in most languages, letter "I" is not capital form of letter "i". There is a [http://bugs.musicbrainz.org/ticket/1835 bug] in Music<code><nowiki></nowiki></code>Brainz [[Guess Case|GuessCase]] capitalization scripts, which replaces "i" with "I", which is NOT true for Turkish language. Please pay special attention to this issue. <br />
<br />
==Discussion==<br />
<br />
Some of the cheaply produced CDs on the markets have pretty "interesting" liner notes. Quite a few of those people don't seem to bother with correct use their own language, they misspell even basic words :-( --[[User:hakan|hakan]] <br />
<br />
[[Category:To Be Reviewed]] [[Category:Proposed Style]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Communication/IRC&diff=7792
Communication/IRC
2006-07-13T05:46:03Z
<p>Dupuy: (Imported from MoinMoin)</p>
<hr />
<div>=MusicBrainz IRC Channel=<br />
<br />
[[Image:Alert.png]] All users of the IRC channel are expected to follow the [[Code Of Conduct|CodeOfConduct]] <br />
<br />
Many of the [http://musicbrainz.org/bio.html MusicBrainz developers], as well as other users who want to chat with them, can be found on the '''#musicbrainz''' channel at [http://freenode.net/ irc.freenode.net] ([irc://irc.freenode.net/musicbrainz irc://irc.freenode.net/musicbrainz]). References to IRC on the Wiki generally refer to this channel. As in many communities the chatters in the channel have developed their own [[MusicBrainz Slang|MusicBrainzSlang]]. <br />
<br />
[http://en.wikipedia.org/wiki/Internet_Relay_Chat Internet Relay Chat] is a type of instant messaging network; you will need an [http://en.wikipedia.org/wiki/List_of_IRC_clients IRC client] to participate, but even without one, you can browse the [http://chatlogs.musicbrainz.org IRC logs] (there is only an extremely crude chronological index by days, but you can also look at [http://chatlogs.musicbrainz.org/today.cgi today's log] and [http://chatlogs.musicbrainz.org/yesterday.cgi yesterday's log]). <br />
<br />
[[Category:To Be Reviewed]] [[Category:Terminology]] [[Category:Communication Forum]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Contact_Us&diff=12921
Contact Us
2006-07-13T05:17:32Z
<p>Dupuy: (Imported from MoinMoin)</p>
<hr />
<div><br />
==Questions==<br />
<br />
Please check the [[General FAQ]], or one of the other pages of [[Frequently Asked Questions|frequently asked questions]] listed in the [[FAQ Index]] to see if your question has already been answered. <br />
<br />
==Mailing Lists & Forums==<br />
<br />
We have several [[Mailing List|mailing lists]], which are also available as [[Nabble Forum|Nabble forums]] for those who prefer a web interface. The '''musicbrainz-users''' [http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users list] or [http://www.nabble.com/Musicbrainz---Users-f514.html forum] is for general discussion of Music<code><nowiki></nowiki></code>Brainz. This is an excellent way to get help or ask questions about this site. These are ideal for active discussions (and controversies!) with a wider audience. <br />
<br />
==Report a Bug==<br />
<br />
Found something that does not work? Please check the [http://bugs.musicbrainz.org/query?status=new&status=assigned&status=reopened&type=bug&order=priority list of bugs] at our [[Bug Tracker|BugTracker]] and if your problem has not been entered yet, submit it on the [http://bugs.musicbrainz.org/newticket new ticket page]. Likewise, if you have an idea for a new feature or improvement, please make sure it's not already on the [http://bugs.musicbrainz.org/query?status=new&status=assigned&status=reopened&type=enhancement&order=priority list of feature requests] before submitting it. <br />
<br />
==E-mail us==<br />
<br />
You can reach the Music<code><nowiki></nowiki></code>Brainz staff directly at one of the following addresses: <br />
{| border="1"<br />
|-<br />
| Support || [mailto:support%40musicbrainz.org support@musicbrainz.org]<br />
|-<br />
| Contribute || [mailto:donations%40musicbrainz.org donations@musicbrainz.org]<br />
|-<br />
| Press enquiries || [mailto:press%40musicbrainz.org press@musicbrainz.org]<br />
|-<br />
| Sponsorship enquiries || [mailto:sponsors%40musicbrainz.org sponsors@musicbrainz.org]<br />
|-<br />
| Other enquiries || [mailto:info%40musicbrainz.org info@musicbrainz.org]<br />
|}<br />
<br />
==Wiki==<br />
<br />
The [http://wiki.musicbrainz.org MusicBrainz Wiki] has a mix of discussion and documentation ranging from the introductory to the esoteric. It is primarily used for intermediate and advanced documentation of the Music<code><nowiki></nowiki></code>Brainz community, conventions, interfaces, and internals. While there's a fair amount of this on the main pages, over time most of is moving to the Wiki, where it can be maintained and extended by the community as a whole. The Wiki is especially well suited for documenting community issues and conventions like the style and editing guidelines, which change over time as a result of the community's interactions, and don't necessarily require development efforts. <br />
<br />
The second use is for detailed and specific discussions. General ideas or opinions are best discussed on a mailing list, but once it gets to the point where there are detailed proposals (and counter-proposals) it makes sense to move discussion to the Wiki, where others can comment in-line and link to related topics, as well as summarize and re-organize the discussion. Additional discussion may still take place on a mailing list or [[IRC]] and if there is general acceptance of the suggestion, it may be a good idea to create a feature request on the bug tracker. <br />
<br />
==IRC==<br />
<br />
Music<code><nowiki></nowiki></code>Brainz developers and users are often to be found in the '''#musicbrainz''' channel on [[IRC]] chat at irc.freenode.net. Please feel free to browse the [http://chatlogs.musicbrainz.org/ IRC log archives]. The [[IRC]] channel is a very informal forum for Q&A or brainstorming, with immediate interactive discussions. <br />
<br />
==Blog==<br />
<br />
The [http://blog.musicbrainz.org Brainz blog] has frequent updates from Music<code><nowiki></nowiki></code>Brainz developers on their progress in implementing new features and projects. While it has a comment feature for feedback, substantive discussion should be on the mailing lists or in the [[MusicBrainz Wiki|Wiki]]. Please feel free to link to our Blog from your own! <br />
<br />
==Edit Notes and Annotations==<br />
<br />
If you are editing the Music<code><nowiki></nowiki></code>Brainz database, be sure to use [[Edit Note|EditNote]]<code><nowiki></nowiki></code>s on your changes, and on changes that you are voting on - your notes will be e-mailed to all moderators who vote on that change (or add a note themselves). This forum is very well suited for specific discussions about particular artists or releases. <br />
<br />
You can also add [[Artist Annotation|ArtistAnnotation]]<code><nowiki></nowiki></code>s and [[Release Annotation|ReleaseAnnotation]]<code><nowiki></nowiki></code>s to the database to communicate with other moderators working on those parts of the database. <br />
<br />
[[Category:To Be Reviewed]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Nabble_Forum&diff=10779
Nabble Forum
2006-07-13T05:15:32Z
<p>Dupuy: new page linked from ContactUs (Imported from MoinMoin)</p>
<hr />
<div>=MusicBrainz Nabble Forums=<br />
<br />
All the [[Mailing List|MailingList]]<code><nowiki></nowiki></code>s can also be viewed as web forums at [http://www.nabble.com/ Nabble]. <br />
<br />
In addition to individual views of each mailing list, you can also see all of the lists as a [http://www.nabble.com/MusicBrainz-f2885.html single forum]. <br />
<br />
You can also post to existing threads, and start new ones; all postings to Nabble are forwarded to the corresponding mailing list as well. <br />
<br />
Just like the mailing lists, users of the Nabble forums are expected to follow the [[Code Of Conduct|CodeOfConduct]]. <br />
<br />
See the [[Mailing List|MailingList]] page for details on the different lists. <br />
<br />
[[Category:To Be Reviewed]] [[Category:Communication Forum]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Contact_Us&diff=12922
Contact Us
2006-07-13T05:05:45Z
<p>Dupuy: (Imported from MoinMoin)</p>
<hr />
<div><br />
==Questions==<br />
<br />
Please check the [[General FAQ]], or one of the other pages of [[Frequently Asked Questions|frequently asked questions]] listed in the [[FAQ Index]] to see if your question has already been answered. <br />
<br />
==Mailing Lists & Forums==<br />
<br />
We have several [[Mailing List|mailing lists]], which are also available as [[Nabble Forum|Nabble forums]] for those who prefer a web interface. The '''musicbrainz-users''' [http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users list] or [http://www.nabble.com/Musicbrainz---Users-f514.html forum] is for general discussion of Music<code><nowiki></nowiki></code>Brainz. This is an excellent way to get help or ask questions about this site. These are ideal for active discussions (and controversies!) with a wider audience. <br />
<br />
==Report a Bug==<br />
<br />
Found something that does not work? Please check the [http://bugs.musicbrainz.org/query?status=new&status=assigned&status=reopened&type=bug&order=priority list of bugs] at our [[Bug Tracker|BugTracker]] and if your problem has not been entered yet, submit it on the [http://bugs.musicbrainz.org/newticket new ticket page]. Likewise, if you have an idea for a new feature or improvement, please make sure it's not already on the [http://bugs.musicbrainz.org/query?status=new&status=assigned&status=reopened&type=enhancement&order=priority list of feature requests] before submitting it. <br />
<br />
==E-mail us==<br />
<br />
You can reach the Music<code><nowiki></nowiki></code>Brainz staff directly at one of the following addresses: <br />
{| border="1"<br />
|-<br />
| Support || [mailto:support%40musicbrainz.org support@musicbrainz.org]<br />
|-<br />
| Contribute || [mailto:donations%40musicbrainz.org donations@musicbrainz.org]<br />
|-<br />
| Press enquiries || [mailto:press%40musicbrainz.org press@musicbrainz.org]<br />
|-<br />
| Sponsorship enquiries || [mailto:sponsors%40musicbrainz.org sponsors@musicbrainz.org]<br />
|-<br />
| Other enquiries || [mailto:info%40musicbrainz.org info@musicbrainz.org]<br />
|}<br />
<br />
==Wiki==<br />
<br />
The [http://wiki.musicbrainz.org MusicBrainz Wiki] has a mix of discussion and documentation ranging from the introductory to the esoteric. It is primarily used for intermediate and advanced documentation of the Music<code><nowiki></nowiki></code>Brainz community, conventions, interfaces, and internals. While there's a fair amount of this on the main pages, over time most of is moving to the Wiki, where it can be maintained and extended by the community as a whole. The Wiki is especially well suited for documenting community issues and conventions like the style and editing guidelines, which change over time as a result of the community's interactions, and don't necessarily require development efforts. <br />
<br />
The second use is for detailed and specific discussions. General ideas or opinions are best discussed on a mailing list, but once it gets to the point where there are detailed proposals (and counter-proposals) it makes sense to move discussion to the Wiki, where others can comment in-line and link to related topics, as well as summarize and re-organize the discussion. Additional discussion may still take place on a mailing list or [[IRC]] and if there is general acceptance of the suggestion, it may be a good idea to create a feature request on the bug tracker. <br />
<br />
==IRC==<br />
<br />
Music<code><nowiki></nowiki></code>Brainz developers and users are often to be found in the '''#musicbrainz''' channel on [[IRC]] chat at irc.freenode.net. Please feel free to browse the [http://chatlogs.musicbrainz.org/ IRC log archives]. The [[IRC]] channel is a very informal forum for Q&A or brainstorming, with immediate interactive discussions. <br />
<br />
==Blog==<br />
<br />
The [http://blog.musicbrainz.org MusicBrainz blog] has frequent updates from Music<code><nowiki></nowiki></code>Brainz developers on their progress in implementing new features and projects. While it has a comment feature for feedback, substantive discussion should be on the mailing lists or in the [[MusicBrainz Wiki|Wiki]]. Please feel free to link to our Blog from your own! <br />
<br />
==Edit Notes and Annotations==<br />
<br />
If you are editing the [[MusicBrainz]] database, be sure to use [[Edit Note|EditNote]]<code><nowiki></nowiki></code>s on your changes, and on changes that you are voting on - your notes will be e-mailed to all moderators who vote on that change (or add a note themselves). This forum is very well suited for specific discussions about particular artists or releases. <br />
<br />
You can also add [[Artist Annotation|ArtistAnnotation]]<code><nowiki></nowiki></code>s and [[Release Annotation|ReleaseAnnotation]]<code><nowiki></nowiki></code>s to the database to communicate with other moderators working on those parts of the database. <br />
<br />
[[Category:To Be Reviewed]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Contact_Us&diff=12923
Contact Us
2006-07-13T05:04:58Z
<p>Dupuy: add DontRenameWikiDocsPages (I can't add ACL as have no rights) (Imported from MoinMoin)</p>
<hr />
<div><br />
==Questions==<br />
<br />
Please check the [[General FAQ]], or one of the other pages of [[Frequently Asked Questions|frequently asked questions]] listed in the [[FAQ Index]] to see if your question has already been answered. <br />
<br />
==Mailing Lists & Forums==<br />
<br />
We have several [[Mailing List|mailing lists]], which are also available as [[Nabble Forum|Nabble forums]] for those who prefer a web interface. The '''musicbrainz-users''' [http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users list] or [http://www.nabble.com/Musicbrainz---Users-f514.html forum] is for general discussion of Music<code><nowiki></nowiki></code>Brainz. This is an excellent way to get help or ask questions about this site. These are ideal for active discussions (and controversies!) with a wider audience. <br />
<br />
==Report a Bug==<br />
<br />
Found something that does not work? Please check the [http://bugs.musicbrainz.org/query?status=new&status=assigned&status=reopened&type=bug&order=priority list of bugs] at our [[Bug Tracker|BugTracker]] and if your problem has not been entered yet, submit it on the [http://bugs.musicbrainz.org/newticket new ticket page]. Likewise, if you have an idea for a new feature or improvement, please make sure it's not already on the [http://bugs.musicbrainz.org/query?status=new&status=assigned&status=reopened&type=enhancement&order=priority list of feature requests] before submitting it. <br />
<br />
==E-mail us==<br />
<br />
You can reach the Music<code><nowiki></nowiki></code>Brainz staff directly at one of the following addresses: <br />
{| border="1"<br />
|-<br />
| Support || [mailto:support%40musicbrainz.org support@musicbrainz.org]<br />
|-<br />
| Contribute || [mailto:donations%40musicbrainz.org donations@musicbrainz.org]<br />
|-<br />
| Press enquiries || [mailto:press%40musicbrainz.org press@musicbrainz.org]<br />
|-<br />
| Sponsorship enquiries || [mailto:sponsors%40musicbrainz.org sponsors@musicbrainz.org]<br />
|-<br />
| Other enquiries || [mailto:info%40musicbrainz.org info@musicbrainz.org]<br />
|}<br />
<br />
==Wiki==<br />
<br />
The [http://wiki.musicbrainz.org MusicBrainz Wiki] has a mix of discussion and documentation ranging from the introductory to the esoteric. It is primarily used for intermediate and advanced documentation of the Music<code><nowiki></nowiki></code>Brainz community, conventions, interfaces, and internals. While there's a fair amount of this on the main pages, over time most of is moving to the Wiki, where it can be maintained and extended by the community as a whole. The Wiki is especially well suited for documenting community issues and conventions like the style and editing guidelines, which change over time as a result of the community's interactions, and don't necessarily require development efforts. <br />
<br />
The second use is for detailed and specific discussions. General ideas or opinions are best discussed on a mailing list, but once it gets to the point where there are detailed proposals (and counter-proposals) it makes sense to move discussion to the Wiki, where others can comment in-line and link to related topics, as well as summarize and re-organize the discussion. Additional discussion may still take place on a mailing list or [[IRC]] and if there is general acceptance of the suggestion, it may be a good idea to create a feature request on the bug tracker. <br />
<br />
==IRC==<br />
<br />
Music<code><nowiki></nowiki></code>Brainz developers and users are often to be found in the '''#musicbrainz''' channel on [[IRC]] chat at irc.freenode.net. Please feel free to browse the [http://chatlogs.musicbrainz.org/ IRC log archives]. The [[IRC]] channel is a very informal forum for Q&A or brainstorming, with immediate interactive discussions. <br />
<br />
==Blog==<br />
<br />
The [http://blog.musicbrainz.org MusicBrainz blog] has frequent updates from Music<code><nowiki></nowiki></code>Brainz developers on their progress in implementing new features and projects. While it has a comment feature for feedback, substantive discussion should be on the mailing lists or in the [[MusicBrainz Wiki|Wiki]]. Please feel free to link to our Blog from your own! <br />
<br />
==Edit Notes and Annotations==<br />
<br />
If you are editing the [[MusicBrainz]] database, be sure to use [[Edit Note|EditNote]]<code><nowiki></nowiki></code>s on your changes, and on changes that you are voting on - your notes will be e-mailed to all moderators who vote on that change (or add a note themselves). This forum is very well suited for specific discussions about particular artists or releases. <br />
<br />
You can also add [[Artist Annotation|ArtistAnnotation]]<code><nowiki></nowiki></code>s and [[Release Annotation|ReleaseAnnotation]]<code><nowiki></nowiki></code>s to the database to communicate with other moderators working on those parts of the database. <br />
<br />
[[Category:To Be Reviewed]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=Contact_Us&diff=12924
Contact Us
2006-07-13T05:01:40Z
<p>Dupuy: changes for better wikidocselt - please update soon as direct linked from blog (Imported from MoinMoin)</p>
<hr />
<div><br />
==Questions==<br />
<br />
Please check the [[General FAQ]], or one of the other pages of [[Frequently Asked Questions|frequently asked questions]] listed in the [[FAQ Index]] to see if your question has already been answered. <br />
<br />
==Mailing Lists & Forums==<br />
<br />
We have several [[Mailing List|mailing lists]], which are also available as [[Nabble Forum|Nabble forums]] for those who prefer a web interface. The '''musicbrainz-users''' [http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users list] or [http://www.nabble.com/Musicbrainz---Users-f514.html forum] is for general discussion of Music<code><nowiki></nowiki></code>Brainz. This is an excellent way to get help or ask questions about this site. These are ideal for active discussions (and controversies!) with a wider audience. <br />
<br />
==Report a Bug==<br />
<br />
Found something that does not work? Please check the [http://bugs.musicbrainz.org/query?status=new&status=assigned&status=reopened&type=bug&order=priority list of bugs] at our [[Bug Tracker|BugTracker]] and if your problem has not been entered yet, submit it on the [http://bugs.musicbrainz.org/newticket new ticket page]. Likewise, if you have an idea for a new feature or improvement, please make sure it's not already on the [http://bugs.musicbrainz.org/query?status=new&status=assigned&status=reopened&type=enhancement&order=priority list of feature requests] before submitting it. <br />
<br />
==E-mail us==<br />
<br />
You can reach the Music<code><nowiki></nowiki></code>Brainz staff directly at one of the following addresses: <br />
{| border="1"<br />
|-<br />
| Support || [mailto:support%40musicbrainz.org support@musicbrainz.org]<br />
|-<br />
| Contribute || [mailto:donations%40musicbrainz.org donations@musicbrainz.org]<br />
|-<br />
| Press enquiries || [mailto:press%40musicbrainz.org press@musicbrainz.org]<br />
|-<br />
| Sponsorship enquiries || [mailto:sponsors%40musicbrainz.org sponsors@musicbrainz.org]<br />
|-<br />
| Other enquiries || [mailto:info%40musicbrainz.org info@musicbrainz.org]<br />
|}<br />
<br />
==Wiki==<br />
<br />
The [http://wiki.musicbrainz.org MusicBrainz Wiki] has a mix of discussion and documentation ranging from the introductory to the esoteric. It is primarily used for intermediate and advanced documentation of the Music<code><nowiki></nowiki></code>Brainz community, conventions, interfaces, and internals. While there's a fair amount of this on the main pages, over time most of is moving to the Wiki, where it can be maintained and extended by the community as a whole. The Wiki is especially well suited for documenting community issues and conventions like the style and editing guidelines, which change over time as a result of the community's interactions, and don't necessarily require development efforts. <br />
<br />
The second use is for detailed and specific discussions. General ideas or opinions are best discussed on a mailing list, but once it gets to the point where there are detailed proposals (and counter-proposals) it makes sense to move discussion to the Wiki, where others can comment in-line and link to related topics, as well as summarize and re-organize the discussion. Additional discussion may still take place on a mailing list or [[IRC]] and if there is general acceptance of the suggestion, it may be a good idea to create a feature request on the bug tracker. <br />
<br />
==IRC==<br />
<br />
Music<code><nowiki></nowiki></code>Brainz developers and users are often to be found in the '''#musicbrainz''' channel on [[IRC]] chat at irc.freenode.net. Please feel free to browse the [http://chatlogs.musicbrainz.org/ IRC log archives]. The [[IRC]] channel is a very informal forum for Q&A or brainstorming, with immediate interactive discussions. <br />
<br />
==Blog==<br />
<br />
The [http://blog.musicbrainz.org MusicBrainz blog] has frequent updates from Music<code><nowiki></nowiki></code>Brainz developers on their progress in implementing new features and projects. While it has a comment feature for feedback, substantive discussion should be on the mailing lists or in the [[MusicBrainz Wiki|Wiki]]. Please feel free to link to our Blog from your own! <br />
<br />
==Edit Notes and Annotations==<br />
<br />
If you are editing the [[MusicBrainz]] database, be sure to use [[Edit Note|EditNote]]<code><nowiki></nowiki></code>s on your changes, and on changes that you are voting on - your notes will be e-mailed to all moderators who vote on that change (or add a note themselves). This forum is very well suited for specific discussions about particular artists or releases. <br />
<br />
You can also add [[Artist Annotation|ArtistAnnotation]]<code><nowiki></nowiki></code>s and [[Release Annotation|ReleaseAnnotation]]<code><nowiki></nowiki></code>s to the database to communicate with other moderators working on those parts of the database. <br />
<br />
[[Category:To Be Reviewed]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=fAQ_Index&diff=4214
fAQ Index
2006-07-13T04:12:38Z
<p>Dupuy: index listing of FAQ pages (Imported from MoinMoin)</p>
<hr />
<div>Index pages just collect pages that deal with a specific topic without that topic being discussed on the page itself. Please keep in mind that a [[Wiki Is A Flat Hierarchy|WikiIsAFlatHierarchy]]. That means that pages can be listed on several indices. Index pages are not a directory tree but are merely clusters for topics. <br />
<br />
The list of [[Frequently Asked Questions|FrequentlyAskedQuestions]] below is generated automatically from all pages ending in FAQ: {{PageList|regex:FAQ$}} <br />
<br />
[[Category:To Be Reviewed]] [[Category:Index]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=FRBR&diff=25926
FRBR
2006-04-23T22:21:55Z
<p>Dupuy: you may not like his attitude, but for your own sake, take the ideas seriously (Imported from MoinMoin)</p>
<hr />
<div>'''FRBR''' is short for '''Functional Requirements for Bibliographic Records''', the title of a document released in 1998 by IFLA, the International Federation of Library Associations. FRBR specifies a '''data model''' for organizing bibliographic (or discographic) databases like [[MusicBrainz]]. If this is news to you, you should at least [http://en.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records read Wikipedia's introduction]. You can also [http://www.ifla.org/VII/s13/frbr/frbr1.htm read the full document] from IFLA's website. If you [http://google.com/search?q=FRBR google for FRBR] there are plenty of easier-to-read presentations of the core ideas. <br />
<br />
==What it says==<br />
<br />
FRBR specifies a data model consisting of three groups of entities: <br />
* '''Products,''' i.e. books, films and records. These follow a hierarchy of four entities: <br />
** '''Works,''' e.g. the novel Robinson Crusoe by Defoe <br />
** '''Expressions,''' e.g. the written novel, a translation, a film script based on the novel, an illustrated abridged version for children <br />
** '''Manifestations,''' e.g. a print edition of this translation of that novel <br />
** '''Items''' or physical copies, worn and torn, one of three held by your local library, each having a unique inventory number <br />
<br />
* '''People''' or corporate bodies (i.e. artists, groups, record companies) responsible for each entity of a product, e.g. the author of a story, the translator, the printer, the publisher, the library that owns a copy <br />
* '''Subjects,''' e.g. events and places where the story takes place, the date when the book was printed, etc. <br />
<br />
==History==<br />
<br />
Despite this spec being almost a decade old, nobody in the library world has really implemented it yet. It is on the verge of becoming the "flying car" of library catalogs, a utopian dream never fulfilled. The [http://catalog.loc.gov/ Library of Congress catalog] is still structured as a bunch of MARC records, which is little more than a 1960s digital equivalent of a 19th century card catalog. One reason for this delay is that FRBR doesn't specify '''who''' is going to do the job, it only says '''how''' it ought to be done. (And then the Y2K bug and dotcom crisis got in between.) Traditionally every library has a ''catalog'' of the books it owns. The idea that information about books (''bibliography'') could be separated from the local inventory was all new to libraries in the 1960s, when cooperative institutions like OCLC were born. With time these co-ops have started to act more and more like private monopoly suppliers that libraries depend on but really hate. Here, have some bibliographic data, the first samples are free, then you have to pay your soul, and we will supply your institution for the rest of its life. Throw in a lifetime subscription to the Encyclopædia Britannica as well. <br />
<br />
Enter the 21st century and Wikipedia. The common knowledge needs not be owned by a monopoly supplier. Every private music collector and library can keep their local inventory in the shape of links to existing, shared information at [[MusicBrainz]]. Find an error, fix it in the shared pool, not in your local inventory. This is how OCLC and Gracenote work. Except that no single entity owns Wikipedia or [[MusicBrainz]], because the contents can be copied freely by anybody. This answers the '''who''' question. <br />
[[Category:To Be Reviewed]] [[Category:External]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=FRBR&diff=25927
FRBR
2006-04-23T22:14:53Z
<p>Dupuy: (Imported from MoinMoin)</p>
<hr />
<div>'''FRBR''' is short for '''Functional Requirements for Bibliographic Records''', the title of a document released in 1998 by IFLA, the International Federation of Library Associations. FRBR specifies a '''data model''' for how [[MusicBrainz]] should be organized. If this is news to you, you should at least [http://en.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records read Wikipedia's introduction]. You can also [http://www.ifla.org/VII/s13/frbr/frbr1.htm read the full document] from IFLA's website. If you [http://google.com/search?q=FRBR google for FRBR] there are plenty of easier-to-read presentations of the core ideas. <br />
<br />
==What it says==<br />
<br />
FRBR specifies a data model consisting of three groups of entities: <br />
* '''Products,''' i.e. books, films and records. These follow a hierarchy of four entities: <br />
** '''Works,''' e.g. the novel Robinson Crusoe by Defoe <br />
** '''Expressions,''' e.g. the written novel, a translation, a film script based on the novel, an illustrated abridged version for children <br />
** '''Manifestations,''' e.g. a print edition of this translation of that novel <br />
** '''Items''' or physical copies, worn and torn, one of three held by your local library, each having a unique inventory number <br />
<br />
* '''People''' or corporate bodies (i.e. artists, groups, record companies) responsible for each entity of a product, e.g. the author of a story, the translator, the printer, the publisher, the library that owns a copy <br />
* '''Subjects,''' e.g. events and places where the story takes place, the date when the book was printed, etc. <br />
<br />
==History==<br />
<br />
Despite this spec being almost a decade old, nobody in the library world has really implemented it yet. It is on the verge of becoming the "flying car" of library catalogs, a utopian dream never fulfilled. The [http://catalog.loc.gov/ Library of Congress catalog] is still structured as a bunch of MARC records, which is little more than a 1960s digital equivalent of a 19th century card catalog. One reason for this delay is that FRBR doesn't specify '''who''' is going to do the job, it only says '''how''' it ought to be done. (And then the Y2K bug and dotcom crisis got in between.) Traditionally every library has a ''catalog'' of the books it owns. The idea that information about books (''bibliography'') could be separated from the local inventory was all new to libraries in the 1960s, when cooperative institutions like OCLC were born. With time these coops have started to act more and more like private monopoly suppliers that libraries depend on but really hate. Here, have some bibliographic data, the first samples are free, then you have to pay your soul, and we will supply your institution for the rest of its life. Throw in a lifetime subscription to the Encyclopædia Britannica as well. <br />
<br />
Enter the 21st century and Wikipedia. The common knowledge needs not be owned by a monopoly supplier. Every private music collector and library can keep their local inventory in the shape of links to existing, shared information at [[MusicBrainz]]. Find an error, fix it in the shared pool, not in your local inventory. This is how OCLC and Gracenote work. Except that no single entity owns Wikipedia or [[MusicBrainz]], because the contents can be copied freely by anybody. This answers the '''who''' question. <br />
<br />
Unfortunately, Wikipedia and [[MusicBrainz]] were created not by the old experts whose life-long experience was summarized in the FRBR specification, but by some kids from the filesharing generation. And so we see a shortsightedly crippled data model with just albums, tracks, and artists, applied only to recorded music. That's not the final solution. <br />
<br />
[[Category:To Be Reviewed]]</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=User:Dupuy&diff=25421
User:Dupuy
2006-04-23T21:58:11Z
<p>Dupuy: updated (Imported from MoinMoin)</p>
<hr />
<div>Alexander Dupuy <br />
<br />
When I first got involved with [[MusicBrainz]] a few years ago, like many other contributors, I found it satisfied some kind of obsessive-compulsive craving to organize and structure data. Many thousands of edits and votes later, the rest of my life got in the way again, and not only am I (probably) no longer in the top-10 or even top-20 editors and voters, I'm not even sure of the fact. However, I'm still keeping up to date with the mailing lists, even though I don't really have time to participate in the IRC discussions. And I'm still interested in the [[Internationalization|InterNationalization]] issues for [[MusicBrainz]], as well as the [[WikiDocs]] project (although I'm not active enough to have been chosen as a [[Transclusion Editor|TransclusionEditor]]). <br />
<br />
You can see more about my interests in my [[Main Site|MainSite]] moderator profile Moderator:dupuy - I used to wonder why there was a Wiki [[User Page|UserPage]] for each moderator as well, but now I think the right thing would be to have an automatic transclusion so that the moderator profile would include the text from the relevant [[Wiki Page|WikiPage]] (once the moderator specified their [[Wiki Name|WikiName]] on the [[Main Site|MainSite]]). <br />
<br />
@alex <br />
----<br />
<br />
<br />
<br />
It's so that you can easily sign your edits and then I have somewhere to leave a note thanking you for all your hard work on the wiki. The [[Edit Type|EditType]] table being particularly nice. -- [[User:bawjaws|bawjaws]] <br />
<br />
''It is also so that people can see how much you have done for the wiki by looking at the [[Back Link|BackLink]]<code><nowiki></nowiki></code>s to this page. Then they can leave a note here thanking you for it; e.g. for [[Restructuring The Documentation|RestructuringTheDocumentation]]. (Unfortunately the [[Back Link|BackLink]]<code><nowiki></nowiki></code>s also show all non-link occurences of "Dupuy". So to see all the pages you edited, we need [http://wiki.musicbrainz.org/wiki.pl?back=@alex another backlink hack] :-) --[[User:DonRedman|DonRedman]]'' <br />
<br />
I love the [[Back Link|BackLink]] hack! It's useful in another way. If people want to refer to me, they should write Dupuy (<code><nowiki>["Dupuy"]</nowiki></code>); when I write something myself, I will sign it [[User:Dupuy|@alex]] (<code><nowiki>[:Dupuy:@alex]</nowiki></code>); the regular backlink finds references to me (whether [[Wiki Link|WikiLink]]ed or not) and the [[Back Link Hack|BackLinkHack]] finds pages that I have contributed to (signed). [[User:Dupuy|@alex]] <br />
<ul><li style="list-style-type:none">now you tell me that I can just sign your name with 'dupuy' when I had such problems with [[Special Purpose Artist|SpecialPurposeArtist]] (want to say thanks for starting that page as well) ~[[User:mo|mo]] <br />
</ul><br />
<br />
{{lang en-native}} {{lang es-fluent}} {{lang fr-fluent}} {{lang pt-some}}</div>
Dupuy
https://wiki.musicbrainz.org/index.php?title=History:Data_Track_Style&diff=22119
History:Data Track Style
2005-12-07T13:32:35Z
<p>Dupuy: (Imported from MoinMoin)</p>
<hr />
<div>=Style for Data Tracks=<br />
<br />
'''Enter "[data track]" as the title (name) for [[Data Track|DataTrack]]<code><nowiki></nowiki></code>s.''' <br />
<br />
'''If a [[Data Track|DataTrack]] appears on a [[Various Artists|VariousArtists]] album, also enter "[data track]" as the [http://musicbrainz.org/artist/33cf029c-63b0-41a0-9855-be2a3665fb3b.html artist].''' <br />
<br />
Note, however, that if the data track comes last on the CD and isn't visible in an audio CD player, the track should ''not'' be entered into [[MusicBrainz]]. <br />
<ul><li style="list-style-type:none">This is an [[Official Style Guideline|OfficialStyleGuideline]]. <br />
</ul><br />
<br />
==Examples==<br />
<br />
[http://musicbrainz.org/album/09dfd85f-e95e-496b-b2e2-4b8c8d2109f7.html Final Fantasy VIII (disc 3)] is an example of a [[Game Disc|GameDisc]] with a single audio track by one artist. <br />
<br />
[http://musicbrainz.org/album/9cd9e81a-2dab-46d0-988e-bb486ddc1b05.html Magic & Mayhem] is an example of a [[Game Disc|GameDisc]] with multiple audio tracks by the same artist. <br />
<br />
[http://musicbrainz.org/album/0de34813-d30e-40ff-b090-b1db54b60d69.html Descent II: Macintosh] is an example of a [[Game Disc|GameDisc]] with audio tracks by [[Various Artists|VariousArtists]]. <br />
<br />
[http://musicbrainz.org/album/a4ccc4e4-ae32-4811-bbac-da7edb6e7410.html Revolution Magazine: Horizons] is an example of a [[Various Artists|VariousArtists]] CD+i audio disc with an initial interactive data track. <br />
<br />
[http://musicbrainz.org/album/c31dc383-610c-4656-bb69-31cbb9ab7fc6.html Źródło] is an example of a CD+i audio disc by a single artist. <br />
<br />
[http://musicbrainz.org/album/6f2baba0-332a-4bb5-bd11-640ec62ffa8f.html Schrei] is an example of an audio disc with a "trailing data track" that contains a music video (you can't see the extra track any more, as it was removed by the [[Remove Track|RemoveTrack]] edit [http://musicbrainz.org/showmod.html?modid=3832243 #3832243]. <br />
<br />
[http://musicbrainz.org/album/c39d27c3-23dd-4ea8-9b2e-49097dbef7c1.html The Fog of War] is an example of an audio disc with a track (#20) entitled "Data" that is ''not'' a [[Data Track|DataTrack]]; rather it is a normal musical track. <br />
<br />
==Rationale==<br />
<br />
[[MusicBrainz]] is about ''music'', not CD-ROM indexing. If a track is not an audio track, we don't care what it contains; we only want to note that it is not an audio track. The use of a standardized title for all non-audio tracks reflects this approach. <br />
<br />
Some audio CDs (such as CD-Extra or other formats) contain extra [[Data Track|DataTrack]]<code><nowiki></nowiki></code>s (they are also used for CopyProtectedCDs). In order for them not to appear or be playable on audio CD players, they are typically placed in one or more separate "sessions" of a multisession CD. Older versions of the [[MusicBrainz Tagger|MusicBrainzTagger]] (and many [[FreeDB]] clients) don't handle multi-session CDs correctly, and treat the additional session TOCs as part of the last audio track (resulting in an increase of 2:30 in the track time) and then include the data tracks from the other sessions. <br />
<br />
Note: The (2:30) is a real time disc-id offset difference. Times when compared to your own personal wav or mp3 files will vary (2:xx) (give or take a few seconds). <br />
<br />
The [[Special Purpose Artist|SpecialPurposeArtist]] '''[data track]''' is used on [[Various Artists|VariousArtists]] albums because we don't care who created the programs on a CD-ROM; we only want to credit artists related to the music or audio on the disc. <br />
<br />
===Why not delete initial data tracks?===<br />
<br />
Because initial data tracks affect the track numbering of all following tracks. The CD+i interactive CD format uses an initial data track, and marks the first playable track as track 2. Although the first track is not playable, it is ''visible'' in an audio CD player as the unplayable track 1. <br />
<br />
Examples of this are any [[Game Disc|GameDisc]]<code><nowiki></nowiki></code>s with playable audio tracks on them, generally the track(s) are the musical score used in the game at certan times, good examples are 'Secret of Monkey Island' and the 'Age of Empires' games. <br />
<br />
Also worth noting is that Age of Empires II and its expansion have only two tracks each, the actual game software in track 1 and the entire musical score in track 2 (it may use [[Index Mark|IndexMark]]<code><nowiki></nowiki></code>s). <br />
<br />
==Discussion==<br />
<br />
Now that using the [[Special Purpose Artist|SpecialPurposeArtist]] '''[data track]''' on [[Various Artists|VariousArtists]] albums is an [[Official Style Guideline|OfficialStyleGuideline]], there is an exception that might be worth making; if a data track contains MP3 or other audio files, it might be worth having the artist for those MP3 files (or [[Various Artists|VariousArtists]], if there are several artists) as the artist for the data track. [[User:Dupuy|@alex]] <br />
<br />
Having the artist of a (single) musical track on a [[Game Disc|GameDisc]] (like the FFVII (disc 3) example above) be the primary artist for the game itself does seem be a bit odd - I put the [http://musicbrainz.org/showmod.html?modid=3852877 conversion] of that album from [[Various Artists|VariousArtists]] up for vote and am willing to take the consensus in that case as the guideline for [[Game Disc|GameDisc]]<code><nowiki></nowiki></code>s with a single audio track. [[User:Dupuy|@alex]] <br />
<br />
----Authors: [[User:TarragonAllen|TarragonAllen]] [[User:Dupuy|@alex]] [[User:mo|mo]] <br />
<br />
[[Category:To Be Reviewed]] [[Category:Style]] [[Category:Official Style]]</div>
Dupuy