#musicbrainz-devel

in that case it should also be moved down a bit, as that definitely seems less important compared to the Artist page.

yeah

nikki: yeah, you're right.

oh, would the release page also include release group stuff?

no, probably not. I've just completely ignored release groups :)

a release group style guideline would be more focused on which releases to group under it, I think that's a seperate thing.

nikki: I moved release and removed the box/volume/disc stuff, and added release groups.

"All tests successful."

happiness and joy!

aCiD2: good news!

out bank had nearly folded and via a shotgun wedding was sold to chase.

over the weekend they switched over to the new banking system.

and they allow online wire transfers!

HOLY SHIT!

woot!

that makes me pretty damn happy.

so no more xe, and dumb clerks who don't know what they are doing?

correct.

I should be able to order the transfers from wherever.

and it should work as fast, if not faster, than when the dumbass clerks were doing it.

ok, off to another free lunch. back for the meeting in a few.

So since the the meeting didn't start at 3pm EST, can I safely assume it will start at 4pm EST?

navap: i think so

navap: yes.

navap: I did that this morning :(

ruaok has changed the topic to: agenda: review, ???

push @agenda, "release editor unit testing"

heh

nikki: can you publish the wikidoc pages Picard_Download, Picard_Plugins and Picard_Scripting?

ok

thanks :)

ruaok has changed the topic to: agenda: review, release editor unit testing, ponies.

uh oh

<BANG>

Welcome everyone!

outsidecontext_: the scripting page isn't in the wikidocs list, should I add it?

greetings from an unseasonably nice San Francisco!

aCiD2: wanna take the lead?

sure thing

so to recap from last week, I was continuing my focus on the release editor and trying to wire it up with the server side

good news is, I'm mostly there!

nikki: it's maybe better as a normal wiki page

nice! again, I'm really pleased to see your progresss on the RE.

You can submit edits to edit release information, editing tracks, adding new tracks and some other stuff

outsidecontext_: I've done the other two pages

nikki: thanks a lot

ruaok: New agenda item: MediaWiki captcha

aCiD2: very nice.

The only bit missing is deleting mediums and new tracklists (not existing ones) -- these need edit types, so a few more hours work

have you touched the stash features yet?

Still haven't touched them yet

ok.

Do we want the stash n for the alpha?

I was about to address that.

I've been focussing on just getting it working, but I understand you want this to "sell" the effort we've been doing :)

I think we should not do that right away.

the sooner we get more eyeballs on the codebase, the better.

yea

lets keep the road to the beta release as short as we can.

we're going to need to start making sure we have that definition down really soon too

I think one of the things I am going to do this week is pick up a list of things that need to be done for the beta release.

aCiD2 probably meant ' (ie, make sure the milestone on bugs.musicbrainz.org is full of exactly everything we want) '

(ie, make sure the milestone on bugs.mb.org is full of exactly everything we want)

I think its become a lot more tangible now.

excellent :)

agreed, aCiD2.

anything blocking you this week?

nope, I have more time this week now that a course finished, 6 more me-hours this week :)

ruaok has changed the topic to: agenda: review, release editor unit testing, summit, moose

:)

nice.

warp: any progress on the style guidelines?

ruaok: I just transferred my proposal to the musicbrainz wiki, and fixed a few issues nikki reported earlier which I forgot.

hi

ruaok: I'll post a link to mb-style after the meeting.

ruaok has changed the topic to: agenda: review, release editor unit testing, summit, mediawiki captcha, colorful ponies

warp: excellent.

anything that you need help with?

not right now, in the future i need some graphic designers/interaction designers to think about how we can make the guidelines themselves more accessible

I've already prodded pronik` about that, and he had some nice ideas which were completely outside the box I was thinking in, so that's good

warp: I can probably rile up some support for that.

right now.

I was about to say that.

I think we should have a clear goal of what we're asking for when we look for help.

now that aCiD2 has managed to design a release editor what doesn't require any new icons, I feel like I have some egg on my face wrt to the BBC designer.

That reminds me, we still have an icon designer I may need to contact soon :)

I have a clear goal, but to reach it we have to focus on the content first ;)

not quite, it does need some

(thats not to say aCiD2 is doing a bad job! au contraire!)

hehe

warp: agreed. let me know when the time comes. or when you have a timeframe for when that will come.

will do.

ijabz_: how are things in NGS search land?

are any of the v2 schema bits blocking you

?

Ive done all the entities to a reasonable degree, though wierd bug with work stopping it working which I havent figured out yet

maybe put up a review for murdos to take a peek?

So I was going to paste the output Im getting tot the wiki or somewhere for comment

that works.

so with all the entities done, those are v2 entities, right?

have you done any v1 work?

how about the json for the web?

Yes thats all finsihed

very good.

(v1)

No json yet, it seems to be just the same as the xml without the brackets

and json should be pretty trivial. can you put a different serializer in front of the v2 data generator?

once the json stuff is there I'll hammer out the web portions on the mb_server side.

but I think I should wait for your webservice work to progress further, I posted a code review of it

I saw that, thanks. I'll be going through that review later today.

anything blocking you this week?

I have some non-mb stuff for the next few days, there was one other comment on the mmdschema I added

I'll look at that comment when I have a decent sized screen in front of me.

editing the schema on a laptop is a pita.

ok, thanks ijabz_ -- I'm really happy with your work on the search server.

I've actually spent a bit of time talking about our search stuff at the mentor summit.

in the end MB data was used as the example in the search session that we had.

ok, my turn.

last week, I hacked on the schema some more and I finished up the first cut of the artist resource for the v2 WS.

its up for review and I got good feedback that should let me continue to crank on it. I'm pleased on that front.

I also went to the digital hollywood conference in santa monica (LA) last week.

heh

but I got some nice contacts, chatted with some good people and we're getting a medium powered server.

I'm going to pick that up on the way home. that will gives us a good replacement machine for one of our machines thats been a little less than trustworthy.

sorry, back now

so, there will be more hosting stuffs in my week.

hi pronik

loads to do. :)

djce: here now?

aCiD2: take it away with release editor unit testing!

ok!

so at the moment, we have unit tests like this - http://gist.github.com/218993

agenda: release editor unit testing, summit, mediawiki captcha, psychadeledic ponies

This tests that if the user submitted those fields, we get the right edit in, which is great. But obivously, most people aren't going to be editing with Curl :)

So we need a way to test the javascript, and I'm really not experienced here, other than knowing about selenium (but never usedit)

I wondered if anyone here had any advice?

I guess the sort of tests we're looking for are going to be "If the user clicks this, then this new row should be added with these form fields" which is sort of mix between unit and functional testing

I know there are other options than selenium.