#musicbrainz-devel

ok, unsched

next

I think I know what it’s saying, it just seems like a terrible idea and too specific.

skip it for now until someone links the ticket? :P

[MBS-960] Manage tags (rename/remove)375

ocharles: doesn't seem that ill defined. just add "artist" and such.

12 sounds OK

12 would be nice

hrm

(depends a bit on what the actual chatlog says ofcourse)

tags aren't much of our focus

I was going to say unsched for this

12 sounds fine, 3 would be nice too.

but if people want it, 12 is ok

ok, sounds like 12

ocharles: it's not surprising that it's not our focus when they're so hard to manage :P

haha

[MBS-209] Add annotations to the web service277

12 imo

half way there, 12mo

12

search has it

although I'm not sure the implementation is what I was expecting

(or what people commenting on the trac ticket before were expecting)

we can flesh that out when we get to it

seeing as search isn't necessarily an implementation of this

how did you get to 209?

warp: it's the 3rd in the list atm

nikki: I think that's what it will be

709 is the third in the list

well what I saw was /ws/2/annotation/

warp: you should refresh :)

I just did :(

Weird

oh... it's moved around now

http://scheduling.ocharles.org.uk/results right?

yea

Ok

Yeah

It changed

:p

kepstin, damn you! :p

Ok, so 12 for 209?

fine with me

yes

[MBS-2086] Aliases: separate localised aliases from other aliases289

I say 12, but because I want this :p

I think the localized aliases are implemented wrong right now, and we should fix them first :/

12 sounds reasonable

unsched, because they have more votes.

kepstin: I'd agree with that too

:P

But I want i18n

I don't mind 12

+1 kepstin

For this, it's a trivial fix

(ORDER NULLS LAST)

And for that, we need localised stuff being easy

(also better, but that's a separate issue)

well, if it's a trivial fix, might as well :)

ocharles: then it might as well be 12 :P

final votes then?

12

I guess

ok

[MBS-709] Allow searching for a deleted entity's edits1108

does /entity/mbid/edits work if the entity is deleted?

no

the mbid gets deleted

oh

Is that one even possible at all, without overhauling edits completely?

and we don't store the mbid in the edits either?

can we please stop deleting mbids?

nope

warp: +1

(Not that that would be a bad thing)

hawke_1: If we stop deleting MBIDs, that's the best solution for now

I think it's probably unsched until we fix things like that then

otherwise, new edit system

so I think unsched too

(both are fairly invasive changes)

ocharles: stop deleting mbids would be a lot of work?

warp: they're stored in the artist table right now, so when the artist is deleted, so goes the mbid

warp: well, we now need to display deleted stuff as deleted, rehaul the pages for deleted entities, exclude them from search

or figure out sensible UI for just about everywhere entities are used

I think it's more work than just flipping a bool

ocharles: ok

unsched and next?

Ok

[MBS-3288] Release group type isn't shown when looking up a release group983

3

3

Cool!

[MBS-2199] Context help for release type when editing release5114

However, a grayed out "type" combo box is shown in the release editor. This is confusing, I suggest that you add one of those question mark things (like the one next to "various artists release") explaining this.

12, judging from the votes.

12 could be OK

But 3 would be better

12, RE

12

12

And hope hrsfjdjf aka JW does it sooner

:p

heh

Someone point him to it

[MBS-2654] Merge Album 'diff' tool3117

12 would be awesome for that

hrm

12 would be cool but no idea how hard it is

And we have lots of 12

Are we getting bad merges at the moment, or are we just not making it as easy as it could be?

Mostly b)

Hmm

I can see it being the next relationship editor that's all...

ok, I think 12, because getting our current interface better should be a priority

put it in 12 and see how many votes it gets.

(encouraging more editing)

it doesn't seem like it would be that hard with only two releases, the problem is more that we can merge multiple releases at once :/

12 also matches what people want

nikki: right

same

At least merge-merge

Not merge-append, probably

sort that out later

Ok

but for now, ticket goes to 12 mo bucket

and need that damn planning status :P

[MBS-1412] Implement edit grouping287

heh

new edit system imo

which means unsched

but I could imagine the diff only diffing two releases and having links to switch which of the mergees to diff against the target

unsched

Hmm

That sounds reasonable

(and unsched)

[MBS-487] Modify edit conditions for destructive edits269

I have no idea why this went through style

(as in, it is not style-related, not as in "it's mad")

yea... it's also not valid to NGS anymore

(not entirely anyway)