#musicbrainz-devel

ocharles: ah, I thought the name of the author on that paper was familiar

a friend of mine works with him

alastairp: oh wow! that's awesome

mcbride is a bit of a hero to me, with some of his work/knowledge :)

ocharles: warp beta is continuing to be a complete pita

slow as hell, 502s, etc

uhh

what's with https://musicbrainz.org/user/delete%20me%20-%20... ?

nikki: I think that's the user rob couldn't delete on the site because they have too much data

they have open edits though

and http://tickets.musicbrainz.org/browse/MBS-4085 is closed as fixed

nikki: yes, closing edits is part of the delete process

rob literally just renamed the row in the editor table and that was it

and maybe removed email/password

so it was implemented differently to what the ticket says. would have been nice if you'd noted that on the ticket :/

I guess I'll just vote no on all their edits then

since they should have been cancelled by someone/something

meh, maybe not

I really just want an abstain that doesn't send me emails, like we used to have

But I like that my abstains send emails

What about a preference? :p

I can comment on an edit if I want to get emails

I have no way of getting edits out of the queue which doesn't involve always getting emails for the fucking thing :(

But sometimes I don't have anything to say (yet) - I want to know what others say if they say something :)

Yeah, that's definitely necessary

I think that's why I don't vote much any more, there's just too much clutter I can't do anything about

it's still possible to say *something* though (even if it's just "commenting to receive edit notes") :/

nikki reosarevok : both of you would like the ticket that asks for a notify-me (not) checkbox in edits (but I cannot find it back), then :)

http://tickets.musicbrainz.org/browse/MBS-3724 this one :P

but that's not what I want really :/ I don't want to have to unwatch every single thing I abstain on

There was a ticket with a checkbox (by foolip?)

hmm

maybe in my dream…

I found http://tickets.musicbrainz.org/browse/MBS-2191

ah yes, this one! So it’s not exactly that either…

maybe this future checkbox could be more almighty like subscribe to all events / unsubscribe from all events

of this edit

maybe complex

bof

hmm. I wonder if nes will help with those

I already said it but I have more experience on *super* nes

have nice week-end, I will replug my super famicom for a little while héhé

/bbq

what's the nes question?

some people want to be notified when an edit closes, but I think most of those cases are so that they can enter further edits

like adding an annotation after a merge was one of the examples

(where you wouldn't want the annotation if the merge fails)

ah, right

or something like: someone uploads an image and I want to replace it with a better image. I can remove their image and upload a new one, but I only want my new image to pass if the original does (since I don't know if the image is correct, I just know how to get a bigger version of it)

would it be able to do things like that?

ah, well this hinges on how we deal with 'pending-but-applied'

but in general, yes, I believe nes can deal with this

the first edit creates the image list [ a ] (one element). Your edit changes the image list to [b]. The failure would then revert it to []. Now we have to merge [], [a] and [b] - which is a conflict

(no 2 sides agree)

so your edit would be put into conflicting mode, and you'd have to resolve that

([] means list, btw)

... maybe we should just have a 'replace image' edit :)

that is a replace image edit

kepstin-work: since I entered the ticket for that, I would like that :P but it's not the only case where you want to do an edit if and only if another edit passes

nikki: I think you entered a duplicate ticket. :D

oh?

I'm pretty sure I made a ticket for MBS-5659 already.

(Although not as detailed as yours.)

it's quite possible.

I'm sure I've seen similar things, but I have no idea if there's one for the exact same problem that's still open. the release editor has had so many similar problems that when a quick search didn't find anything, I figured I might as well just enter it just in case

nikki: MBS-5393

Read and judge. It's been a while, but your ticket sounds very much like how I remember my experience leading to that ticket.

But yeah, it's better to enter a dupe and have it closed as duplicate than not to enter a non-dupe.

warp: What was that testing thing you mentioned that'd output in a format MBJenkins could read?