#musicbrainz

but I failed at adding it to the WS

GET /ws/1/tag/ should return list of user's tags

because if we want to have applications to support tagging, they need to know what tags are already there

yep.

wanna split the tasks? you do this one and I do the transaction mucking?

ok

ok, on to coverart ARs.

MBChatLogger: off

is not logging

is logging

so....

luks: do you think that changing the coverart support to have direct links is a good idea?

mbchatlogger: off

is not logging

is logging

I hate this BS.

and that's who was hiding in the grassy knoll.

:P

lol

now some more productive question... :)

welcome back

shoot.

when do we want to have the test version of the next release ready?

next week?

I'm afraid I wont make it through my bug list before then,

its looong.

and I'm afk from 24.8 til 3.9

and my brain is scheduled for dry cleaning on 5.9 :)

I haven't looked - has anyone put in a bug yet for the screwy display of edit notes on edits?

example: http://test.musicbrainz.org/mod/search/results....

the timestamp moved to in front of the notes, and is causing all sorts of funkyness

I think this xhtml branch can't do the release

it would cause too many problems

would more time help?

the menu parts seem ok, but the rest of the pages still need some work

er, *can't do to the release

ruaok: I'm not sure

separate non schema change release?

it would be probably safer that way

ok.

I can keep working on bugs for the next week and maybe we can get a an early version of the new branch up by the time I leave>?

then when I get back I can work on more bugs and the tagging improvements.

UI improvements.

how does that sound for an approach?

sounds good

so, shoot for say... a formal call for testing on the 23rd?

Could I make a suggestion?

yep, that's fine

ok. deal.

brianfreud: its never stopped you before. :)

LOL

Problem I always run into on test is I'm normally not really sure what is new that needs testing.

how about we issue a changelog before the test?

Any chance of a list of the new stuff that is aimed at the release, so we know what specifically to test?

yeah, that's the idea

we'll include that in the formal test announcement.

we could also revive something like that in the wiki: http://wiki.musicbrainz.org/ServerReleaseNotes/...

could be useful to track what should be tested

?

thanks for volunteering murdos!

ah ah :)

:-)

ok, I'll start something, but you know it's a wiki anyone can contribute ;)

I will write up the tagging stuff, for sure

thanks :) anyway I couldn't have written the tagging stuff ^^

luks: on the other thing, I have acid2 on IM - you need to talk to him at all about it now?

no, it's too late for me to talk about technical things in picard

lol, ok

lol

brianfreud: I see you added something to the VS wiki page...

ya, a few

I'm slowly going through this list and adding them one by one - http://89.173.152.204/~lukas/mb/vs.php

needed something to do while I ignore Morricone :P

I'd like to have the 302 ... series complete

yes, I saw your label note - I added a few other cancelled releases to the list

nice

you adding the colosseum events?

not for now

only if there already is now without cat# info

*is one

I see CVS numbers, but not VSD ones - oh, right, you're doing the 302s...

I wish there was some way to edit a wiki table as a table...

editing a table as large as this one in wikicode's a pain in the neck

do spreadsheets export to XHTML? or can you embed a spreadsheet as PDF? something like that?

or XML?

Best I've found is to take the table, dump it in Excel, and data -> columns on "|"

then re-add the |'s later, make sure to incorporate any changes since I snagged my copy (luks, whoever), add them in, and paste it all back

yeah... primitive but effective

a true moinmoin wysiwyg table editor, with basic sort, etc would be so nice

wikipedia recently added sortable tables, though I don't know what they're like to edit

i'm nore familiar with mediawiki than moinmoin

wow. we have nearly 10k labels. impressive. :)

||CELL 1||CELL 2||CELL 3||CELLL 4||

over and over and over

So I'm working with "||1997||CD||VSD-5766||Batman||various McNeely, J. C||" or "||?||Cassette||VSC-5272||[wiki:Album:d2c316f5-9839-4a2d-9526-fed8316f2969 Back To The Future Part III]||||"

just really ugly in plain text

mooo

respond tomorrow if you're too tired.

well, the refcount value doesn't represent the tag usage

that is, how many people used it

so for generating a tag cloud or anything else that need "weigth" tha tags, it's not the best option

but I'm not sure if it's worth tracking also the real usage...

no clouds!

id rather do it with colour

how?

that is to track cumulative tag usage, not on a per entity basis?

something like darkest and reddest for the biggest, lighter towards orange &yellow for smaller

ruaok: yes

untikl you get to lime green for smallest

no blue?

or something

catcat: this makes till a tag cloud :-P

blue is darker than yellow again id say

Moos

e

luks: I dont see the immediate benefit of that. can we just leave it be for now?

roy g biv

sure

muuuzee

the per entity clouds would work ok with that we have, right?

Tag clouds are awesome!

yes, this is only for global tag view

i'd only recommend using color if it meets accessibility standards.

They're an efficient, easy to understand method of conveying multiple properties associated to one given item

ok, I can do with out that.

tag clouds are hatefull, i cnt pay attentino t owhats one screen when huge blobs of texxt scream at me

yllona: it'd be niftier if you could say I like colour, I like clouds, I like greyscale, ...

yes, for example, I HATE this one... http://www.rockymusic.org/tags-all.php

Tag clouds also grab attention and allow for the better flow of one nav point to another ;)

ugh

ding brainfrø: thats exacklty why i disliek them

ha! totally useless.

the MB ones don't look like that

...oh, and "don't show tags", too, I suppose.

its noize for the eyes