19:35:46 #startmeeting 19:35:46 Meeting started Wed Jun 29 19:35:46 2011 UTC. The chair is lamiette_. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:35:46 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:35:54 #topic Meeting Attendees 19:36:31 #info dobedobedoh is Andrew Nicols - LUNS Ltd, UK 19:36:36 #info anitsirk is Kristina Hoeppner from Catalyst IT in Wellington, NZ 19:36:46 #info rkabalin_ is Ruslan Kabalin, LUNS Ltd., Lancaster, UK 19:36:52 #info richardm is Richard Mansfield from Catalyst IT in Wellington, NZ 19:37:02 #info lamiette_ is Stacey Walker from Catalyst IT in Brighton UK 19:37:06 #info hughdavenport_ho is Hugh Davenport from Catalyst IT in Wellington, NZ 19:37:10 anitsirk: what did i do ? 19:37:22 oh you're doing meetings 19:37:24 #info dan_p_ is Dan Poltawski, LUNS ltd uk (on train) 19:37:28 #info thomaswbell88 is Thomas Bell from TDM Ltd, UK 19:37:29 * Mjollnir` goes away again 19:37:30 #info is Francois Marier 19:37:30 #info bugg_home is Brett Wilkinsa from Catalyst IT in Wellington, NZ 19:37:39 Brett Wilkins* 19:37:43 #info ricardomano is Richard Hand from TDM Ltd, UK 19:37:49 hi Mjollnir`: you were on the train once on your laptop and also walking down the platform with your laptop open so you could attend the first dev meeting :-) 19:38:50 oh yes 19:38:54 kevin made a photo 19:39:04 right, is that everyone ? 19:39:12 Are we doing the . Thing again, for new atendees? 19:39:20 pxh was here earlier 19:39:23 ? 19:39:26 ! thing sounds good, what is thing? 19:40:06 #info pxh is Piers Harding from Catalyst IT in Wellington, NZ 19:40:31 * pxh will be here for 20 minutes 19:40:33 dan_p_: what is the . thing for new attendees? 19:40:36 the . (on a single line) is to indicate that you're doing talking 19:40:48 so even if you write a multi-line comment 19:40:59 like this one, with enters between them 19:40:59 pxh: that means we should talk about web services first? 19:41:12 anitsirk: I agree 19:41:14 then you can still indicate you're done 19:41:15 . 19:41:22 sorry fmarier_ 19:41:39 When you finish what you are saying put a . On line when done. So people dont need to wait 19:41:46 anitsirk: can do - was not sure what people want to know about it ? 19:41:51 Argh sorry. Slowtyper 19:42:42 pxh: There was. Some interest in web services at mahara uk, would be good to know what you are working on 19:42:48 . 19:42:59 . 19:43:00 OK 19:43:07 #topic MNet future -- We're adding Web Services to 1.5 19:43:16 so the basic are: 19:43:18 hmm no power;) 19:43:31 #topic MNet future -- We're adding Web Services to 1.5 19:43:33 documentation is at https://wiki.mahara.org/index.php/Plugins/Artefact/WebServices 19:43:43 #link https://wiki.mahara.org/index.php/Plugins/Artefact/WebServices 19:44:08 I farmed it out into an artefact plugin because it is directly derived from Moodle web services in 2.x 19:45:19 it follows the pattern of Moodle Web Services quite closely in terms of authentication via tokens or username/password, and it's use of Zend web services 19:46:05 So, it can potentially replace Mnet feature? 19:46:06 features are: SOAP, REST (really just basic HTTP post parameters or JSON), and XML-RPC 19:46:36 Auth via WSEE for SOAP, as well as the tokens/users (as mentioned before) 19:47:13 it's plugable - as in it searches for externallib.php, and service.php definition files (like Moodle) at upgrade 19:47:26 But Moodle web services are (supposed to be) pluggable, is the same true here 19:47:37 rkabalin_: I would hope that it could quite easily replace mnet if needed 19:47:41 Grr, sorry 19:47:45 * rkabalin_ sorry for interrupting 19:47:58 yes dan_p - it is 19:48:36 more features: has example commandline clients, and I'm just about to commit an interactive web based test client 19:48:42 Are there advantages/limitations of making it a plugin itself? 19:48:47 this was for the Ministry of Education NZ 19:49:08 they wanted SOAP, but I wanted the rest (pun intended) 19:49:29 pxh: nice one :) 19:49:41 lol. you probably need it as well ;-) 19:49:52 It also can be used as API for various remote user/group/institution management tasks 19:49:58 Harsh! 19:50:00 from the MoE point of iew the main thing missing is signatures and encryption from WSSE - but nobody uses it 19:50:11 ... but they are a guvament department 19:50:44 yup - rkabalin_ - should have said that - there are 19 functions in the API already 19:50:56 that is cool 19:51:22 why an artefact plugin and not a new top level plugin type ? 19:51:24 and - to finish - I want to add OAuth as that will open it up properly to 3rd party dev 19:51:25 . 19:51:28 not that i really have any say :) 19:51:45 Mjollnir`: ignorance probably 19:51:55 pxh, can it talk to moodle (2.x) via this API? 19:52:00 Mjollnir`: time constraints, we'll be moving it 19:52:27 Mjollnir`: ... on my part that is 19:52:55 is it really less work to make it an artefact plugin and have to implement contracts that you don't need than make a new top level plugin ? eh, maybe i dunno 19:52:59 :) 19:53:19 * dan_p_ alighting train, connectivity unknown 19:53:24 bugg_home: I haven't had time to test this yet - one of the things I wanted to do was to try and get it talking over the Moodle hub (in a limited way) but I'm still trying to deliver the original requirement to the MoE 19:54:27 .. as they are paying for it at the moment 19:54:29 pxh: so it's derived from Moodle 2.x but tested/written to work with 1.9 only at this stage? 19:56:14 lamiette_: I haven't got as far as integration testing etc. with Moodle yet - once I get the MoE requirement behind me - I can look at making this useful to the wider Mahara community 19:56:25 awesome 19:57:13 pxh: Sounds good 19:57:18 yeah, that sounds great 19:57:21 but anyway - useful things would be OAuth, and MNet replacement 19:57:23 Look forward to reviewing on gerrit for master ;) 19:57:36 #info pxh has writtten a web services framework, based on the Moodle 2.0 web services Further information at https://wiki.mahara.org/index.php/Plugins/Artefact/WebServices 19:57:46 (sorry guys, i'm a bit slow on this chairing thing!) 19:58:01 the first lms to integrate it with is not moodle to ensure that the api also works with others as mahara and moodle are closer to each other than mahara and another system 19:58:02 so with one feature we can potentially resolve two issues: Mnet and API 19:59:00 #info pxh> features are: SOAP, REST (really just basic HTTP post parameters or JSON), and XML-RPC 19:59:14 #info Auth via WSEE for SOAP, as well as the tokens/users (as mentioned before) 19:59:23 pxh: When do you expect to submit this, and are you hoping to have it in 1.5? 20:00:38 any more questions for pxh ? 20:00:41 dobedobedoh: it needs work on cleaning the code base out - removing unnecessary cruft from the Moodle base - then it needs some fairly critical review 20:00:46 * rkabalin_ thinks it is already in contrib 20:01:19 rkabalin_ yup - in contrib 20:01:28 .. but not in core 20:01:34 Cool. Hadn't seen it 20:01:47 * dobedobedoh has no further questions 20:01:58 .. if it were to go in core then it would be moved out of being an artefact plugin 20:02:08 righto, we're half an hour through and pxh said he had to move on at 20minutes 20:02:26 plugin is at https://gitorious.org/mahara-contrib/artefact-webservice 20:02:38 #link https://gitorious.org/mahara-contrib/artefact-webservice 20:02:53 #info available as a contrib plugin 20:02:53 lamiette_: thought I was on duty to take kids to school - but Marysia is doing it 20:03:07 lucky :) 20:03:31 rkabalin_: did you want to talk about the future of MNET while we're on a similar topic? 20:03:39 or was that just a lead in to pxh web service? 20:04:30 Yep, a sort of, I was just going to rise the issue and notify that we have to start thinking about Mnet stuff 20:04:58 I shall topic it and you can have the stage 20:05:12 not really needed 20:05:20 okay ... 20:05:21 since we covered it in this discussion 20:05:38 .. 20:05:38 I'm going to info something though :P 20:06:14 #info we have to start thinking about Mnet stuff: largely due to this from Moodle HQ http://moodle.org/mod/forum/discuss.php?d=175158 20:06:25 right, is that all for MNET and web services? 20:06:37 that's all from me 20:06:44 yep 20:06:58 #topic Bug status proposal 20:07:05 fmarier_: this one was yours 20:07:49 ok, so let me start with the milestone thing 20:08:08 so far, we've used milestones on the tracker for two things 20:08:31 1- as a bit of a TODO list for the upcoming release (that is, bugs that have a milestone but aren't done yet) 20:09:06 2- as a changelog or a detailed version of the release notes (once the release is done and the bugs are fixed) 20:09:26 to make this more useful for #2, I'd like to propose the following 20:10:02 we omit from the milestone bugs that don't apply to the stable releases 20:10:24 so for example, if you add a new feature (say sitemaps) and they have a bug, 20:10:49 then the fixup bug doesn't retain the 1.5 milestone when it's fixed 20:11:41 the original feature bug goes onto the 1.5 milestone of course because it's one of the relevant changes from the stable branches, but the bug that got fixed in it isn't very relevant to people upgrading from 1.4 20:12:12 #info milestones have been used for marking bugs to upcoming releases and as for a changelog/detailed version of the release notes 20:12:15 in that case, you'd just mark the bug as "fix released" without a milestone 20:12:15 fmarier_: makes sense to me 20:12:31 because when you use "fix committed", you must specify a milestone 20:12:42 So the milestone is more for bugs fixed since the last release, rather than aimed for the next 20:12:55 otherwise the bug gets into that state and isn't listed anywhere so nobody remembers to flick it to fix released once 1.5 is out :) 20:13:03 dobedobedoh: it's for both 20:13:27 Ah I see 20:13:28 but once a bug is fixed, you can remove the milestone if it doesn't make sense to have it stick around 20:13:30 #info suggestion: for better changelog only mark main feature bugs with the milestone and any follow up fixes to that feature just as "fix committed" ommiting the milestone 20:13:47 lamiette_: that's slightly wrong 20:13:50 oh 20:13:55 I misunderstood then sorry 20:14:03 we mark ALL new features against the milestone 20:14:10 and all bug fixes that apply to 1.4 20:14:12 #undo 20:14:12 Removing item from minutes: 20:14:22 it's the bugs that only affect master that don't need to go on there 20:14:35 for example, we broke the creation of new institutions recently 20:14:51 but that doesn't need to be in our release notes, because we've never release a version of mahara with that bug 20:15:12 so we would mark it as "fix release" with no milestone once it's been merged 20:15:13 . 20:15:25 I see fmarier_ 20:16:31 so basically all new features and previous relese fixes are marked with milestone 20:16:31 so anyways, i want to run it past all of you to see if you have any objections 20:17:15 richardm brought something up: if you change a new feature in a significant way, then that should probably also have the milestone set so that it's visible 20:17:45 fmarier_: yup 20:17:49 but if you're just fixing it so that it does what it was supposed to do in the first place when you merged it on master, then it's probably not worth it 20:17:55 . 20:18:10 rkabalin_: yes 20:18:11 i'd also suggest we could take care of thta case by repoening the feature bug 20:18:30 richardm: true 20:19:05 richardm: so in the case (using something I know) of dropdowns we could open the existing feature bug again for the inst membership navigation move to Groups yeah? 20:19:22 lamiette_: yeah, that's a good idea 20:19:25 sweet 20:19:28 sounds good 20:19:47 sometimes if it's a regression we don't know what feature caused it though :( 20:20:14 richardm: I suppose this only works for things we know then, but that'd at least take care of a fair amount 20:20:33 richardm: if you know it's only on master, then you don't need the milestone 20:21:16 so everyone understand/ in agreement? 20:21:29 what i'm suggesting is a guideline, we can see how it goes and adjust if anything we haven't thought about pops up 20:21:34 fmarier_: will you document this? :) 20:21:49 yes, i'll update the bug status page if everybody agrees 20:21:59 I like reopening idea, we will have less bugs then and it will be easier to follow all the stuff related to the particular featute 20:22:09 I agree 20:22:45 #action fmarier_ to update the bug status page with new "milestone" usage guidelines 20:23:08 less issues on the tracker I mean 20:23:12 fmarier_: you had a couple more points in that list? 20:23:24 the other minor point i had in there was that all new features added to master should have a bug on the tracker 20:23:35 that will help heaps when we write the release notes for 1.5 :) 20:23:36 agreed 20:23:51 yup, agreed 20:23:53 makes sense 20:24:01 I was also going to suggest that we add a Makefile target to check that they're also specified in the commit message 20:24:07 agree (even though i'm a serial offender) 20:24:09 In a specific format 20:24:19 dobedobedoh: that's on fmarier_ 's list :) 20:24:24 * dobedobedoh added it there ;) 20:24:31 ohhhhh I seee 20:24:38 dobedobedoh: that would however imply that every commit needs a bug number, right? 20:24:47 which we haven't enforced so far 20:24:52 Correct 20:25:00 I thought that the two would go pretty much hand-in-hand 20:25:04 do people want that? 20:25:18 #info every new feature on master should have a bug report associated with it 20:25:25 i personnally can see that for some small commits, it's a bit overkill 20:25:29 (like a typo fix) 20:25:35 sortof makes sense 20:25:45 I'm less keen on forcing bug numbers for every commit 20:25:50 I think it would really help with the changelogs -- as I understand (and correct me if I'm wrong), it would automatically fill the changelog -- https://launchpad.net/mahara/1.4/1.4.0 under "View the full changelog" 20:25:50 it'd be a good rule of thumb, but not something to actively enforce 20:25:58 Fair enough 20:26:04 small fixes can just be tagged to a default bug of say "Fix typos" etc 20:26:17 dobedobedoh: i thnk it's the milestones that fill the changelog 20:26:24 yeah perhaps it should be actively requested by reviewers 20:26:35 except for trivial cases 20:26:51 fmarier_: if we do that we could see how often bug numbers are requested and used 20:26:54 we could put it in the minaccept check, and then discard it if it's trivial 20:26:55 Perhaps that's a better solution -- reviewers requesting it 20:27:00 and if it's then worth making it an enforcement etc 20:27:23 Or, if it is trivial, using something like (minorbug) instead of (bug #xyz) 20:27:24 but better 20:27:24 . 20:27:59 dobedobedoh: yeah, I like minorbug idea 20:28:06 to me, it seems similar to: -1, your commit message doesn't really explain what you did 20:28:22 it's a subjective thing that relies on the reviewer's good judgment 20:28:52 I think it's also overkill when you have a series of commits for 1 feature 20:28:53 I'm happy to leave it up to the reviewer 20:29:04 it doesn't always make sense to use the same bug number 20:29:17 (but maybe you need to create another bug at that point) 20:29:28 richardm: agreed. 20:29:57 right, lets move on yeah? 20:30:26 I don't mind either way, but I think that we should be actively trying to encourage use of bug #s so reviewers demanding works for me :) 20:30:27 do we have agreement on being stricter about forgotten bug numbers without making it mandatory? 20:30:43 yes, agree 20:30:46 (mandatory for new features though) 20:30:49 yup 20:31:00 agree 20:31:03 yup 20:31:10 yes 20:31:14 yes 20:32:02 #info reviewers to be stricter about suitable bug numbers for features submitted to gerrit - isn't mandatory though 20:32:26 right, a quick topic now: 20:32:31 #topic MaharaUK2011 20:32:40 seeing as this just happened 20:33:00 i wanted to bring it to attention in case anyone had anything interesting to say about it 20:33:48 one rumor i've heard from it is that we're going to have a northern UK maharauk12 ;) 20:34:02 That's the plan 20:34:29 LUNS and TDM have both offered to host maharauk, so we've suggested that 12 is in Lancaster, hosted by LUNS 20:34:35 and 13 is in the West Midlands, hosted by TDM 20:34:46 I don't think its a underground secret, but it's planned ... as above :P 20:34:58 #info LUNS and TDM have both offered to host maharauk, so we've suggested that 12 is in Lancaster, hosted by LUNS and 13 is in the West Midlands, hosted by TDM 20:35:06 We're waiting for feedback from the governance group as far as I understand 20:35:18 sweet 20:35:24 sam told me that meredith and roger are writing the conference report. lamiette_ do you have any idea if there is a 100 words or so in it for the newsletter (out tomorrow) or shall i just write that it happened at that the report will be on the web site soon? 20:35:28 . 20:35:30 other things were: 20:35:39 great interest in skins from lots of people 20:35:51 There was also talk about some entity hosting online 'conferences' inbetween during the year 20:35:58 . 20:36:20 thomaswbell88: webinar type things? 20:36:33 and anitsirk's what was it 22.5 million ways to get involved (?) being quite a popular discussion 20:37:01 yep, it was asked as a question by a delegate and followed up with a few, mmm's and arrr's 20:37:30 anitsirk: not sure, but I can check with them tomorrow morning 20:37:33 * dobedobedoh has a list of feature ideas that he thought up during the conference to add to the tracker 20:37:40 anitsirk: newsletter for tomorrow NZ time yeah? 20:38:08 * lamiette_ and paul did the navigation dropdown thing while at the conference 20:38:12 haven't heard back from meredith yet. yep, NZ time. so your tomorrow morning would still be fine if the text comes through with it. just 100-150 words though please. that's enough. 20:38:18 inspired by thomaswbell88's page editing JS 20:38:37 anitsirk: I'll chase it up 20:39:02 oh, fmarier_ : we had the keysigning party 20:39:02 thank you. otherwise i'll just mention it and refer to the web site 20:39:04 there was no cake 20:39:12 huh? 20:39:25 The key signing party consisted of lamiette, rkabalin, and myselft 20:39:32 it was rocking! 20:39:37 what is a key signing party? 20:39:42 cool, we'll have a stronger trust path between NZ and the UK now :) 20:39:53 Indeed :) 20:39:59 oh the gpg key? 20:40:02 anitsirk: signing each other's gpg keys 20:40:02 anitsirk: signing gpg keys, so we know to trust each other 20:40:06 they are real people now, not I I'm afraid 20:40:17 #link http://cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html 20:40:21 for the gory details 20:40:30 thomaswbell88: We'll get you gitted and gpg'd up soon Im' sure ;) 20:40:55 #info There was also talk about some entity hosting online 'conferences' inbetween during the year (webinar type things) 20:41:02 rkabalin did a presentation on gerrit, and I did a tour of git to get people more interested in developing features 20:41:23 slides are available online 20:41:28 emphasis was definitely on contributing to mahara this year 20:41:34 Definately 20:41:37 oh slide links everyone ? 20:42:20 #info twitter hashtag #maharauk11 for anyone interested in seeing what attendees had to say 20:42:39 #link http://t.co/dFHqjYX - Git in Mahara 20:43:00 http://www.slideshare.net/rkabalin/presentations - both my presentations 20:43:28 I fumbled through a 'non-presentation' (no slides) on the dev day 20:43:29 #link http://www.slideshare.net/rkabalin/presentations 20:44:10 #link http://www.slideshare.net/andrewnicols/presentations for mine 20:44:25 ok. if everybody posts their presentation links, here's the 21 3/4 ways to get involved in mahara (recording is so far only on youtube) 20:44:26 rkabalin_: i really liked your gerrit presentation 20:44:28 #link http://www.slideshare.net/4nitsirk/21-34-ways-to-get-involved-in-mahara 20:44:44 If anyone is interested in more info on the isolated institutions feature, rkabalin also presented on that 20:44:44 well, the slide contents at least, i wasn't there to see the live thing ;-) 20:44:47 fmarier_: thanks 20:44:48 thomaswbell88's tools panel http://yfrog.com/gzbkqiej 20:45:01 #link http://www.youtube.com/watch?v=Rbz9vST0CLw recording 20:45:15 * dobedobedoh thinks that's all he has to say about maharauk11 20:45:45 #link Mark Osbornes keynote http://prezi.com/dubgzzefzioj/maharauk-open-for-learning/ 20:45:48 yup 20:45:50 lets move on 20:46:05 #topic Mahara Reviewer applications# 20:46:12 we have three: 20:46:17 hughdavenport_ho: 20:46:20 bugg_home: 20:46:24 and lordp 20:46:28 wait 20:46:35 ? 20:46:48 I was going to mention thomaswbell88's idea 20:47:00 about badges on the forum 20:47:18 shall we just do it after the applications? 20:47:18 (see 3.2 on agenda) 20:47:23 ok 20:47:38 oh right, sorry rkabalin_ 20:47:57 applicants, please step forward. lorp should be here now as well. 20:48:16 hello 20:48:22 hi all 20:48:33 #info Hugh Davenport Mahara reviewer application 20:48:49 #info Brett Wilkins Mahara reviewer application 20:49:09 so who is a current reviewer (and online) at the moment? 20:49:14 * fmarier_ is a reviewer 20:49:21 * dobedobedoh is a reviewer 20:49:26 #info Darryl Hamilton Mahara reviewer application 20:49:32 I think I am 20:49:38 #info lordp is Darryl Hamilton 20:49:46 * rkabalin_ is reviewer 20:49:49 * richardm is a reviewer 20:50:03 lamiette_: yup you are 20:50:12 Just missing dan_p who'se probably lost packets 20:50:17 so we've got five? 20:50:24 5 out of 6 20:50:26 is five what we need? 20:50:38 * lamiette_ forgets how many we need 20:50:48 we haven't really set a quorum, this is the first time we do this :) 20:51:01 but if we had only 1, it would be a bit dodgy 20:51:07 right, let the games begin then! 20:51:07 5 is plenty i'd say 20:51:11 consensus decision rules, with those at the meeting entitled to vote 20:51:33 first up: hughdavenport_ho 20:51:35 * dan_p is back 20:51:37 hello 20:51:38 dobedobedoh: those _reviewers_ at the meeting :) 20:51:39 http://meetbot.mahara.org/mahara-dev/2010/mahara-dev.2010-11-10-07.34.html FYI 20:51:52 sorry yes, only reviewers 20:52:13 hmm, I haven't been doing "agrees" oops 20:52:42 anyway - vote? 20:53:06 and who is sponsoring 20:53:11 fmarier_: are you for all three? 20:53:15 any questions for hughdavenport_ho ? 20:53:18 some info on what I have done https://wiki.mahara.org/index.php/User:Hughdavenport 20:54:03 . 20:54:44 btw, the "becoming a reviewer" process has been documented here: https://wiki.mahara.org/index.php/Developer_Area/Code_Review 20:55:14 (slightly modified version from the meeting log above given that we no longer have committers) 20:56:18 do people need more time to read hughdavenport_ho bugg_home and lordp 's pages? 20:56:30 #link https://wiki.mahara.org/index.php/Developer_Area/Code_Review 20:56:40 #link https://wiki.mahara.org/index.php/User:Hughdavenport 20:56:54 #link https://wiki.mahara.org/index.php/User:Brettwilkins 20:57:00 * dobedobedoh is ready to vote 20:57:01 #link https://wiki.mahara.org/index.php/User:Darrylh 20:57:39 * fmarier_ is ready as well 20:57:47 * rkabalin_ ready to vote, in fact read through their reports prior the meeting 20:57:53 ditto 20:57:59 yep, me too 20:58:12 ready to vote!! 20:58:25 dan_p: awesome we have a full house :) 20:58:34 lamiette_: ready? 20:58:40 yup 20:59:02 * fmarier_ moves to accept hughdavenport_ho as a Mahara reviewer 20:59:19 * rkabalin_ accepts hughdavenport_ho as a Mahara reviewer 20:59:20 * dobedobedoh moves to accept hughdavenport_ho as a Mahara reviewer 20:59:36 * richardm accepts hughdavenport_ho as a Mahara reviewer 20:59:42 * dan_p accepts hughdavenport_ho as a Mahara reviewer 20:59:54 * lamiette_ moves to accept hughdavenport_ho as a Mahara reviewer 21:00:18 fire alarm at catalyst 21:00:23 fireall at catalystback in a minute or later 21:00:28 lol 21:00:30 typical 21:00:31 nice :) 21:00:31 :P 21:00:35 lol 21:00:37 lets talk about them while they're gone 21:00:40 we were overdue for a firedrill 21:00:43 best timimg 21:00:50 * fmarier_ is supposed to be the fire warden 21:00:56 heh 21:01:03 * bugg_home is supposed to be fmarier_'s backup 21:01:08 we can still vote without them, all the reviewers are still here 21:01:09 xD 21:01:12 double heh 21:01:24 k, anyway 21:01:24 who's not here? just anitsirk ? 21:01:28 was that all of us? 21:01:29 fmarier_: peterb won't even be at work yet 21:01:37 fmarier_: anitsirk and lordp 21:01:45 ok, let's vote on bugg_home then 21:02:48 lamiette_: that was all of you 21:03:04 cool 21:03:05 any questions for bugg_home? 21:03:05 #agreed Hugh Davenport to become Mahara reviewer 21:04:09 none from me 21:04:20 I was at a wedding this weekend, the mahara-dev proces feels strangely familiar ;-) 21:04:32 dan_p: lol 21:04:47 who's kissing the bride then? 21:04:51 hah, those catalyst folk, what lols 21:04:53 * fmarier_ bags not 21:04:56 uhhh... 21:04:57 who's the bride? 21:04:58 ooh shit 21:05:01 they're back :p 21:05:08 * hughdavenport_ho thinks i should leave now... 21:05:42 moving on 21:06:19 * lamiette_ moves to accept bugg_home as a Mahara reviewer 21:06:28 * dobedobedoh accepts bugg_home as a Mahara reviewer 21:06:53 #agree 21:06:55 * richardm accepts bugg_home as a Mahara reviewer 21:07:06 * rkabalin_ accepts bugg_home as a Mahara reviewer 21:07:17 * dan_p accepts bugg_home as a Mahara reviewer 21:07:31 arise, sir bugg_home 21:08:09 richardm: I'll try to not be sick and make it into work today ;) 21:08:22 arise, sir bugg 21:08:44 * dan_p wonders if we can sneak any extra mahara-dev vows 21:08:45 right, so time for lordp 21:09:12 * dobedobedoh accepts lordp as a Mahara reviewer 21:09:23 #agree 21:09:26 #agreed Brett Wilkins to become a Mahara reviewer 21:09:28 * rkabalin_ accepts lordp as a Mahara reviewer 21:09:29 * richardm accepts lordp as a Mahara reviewer 21:09:30 #agree 21:09:38 fmarier_: can I action these to you? 21:09:43