#musicbrainz

I'm curious how people think it should be handled though :)

ruaok: do you think mb will ever start hiring people?

yes.

this fall.

mb offices with a bunch of people hacking away would be awesome

really!? awesomeness :D

yes. we should have money to throw at a dedicated mb_server dev

I assume still internet based, but still cool

yep.

aCiD2: do you have libofa install on your linux box?

would you mind trying to test a new tarball for me?

yup, installed it earlier I believe

would anyone?

sure

its not anything new -- I just need to sanity check this tarball.

slowest 500kb download evar -_-

ya, sorry.

ga, fucked up the timestamps.

clock on that box is bork

checking whether build environment is sane... configure: error: newly created file is older than distributed files!

that what you mean re: clock?

ya. one sec.

lemme fix the time and rebuild. :)

):

aCiD2: re-download please.

aCiD2 has become an official build-guinea-pig :)

good enough for me!

milosz is now known as deadchp

the title of guniea pig or the tarball?

haha, the title so far :P

make was fine

ruaok: make ran without errors, do you have a test target or anything I should run too?

naw, make is what I am mostly concerned with.

thx!

np :)

What is the wiki markup for adding sig to a mbwiki page?

bonjour murdos!

hallo ruaok!

:-)

aCiD2 did a write up of the summit: http://docs.google.com/Doc?id=dfbhxt9d_236fj386vh

I need to flesh that out and post it somewhere

yo murdos :)

good news!

hi aCiD2 :)

i'm not very good with words, so it may well be a little verbose at points... that or just make absolutely no sense :P

it needs to be on the wika

don't seem complete: dmppanda said to me there were gin tonic and nightclubs ;)

:P

loi

that was the afterhours afterhours.

lol

so the plan is that BBC start to work on NGS from the TemplateToolkit version?

oh good point actually murdos, I meant to ask you this ruaok... what is the status about the BBC working alongside my work?

I haven't heard much since leaving london.

so, I don't know.

anyone I should email?

the only thing I was worried about was them getting ahead of you.

naw.

:)

okie dokie

so ruaok, what the roadmap in the near future for the server?

near future...

do you still plan to do an non-db-schema release?

no.

the next release will be schema change.

drop table trm;

part of that will be trm removal, various bugs, tag improvements, probably cd lookup improvements.

and whatever you and luks would like to squeeze in.

oki

then we'll proably have a release with niklas' discography support.

then a release with aCiD2's TT work much later this year.

what is the purpose of cd lookup improvements?

then all work going forward should be based on TT.

sure, go for TT !!

to make the cd lookup features a little easier to use.

ruaok: sounds like a good time as well, I really want to get this polished before we push it out

make sure everything is done as cleanly as it can :)

mainly to make it so that we can use it to make money to hire more devs.

aCiD2: yep. :)

and what about timestamped entites which will allow google search, RSS, ... ?

not sure if we can make the google search happen just yet, but that is scheduled for the next release

and then we'll be flooded by new users :|

you say it like it's a bad thing :P

with its good and its bad

that part of the issue I'm worried about.

indeed. too much traffic == bad.

huge influx of users is also bad for the community.

I'm not sure the moderation system is ready for that

hmmm

we proabably need to move the WS to EC2 before we can have enough capacituy on the main servers for that

Heheh

Hadoop cluster!

I failz to see how hadoop will help here.

Oh storage, not computation

ruaok: got a minute? I've a question about db schema for ratings

shoot

I'm not sure it'a good idea to have separate tables for aggregate ratings

aCiD2: was it you harping on about trying to get data out of rolldabeats a while ago?

there's 1 rating for 1 entity, so we could have the rating in the artist table e.g.

IN the artist table?

or artist_rating?

will allow to use less dabase requests

yes, in the artist table

certainly no in the artist table.

that conflates too much data.

you think?

the problem will be on the artist page or a release page

and we want to keep the raw ratings separate from the main metadata.

we will load the release ratings + n*ratings for the tracks

for instance, in tags we have raw tags in the rawdata server and the aggregate tags in the main server.

Sure, for the raw tables I will keep separate tables : http://bugs.musicbrainz.org/browser/mb_server/b...

this way we can have the raw data grow big -- without needing a STUPIDLY large database server.

ok.

but in the end, once you've calculated the averate rating, you only have 1 rating for 1 artist

the tags are very similar to the ratings.

we keep the aggregate tags up to date automatically.

and the user may not always want to know the tags.

user in this case could be a WS caller or a mason/tt page asking for data.

exepted that you've many tags for 1 artist, but only one rating (says 3/5)

by creating better granularity we can better tailor our database requests.

it should still be in a separate table.

ok

I used to think much like you, but pretty much all those conflating decisions I've come to regret.

for instance the page column in the entities.

that is used for paging the browse pages.

works, but it doesn't belong in those tables.

now, luks and I were just talking about creating artist_meta and track_meta tables.

oh yeah, timestamps.

see, luks feels that even timestamps should not be inthe main tables.

but in a separate _meta table.

let's create the _meta tables and put the aggregate rating and timestamps in there.

how does that sound?

ok for me, you're the db architect :)

me?

oh boy, we're in trouble.

whenever I do something I ask luks to tell me how i screwed it up and how to fix it. :)

yes lol, you've much more experience than me of real application

ok :)

:-)

hmmm. how do we do this?

given that the timestamps are in trunk and your stuff is in a branch...

I've branched rating recently

so maybe I've it