#musicbrainz-devel

I *think* I’ve been there once.

grand canyon later today, and then onward to Page, probably, for horseshoe bend/antelope canyon/that sort of thing

was a loooong time ago.

then up into utah for arches, bryce canyon, etc.

oh, ianmcorvidae did we note down the password for dib somewhere?

it's insyswiki, I thought

I’ve got ernie racked, but the switch seems to refuse passing packets along.

I thought so too,but I can’t find it now. :(

Anyway, it's past 9 CEST now.

ah ha time has come.

:D

someday I am going to show up at your house at 9 and sit on you.

hm. lemme search for it

you know, for old time sake.

ianmcorvidae: thanks.

I’ll go first for review...

last week I took tuesday - thursday off for our second anniversary.

in the background I coordinated getting ernie setup.

ernie is now racked and reachable. localhost setup is done.

now the massive task of getting everything into chef for building the gateway pair starts. not fun. long road.

oh and some gsoc fretting.

who is next?

I guess I can

if you can put up with my slow typing :)

go

so primarily I've been on sitemaps, as always

I have a basic start on the last-modified stuff in progress, which I sent in an email to rob

I'll finish talking and then find the appropriate links

but anyway, I've set up the tables and the stuff so the sitemaps code can use it, and started writing code to generate triggers from a declarative JSON format

sorry,I ran out of time to respond.

mañana.

that defines the dependencies between pieces of data

no huge deal, though I was worried you hadn't gotten it at all, so at least a "hey, got the email" would be appreciated :)

k

anyway. I've written the code for the easiest triggers, next I deal with the problem of intermediate linkages, starting first with l_artist_work stuff for things that appear on the work overview

I do intend to work on this while traveling, hopefully I can have a PR up for everything to have the works sitemaps have last-modified information by next meeting (hopefully sooner)

fabu!

andd then it's on to the more ridiculous entities, especially artists

https://bitbucket.org/ianmcorvidae/musicbrainz-... is my branch

https://bitbucket.org/ianmcorvidae/musicbrainz-... is the start on triggers

I’ll have a look tomorrow.

format somewhat pending for the intermediate links stuff, I'm at least thinking I'll need to establish a separation between stuff that needs triggers (e.g. l_artist_work) vs. stuff that's just joins(link,lin_type)

but anyway, that's where I am. I also did some schema change and other review to try to keep things moderately moving

fin.

gonna go order something so starbucks doesn't get upset at me

LordSputnik: go

ianmcorvidae: don’t drink the coffee!!

On Wednesday, we officially launched the BookBrainz beta

I never saw anything about it. :(

IT's got search, entity and relationship creation, and nice stuff like that

Oh, and messaging

(and my clipboard is broken, so I can't copy paste :()

Next month, we'll hopefully be focusing on improving client/server interaction on the site

We're planning to use socket.io and React.js to get better handling of forms (sending and validating data in realtime)

And that'll allow us to implement entity editing, and to simplify our existing entiy/relationship creation code

Other than htat, we're also going to work on improving tests and docs, and maybe implementing JSON-LD in the WS

And we're having a meeting at 21:30 UTC in #bookbrainz-devel if anyone is interested in coming :)

done!

bitmap: you around?

yes

hi

hi. go.

I helped move BB to sakura early in the week

thanks for that. :)

submitted a long-in-the-works PR to make writing/deploying our JS a lot easier, which basically replaces browserify

I tweaked some nagios settings to make room for BB there

I worked on MBS-6065 which stops ISEs from people submitting artist/label forms twice, but it adds some locking that I'm unsure about

I'd glanced at that but I'm unsure as well, need to think more

building on that PR I moved some of the duplicate entity checking code to the client so it's more instantaneous (and removes FormHandler code in the process)

which can be seen on http://bitmap.mbsandbox.org/artist/create by entering a dupe artist name (but be warned rika is slow)

Yay less formhandler :p

the rest of the week I just spent working on the UI for my schema change patch

I put up the actual SQL bits for it already

fin

reosarevok: go

I was getting back to normal from the crazy BBC stuff

A few style tickets got closed or implemented, and more will this week

Apart from that I was cleaning up a lot of composers for organ because why not and the general support mails

One of the style tickets for this fortnight should involve getting rid of some guess case code, which is nice

And that's about it really

welcome back from the BBC gig. I hope that filled the coffers a bit.

chirlu`: anything from you?

Well …

He got made a forum moderator, if that counts! :p

(hope that bit is working now...)

I finished the PR to let destructive edits wait a while longer before being applied, which I still hope might get into today’s release as a non-beta-testing-anyway thing.

reosarevok: Yes, working now, though I had no chance to actually delete something yet.

Ok :)

I also mostly did the remove empty_artists() etc. bit (excluding tests) and one or two bug fixes.

End.

I was at a folk music camp, https://musicbrainz.org/event/1bf22dee-b1d4-4a6... , and has returned to finish off the traditional part of the BBC job. Fin.

anyone else?

nikki has changed the topic to: Deep freeze week | Agenda: reviews/general discussion, GSoC (ruaok), next release date (chirlu), wikipedia/wikidata links (nikki)

ok, onward to topics then.

GSoC.

chirlu` has changed the topic to: Deep freeze week | Agenda: GSoC (ruaok), next release date (chirlu), wikipedia/wikidata links (nikki)

ianmcorvidae: do you have any more input on the gsoc stuff?

I've been meaning to go comment again -- when is the deadline for us?

that one browse proposal looked good, but I wonder how java will fit into the equation.

to be honest, both browse/search ones look good for different reasons

we need to have the desired number of slots set for tomorrow.

both?

ian's connection is being weird

ianmcorvidae: I think we should chat a little bit about this stuff after the general meeting.

to me

okay back, stupid thing

ruchiranga and weeksio both are applying to the same thing, anyway

and yeah, sounds good to me

I should refresh my memory as to the other proposals

the ios one looks interesting but hard for us to find a mentor for, which I think you already said

the AB ones I think you have a handle on

or have deferred to alastairp, yes.

but we can pause for now and discuss after, if you'd like

ok, I gues we can wrap this up for now and go on...

chirlu`: next release

chirlu` has changed the topic to: Deep freeze week | Agenda: next release date (chirlu), wikipedia/wikidata links (nikki)

I happened to notice that it is five weeks from today to the schema change release.

already?

So the question is, how to divide these five weeks? 3+2, 2+3, 2+2+1?

I'd propose 3+2

I vote for 2+3

Heh.

given that ianmcorvidae is traveling, 3+2 makes the most sense to me

Ah.

Sure.

yeah

I'd say 3+2 too, because we generally don't want to lump too much other non-schema stuff in

and I need to deal with taxes and such sometime soon >_<

(some after the meeting, need to mail some stupid thing because the IRS thinks I made an extra $25k I didn't in 2013)

yeah. tell me about it.

:(

obnoxious. anyway, I think 3+2

1096 are so arcane.

they must be typewritten on their form or handwritten on their form.

yes, lets go 3+2.