BrainzBot (~BrainzBot@musicbrainz/bot/BrainzBot) has joined #metabrainz
2017-03-20 07959, 2017
BrainzBot joined the channel
2017-03-20 07959, 2017
Freso
Oh.
2017-03-20 07959, 2017
yvanzo
Similarly, I am in favor of won't fix, for the same reasons.
2017-03-20 07959, 2017
CallerNo6
+1
2017-03-20 07902, 2017
Freso
Soz.
2017-03-20 07929, 2017
BrainzBot joined the channel
2017-03-20 07929, 2017
reosarevok
This is a bit more annoying to revert
2017-03-20 07938, 2017
reosarevok
But I still think it makes sense to leave it auto-editable
2017-03-20 07952, 2017
yvanzo
Thanks for these comments by the way.
2017-03-20 07957, 2017
reosarevok
(so won't fix)
2017-03-20 07916, 2017
Freso
The data is still available in the edit history, and Track MBIDs are preserved, so no data is lost with the moves back and forth.
2017-03-20 07927, 2017
CatQuest
yes
2017-03-20 07943, 2017
CatQuest
it could have been confused for track re*ordering*
2017-03-20 07949, 2017
CatQuest
which is a mess if it was auto
2017-03-20 07910, 2017
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | GSoC Getting Started: https://goo.gl/JTNkn0 | MeB meeting agenda: DR: MBS-7108 (yvanzo), Picard feat. plugin (reo); next week: DR: CB-244 (Gentlecat)
2017-03-20 07912, 2017
reosarevok
(track reordering is *also* easy to revert, but that's a topic for another day)
2017-03-20 07918, 2017
Freso
I think this is decided too, no?
2017-03-20 07919, 2017
CatQuest
:O
2017-03-20 07922, 2017
reosarevok
Yup
2017-03-20 07924, 2017
Freso
Or is anyone against Won't fix?
2017-03-20 07929, 2017
Freso
Let's move on:
2017-03-20 07931, 2017
Freso
reosarevok: Picard feat. plugin
2017-03-20 07941, 2017
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | GSoC Getting Started: https://goo.gl/JTNkn0 | MeB meeting agenda: Picard feat. plugin (reo); next week: DR: CB-244 (Gentlecat)
2017-03-20 07911, 2017
reosarevok
So. The only thing between me and a "let's no longer standardise "ft." and whatnot to "feat."" guideline change is the lack of a Picard plugin to re-standardise it for people who want that
2017-03-20 07940, 2017
CatQuest
:O
2017-03-20 07952, 2017
reosarevok
I probably could learn to write Picard plugins since it sounds like an easy one, but tbh I have a huge amount of things to do as it is, so I'd be very nice if someone else volunteered ;)
2017-03-20 07904, 2017
reosarevok
...er. It'd be
2017-03-20 07909, 2017
Freso
samj1912: ^ :p
2017-03-20 07912, 2017
reosarevok
(I'm always nice)
2017-03-20 07917, 2017
CatQuest
you should be nice too
2017-03-20 07928, 2017
CatQuest
(especially to whoever does it:D)
2017-03-20 07942, 2017
Leftmost
I have enough on my plate, but I desperately want to no longer standardize feat. (And, in practice, I don't. :-P)
2017-03-20 07944, 2017
Freso
There is already a feat. plugin (or several?), so they should probably "just" get updated with new code.
2017-03-20 07953, 2017
reosarevok
So yeah, if anyone is willing to take this on, it should be just a simple regexp
