#musicbrainz-devel

ruaok: I mostly spent my week on small stuff while waiting for more release editor feedback.

arhg. its the edit side of the AR mess.

aCiD2`: might be good to ask murdos / luks on that. they wrote the migration script.

aCiD2`: I'd probably vote for readonly again.

I think it might be safest to go all historic here. sadly, we won't benefit then from being able to search edit_artist for artist related ARs, but given the time, it's the most likely to work

+1

preserves history the best.

warp: right, it's just a lot of people have been begging for us to fix this :)

warp: lets cover bits about the RE in a little bit.

ruaok: I've helped aCiD2` with a few of these readonly edits, sadly one duplicate.

bummer.

warp: have you looked at the widgets and proposal tracker proposals for SoC?

ruaok: yes, I had a look on friday, gave leftmost some feedback on irc and wanted to give xiainx some feedback too. but some other stuff came up and I never got around to poking xiainx on irc.

ok.

ruaok: I'll add my comments to the proposals after this meeting.

I generally feel that the applications are pretty light on details so far.

definitely.

warp: thanks. I'd like to get the students feedback on what is lacking.

I guess my template is partly to blame because I didn't ask *specific* questions about the proposals themselves.

although the proposals application is just hard, because we're fuzzy on what exactly we're looking for (we don't really know :).. and it's something which should be created to fit the workflows of the StyleCouncil.

I think I need to save the proposal template on the wiki for next year.

agreed.

anything else warp?

hm, no, nothing else noteworthy.

is there any documentation about the style council that you would recommend reading?

as for my week... we had the board meeting. I did a load of finances and quite a few business related calls.

xiainx: if you have some time after this meeting I can explain the process and our issues with it a bit better.

and I spent a ton of time dealing with SoC. proposals, chasing students, reading messages, that type of stuff.

more on some of that when we get tot he UX stuff.

anyone else for updates? ijabz, murdos, navap, nikki?

pronik, bueller, brianfreud?

oh, I did forget to mention something. I took some earlier to get back into style issues. I'll be posting a Post NGS artist page at some point this week.

s/some/some time/

excellent. looking forward to it.

Not really, I lost my virtualbox image so I've been staying away from VB for the time being and just working on documentation.

navap: bummer. :(

fixed two minor bugs

:o have you lost any work?

I lost my work on the menu branch because I hadn't pushed that, but all my edit stuff is on github (phew!)

sounds like you need a dev box, navap.

s/menu/home page/

how did the VB die?

I've got screenshots I can work off of to recreate the home page though, so not a big deal.

ruaok: No idea, VB had an error when I started, I checked the FAQs and it said to reinstall and that reinstalling doesn't touch your existing machines, I reinstalled and everything was gone.

oh bugger. :(

blame it on oracle ;)

damn open soruce software.

ok, moving on to SoC stuffs.

Yeah, but I'm really loving how github has (mostly) everything :)

xiainx, jensl, carols: any comments questions about SoC?

not really

nope. :-)

i work on the UI mock up, you did not leave any further questionts so i think everything else is clear?!?

i sent my instructions to the mentors list :-)

jensl: my comment was about the use about the non-native UI.

disobey it and i will have comments.

:-)

ok

jensl: I still have to think about how I feel about that.

no problem

students, keep your eyes peeled on proposals soon though :) I've finally had time to go through them, and just have to work my notes into a format to give you

I generally hate being at the mercy of some other toolkit. if that toolkit goes away we can't update our app anymore.

could I get feedback on what still needs more detail in my proposal at some stage

but I like the possibility of having an iphone app come out of this too.

ruaok: what's the license on the toolkit?

warp: I haven't looked.

i think it is gpl

jdamcd: I can give you some more feedback in a minute. I think your app needed the lest amount of more detail.

if it's GPL compatible open source, then it's not _too_ bad to rely on it.

warp: agreed.

the other concern I have it that we'd be delivering two mediocre apps, instead on one good one.

it is MIT

ruaok: agreed :)

warp & aCiD2`: I'd love to get your feedback on the use of these two toolkits.

ruaok: I'll have to take a better look

jensl is willing to go java native if we prefer it.

ok, thanks.

any other questions about SoC?

I'm pretty anti generated code stuff for the reasons that were mentioned, but I'll have a look too, time permitting

which toolkit are we talking about exactly?

concerning phonegap, there are 3 possibilities, 1) using phonegap to port the mobile optimized pages / web app native to different plattforms, 2) build hybrid application with mobile optimized pages using native web UI component + additional functionality for barcode scanning, 3) complete native application

phonegap and jqtouch for UI

warp: phonegap and jqtouch

jensl: ok, thanks. I'll have a look.

but jqtouch is optional

aCiD2`: thanks.

ok, onward to UX stuffs.

ruaok has changed the topic to: agenda: UX stuffs, replication

so, RagingAmazon is not going to apply for SoC since we all feel that she does not code enough to really qualify for SoC.

but, in exchange for recommendation letters, credit and dinner she will help us anyway. :)

so on wednesday her and I will spend the day working on taking the release editor to task.

warp: I think you and I should spend some time today/tomorrow talking about exactly what still needs to be addressed for the Re.

ruaok: ok, tomorrow would be better. I'd like to give xiainx feedback after the meeting, and then sleep.

maybe we should have another release editor meeting tomorow?

warp: sounds good.

how about in 23.5 hours from now?

ruaok: yes, ok with me.

aCiD2`, navap, nikki: can any of you make that?

ugh 23.5 hours lol that always confuses me. But yeah, I think I can make that :)

I'd love more eyes to pick apart the issues in the RE.

I think so!

navap: 3pm your time. :)

:)

ok, its officially on the schedule. I will invite RagingAmazon as well.

yay

warp: replication. go!

I want to continue on the sorting issues (MBS-136), for that I could really use some data nikki entered on test.musicbrainz.org

did it disappear again?

ruaok: can I get test replicated to here? is that running?

nikki: no, some good test data under morning musume still :)

not right now.

and in order to re-start it I would need to reload the data on test.

aCiD2`: all the pending schema changes are in now, right?

ruaok: urgh, so the test data will actually be destroyed in the process of trying to get it to me? meh!

warp: sadly, so.

afaik

ruaok: no, work aliases are still missing

murdos: we can do that without a new upgrade though

murdos: what needs to be done there?

just a work_alias table, right?

yes

ruaok: in that case perhaps it would be easier to just make a backup of of the current db and load it here.

aCiD2`: adding or modifying a table requires the replication to be changed.

ah..

warp: ok, i can do that.

murdos: are you working on this last change?

the work_alias is nearly done, I just missed the unit tests

ok, great.

I'll restart the replication once the work_alias patch has been accepted.

murdos, sounds like I need to add this to search index ?

and in the meantime I will dump the DB on test make it avaiulable to your warp.

ijabz: yes

ruaok: great!

ok.

anything else for today's meeting?

murdos could you raise an issue for me , with details ?

ijabz: ok

ruaok: can we talk about commit notifications?

murdos: go!

warp has changed the topic to: agenda: commit notifications

ruaok has changed the topic to: leftover rabble