Dev chat reminder

[Robert Kaye]

Remember that we've got our weekly dev chat on Monday June 29 in IRC
in  #musicbrainz-devel on irc.freenode.net . We're going to meet for
about 1 hour at 8pm UK, 9pm mainland  europe, THREE pm EST, NOON PST.

We'll probably have another fairly short meeting as we're still very  
much heads down for NGS.

--

--ruaok      "Vague, but exciting..." -- Mike Sendall on the WWW  
proposal.

Robert Kaye     --     rob@...     --    http://mayhem-chaos.net






_______________________________________________
MusicBrainz-devel mailing list
MusicBrainz-devel@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel

[Kuno Woudt-2]

Hello,

On Sun, Jun 28, 2009 at 11:14:04PM -0700, Robert Kaye wrote:
> Remember that we've got our weekly dev chat on Monday June 29 in IRC
> in  #musicbrainz-devel on irc.freenode.net . We're going to meet for
> about 1 hour at 8pm UK, 9pm mainland  europe, THREE pm EST, NOON PST.
>
> We'll probably have another fairly short meeting as we're still very  
> much heads down for NGS.

Apart from NGS development and a few lines about bugs in the current
server release we also discussed Nabble / mb-users a bit.  Log
reproduced below:

21:00 <@ruaok> <BANG>
21:00 <@ruaok> welcome to the meeting everyone!
21:00 <@ruaok> aCerCer: ping!
21:00 <@ruaok> aCiD2: lead off with the review for last week, please!
21:00 < aCiD2> Sure thing :)
21:01 < aCiD2> I got all of the edit types for the milestone written in the first part of the week - to recap this is create/update/delete/merge for artists and labels, and update/delete/merge for release groups
21:01 < aCiD2> I spent the rest of the week writing forms to enter these edits too, and we have forms for create/update/delete artist and label
21:01 < aCiD2> With the merge forms coming later
21:01 < aCiD2> Which brings us to one problem you guys can hopefully give me some feedback with now :)
21:02 < aCiD2> The release groups use artist credits, and I don't know how to allow users to enter an artist credit
21:02 <@ruaok> ah, so the editing is done for simple artists now?
21:02 < aCiD2> I think so yea
21:03 <@ruaok> I think we should discuss this after the meeting.
21:03 < aCiD2> ok :)
21:03 <@ruaok> I think this isn't a short topic.
21:03 < aCiD2> And just to clarify: http://wiki.musicbrainz.org/Next_Generation_Schema/Roadmap :)
21:03 <@ruaok> I've been following that -- thanks for keeping it up to date.
21:03 <@ruaok> what about "DB schema + Perl code for ratings" ?
21:03 <@ruaok> is that code about?
21:03 < aCiD2> No, there is code about for tags, but not ratings
21:04 <@ruaok> I'd like to finish all items from both milestones this time. :)
21:04 <@ruaok> is it much work?
21:04 < aCiD2> I haven't even had time to go back to the tags this week, so I couldn't do that
21:04 < aCiD2> Not a huge amount, I don't think
21:04 <@ruaok> ok, before we go on to post milestone 2 items, please finish that one off.
21:04 < aCiD2> It's just read access to ratings, right?
21:04 < luks> I'll do that
21:05 <@ruaok> ok, kewl.
21:05 <@ruaok> how was your week luks?
21:05 < luks> I still haven't done much work
21:05 < luks> mostly reviewing patches
21:05 <@ruaok> that helps a lot tho.
21:05 < luks> I've added caching, some UI changes on the artist pages
21:05 < luks> -s
21:05 < luks> but nothing else
21:05 < aCiD2> And relationships, thanks for getting that
21:06 < luks> oh, and that
21:06 <@ruaok> you available for talking about artists credits after this?
21:06 <@ruaok> yes, thanks for that.
21:06 <@ruaok> having a UI will make my work easier.
21:06 < luks> aCiD2: btw, the tags patch is actually still waiting for you - apply_tags can't be committed as it is
21:06 < luks> aCiD2: but I can finish the patch
21:06 < aCiD2> I know, I was planning to finish it
21:06 < aCiD2> If you want to take it over, feel free
21:07 < luks> I can it along with the ratings one
21:07 <@ruaok> as for me, I did some bug fixes on the old release and worked on AR stuffs.
21:07 < aCiD2> I just haven't had time to go back and work on it, with all the work on edit types and forms this week
21:07 <@ruaok> so far the AR stuffs have been to get familiar with the new structure.
21:07 <@ruaok> not so much doing actual work.  that comes this week I hope.
21:08 <@ruaok> but sadly, I have more old bugs that need to be fixed.
21:08 < aCiD2> hopefully not too confusing, is it? :)
21:08 <@ruaok> its more complex, thats for sure.
21:08 <@ruaok> one sec
21:08 <@ruaok> yum. pizza arrived.
21:08 < aCiD2> :)
21:09 < aCiD2> once you get the whole system in your head, it's quite clear - i'm always around for qs
21:09 <@ruaok> luks: you have 3 important bugs left on the mason codebase.
21:09 <@ruaok> any chance you could work on those post the milestone?
21:09 < luks> hm, three?
21:10 <@ruaok> 5150, 5175 and 5188
21:10 <@ruaok> warp did a head check for me on which bugs that are open should be fixed.
21:10 <@ruaok> and the answer was pretty much all of them. :-(
21:11 <@ruaok> tho none of the bugs are too big, methinks.
21:11 < luks> 5188 is really an easy one
21:11 < luks> but I'll try
21:11 <@ruaok> thanks.
21:11 <@ruaok> I'l do an update of the server later today with the bugs fixed last week.
21:12 < luks> it means a new step in the release editor workflow
21:12 -!- ruaok changed the topic of #musicbrainz-devel to: agenda: NGS milestone, NGS bug tracking, nabble, ponies
21:12 <@ruaok> which bug?
21:12 < luks> 5188
21:12 <@ruaok> ok.
21:13 <@ruaok> aCiD2: the tasks left on http://wiki.musicbrainz.org/Next_Generation_Schema/Roadmap
21:13 < warp> ruaok: probably adds up though :/  
21:13 <@ruaok> any chance to get some more done before the day is out?
21:13 <@ruaok> or at least get them into review?
21:13 < aCiD2> Yes, I'd like to get everything but edit release group into review
21:13 <@ruaok> sweet.
21:14 <@ruaok> that only puts us marginally behind schedule.
21:14 < aCiD2> I don't think I can realistically get edi release group in because of how complex artist credits could be to enter
21:14 < aCiD2> That's going to take more than a few hours :(
21:14 < aCiD2> My bad leaving that til the end, should have tackled it first
21:14 <@ruaok> and given how few person-hours we've had, I'm stoked.
21:14 <@ruaok> aCiD2: we'll deal.
21:14 <@ruaok> ok, take away NGS bug tracking
21:14 < pronik> aCiD2: it's ruaok's day's end, a couple of hours more away ;)
21:15 < aCiD2> :D
21:15 <@ruaok> heh.
21:15 < aCiD2> right, basically as I was working all over the place this week, I noticed some things where I thought "hmm, that's not doing quite what it should" - so I'm wondering how to best track these issues
21:15  * ruaok isn't a slave driver
21:15 < aCiD2> now that we use unit tests, I'd like to make use of TODO: {} blocks in the test, which is for tests which should intentionally fail
21:15 < aCiD2> But where do we put them? We can either have a todo.t file that is updated with known problems, or we have bugs in the tracker, with the failing unit tests attached
21:16  * ruaok wonders if luks has thoughts on this.
21:16 <@ruaok> somehow this seems a little cumbersome to issue tracking.
21:16 < aCiD2> and a bit too programmery for the tracker too
21:17 <@ruaok> what about a wiki page?
21:17 < luks> why not put them when they would normally belong?
21:17 < luks> *where
21:17 < aCiD2> luks: like t/data_artist.t
21:17 < luks> yes
21:17 < aCiD2> I can do that, my main concern was making sure they didn't get lost
21:17 < luks> I don't think searching for TODO blocks is such a problem
21:17 < aCiD2> but Test::Harness does mention "Skipped x tests for TODO" so we'll probably not lose them
21:18 < aCiD2> I think they should probably be in the code, so we'll know if we "accidently" fix them
21:18 <@ruaok> code proper or test cases?
21:18 < aCiD2> test cases
21:18 < luks> if they are in TODO, and you accidentaly fix it, the test suite will "fail"
21:18 < aCiD2> I'll put them in the respective test modules, that's fine
21:19 < aCiD2> yea, I know
21:19 < aCiD2> we wouldn't get that if they were in a wiki
21:19 <@ruaok> yep.
21:19 < aCiD2> ok, in the tests they go :)
21:19 <@ruaok> ok.
21:19 < luks> what kind of problems are talking about, btw?
21:19 < luks> little bugs, or design issues?
21:19 < aCiD2> like edit artist not excepting undef to clear fields
21:19 < luks> aha
21:20 < aCiD2> and annotations should combine on merge, etc
21:20 < aCiD2> those sorts of issue
21:20 <@ruaok> anything else on NGS that we should discuss?
21:20 < aCiD2> Yea, where we go after today :)
21:21 <@ruaok> you mean after artist credits?
21:21 <@ruaok> :-)
21:21 < aCiD2> yup
21:21 < aCiD2> after the milestone
21:21 <@ruaok> more edits.
21:21 < aCiD2> the roadmap is a bit vague
21:21 <@ruaok> ok, lets work on that once we get some of these other issues cleaned up.
21:22 < luks> that's because now the UI design pain will come :)
21:22 <@ruaok> sadly, yes.
21:22 <@ruaok> artist credits are the first portion of that.
21:22 <@ruaok> lets leave this for now and return to artist credits last or after the meeting proper.
21:22 <@ruaok> pronik: lets talk about nabble.
21:22 < pronik> nabble, ok :)
21:23 < pronik> v1 has lot its skin, as it turns out
21:23 -!- ruaok changed the topic of #musicbrainz-devel to: agenda: nabble, artist credits, ponies
21:23 < pronik> v2 is set up, but has no mb css yet
21:23 < pronik> ruaok should have embedding code
21:23 < pronik> luks proposed killing the mb-users mailing list and thus move all user support to forums
21:24 < pronik> I tend to agree on that one
21:24 < aCiD2> i think I do too
21:24 <@ruaok> I do have the embedding code. but it should be renamed.
21:24 < pronik> I further propose we use nabble v2 archives and embed them into main site
21:24 <@ruaok> anyone against that?
21:24 < pronik> renamed?
21:24 <@ruaok> yes, cause now its named "Forums"
21:25 <@ruaok> we just need to call it something else.
21:25 <@ruaok> so, go ahead and finish the v2 skin.
21:25 < pronik> it's renamed on nabble's side already
21:25  * warp suggests "Mailing lists"
21:25 < warp> :P
21:25 < pronik> there is only one link to change in the embedding code
21:25 <@ruaok> then I will finish the embedding and push it live.
21:25 <@ruaok> warp: yes, of couse. :)
21:25 < pronik> is there anyone who wants to do some css?
21:25 <@ruaok> and once its live and we're happy with it we can kill the users list?
21:25 <@ruaok> navap: you around?
21:26 <@ruaok> navap is the resident CSS wonk around here. :)
21:26 <@ruaok> see if you can catch him.
21:26 < pronik> as usual :)
21:26 < pronik> we can start with current color scheme and adapt it
21:26 <@ruaok> ok, unless someone wants to talk about ponies, the official meeting is nearly over. anyone have any other topics?
21:27 < warp> not entirely sure about killing mb-users.
21:27 < warp> it had between 10 and 20 posts in recent months, but e.g. april 2009 has 116 posts on mb-users.
21:27 <@ruaok> warp: something seems wrong about that, but I can't articulate that thought.
21:27 < pronik> wrong about killing mb-users?
21:27 <@ruaok> yea
21:27 < aCiD2> Why not take it to mb-users itself?
21:28 < aCiD2> Need to ask the people who actually use it what they think I guess
21:28 < pronik> ah, a volunteer :)
21:28 < aCiD2> haha
21:28 <@ruaok> heh. lets leave aCiD2 to coding please.
21:28 <@ruaok> but I do like that idea. can you please ask pronik ?
21:28 < pronik> ok
21:28 <@ruaok> thx
21:28  * pronik does M-x gnus :)
21:28 <@ruaok> anything else?
21:29 <@ruaok> ok, then lets close this meeting. following immediately afterwards is the artist credit discussion in the main channel.
21:29 < navap> pronik: Sorry about the Nabble theme, I did play around with it but got to a point and then didn't know what to do.
21:29 <@ruaok> sounds like some coordination would help that.
21:30 <@ruaok> oh, here is another thought.
21:30 <@ruaok> pronik: the upcoming edit types will need a lot of thought.
21:30 < navap> All I really ended up doing was changing a handful of colours to the traditional orange and purple.
21:30 <@ruaok> like the artist credit UI.
21:30 <@ruaok> could we enlist your help with balsamiq?
21:31 < pronik> navap: that'd be enough I guess
21:31 < pronik> ruaok: yes of course
21:31 <@ruaok> pronik: sweet.
21:31 <@ruaok> please participate in the next meeting then.
21:31 <@ruaok> should we hold a pre-meeting planning meeting?
21:31  * ruaok slaps himself.
21:31 <@ruaok> <BANG>
21:31 < pronik> I've only missed one so far
21:31 <@ruaok> meeting adjourned. :)
21:31 <@ruaok> warp: please do the honors. :)
21:32 < warp> ruaok: will do
21:32 <@ruaok> thx warp and thanks everyone for your time.
21:32 < warp> happy hacking everyone :)

-- kuno / warp.


_______________________________________________
MusicBrainz-devel mailing list
MusicBrainz-devel@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel