#musicbrainz-devel

luks, maybe you can help.

for a chained controller, the return value of the root controller gets stashed into the stash.

right?

ruaok: what does 'keeping them around' mean? :)

if so, what key name is it stashed in?

uh, I don't know

luks: cluttering up the propsal space with dead stuff.

but I don't believe so

ruaok: that's the point, there is no proposal space

regarding catalyst, I think only stuff you stash manually gets stashes

It means we reduce the clutter in the wiki by deleting lots of confusing and poorly written documentation pages.

luks: Thanks for the label/catalog clarifcation

ruaok: ding :)

It's just setting them as official dead+abandoned, closing any relevant tix requesting them, etc. Anyone can of course propose it newly in future, but this 'officially' closes out any 'stalled and wtf-is-the-status' proposals

ruaok: I don't know the answer to your chained _load question.

does anyone know what is happening with musicbrainz-sharp

hi

i think i'm going to be late to work

may not make it to the meeting until ~20 past

alastairp: hurrryryyy!

alastairp: we can do it next week...

aCiD2: http://git.musicbrainz.org/gitweb/?p=musicbrain...

on the load function, where does the return value go?

ruaok: don't want to have to put it off /again/ ;(

ok.

_load is not a Catalyst action, it's a regular function

for Tag it goes to $c->stash->{tag}

luks: thanks! thats the info I was looking for.

luks beat me too it :)

Hi everyone :)

hey philip6137 :)

Leftmost: you around too?

I think that's all our gsoc potentials

Around enough.

Wow 17 nicks in here, that's probably a record.

aCiD2: I have trouble merging my changes into next, is that normal? (they're branched off master ofcourse).

warp: normalish, but it hasn't happened to me yet :)

i guess some of my potential work is conflicting with you

so now I just do git format-patch master; git checkout next; git am 0*patch

huh?

aCiD2: well, I get conflicts on stuff which I'm not changing.

which means that something that got into master is conflicting, which is weirder

but why the format-patch stuff?

aCiD2: "it works", no other reason.

it just seems a long way round rather than just "merge" *fix conflicts* then "commit"

aCiD2: but with git format-patch + git am I don't have to do anything, the conflicts don't show up.

i'm here

nothing in my change is conflicting, it's the history which merge brings in with it. or something. I don't fully understand it :)

<BANG>

MBChatLogger has changed the topic to: http://musicbrainz.org/#devel

warp: right, that's what I mean about something in master

Welcome everyone!

i'll have a look soon :)

ruaok has changed the topic to: agenda: gsoc, review, schedule, agile, [what else?]

hi murdos!

right-o.

hi ruaok! hi all!

Hey

I'm seeing an awful lot of propsective gsoc'cers in here, so lets put that on the agenda and start there.

dear gsoc potential students: do you have any questions?

comments?

I have two quick requests which I'll just add to the topic.

warp has changed the topic to: agenda: gsoc, review, schedule, agile, makefile, pg sorting [what else?]

i have no questions :) easy right?

good. :-)

oh, release editor / artist credits..

I think for the time being, expectations are pretty clear.

philip6137, Leftmost jensl?

yes?

warp has changed the topic to: agenda: gsoc, review, schedule, agile, release editor, makefile, pg sorting [what else?]

muaha

do you have any qeustions regarding gsoc?

quick one maybe:

I dont really have question :)

the while team is assembled ready to answer questions. :)

yes one

dzan first, jensl next.

2 people on mailinglist for android, me for android and philip6137 too, 4 total? or even more?

do your prefer to have a first official proposal quite early on google

so that you might get the chance to ask questions again

I am here too, sent to mailing list about the Android proposal

or just final one...

dzan: I would expect more. its seems to be a popular suggestion.

jensl: yes, the earlier the better.

jensl: early is always better IMO.

that way we can give you feedback.

ok

do you have proposals for the other ideas ?

actually i discuss almost everything on the mailing list

in general, those people who work with the community and adapt their proposals based on community feedback have better chances at being accepted.

philip6137: see our ideas page.

we're also very much open to you bringing your own idea in.

and its ok to submit more than one proposal.

i gonna concentrate on the android proposal and won't submit any others

last call for gsco questions.

i could also do iphone but from your replies i result that you prefer android

navap: yes but no

navap: yes.

you'd do it like me and luks did

separate proposals, but heavily orientated around working together

jensl: one think I am considering... if we don't get a third student interested in another topic, I would consider having one for android and one for iphone.

So focus on two separate specific proposals, but work together to achieve both?

but I am guessing that is unlikely.

navap: we can pretty much do anything we want.

include tell the students that we like what to put in their proposals.

"gee, this guys says exactly what I am looking for. s/he's perfect!"

ruaok: ok, will mention that i can do the stuff also on the iphone

and that is perfectly legit. google makes very few rules about what we can't do.

jensl: ok.

ok, onward. review from last week.

warp: go!

you've got 3 slots?

oh sorry :)

dzan: we've requested 3.

np

as you may have noticed, I spent almost the entire week on the release editor.

yay

Pour NGS?

ruaok has changed the topic to: genda: review, schedule, agile, release editor, makefile, pg sorting [what else?]

I tried to fit it in better with the existing js code, which made it much more modular... and better testable.

warp: go something for us to look at?

ruaok: it's not merged into next, but available from git.musicbrainz.org. I submitted it to codereview in three parts.

so yes, please all have a look.

ok, I should be able to get to some reviews later today.

I can't wait to see in action. :)

on the review note.. I've got some that are almost a month old - could those please get looked at?:)

aCiD2: gimme a list of what needs the most attention.

aCiD2: I looked at everything in code review, but often I just don't have enough of a clue what's going on yet to say something sensible about it.

ruaok: none need attention, but it'd be nice just to clear it up

they aren't blocking me

ok, I'll go by age then.

anything else warp?

ruaok: nothing which I didn't stick in the agenda seperately :)

:-)