07:30:20 <dobedobedoh> #startmeeting
07:30:20 <maharameet> Meeting started Wed Jan 19 07:30:20 2011 UTC.  The chair is dobedobedoh. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:30:20 <maharameet> Useful Commands: #action #agreed #help #info #idea #link #topic.
07:30:22 <dobedobedoh> #chair anitsirk
07:30:22 <maharameet> Current chairs: anitsirk dobedobedoh
07:30:37 <anitsirk> hello all
07:30:39 <anitsirk> http://wiki.mahara.org/Developer_Area/Developer_Meetings/January_19_2011 agenda for mahara developer meeting 3
07:30:49 <rkabalin> Good morning all
07:30:50 <anitsirk> * Items from previous meeting
07:30:56 <anitsirk> * Basic tests (fmarier) make minaccept and make push
07:31:03 <anitsirk> * Status / Priority / Milestone in Launchpad and how we use them (fmarier)
07:31:10 <anitsirk> * Graphs in Mahara Statistics proposal (anzeljg) see mockups, pChart could be used for drawing graphs
07:31:16 <anitsirk> * Next meeting
07:31:23 <anitsirk> * Any other business
07:31:29 <anitsirk> #topic attendees at this meeting
07:31:36 <anitsirk> please let us know your nick / name to show that you are attending this meeting.
07:31:53 <dobedobedoh> dobedobedoh -- Andrew Nicols @ LUNS Limited in the UK
07:31:54 <anitsirk> obviously i'm here. ;-)
07:32:09 <anitsirk> anitsirk: Kristina Hoeppner from Catalyst IT in Wellington, NZ
07:32:13 <rkabalin> rkabalin - Ruslan Kabalin @ LUNS Ltd.
07:32:20 <fmarier> fmarier -> Francois
07:32:29 <richardm> richardm: Richard M
07:32:38 <anitsirk> fmarier: you'll be the star of today's meeting
07:32:55 <anitsirk> anzeljg: are you already here?
07:33:32 <anitsirk> ok. pretty quiet. doesn't seem like others here yet. let's get started then
07:33:33 <anitsirk> #topic Items from previous meeting
07:33:41 <anitsirk> #info richardm to appoint lamiette and dobedobedoh as forum mods in Community forum -> done
07:33:49 <anitsirk> #info dobedobedoh will add minutes to wiki and create pages for next meeting -> done
07:33:56 <anitsirk> #info dobedobedoh and azeljg to go over skins patches to try and get them into 1.4
07:34:13 <anitsirk> dobedobedoh: did you work on that?
07:34:16 <dobedobedoh> I've not had a chance to go over the patches with anzeljg though he has sent htem my way
07:34:42 <anitsirk> do you want to discuss anything or shall we move on to your next item from last week?
07:34:44 <dobedobedoh> Unfortunately, I've only had a few minutes to look at them so far. I'm hoping that I may have a bit more time after this weekend
07:34:45 <richardm> No, neither have i yet
07:35:05 <dobedobedoh> Don't think there's anything I can add right now, probably best move on...
07:35:14 <anitsirk> #info dobedobedoh to beg/borrow/steal/invent a forum code of conduct and place on the wiki
07:35:25 <dobedobedoh> I've started on the forum code of conduct, but again haven't had a chance to get anywhere real with it
07:35:46 <fmarier> dobedobedoh: were you planning on basing it on the Ubuntu code of conduct?
07:35:55 <fmarier> (which is CC licensed)
07:36:02 <dobedobedoh> Ahh.. That would make life easier
07:36:16 <dobedobedoh> I was looking at the Moodle CoC which hasn't got a license AFAIK
07:36:31 <fmarier> http://www.ubuntu.com/community/conduct
07:36:46 <fmarier> ah, i didn't know Moodle had one :)
07:36:47 <dobedobedoh> Thanks
07:36:58 * fmarier hopes he hasn't violated it in the past
07:37:37 <anitsirk> do you need additional info, dobedobedoh, or continue checking / re-writing?
07:37:37 <dobedobedoh> I'll try and get that finished in the next two weeks and pass it on for a sanity check
07:37:46 <dobedobedoh> Not at present, just more time!
07:37:51 <anitsirk> #action dobedobedoh to check the ubuntu code of conduct which is CC licensed for the mahara code of conduct
07:37:59 * fmarier hands dobedobedoh a bit more time
07:38:11 <dobedobedoh> ;)
07:38:12 <dan_p> Lo
07:38:21 <anitsirk> had forgotten to note down previous action item.
07:38:21 <anitsirk> #action dobedobedoh and azeljg to go over skins patches to try and get them into 1.4
07:38:40 <anitsirk> hi dan_p
07:38:51 <dobedobedoh> There are also still some actions left over from the first meeting
07:39:08 <dobedobedoh> #info Mjollnir` to merge phpunit branch into master
07:39:22 * dan_p In moving vehicle
07:40:10 <anitsirk> dobedobedoh: Mjollnir` isn't here. has anybody heard from her?
07:40:22 <fmarier> anitsirk: she's on holiday at the moment
07:41:07 <anitsirk> ah. that's right
07:41:11 <anitsirk> #info iarenaza to draft language pack release policy
07:41:14 <dobedobedoh> #action Mjollnir` to merge phpunit branch into master
07:41:30 <fmarier> what was that langpack policy for?
07:42:28 * dobedobedoh reads the logs
07:42:41 <dobedobedoh> Things like telling translators not to publicised non-blessed sites
07:43:38 <dobedobedoh> Anyone heard from iarenaza?
07:43:47 <anitsirk> nope
07:43:57 <anitsirk> maybe he's also on vacation
07:44:09 * dobedobedoh wishes he was
07:44:45 <anitsirk> #action iarenaza to draft language pack release policy
07:44:49 <anitsirk> shall we continue?
07:45:17 <fmarier> sure
07:45:20 <dobedobedoh> yup
07:45:21 <anitsirk> #topic Basic tests (fmarier) make minaccept and make push
07:45:28 <fmarier> right, that's a quick one
07:45:48 <fmarier> basically, it's just a reminder that we should all run the minimum acceptance tests before committing
07:45:54 <fmarier> so "make minaccept" runs them
07:46:02 <fmarier> and "make push" is a handy replacement for "git push"
07:46:11 <fmarier> which runs "make minaccept" prior to "git push"
07:46:21 <fmarier> (and doesn't push if it fails the tests)
07:46:42 <dan_p> That's cool
07:46:54 <fmarier> also, if you can think of any other quick tests that should be done prior to pushing, feel free to suggest additions to that script
07:47:12 <anitsirk> #info everybody to run minimum acceptance tests before commiting
07:47:13 <fmarier> i know that dobedobedoh (i think) has added something to check for Signed-Off-By headers
07:47:24 <fmarier> which is a great idea
07:47:49 <anitsirk> #info "make minaccept" runs them and "make push" is a handy replacement for "git push" which runs "make minaccept" prior to "git push" (and doesn't push if it fails the tests)
07:48:05 <fmarier> and that's all I had for that, unless anybody has anything to add
07:48:08 <dobedobedoh> Yup that's in there, but currently not as a requirement of the make push
07:48:27 <fmarier> dobedobedoh: is it not?
07:48:36 <dobedobedoh> ack - yes it is
07:48:36 <fmarier> push: minaccept checksignoff
07:48:37 <fmarier> git push
07:48:43 <dobedobedoh> didn't see it in the push line ;)
07:48:47 <fmarier> :)
07:49:09 <anitsirk> #info push: minaccept checksignoff checks for signed-off-by headers
07:49:10 <rkabalin> that is interesting, will definitely test it
07:49:44 <fmarier> i guess we can move to the next item then
07:50:00 <anitsirk> and here i thought i heard you typing something else, fmarier  ;-)
07:50:01 <anitsirk> #topic Status / Priority / Milestone in Launchpad and how we use them (fmarier)
07:50:32 <fmarier> right, here's how we are currently using the different fields in the launchpad tracker
07:51:13 <fmarier> status: is "new" initially when the bug is created
07:51:40 <fmarier> then once we look at it and decide on a priority and a milestone, we move it to "triaged"
07:51:55 <fmarier> triaged is for bugs which we have not even tried to reproduced yet
07:52:33 <fmarier> it gets moved to "confirmed" once we have been able to reproduce it
07:52:54 <fmarier> or to "invalid" if it's not actually broken or not a bug in Mahara
07:53:06 <fmarier> "in progress" is obvious
07:53:18 <fmarier> "fix committed" is for when a fix is committed to git
07:53:40 <fmarier> and it is flipped to "fix released" once there is a release (i.e. a tarball) which includes the fix
07:54:00 <fmarier> "incomplete" is for when we need more info to be able to reproduce the bug
07:54:31 <fmarier> the neat thing about "incomplete" bugs is that they auto-expire after x days (i think it's 30 or 60 days) if nobody adds anything
07:55:18 <anitsirk> #info current use of status / priority / milestone in launchpad: 1. status "new" -> bug is created; 2. once we look at it and decide on a priority and a milestone, we move it to "triaged"; triaged is for bugs which we have not even tried to reproduced yet; 3. it gets moved to "confirmed" once we have been able to reproduce it or to "invalid" if it's not actually broken or not a bug in Mahara; 4. "in progress" is obvious; 5. "fix
07:55:19 <anitsirk> committed" is for when a fix is committed to git; 6. and it is flipped to "fix released" once there is a release (i.e. a tarball) which includes the fix; 6. incomplete" is for when we need more info to be able to reproduce the bug
07:55:21 <fmarier> in terms of "importance", that's of course, highly subjective, but is often just a gut feeling about the relative importance of something versus the other bugs
07:55:35 <fmarier> if it's a regression, it's usually more important
07:55:49 <fmarier> than if it has always been broken and  has never worked
07:56:24 <fmarier> finally the milestone is what we use as a TODO list for what needs to happen before a release
07:56:49 <anitsirk> #info "importance" is highly subjective, but is often just a gut feeling about the relative importance of something versus the other bugs; if it's a regression, it's usually more important than if it has always been broken and  has never worked
07:56:54 <fmarier> and it also gives a neat overview of all of the bugfixes that went into a release
07:57:10 <fmarier> for example, we're looking at this page for the 1.4 release: https://launchpad.net/mahara/+milestone/1.4.0
07:57:21 <richardm> we should put all that on wiki.mahara.org
07:57:24 <anitsirk> #info milestone: a TODO list for what needs to happen before a release and it also gives a neat overview of all of the bugfixes that went into a release
07:57:33 <richardm> oops i just volunteered didn't i
07:57:50 <fmarier> richardm: agreed and yes you just did :)
07:57:52 <anitsirk> fmarier: should be easy to find in the logs because it's now tagged with "info"
07:58:21 <dobedobedoh> Should we select the next intended release as the Milestone, and then let the release manager decide whether that bug/feature should make it?
07:58:29 <anitsirk> #action richardm  to post on the wiki how we use status / priority / milestone in mahara
07:58:56 <fmarier> dobedobedoh: what we usually do is periodically go through the bug list and decide what we want to fix before 1.4
07:59:01 <dobedobedoh> Obviously, where a bug only affects master, that's moot, but some bug fixes may change the way something works quite a bit
07:59:16 <fmarier> but of course if you volunteer to fix something before a release, feel free to set the milestone accordingly
07:59:24 <dobedobedoh> Okay cool
07:59:35 <fmarier> we'll readjust as we get closer to the release date anyways
07:59:41 <fmarier> none of these things are promises
08:00:06 * rkabalin thinks about walled garden
08:00:22 <anitsirk> i think that such a change from the milestone that the release manager has set to one other developer would need a comment on the bug so that it's not changed again during the next periodical review of the bugs
08:00:25 <fmarier> dobedobedoh: well, if you fix a bug in master and you mark the bug as fix committed, you should set 1.4 as the milestone
08:00:37 <fmarier> because that's when it will first show up in a release
08:01:11 <anitsirk> #info example: if you fix a bug in master and you mark the bug as fix committed, you should set 1.4 as the milestone (because that's the next release)
08:01:36 <fmarier> does that make sense?
08:01:41 <dobedobedoh> okay. That clarifies things
08:02:02 <rkabalin> thanks fmarier, that is useful
08:02:05 <fmarier> that's pretty much our understanding so far of how to best use launchpad's fields
08:02:07 <dobedobedoh> thanks
08:02:13 <fmarier> but it has changed a few times :)
08:02:36 <fmarier> what i've described is what we've found useful while releasing 1.3
08:02:56 <fmarier> oh and I should probably mention the "opinion" status field
08:03:01 <fmarier> that's a fairly confusing one
08:03:13 <fmarier> but basically it's a softer version of "wontfix" or "invalid"
08:03:29 <fmarier> it means "wontfix" but it's said like "we agree to disagree about this"
08:04:00 <anitsirk> #info "opinion" status field in launchpad: it's a softer version of "wontfix" in the sense of "we agree to disagree about this" or "invalid"
08:04:18 <fmarier> http://blog.launchpad.net/bug-tracking/new-bugs-status-opinion
08:05:09 <dobedobedoh> Is the opinion field limited access in some way -- I don't see it
08:05:25 <fmarier> dobedobedoh: do you see wontfix and invalid?
08:05:40 <dobedobedoh> Under Status
08:05:49 <dobedobedoh> Ah - there it is
08:06:03 <dobedobedoh> Couldn't see it for the life of me
08:06:27 <fmarier> anyways, i'm not sure we've used it
08:06:46 <anitsirk> i think i saw it once or twice because the bugs had expired and a notification was sent
08:07:04 <rkabalin> I can see opinion
08:07:14 <rkabalin> on the new bug
08:07:32 <fmarier> another thing about the bug tracker is that i wanted to say kudos for putting tags on bugs :)
08:07:36 <rkabalin> works for me on this one https://bugs.launchpad.net/mahara/+bug/703980
08:08:10 <fmarier> actually, we have 3 bugs marked with Opinion: https://bugs.launchpad.net/mahara/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=OPINION&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_
08:08:11 <fmarier> branches=on&field.has_no_branches.used=&field.has_no_branches=on&search=Search
08:08:20 * anitsirk needs to remember to put tags on bugs
08:08:35 <fmarier> nicer url: http://ur1.ca/2xhiu
08:09:05 <fmarier> one of the tags on there is "bite-sized"
08:09:12 <dobedobedoh> Didn't quite get that one...
08:09:28 <rkabalin> I guess it means small
08:09:32 <fmarier> the idea is that if we get a good list of bite-sized ones, we could advertise Mahara on http://openhatch.org/ and (potentially) get new contributors
08:09:34 * dobedobedoh guesses so to
08:09:44 <anitsirk> http://ur1.ca/2xhiu - current bugs with "opinion" for mahara
08:09:44 <fmarier> yeah, bite-sized = very easy bug to fix
08:10:35 <rkabalin> so, the idea is that existing contributors should not touch it?
08:10:37 <fmarier> basically if you're new and you're looking to make a contribution to Mahara, or if you're at the end of the day and want to fix one last one, this could be a useful list
08:10:51 <fmarier> rkabalin: no, by all means if you want to fix bugs, go for it :)
08:11:27 <rkabalin> Then noting will be left for the newcomers ;)
08:11:28 <fmarier> but if you triage bugs for example and find a really easy one, then it's worth also tagging it
08:11:46 <fmarier> rkabalin: i doubt we'll fix all of the bugs anytime soon
08:11:52 <fmarier> but in any case, it would be a great problem to have !
08:11:55 <anitsirk> #info tag a bug with "bite-sized" to show that it may not take long to fix the bug and may bring in new contributors who want to start small
08:13:00 <anitsirk> #action everybody should try to tag bugs to group them together
08:13:16 <fmarier> anyways, that's all i had for this item
08:13:23 <rkabalin> do we need any tagging policy?
08:13:42 <rkabalin> say to have them groupped correctly
08:13:47 <anitsirk> i don't think how we could manage that and post it for people to remember to check that page
08:13:52 <fmarier> i'd say let's just see what happens
08:14:04 * anitsirk thinks so, too
08:14:25 <fmarier> and feel free to suggest anything you think is a good idea at the dev meeting
08:14:38 <dobedobedoh> me too, though it may be worth adding a note about tags to the how to file a bug info
08:14:41 <fmarier> or you can also just tag other people's bugs
08:15:03 <fmarier> i'm not sure we necessarily want users to tag bugs though
08:15:21 <fmarier> it increases the burden for them and they may not know what tags are appropriate
08:15:22 <anitsirk> dobedobedoh: do you mean there is a wiki page or do you refer to my forum post from last year?
08:15:49 <fmarier> whereas a developer has a better idea what area of the code a particular bug report is about
08:15:58 <dobedobedoh> Fair enough
08:16:41 <anitsirk> #info bug tagging is not communicated to general users because they may not know which ones are appropriate. at the moment only developers should worry about that and use that function
08:17:07 <anitsirk> shall we move on? there are still 3 items though maybe relatively short
08:17:30 <anitsirk> just an action item that i had forgotten to paste in earlier:
08:17:45 <anitsirk> #action everybody to run minimum acceptance tests before commiting: "make minaccept" runs them and "make push" is a handy replacement for "git push" which runs "make minaccept" prior to "git push" (and doesn't push if it fails the tests) and push: minaccept checksignoff checks for signed-off-by headers
08:18:00 <anitsirk> #topic Graphs in Mahara Statistics proposal (anzeljg)
08:18:07 <anitsirk> did anybody talk to him about that?
08:18:12 <dobedobedoh> anzeljg has just posted on the forum to ask about the meeting and he's on mahara.org now, so he may appear soon...
08:18:15 <anitsirk> http://mahara.org/view/view.php?id=5856 for mockups
08:18:22 <anitsirk> http://www.pchart.net/ pChart could be used for drawing graphs
08:18:37 <dobedobedoh> It makes some pretty graphs
08:18:50 <rkabalin> yes, that looks great
08:18:58 <fmarier> looks like the graphs are static images like the ones we are currently using
08:18:59 <fmarier> ?
08:19:06 <fmarier> but prettier of course
08:19:23 <anitsirk> they are balsamix mockups from nigel from way back then
08:19:31 <anitsirk> *balsamiq
08:19:51 <anitsirk> maybe he just suggests to use pChart to create them
08:19:55 <fmarier> anitsirk: no, not those ones, the ones on the other link
08:20:04 <fmarier> (pChart)
08:20:12 <dobedobedoh> I think the only real difference between the current graphs and pChart is the prettiness
08:21:16 <fmarier> if someone wants to port the existing graphs to it, that sounds good
08:21:36 <fmarier> was that the intention behind this agenda item?
08:21:48 <anitsirk> let's keep his agenda point for the next meeting because we are only guessing right now
08:22:04 <dobedobedoh> +1
08:22:06 <rkabalin> agree
08:22:16 <fmarier> cool, next item then?
08:22:17 <anitsirk> #topic Graphs in Mahara Statistics proposal (anzeljg)
08:22:28 <anitsirk> oopps. meant to be
08:22:32 <anitsirk> #action Graphs in Mahara Statistics proposal (anzeljg)
08:22:38 <anitsirk> #topic Next meeting
08:22:49 <anitsirk> any suggestions for the month of february?
08:23:00 <dobedobedoh> I assume we're switching times again, unlss anyone has any objections?
08:23:03 <anitsirk> keeping with the rotations, it seems like NZ is on again for the morning?
08:23:24 <dobedobedoh> I realise that the times we've picked are very biased towards Europe and New-Zealand
08:23:45 <fmarier> well, that seems to be where most developers are based :)
08:24:05 <dobedobedoh> A month from today would make it Tue 15th Feb GMT/Wed 16th Feb NZ
08:24:41 <anitsirk> US east coast is bad but west coast is 11:30 for 7:30 a.m.
08:24:49 <anitsirk> (GMT)
08:24:59 <dobedobedoh> rkabalin: Is that week bad for us do you think?
08:25:16 <fmarier> how about the week after?
08:25:23 <fmarier> 22 Feb / 23 Feb
08:25:38 <dobedobedoh> That's probably better for us to be honest
08:25:43 <rkabalin> dobedobedoh: that might be a busy one
08:25:53 <rkabalin> yep, 22/23 is fine
08:26:03 <anitsirk> that won't work for me (conference), but don't wait on it if everybody else can
08:26:18 <fmarier> anitsirk: when is the conference?
08:26:27 <fmarier> like would the 24th be any better?
08:26:35 <anitsirk> 23rd to 26 with setup on the 22nd
08:26:45 <anitsirk> but maybe i can make the 22nd in the morning
08:26:48 <anitsirk> don't know yet
08:26:52 <dobedobedoh> We can do tail end of the previous week
08:27:45 <anitsirk> that would be 18 feb?
08:27:49 <fmarier> 17 feb for them
08:27:49 <anitsirk> hi laurent_tdm ioniser1 and lamiette
08:27:53 <anitsirk> fmarier: yep
08:28:17 <dobedobedoh> rkabalin: You think that 17th Feb would be fine?
08:28:34 <rkabalin> dobedobedoh: I think so
08:28:46 <rkabalin> should be fine
08:29:01 <fmarier> so 17/18 then?
08:29:32 <dobedobedoh> 19:30 GMT/08:30 NZ? (time zones break my head)
08:29:34 <anitsirk> shall we say 7:30 pm GMT (8:30 a.m. on 18th for NZ) and in the afternoon for USA?
08:29:55 <dobedobedoh> Sounds good to me
08:30:01 <rkabalin> yep
08:30:13 <anitsirk> http://bit.ly/e29nNk date and time for next dev meeting
08:30:18 <anitsirk> all agreed?
08:30:22 <dobedobedoh> yup
08:30:46 <fmarier> yep
08:30:54 <ioniser1> I guess so
08:31:01 <rkabalin> yes
08:31:12 <anitsirk> #info next developer meeting on 17 February 2011 at 7:30 pm. GMT http://bit.ly/e29nNk
08:31:34 <anitsirk> irc://irc.freenode.org/#infoagree next developer meeting on 17 February 2011 at 7:30 pm. GMT http://bit.ly/e29nNk
08:31:38 <anitsirk> ?
08:31:51 <anitsirk> #agree next developer meeting on 17 February 2011 at 7:30 pm. GMT http://bit.ly/e29nNk
08:31:57 <anitsirk> next topic
08:32:03 <anitsirk> #topic Any other business
08:32:12 <fmarier> i've got two links to share with people
08:32:18 <fmarier> http://identi.ca/launchpadstatus
08:32:22 <fmarier> http://status.gitorious.org/
08:32:35 <fmarier> first thing to check if you're having problems with either of these services :)
08:32:53 <anitsirk> both sites load fine
08:33:08 <dobedobedoh> Excellent
08:33:17 <fmarier> anitsirk: they're for announcing downtimes and outages
08:33:21 <richardm> gitorious has been pretty unreliable
08:33:44 <rkabalin> Wiki is sometimes very slow, I have been wating for link dialog for 60 sec yesterday
08:34:00 <fmarier> rkabalin: the wiki is hopefully going to be migrated soonish to mediawiki
08:34:00 <rkabalin> that might be a network connection, though
08:34:07 <dobedobedoh> I'll put the minutes from this meeting on the wiki
08:34:19 <anitsirk> fmarier: sorry for the confusion
08:34:24 <fmarier> it's a pretty horrible setup at the moment
08:34:25 <laurent_tdm> I am catching up. Hi everyone. I am taking note of the next meeting.
08:34:36 <dobedobedoh> #action dobedobedoh will add minutes to wiki and create pages for next meeting
08:34:36 <rkabalin> fmarier: that is cool
08:34:39 <fmarier> with some dot net stuff that needs to be restarted on cron because it leaks memory
08:34:45 <anitsirk> thanks dobedobedoh
08:35:36 <fmarier> also, we'll be moving mahara.org and wiki.mahara.org to https as suggested by dobedobedoh
08:35:42 <dobedobedoh> w00t :)
08:35:55 <fmarier> no timeframe yet, but "soon" :)
08:36:12 <anitsirk> #info check http://identi.ca/launchpadstatus and http://status.gitorious.org/ (for announcing downtimes and outages)
08:36:58 <anitsirk> #info fmarier and richardm will be moving mahara.org and wiki.mahara.org to https as suggested by member:dobedobedoh
08:37:05 <dobedobedoh> I've also adjusted the meetbot to use meetbot.mahara.org for new minutes
08:37:38 <anitsirk> dobedobedoh: i'm slowly getting the hang of meetbot. good to chair a session to know the command faster :-)
08:37:45 <anitsirk> anything else?
08:37:49 <rkabalin> I have updated mahara-contrib/patch-adminlang.git with 1.3, there is a guy on the forum who were interested to begin translating Mahara on Croatian.
08:37:59 <fmarier> rkabalin: thanks a lot for that
08:38:13 <richardm> Yeah rkabalin that is awesome
08:38:28 <rkabalin> no problem, it just took 10 mins to be honest
08:38:54 <fmarier> there is a guy wanting to translate mahara to bulgarian, but he needs a bit of a crash course in git (or installing mahara or something) does anybody have time to get in touch with him?
08:39:03 <richardm> cool, i thought it'd take quite a while
08:39:40 <richardm> I think there's a wiki page somewhere about translation & git
08:40:03 <fmarier> yeah, i think he'll need to exchange a few email with someone though
08:40:09 <rkabalin> richardm: David did a very good job, I have to admit - very few merge conflicts
08:40:30 <anitsirk> http://wiki.mahara.org/Developer_Area/Language_Packs info on translating mahara
08:40:35 <richardm> http://wiki.mahara.org/Developer_Area/Language_Packs/Translating_and_Git
08:41:20 <anitsirk> anything else to discuss?
08:41:45 <ioniser1> fmarier i could have a go with the language thing after the academy week
08:42:13 <fmarier> ioniser1: ok, remind tomorrow and i'll give you the details
08:42:23 <ioniser1> ok, if i see you.
08:43:13 <anitsirk> if there is nothing else, i guess we could conclude this meeting. what do you think, dobedobedoh, master chair?
08:43:21 <dobedobedoh> heh ;) I was just thinking the same thing
08:43:27 <dobedobedoh> Thanks for chairing anitsirk :)
08:43:35 <dobedobedoh> Are you happy to chair the next meeting too?
08:43:44 <anitsirk> you are welcome.
08:44:12 <anitsirk> ohoho. isn't that a rotating job? if i'm in wellington, i can certainly do so though.
08:44:26 <dobedobedoh> Perhaps it should be a rotating job
08:44:51 <anitsirk> anybody wants to volunteer? ;-)
08:45:05 <ioniser1> ^^
08:45:07 <dobedobedoh> Well volunteered ;)
08:45:09 <anitsirk> i guess the first leave ;-)
08:45:54 <lamiette> wth - fffing netsplit or something, I logged off thinking no one else had turned up
08:46:12 <dobedobedoh> Well, I'll call and endmeeting now then. I guess we'll assume that anitsirk is charing the next meeting and perhaps we can alternate next time
08:46:20 <dobedobedoh> Unless there are any objections
08:46:26 <anitsirk> #agree anitsirk chairs next meeting
08:46:28 <ioniser1> nope
08:46:38 <dobedobedoh> Thanks all for your input
08:46:40 <dobedobedoh> #endmeeting