#musicbrainz-devel

ocharles: I'll be working as normal throughout most of the christmas/new year nonsense, so I will probably be available.

if so, we might want to move to the Friday before (21st) or maybe the new year, perhaps 3/1/2013

warp: alright, lets just go with xmas eve

(I expect 2013 will be different)

ocharles: ok, if my schedule changes I will let you know as soon as I do :)

sounds good!

* oliver.g.charles: MBS-5497: Upload images to CAA with mediatype 'image'

* oliver.g.charles: Fix syntax in CoverArtArchive

kepstin-laptop nikki: Yep. That would be something we'd like to see fixed. :D Also, I wish there was a way to tag tickets. "MusicBottle approved ticket" :p

justinzane: luks would be the one to talk to. :) He's the developer of both Picard and AcoustID.

bitmap might also be able to help

jonnyjd

jesus2099: I don't think he's reading the chatlog. If you need him, best poke him directly.

Freso: well…how ?

wait for him, right ?

jesus2099: Or... mail him through mb.o or GitHub? What do you need him for?

Freso: this http://github.com/JonnyJD/musicbrainz-isrcsubmi... ;)

JonnyJD has cool sunglasses

Yeah, I just saw that in my mail.

Then you've already contacted him.

nikki: <bdi> being inserted everywhere now ?

ocharles: ↗

warp: ↗

even for <bdi>editor names</bdi> for instance

every where that you can have RTL i believe

ocharles: is it possible on editor user name ?

i would think so

then it’s missing in some places like the editor page’s <h1>

then that's a bug

i don’t know which one is the bug ;p

not sure a RTL user name is possible

I’m right handed btw, I can’t test that

i don't see why a RTL username shouldn't be allowed

after all, if that's what your name is, you should be able to call your account that

jesus2099: I wouldn't say everywhere. it's being inserted in a number of places where it was causing problems

jesus2099: and I don't know for sure, but I think <h1> probably provides enough isolation on its own without <bdi> being necessary

hm, release happened, should it still be chilly?

well, it's still chilly here :P

but I don;t think it's a weather forecast, so probably not

it's warm enough that all the ice that formed on the trees this morning is melting and dripping off.

sounds like rain if I go outside.

hah, nice

it was snowing a little bit again earlier

but nowhere near enough to actually settle on the ground

it's apparently 14C here

just barely above 0°C here.

looks like where I would have been this time last year it's... huh, actually pretty warm for there, about 45F

No topics for meeting ?

I thought there were, but apparently they aren't in the topic

1°C here apparently

hmm. about 2°C

I know we at least chose some DR things to look at, or so I thought, but I could be totally misremembering :)

yeah, somebody wiped it ?

hm, mine says it was set by me last monday at about two hours after the meeting

yep

\o/

hm, nope

we did postpone the discussion about ijabz' WS doc, so that should be there

discussion on 2021 was tabled and reosarevok was putting together/has put together a wiki page on recording-related issues

meeting time!

warp has changed the topic to: tropical week | http://musicbrainz.org/#devel | agenda: reviews, DR tickets

ianmcorvidae: I am going to be jumping into another meeting in 30 minutes.

hello ruaok, ianmcorvidae, everyone!

can you do me a favor and finish up this meeting for me?

o/

sure, looks like at present our list is short so we'll see what happens

well, maybe we can have it all done. :)

ok, lets start.

I'll go for review first, get it out of the way.

loads and loads of paperwork, finances, chasing after people for money.

what is interesting is that the number of requests for people taking licenses to our data has sharply increased.

quite a few conversations around that, which should drastically improve our financial situation soon.

sadly, unless I pull another miracle we may end up in the red for the year. first time evar.

if this were corporate america the board would fire me and replace me with some idiot.

ooo, that's sounding nice

the licenses bit, not the firing bit

thankfully this is not corporate america.

you get to keep the current idiot. :)

:D

well, if this was corporate america we'd also be using accrual accounting, right? ;)

I made a little progress on the RSS feed stuff and I hope to return to that later today.

ianmcorvidae: ha, yes. ;)

if this is corporate america we wouldn't be using haskell

:(

s/is/was/

there was one other interesting thing, but it escaped me now.

oh on the bandwidth front.

I upped out commit to 15mbits.

and asked to have it applied to last month, which promptly saved us $150. :)

so, we have more breathing room, but we should still talk about reducing bandwidth. :)

ok, thats it for me.

who is next?

and update the graphs!

warp: go

I can go whenever, my week wasn't complicated

I spent a big chunk of monday doing the beta release, i.e. merging stuff into beta, resolving conflicts and in general making a mess for ianmcorvidae to clean up :(

(sorry again for being an ass about that, heh)

after that I mostly did some related cleanup work on small issues nikki found in the beta release

wednesday and thursday I spent trying to find the bug causing MBS-5637 and fixing it

I skipped friday, and today I spent writing a cleanup script which should fix the bad data caused by the underlying problem which also triggers MBS-5637.

this touches areas of the database where I've never poked around in with SQL before

so I would like ianmcorvidae and ocharles to review both commits, and especially the cleanup script.

alternatively, give me some suggestions on how I can better test it :)

on CR, or?

yep, will be reviewed tomorrow

ianmcorvidae: yes, both the cleanup script and fix to prevent future bad data are on code review. labeled MBS-5637.