#musicbrainz

when they have an iso code, sure

but making one up would be silly, 'cause they're bound to get one

yup, and the result isn't official yet

that too

I bet they end up wanting their own language too

as if trying to distinguish serbian, macedonian, croatian and bosnian wasn't already hard enough

night all

Knio1 is now known as Knio

morning

hi!

MingVase is now known as MartinRudat

what'd you do?

dropped a (largeish) board on my leg. it hurt a little.

...and my mum wonders why I won't wear shorts to work even in mid-summer... =)

G'day keschte

hi keschte

hi keschte

to your email: I noticed the discussion but had no time to take part then :)

hi Sim ..eh Shepard

hi nikki_

np

i did not like the ideas they had about overloading album/release even more, so i intervened.

hah

nikki_, Nyght: mb-users RFV Release

but since you probably don't read users, you missed it ;)

nikki, but how big is the card, and how big is your handwriting? :P

I read users, but I saw the whole, stop shooting, I have more work and ended up not reading into much after that. Reading now

Then again honestly I got slightly soured from the constant negatives without suggestions.. so, took a break from that too.

I hate it when I wake up and press play on iTunes, but my speakers are both way up from watching something last night

keschte: ah, I did read it

http://thedailywtf.com/forums/thread/73098.aspx <-lol

mustaqila: 3 by 5 inches and normal sized

Nyght: now if i get that right, shooting is something i'd do if i were agressive, right?

have you seen the emoticon...

Ah

and Nyght: not reading mb-users is perfectly normal, nothing anybody has to explain themselves if they don't

exam time

bye

Good luck!

good luck nikki

keschte: yes, Frederic stated it, didn't mean he was getting the aggressive end of anything. ;)

Mmm, but I do try to keep up on users.. I feel that's part of actually keeping in step with a lot of things to do with musicbrainz

mb-users = drama over emails, where you can watch metaphorical chimpanzees throw their crap at each other, after agreeing on the odd small matter

That's about as much as I can grasp from it, so I like to avoid reading it :

)

Nyght: experts, development is the lists that matter, imo.

style is very dramatic, too

muz, for the most part I don't agree. I see it as people that are passionate about their hobby, but sometimes forgetting that all negative doesn't create something in the end.

mustaqila: a wee bit negative, but one can say that :)

now that we've agreed that we will calmly put an end to such demanding threads, it should change for the better

I hope so keschte, it's nice to have a "want list" or, a "this would be nice in the future", but ultimately what we can count on is what we have. What we desire, would be nice.. but unless those people are willing to roll up their sleeves, they're not part of the solution.

i've seen the term http://en.wikipedia.org/wiki/Meritocracy in the wiki lately, i like that. if you want things to change, roll up yer sleeves :)

yes, a very good structure for something like musicbrainz.

I mean, I can say, this would be nice.. but, if I want to implement it, I have to document and start to put it into order. work along side with the devs, or make my idea catchy enough that it inspires one of the devs. :shrugs:

maybe you've seen it. i ported the documents from the main server to the wiki

i do not expect other people to do dev work on the server 'cos of: http://wiki.musicbrainz.org/Development/Server

i'd be glad if you could review the pages under "Development" and "Products" for spelling, since they will be official wikidocs pages directly linked from the menu on the page

Sure thing. :) I'll do that right now.

just search for the respective terms in the title search. this will turn up all the relevant pages

at the moment I'm just following along the links, then I'll do a broad search

if you find the pages have too few interlinks, we could add more certainly.

so far I'm liking it.. I am a bit web minded, so I'm thinking perhaps a next. but usually on wiki that's not needed at all.

Still getting used to the wiki mentality.

hmm.. if liner notes say "arranged, mixed & recorded by ..." then I guess I shouldn't use the "arranged" from the composition class, right?

wiki mentality? pretty mental, for sure... =)

very mental, nuts all a' ya. ;)

shep, I would take that arragement as composing myself. In the manner of arranging how the piece is going to play out.

keschte: Is this "programmer" reference? In all cases, by doing a plain "checkout" of the appropriate module you retrieve the latest development copy, which will not necessarily be stable. If you want a stable copy, corresponding to a particular release, you'll need to find the correct Subversion tag corresponding to the release you want, then you can then fetch the release in question.

because it's very confusing to me, but if it's programmer reference, that would explain it. :)

sounds like one to me...

where did you find it :)

again, it may be very "normal" and therefore just "over my head" in this instance, and that's cool.. but, if it's supposed to be "generally" understood, we have to work on it :D

ok.. it needs some understanding how development/release cycles work.

there are versions(or tags) of the project in the source control

okay

then there is /trunk which is the development copy

which is unstable.

the version currently on test. is trunk, it could be another named branch, too.

So, there's truck, and then there is branches (for lack of a better name) the branch can be checked out. But, the trunk is what is running on test?

/s/truck/trunk/

and checked out, in the form of library type check out? Or?

Nyght: you can check out any revision of the entire source-tree, but trunk, and tags/release-whatever are nice names for particular versions.

i've written a paragraph "version" here which explains it: http://wiki.musicbrainz.org/Products/Server/Dow...

any branch, and trunk can be checked out

branches is not a bad name for the concept.

that helps Martin. Thank you, because tags is also confused with the tagging, tags of music.

one can start developing a feature on a branch, then merge the changes back to trunk.

thats how it normaly works

That is a lot more clear keschte, can you shift some of that to the other, I am gettting the most from the first and third paragraph

Okay, thanks both of you to help clarify.. now, to try and make it clear from the very barest clarity I have. :D

but since the pages under Development/ are targetted at developers, that should not be an issue

That's what I asked in the first place. :D

so, it doesn't need to be clarified, and can go unchanged.

i'll move the checking out paragraph below the list of projects

because any dev worth their salt should know exactly what you're talking about.

are you currently editing it?

Nope, have nothing open in edit mode

Martin, That's when you have that big stamp in red letters BETA IDIOT!

=D

ok, i rephrased the sentence a bit: http://wiki.musicbrainz.org/Development/Projects

Nyght: to be stamped on the forehead of someone who complains that there are bugs in the most recently submitted code?

Yes Martin, exactly!

in reverse letters so when they look in the mirror it's plain to see. :D

heh. =)

lol

okay, so I'm a bit spunky tonight. :) it reminds me of the guy that was asking if Musicbrainz broke up mp3's from a streaming radio, and how might it be gone about to label them.. and I said, hmm,. look up the lyrics on the web, input them into the tag and if you want to split them, edit them and split it.. he said thanks and left rather quickly. :D

Oh, i should giggle over that.. but, it was sorta amusing at the same time.. I mean, ya know... we said it couldn't do it.. then what do you expact for an answer? Let's get right onto developing it so it can?

/s/should/shouldn't/

another quick question keschte, in this sentence excerpt "allows to request" from this sentence (which allows to request data from the RDF web service and look up TRM IDs from WAV audio data.) it allows a user. developer, who is it allowing?

I presume it allows the user, via the client, and the client library... *shrugs*

I'm assuming that too Martin, but I might as well get it right the first time. :)

okay, I made it end user, if it turns out it's something else, I'll change it then, or keschte can change it. ;)

good... i was away for a sec