#musicbrainz

heey this is mo from my mothers machine :DDDDD

Hi, could anyone give me a clue why MP3 files are greyed out in Picard. I am using Feisty Fawn

sudo apt-get install libtunepimp5-mp3

:)

Thanks, luks . I use aptitude :)

SerialNumber^ has joined #MusicBrainz

rawr

ping katta

howdy mo :)

:D

mo has internet

mom*

:)

she is katta

you can say hi to her if you like

she's away watching "millions of bats on TV"

funfact: in norwegian "of" is 'av' but "off" is also 'av'

Knio1 is now known as Knio

hi katta :)

brianfreud: how do you keep track of those edits which you added a note, but are waiting for the original editor to do some fixing and such?

That's where abstaining only on those I'm leaving such notes on come in handy

I just do a adv search for all open edits I abstained on

ok, hm... i also abstain when i don't have an opinion but don't want to see the edit again.

well, you coul;d further limit to add release edits

i already assumed that :)

:P

also, a bunch i prefer they would fix it, but in general the add release edit isn't too bad and I already voted yes.

i could ofcourse abstain those too if i know i'll get back to them. hmmm.

yeah, a "follow up on me" checkbox would be nice to mark those

i mean, the problem is only if the original editor doesn't respond. if he does, i'll see the notes.

i'll try to use that abstaining method of yours.

yeah - pretty much, if it needs follow up, but I voted yes, I have to pull it from the emails. the abstains tend to be the ones needing more - verification urls or whatever

:P

omg

my mum learns stuf fast

Now grooving to: Chachani ~ Tamia (from Vol. 6: Perumanta)

MBChatLogger: off

is not logging

is logging

can i again say what a stroke of genious http://wiki.musicbrainz.org/kuno/CurrentProposa... is?

uh

i mean http://wiki.musicbrainz.org/kuno/CurrentProposals

kuno ftw

btw mo, I tried to ID the authors of the older proposals, but can you couble check that I listed you for the right ones in there?

yes

cool

there isalso one where i propose adding [instrument] to 'was member of' (or adda seperate one)

CatCat: thanks :)

its i nthe mailing lsit

I that page should track only style proposals

no it shouldnt

it shoudl track all proposlas

no devidings

it doesn't make much sense to track most of the feature proposals

besides its warps page :D

does to me

because it's not just a simple decision: let's do this

it can be seperate later

it needs to be actually done, which involves a lot of work

seperated*

while for style proposals, the decision is the only thing you need

but findign and listign all proposals was a good job, currently stuff is a *mess*

true

luks: a lot of the proposals need just to be made official, just never were - the three caps ones for example

but its still under warp for that reason

its not complete

yeah, he said he's gonna move it, just didn't think it'd get fleshed out so quick

yes

brianfreud: I meant things like "Artist Role Inheritance Proposal"

or "Album Rework Proposal"

well, why not list them?

they're active proposals, right?

luks: i sort of agree.

because they will never be implemented in that way

amnd then 'current style porposales can be oen page and 'current feature propsoals camn be another

right - so they ought to be marked historical, rather than active proposals then

amny of those can be 'preserved ofr historical purposes'1

those are proposal you can steal ideas from then working on a feature

brianfreud: jikns

luks: exactly

so why do they need tracking, if they never will be implemented fully?

hence historical, but oughtn't to still be marked CategoryProposal and no "this is for historical blah" note - makes it hard to distinguish truely active from "dead"

luks: would you prefer seperate pages, like CurrentStyleProposals and CurrentFeatureProposals?

if only so they get noticed, marked historical, then removed

thats what i said :P

I'd prefer a CategoryHistorical

thats great frø

get to it >:D

warp: we already have a few pages for RFEs

+ trac

luks: trac is mostly for tracking issues, not their proposed solutions.

well, track can link to the proposed solutions

track

we also had wiki.musicbrainz.org/CurrentProposals, but it was WAY out of date

luks: yes, true.

luks: you have to remember that a) this was a rawdata list fetched from wiki and mailing lists, b) it can be fixed/refined alter c) its in uh 'alpha' right now :D

hehe, yup

alpha 0.2

yes

it makes sence to seeprate featurws fro mstuyle

i dunno, it's just that I think filling it with RFEs kills it's usefulness

my main goal was to track the style issues, because they are often forgotten and usually not that much effort to follow up on and get some closure either way.

and luks;: remember that you know more avout how the server will be lookign the next year(s) than anyone esle talkign right now

:)

warp: yes

well, finding all the open proposals is, imho, the 1st step. then sorting into some sort of categorys, then figuring which just need to be quickly passed, or marked historical only

brainfraud said however sicne their foudn the old feature things

can be marked has historical and put in a category and moved of that page

yes

so the finished moved-onto-actual-page-not-just-subpage-page can be what luks said probably

and what warp intended

(wich isorta agree with)

but the initial findign of all the proposals (be it style or feature) was a good idea

not exactly

and i just csme with a great idea

http://wiki.musicbrainz.org/AlbumRework for example

it's an idea, not a proposal that should be implemented

the naming scheme for all those pages is very inconsistent :)

then mark it as that on warps page :)

http://wiki.musicbrainz.org/NextGenerationSchema has many more of those

anyway, i'm off to a movie. will do splitting up at some point, will hopefully read the rest of todays backscroll when i get home.

thanks for the feedback :)

and I should probably remove the rap one, now that is was vetoed :)

someone vetoed it?

gecks