#musicbrainz-devel

ruaok: that's it.

great. thanks for tackling that.

one quite note: last month I gave a music tech talk in London that Ian had to endure:

if anyone is interested.

nothing earth shattering in there. :)

ianmcorvidae: how about your week?

sure

so, my week was straightforward

monday: making an ass of myself while cleaning up some merge snafus

tuesday-sunday: ingestr

wasn't quite a full week hours-wise, but I've gotten a good bit of focused work done on ingestr

ingrestr: \ø/

I'll be writing up a wiki page on where I am with that, design decisions, etc

so, is ingrestr going to stick or are we going to call it nommr? :)

that's in a sec, actually :)

warp: did you just call me FAT??

lol

feature-wise there's a couple things left: interface glue for doing matchings to MB (probably hijacking /ws/js for some autocomplete) (all the actual code to make them work is done, just need to make the javascript go)

warp: high definition ruaok ?

eep

lol

and some things about importing automatic matchings

but in general it's looking pretty good :)

hoping to put it up somewhere with some set of data in the next couple days

as for names

ingestr is boring :P

and was somewhat interim

7digital already has Gester, btw

or maybe they spell it as Jester

heh. we know what happens to interim names.

yeah, that too

see X-rays. :)

but either way, that's taken ;)

in some various channels I've discussed some other options for names

one was nom[me]r, off of 'om nom nom'

om nom nom

the other was to go with our other long-lasting interim name and choose a star trek character

ha!

+1 to geordi. :)

decided that 'data' was a bit too silly

ha!

obviously not a terribly important decision, but if folks have thoughts/ideas, prod me

ianmcorvidae: we have musicbrainz-data so that'd conflict a bit too

I like the name ingestr

indeed :)

ianmcorvidae: you should make the final decision. its your baby now.

ocharles: on that note, you should put a picture of Data in the readme file for that, clearly ;0

As long as we stick with TNG.

I should mention that I had a call with MetroLyrics, a sister company to last.fm.

Leftmost: lol

they are going to go ahead and match their tracks to MB.

ianmcorvidae: am I missing a reference? :P

(anyway, that's all for me)

and then send us a dump of their matching for review.

ocharles: http://en.memory-alpha.org/wiki/Data

for the first go-round I asked for the best, most strict matching.

so that we can feed that nommr/geordi and have a look at the matching.

ianmcorvidae: ah. not having seen star trek makes me miss these things :)

ocharles: you're next

Besides, Data doesn't eat.

ha!

lol

ok, I had a really productive week with NES

Leftmost: he does: electrons

check out this graph:

that's the amount of tests we have - which is climbing at a really healthy rate

of the new functionality I added last week, we have: works, iswcs, isrcs, secondary release group types, puids, tracklists and mediums, release labels, and url entities

wow, nice

the musicbrainz-data-service itself is slowly catching up and exposing the functionality that the library has, but it's naturally still behind; the library is just more fun to work on

over the weekend I studied "A Formal Investigation of Diff3", and battled with my keyboard first producing https://gist.github.com/71e55997e854133b0a4c

and then finally reducing that absolute mess to https://github.com/ocharles/diff3/blob/master/s... :)

so - I'm now ready to add Tracklist merging

the current implementation conflicts if either side has changed (only linear editing works) which is... shit. :)

tomorrow I'll hopefully wire this in to NES

of the "high priority" nes stuff still to do, I have...

ugh, yeah, tracklist conflicts are annoying at present, looking forward to improvements

relationships still need to be looked at again (they are still missing), and I need to think about how deletions work

ianmcorvidae: they will still conflict in pretty much the same way

but at least now you can resolve them

heh, fair enough :)

so nothing today other than the release

fin.

right-o.

sounds like a productive week all around.

ok, who else for review?

Talking of names I have some news, I have just released a new Musicbrainz based Tagger called SongKong http://www.jthink.net/songkong/index.jsp so Id like to add that to the tagger affiliate programme

ijabz, nikki, reoabsent?

ocharles: I'll try to grab some time this week for NES. on which weekdays are you planning MB work this week?

then hit me with the link.

warp: pretty much all of them. last.fm work finishes this week, so i'm just wrapping up things with them

the Yate tagger also now has a page and then we can get both of them added to menu.

ocharles: ok

ok, If anyone is interesrted in trying it out and giving me some feedback i have a few free licenses to dish out, just pm me

ocharles: when do you go on holidays, so everyone knows?

ijabz: mac supported?

if so, hit me.

yep

ah, good to know yate's actually part of the affiliate program, been watching the wiki edits and wondering :)

anyone else for review??

I'm on holiday 18th dec to the new year

so, on the WS issues and the recording issues...

mostly a holiday anyway, i'll probably still be around and hack on NES as I feel like it

ocharles: ok

:)

ocharles: will you be around for the release that happens during then?

ianmcorvidae: ya

saw discussion of that earlier, hence :)

good.

cool, cool

I need to review the WS issues doc this week and see if I can clean up the comments.

after that I would like to have a meeting that is dedicated to that topic.

got to go afk, on the recording issues, reo has done: http://wiki.musicbrainz.org/User:Reosarevok/Rec...

ok, time for me to go.

ianmcorvidae: can you please lead the meeting through the DR stuff?

LordSputnik: thanks. I'll also try and review that this week.

ok, thanks everyon!

+e

bye ruaok!

sorry I need to run off!

sure

ttfn!

thanks!

so, DR stuff

are we done with reviews?

I think so, unless there's someone else?

apparently not :)

cool

so, as LordSputnik linked, reosarevok's put together a page on recording-related issues, which came out of our discussion last week on MBS-2021

my understanding is that this is to serve as an overview of the issues as we consider how best to fix issues with recordings/tracks generally

and we feel it's best to tackle them all at once?

I think that's not quite clear

ok

I think the intention here is to figure out what exactly is best to tackle

reosarevok has grouped them fairly reasonably; the style discussions are very broad while the tickets are sometimes narrower than they maybe should be

(in my opinion, of course)

so, hm.

give us clear bikesheds for which to decide the colour!

heh, exactly