07:31:17 #startmeeting 07:31:17 Meeting started Wed Mar 23 07:31:17 2011 UTC. The chair is rkabalin_. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:31:17 Useful Commands: #action #agreed #help #info #idea #link #topic. 07:31:29 #topic Meeting attendees. 07:31:52 Please put #info in from of your names 07:31:53 #info anitsirk: Kristina Hoeppner from Catalyst IT, Wellington, NZ 07:32:01 #info Andrew Nicols, LUNS Ltd, UK 07:32:15 #info Stacey Walker Catalyst IT Europe 07:32:22 #info rkabalin_ Ruslan Kabalin from LUNS Ltd., Lancaster, UK 07:32:26 #info anzeljg: Gregor Anzelj, Slovenian langpack maintainer, plugin developer 07:32:43 #info David Drummond from Catalyst 07:32:53 #info richardm: Richard Mansfield from Catalyst 07:33:22 fmarier should be around as well 07:33:39 #info fmarier Francois Marier 07:34:15 ok, that is everyone I guess 07:34:25 #topic Items from previous meetings 07:34:47 #info dobedobedoh to check the ubuntu code of conduct which is CC licensed for the mahara code of conduct 07:34:50 iarenaza sent an email saying that he can't attend, but he sent some info through regarding his action items 07:35:15 anitsirk: that is fine 07:35:19 rkabalin: Sorry, but I *still* haven't had a chance to do this. My current workload should ease off on Friday 07:36:21 OK, I move it to the next meeting then 07:36:29 :) 07:36:46 #action dobedobedoh to check the ubuntu code of conduct 07:37:03 #info dobedobedoh and azeljg to go over skins patches to try and get them into 1.4, richardm will also take a look at them 07:37:36 rkabalin_: I still haven't done that 07:37:42 I'll try to rebase with current mahara master 07:38:33 #action anzeljg try to rebase his skins patches with current mahara master 07:38:37 I talked with richardm and he said that including it in 1.4 may not be possible 07:38:39 anzeljg: is the current version pushed anywhere? 07:38:58 just a moment... 07:39:42 #info the new url of anzeljg's test server is http://mahara.ledina.org/DEV/ login and pwd stayed the same 07:39:59 #info there you can test the skins 07:40:07 yeah, I was thinking it's getting a bit tight if we keep to the end of april deadline 07:40:20 the latest (unchanged version) is here: #link http://gitorious.org/~anzeljg/mahara/anzeljg-mahara 07:40:46 there is only skin support on this clone 07:41:15 dobedobedoh: will you be able to go through patches in April? 07:41:26 ok cool, I will try to take a look at it, but will go through the high priority bugs first 07:41:47 I'm not sure -- it depends on my other commitments 07:42:02 richardm, dobedobedoh and fmarier all have admin privileges at that clone 07:42:05 I'd like to but since I first volunteered, I haven't acually had a chance :( 07:42:28 ok, then I re-assign it to richardm and you both 07:42:56 Ok that sounds good 07:43:21 #action richardm dobedobedoh Go through azeljg's skins patches to try and get them into 1.4 07:43:37 #info iarenaza to draft language pack release policy 07:43:44 that is done 07:44:01 #link http://wiki.mahara.org/Language_Packs/Language_Pack_Release_Policy 07:44:11 Great 07:44:27 #info Graphs in Mahara Statistics proposal (anzeljg) 07:44:33 #info iarenaza also writes: H31nz was in touch with me and provided some valuable feedback that 07:44:33 has been incorporated to the draft 07:45:36 sorry for being so slow in copying. that's all that he had to say for this item 07:46:13 Graphs: I just proposed this. I wanted to include it in the survey artefact, I'm working on, but haven't had the time to do it. 07:48:36 anzeljg: i like the plugins you produce because they add great functionality to mahara. i think you are the plugin developer par exellence for mahara 07:49:07 OK, shall I postpone this as action? 07:49:08 +1 to that :) 07:49:15 thank you for kind words anitsirk, I'm blushing now... 07:49:26 i think the action (proposing the idea) is done 07:49:28 it's true :-) 07:49:47 and we all agreed that it sounds like a good idea 07:49:56 fine with me 07:50:02 ah, yep 07:50:46 that is indeed a good idea having them added to mahara 07:50:55 #info rkabalin to summarize his ideas of notifications of objectionable content on a subpage 07:51:44 I have written a very brief spec on that http://wiki.mahara.org/Developer_Area/Specifications_in_Development/Objectionable_content_reporting 07:53:15 * fmarier agrees with the destination user in rkabalin_'s spec 07:53:46 should we then have objectionable content reporting for any artefact? you have blog in there, but images and other docs also have their own artefact page. they should be treated equally, i think. 07:54:06 One thing I'd like to add -- it would be good to be able to object to Users as a whole and have notifications sent to the site/institution admin 07:54:22 I don't think we even have notifications of wall posts yet either 07:54:30 nope we don't 07:54:55 dobedobedoh: isn't the objection to one user based on his actions? 07:55:36 anitsirk: Possibly, but if someone reports objectional content in a forum, then the forum moderators receive the message 07:55:56 If the forum mods determine that the user is actually a spammer/bot, but they aren't site/institution admins, they can't remove the users 07:55:59 user* 07:56:07 So they need an escalation method 07:56:10 dobedobedoh: good point 07:56:17 that's true 07:56:35 perhaps moderator should be able ot disable the user 07:56:46 Case in point is mahara.org -- I'm a forum mod and can remove messages, and remove users from the groups, but not disable the user in any useful fashion 07:56:52 So spammers can just rejoin the group and spam again 07:57:03 rkabalin_: that would give too much power to moderators i think 07:57:04 forum: do you mean "moderators" also in the sense of admins of the group if there is no official forum moderator, dobedobedoh ? 07:57:21 I wonder if the objections could add the user to a watchlist that the admins could then monitor if they keep getting objections etc? 07:57:22 anitsirk: I was thinking as a group admin 07:57:32 i guess what you want is a way for a group admin to ban a user from joining the group 07:58:03 fmarier: Something like that would be good 07:58:09 +1 07:58:17 #info perhaps what we want is a way for a group admin to ban a user from joining the group 07:58:25 +1 07:58:30 #agree 07:58:40 anyways, maybe we should move on since we have quite a few items left on the "previous actions" list as well as on the agenda :) 07:58:54 ;) ok 07:59:01 what's the next step on this particular feature? 07:59:10 is this something you're planning on implementing? 07:59:45 just an idea at the moment 07:59:52 or was it mostly to write a spec before filing a wishlist bug on the tracker? 08:00:45 ok, in that case, i would suggest: action for ruslan - file a wishlist bug on the tracker :) 08:00:46 a sort of, but I think we should start with forums if the time for this feature will be allocated 08:01:29 #action rkabalin_ file a wishlist bug on the tracker with objectionable content report items 08:01:43 #info richardm checks if objectionable content notifications already go to institution admins besides site admins 08:01:50 that is done I think 08:02:10 do you mean that richardm checked or that notifications go to institution admin as well? 08:02:39 there was I patch if I remeber correctly 08:02:43 I was afraid of looking bad at the next meeting so i did it. 08:03:02 Should be working now 08:03:05 well done richardm! 08:03:08 cool 08:03:16 #info anzeljg will put more details about using pChart as framework for rendering graphs in Mahara on the bug tracker 08:04:00 done: https://bugs.launchpad.net/mahara/+bug/721496 08:04:31 fine 08:04:47 #anzeljg to further look into flickr and picasa photo block 08:04:52 #undo 08:04:52 Removing item from minutes: 08:05:04 #info anzeljg to further look into flickr and picasa photo block 08:05:23 I did that by extending galler block 08:05:31 awesome 08:05:33 it works on my localhost 08:05:59 * dobedobedoh learns a new meetbot feature 08:06:09 tried to show it to you guys and uploaded it to our school server http://mahara.ledina.org/DEV/, but got error message 08:06:26 URL file-access is disabled in the server configuration 08:06:32 that is the error 08:06:54 need some time (days) to sort it out, than send you an e-mail with details... 08:07:31 #action anzeljg send an e-mail with details on flickr and picasa photo block 08:08:00 #info iarenaza to provide anzeljg with google apps for education account(s) for further testing of the google apps plugin 08:08:02 a brief descritption: gallery block is extended so the user can add photos from mahara or from external gallery (Flickr, Picasa, Panoramio and Photobucket currently supported - having troubles with Windows Live Photo Gallery) 08:08:22 user can also choose thumbnails, square thumbnails or slideshow 08:08:43 wow, i'm looking forward to seeing that! 08:08:52 would be initersting to have a look 08:09:09 ok, next item 08:09:11 sounds great 08:09:11 gallery block now uses slimbox2 (http://www.digitalia.be/software/slimbox2) fore rendering photos when user clicks on thumbnail 08:10:03 anzeljg: that sounds cool 08:10:05 anzeljg: cool, sounds much better than the basic one in the old gallery block 08:10:50 * richardm is sucked in by the page title 08:11:05 i'll try to sort it out in a couple of next days - got newborn two days ago, so i don't have much time currently :) 08:11:17 anzeljg: congratulations! :) 08:11:23 thanx 08:11:27 anzeljg: congratulations! 08:11:27 wow, congratulations 08:11:27 congrats anzeljg! 08:11:28 congratulations, anzeljg 08:12:15 #info iarenaza to provide anzeljg with google apps for education account(s) for further testing of the google apps plugin 08:12:20 #info from iarenaza: I have the Google Apps domain up and running already (so I can provide accounts as needed), but haven't looked anything about Live@edu yet (terms and conditions, technical requirements, etc.). I hope I'll have a bit of free time at the end of next week to have a look at it. 08:12:42 we can combine google apps and live@edu updates 08:13:13 i had an email conversation with live@edu support but they didn't quite understand my query though i thought it was clear. :-( maybe i should have drawn an image 08:13:28 ;) 08:13:52 they didn't know if their url's were different for live@edu account created documents to the regular live account 08:14:02 anyway, thanks to iarenaza, we'll soon know 08:14:26 i guess, we can make it an action item that iarenaza will sort out the live@edu account details 08:15:01 #action iarenaza further look at Live@edu accounts 08:15:36 rkabalin_: we can skip action items 12 and 13 from last meeting :-) 08:15:43 yep 08:15:53 #info richardm to add a list of plugins-in-use for the weekly stats push 08:16:17 Yep, done i think 08:16:30 great 08:17:32 Ace 08:17:40 I am wondering if stats available for ordinary users? 08:17:58 Nope, not yet, they're in the admin area only 08:18:06 ok 08:18:07 which stats would you show normal users? 08:18:47 Well there's a graph of the number of sites, it's boring but not revealing 08:18:54 something like this would be cool: http://moodle.org/stats/ 08:19:28 we can get country distribution for instance in terms of sites and users 08:19:28 #agree 08:19:50 but we may not have all the info yet 08:20:09 however, it's a good guide in terms of what information can be made public 08:20:59 they've added a lot of stats. they also started out small. :-) 08:21:29 perhaps richardm or fmarier can write a spec for what we can have on public stats page 08:21:56 just outline it on wiki 08:22:10 I don't think we'll have time for that before the next meeting 08:22:23 yeah, i think we have lots of things on our plates already :) 08:22:33 releasing 1.4 comes to mind :) 08:22:52 ok, let's leave it for the moment 08:23:05 #info fmarier is going to try to get in touch with Mjollnir` and get the unit test work she did merge into master 08:23:36 done: richardm found the code and pushed it here: http://gitorious.org/mahara/mahara-shared/commits/phpunit-old 08:23:42 * anitsirk is wondering how to keep track of action items for the meeting after next or even after that. probably just create wiki pages and put the info in. 08:23:44 not merged yet though 08:24:09 It'd be really good to have the phpunit tests 08:24:13 anitsirk: good idea 08:24:22 anitsirk: http://wiki.mahara.org/Developer_Area/Current_Tasks 08:24:30 i've added the stats thing to the backlog 08:24:43 thanks fmarier 08:24:56 ah even better 08:25:00 thanks fmarier 08:25:23 so we don't have to keep those as action items for meetings 08:25:46 yeah. is better place, esp. with items for which we don't know yet in which meeting they can be addressed 08:25:55 also: the backlog is not ordered by priority 08:26:23 #info tasks / action items that we want to keep track of, but can't address until the next developer meeting are tracked at http://wiki.mahara.org/Developer_Area/Current_Tasks 08:26:42 thanks anitsirk 08:26:47 #agree 08:26:48 that also shows what tasks we're working on by the way 08:27:16 lamiette and i (mostly lamiette actually) are doing the stable release 08:27:22 and i'm setting up gerrit 08:27:33 #info phpunit code is pushed here http://gitorious.org/mahara/mahara-shared/commits/phpunit-old 08:28:23 feel free to take something from the backlog and put your name beside it of course :) 08:28:45 any idea when gerrit will go live? 08:29:15 rkabalin_: yes and it's on the agenda :) 08:29:19 :) 08:29:47 so we can skip that item as we'll get back to it shortly 08:31:08 ah, I have not updated agenda page since yesterday 08:31:27 ok, let us move to the agenda then 08:31:29 there've been some additions ;-) 08:32:00 #topic lang.mahara.org and AMOS roadmap and funding? [iarenaza] 08:32:36 he's not here and i don't have any info on this item. 08:32:50 true, sorry 08:33:01 no worries. could have been in his email. ;-) 08:33:19 I will move this to the next meeting then 08:34:01 it was great that he had provided info on his action items. i think we'll revisit the lang.mahara.org stuff next time 08:34:13 #action rkabalin_ move lang.mahara.org agenda item to the next meeting as iarenaza is not present 08:34:32 #topic Forum post editing (bug #731990) [Francois] 08:34:37 I suggest starting by giving everybody a chance to take a look at https://bugs.launchpad.net/mahara/+bug/731990 08:34:55 that we can discuss what we think we should do 08:35:28 I had considered an alternative -- providing a countdown timer (JS) on the edit post page telling the user how long they have to edit their post 08:35:43 And not extending the time allowed to post 08:35:51 i put that bug on the agenda there because we didn't reach a conclusion on the tracker and was hoping for a larger discussion 08:36:12 dobedobedoh: that is slightly unusual for the forum ;) 08:36:58 will create a feeling of exam ;) 08:37:20 there is that 08:37:25 on the other hand, it's a reflection of what is happening 08:37:37 there is a countdown as soon as the post is submitted :) 08:37:49 But why should we extend the time limit -- if the limit has been set, it's probably there for a reason 08:37:52 what about having a message after the submission of the forum post saying "You have 30 min to edit your post before it is sent out" (like Moodle)? 08:38:04 currently nobody knows how long the editing period is 08:38:33 anitsirk: that sounds reasonable 08:38:47 #info having a message after the submission of the forum post saying "You have 30 min 08:39:11 that's a good idea 08:39:20 what do others think? 08:39:27 Why should you even get an editing period? I think it's only there because of moodle. But if you mess up, you could just delete the post & post it again. 08:39:43 I'm surprised we don't already have that message 08:39:46 richardm: it's useful to fix typos 08:39:47 we shouldn't make it too complicated. ;-) the editing possibility of a forum post is for small spelling mistakes, small additions etc. but not for major edits. that's when you write a new forum post. therefore, a simple message should suffice 08:40:14 And if you have less than $x minutes, the timer too? 08:40:24 richardm: can a normal user delete the post after the editing period? 08:40:38 Hm, maybe not, I don't knwo 08:40:46 i would not include a time. that sounds very much like exam time. 08:40:54 include a timer i meant 08:41:26 I think we probably should just indicate how much time left when editing page is open rather than doing complicated stuff 08:41:35 rkabalin_: agreed 08:41:35 #agree 08:41:46 Yeah - that would be good #agree 08:41:51 #agree 08:42:21 should i update the bug on the tracker? 08:42:25 #action rkabalin_ add time left indication to forum editing page 08:42:28 that'd be great 08:42:41 yes plese, and assign it to me 08:43:00 rkabalin_: you can remove the action item, since there's a bug for it already 08:43:41 fmarier: good question, probably not 08:43:58 how about that magic #undo ? :) 08:44:11 might only work for the previous line 08:44:26 undo only removes the last line I guess 08:44:29 #undo 08:44:35 #undo 08:44:35 Removing item from minutes: 08:44:36 let's try it :) 08:44:41 it worked! 08:44:59 it was, after all, the last line that starts with a # 08:45:14 good to know 08:45:17 cool, i think we can now move to the next item 08:45:39 #topic Status on code reviews [Francois] 08:45:50 ok, so first of all 08:45:59 #link https://reviews.mahara.org/ 08:46:08 (is that the right way to add links?) 08:46:27 yep 08:46:29 yes 08:46:42 so gerrit is running, but it's not 100% finished yet 08:46:47 though if the line starts with a link you don't necessarily need the #link 08:46:54 though it should work without #link as well 08:46:58 i will be testing it with richardm in the next few days 08:47:55 once it's ready, i'll post about it on the forum 08:48:03 #info Mahara code review #link https://reviews.mahara.org/ 08:48:08 BTW: #undo: Remove the last item from the meeting minutes. Only applies to commands which appear in the final output. (Chairs only.) from http://meetbot.debian.net/Manual.html 08:48:26 but basically, we will be making this repo read-only: http://gitorious.org/mahara/mahara 08:48:42 only the gerrit user will be pushing to it 08:48:59 developers will instead be pushing their code to a separate gerrit repo 08:49:15 and they'll get pushed to the real repo by gerrit once they have been reviewed 08:49:49 sounds good 08:50:13 because the main repo will turn read-only, i've created http://gitorious.org/mahara/mahara-shared for times when we need to collaborate on a branch 08:50:25 #info basically, we will be making this repo read-only: http://gitorious.org/mahara/mahara only the gerrit user will be pushing to it developers will instead be pushing their code to a separate gerrit repo and they'll get pushed to the real repo by gerrit once they have been reviewed 08:50:37 so if you want multiple devs to pull and push on a branch, you can use that 08:50:50 the main repo now only has the release branches and the master branch 08:51:32 the only other thing i wanted to say about gerrit is that you can all create your account now. the instructions are here: http://wiki.mahara.org/Developer_Area/Git_Repository_Policy 08:51:37 #info http://gitorious.org/mahara/mahara-shared to be used for devs collaboration 08:53:32 #info gerrit account instructions: http://wiki.mahara.org/Developer_Area/Git_Repository_Policy 08:53:43 right, so if nobody has questions, we can move to anitsirk's item 08:53:52 fmarier: All looking good 08:54:08 sounds good to me 08:54:21 if you want to play with gerrit, feel free to comment on the merge request i put there :) 08:54:35 https://reviews.mahara.org/1 08:54:47 #topic Documentation management 08:54:52 #idea the idea is to improve the mahara documentation. 08:54:53 #info currently, the documentation sits in the wiki and is not really updated. most information is very old and often only applicable for 1.2. craig made an effort to put 1.3 things into the user guide. however, i think the current system of doing documentation does not work very well and some re-thinking is necessary. 08:54:53 #info the way koha manages their documentation is interesting: have everything in git, use an xml editor and docbook to produce the documentation which has the output format html but can also be printed easily as pdf manual. 08:54:53 i like that approach because it allows the documentation to sit in one place and different output formats are generated easily. 08:55:39 thanks Kristina 08:55:47 I was just about to suggest having it in git and to use that approach 08:55:58 * fmarier would love to submit patches to the documentation manager using git-send-email :) 08:56:14 chris cormack, a colleague who is involved in the koha project, suggested to use asciidoc instead of the xml editor and docbook because it is easier, more readable and highly versatile. 08:56:14 #link http://www.methods.co.nz/asciidoc/ 08:56:15 It's something that we currently do for some of our internal docs using texinfo 08:56:15 another colleague, brenda wallace, suggested doxygen. 08:56:15 #link http://www.stack.nl/~dimitri/doxygen/ 08:56:15 doxygen is geared towards generating documentation directly from comments in the code. that would be an idea for a developer documentation but not for the user documentation. 08:56:15 #info: does anyone of you have any suggestions for a tool combination because you have already worked with one or like one in particular? so far, i have not made any changes and am still in the investigation phase, but lean towards trying out asciidoc. 08:56:21 that would be great, fmarier. 08:56:57 it's surprisingly readable: http://www.methods.co.nz/asciidoc/asciidoc.txt 08:57:06 (that's the source file) 08:57:09 the idea was to have it in git so that developers who use git all the time anyway, might submit something 08:57:30 fmarier: that's why chris suggested it instead of xml because you can actually read it and it's easy to write. 08:57:30 anitsirk: yeah doxygen is for API documentation, not for a user manual 08:57:56 should we consider it for a developer documentation? 08:57:59 the fact that it's not XML means that git diffs will actually be useful 08:58:07 just a question or consideration: what about translating documentation in other languages? 08:58:24 the japanese lang maintainer does that already, i think 08:58:31 i mean, i have too much work with translating mahara - there's no time for documentation... 08:58:35 anitsirk: API documentation is a very large task, but yes, something like doxygen makes sense 08:59:24 anzeljg: maybe there's a way to tag pages and include content from other languages 08:59:32 anitsirk or rangi: how is the koha manual translated? 08:59:33 in terms of the documentation content: i'd like to separate it into mahara pre 1.4 and mahara 1.4 and not combine everything in one because i think that will get too messy. 08:59:48 mhh. good question. i don't know actually. 09:00:05 but nicole's english manual is definitely the bible. 09:00:06 anitsirk: if it's in git, you can have a 1.3_STABLE branch as well as a master branch :) 09:00:19 oh yeah. :-) 09:00:24 so the manual repo would have the same branches as the code 09:00:47 * dobedobedoh afks for 10 minutes and wants to be around for httpswwwroot talking 09:00:56 i would also like to incorporate the "user generated tutorials" into the documentation so that they aren't separate anymore as many make very good screencasts. 09:01:04 fmarier: its docbook, people are doing it manually 09:01:14 hi rangi :-) 09:01:29 rangi: so using asciidoc would work the same way i guess 09:01:37 hi rangi 09:02:10 does anybody have a better suggestion than asciidoc? 09:02:14 if nobody has objections to asciidoc, i'd like to proceed with a trial that way and see what i'd have to do next, whom to ask for the set up etc. 09:02:41 sounds good to me 09:02:47 fine 09:02:54 fmarier: yep id imagine so 09:02:59 http://git.koha-community.org/gitweb/?p=kohadocs.git;a=tree 09:03:55 hi rkabalin_ 09:04:03 #action anitsirk proceed with asciidoc trial and come up with more info 09:04:24 sounds good to me. 09:04:33 anitsirk: you now have a git repo for it: http://gitorious.org/mahara/manual 09:04:45 i can assist with setup and initial pushing 09:04:52 and i know whom to ask if i have questions. :-) thanks fm 09:04:55 thansk fmarier 09:05:03 #info repo for mahara manual http://gitorious.org/mahara/manual 09:05:37 next item? 09:05:46 yep 09:05:52 #topic Proposing to license the Mahara wiki content under CC BY-SA 3.0 Unported [Francois] 09:05:56 fmarier: we had jenkins running xml validation on the docbook files too, im picking you can do the same with asciidoc 09:06:18 yeah it would be good to create a test suite for the user manual 09:06:30 it we can find a "lint" checker-type of program 09:07:10 ill ask the evergreen devs, they use asciidoc for their docs 09:07:18 awesome 09:07:18 * rangi will let you get back to your meeting now :) 09:07:29 hey, you are part of it, rangi :-) 09:07:41 rkabalin_: that looks like an action item for rangi ;-) 09:07:50 thanks for your input and for asking the evergreen guys 09:09:04 #action rangi to ask the evergreen guys if they have a test suite for their asciidoc manual 09:09:08 #action rangi ask evergreen devs about using asciidoc for docs 09:09:16 #undo 09:09:20 #undo 09:09:20 Removing item from minutes: 09:09:27 oops :) 09:09:31 fmarier: only the chair can undo :-) 09:09:35 ah good then 09:09:37 yep 09:09:57 alright, back to the wiki 09:10:31 i have proposed on the community forum that we license it under CC BY-SA which is the CC license closest to the license that the Mahara code is under 09:10:45 i have made a list of all contributors to the wiki 09:10:51 #agree with your proposal 09:11:04 * rkabalin_ I probably should have undo the previous topic command and enter it again since we continued discussion 09:11:05 i have 43 people who have made more than 1 non-triviall contribution to the wiki 09:11:38 basically i'm going to email all of them to ask for their permission 09:12:11 since nobody has objected publicly or privately 09:12:39 however, i could skip emailing all of you if you could just type #agree here :) 09:12:41 I objected privately :) 09:12:45 (just kidding) 09:12:53 #agree 09:12:53 sounds good. i guess that needs to be done as not everybody may have read the forum thread 09:12:55 #agree 09:13:00 #agree 09:13:06 #agree and did that privately if memory serves correctly ;) 09:13:50 anzeljg: yeah i think you did (one or two people did already but i forgot to write it down in my spreadsheet) 09:14:11 * dobedobedoh returns 09:14:47 dobedobedoh: do you agree to licensing the wiki under CC BY-SA ? 09:14:53 ok, is that everyone I guess 09:15:09 Yup 09:15:11 #agree :) 09:15:15 awesome 09:15:27 i have only 38 people to email now ;-) 09:16:12 now that dobedobedoh is back, we can move to the https item 09:16:31 Thanks for waiting! 09:16:34 however, i was hoping that inaki would be here 09:17:00 #action fmarier email 38 people to ask lisence permissions 09:17:12 because based on his last comment, i'm not sure whether he agrees or is angry about the proposal 09:17:23 i think he's cool with it 09:17:32 #topic Removal of httpswwwroot (bug 646713) [Francois] 09:17:34 ( we are talking about https://bugs.launchpad.net/mahara/+bug/646713 ) 09:18:51 the proposal for that bug is to get rid of https logins and encourage full https 09:18:56 as I mentioned on tracker, I agree that we should depricate httpswwwroot 09:19:16 And since I made the original suggestion, I think you can assume that I #agree 09:19:34 fmarier: you gave a good argument why partial https implemetation is not a good idea 09:20:09 so, I guess inaki would not object 09:20:37 we'll have to be careful about the upgrade 09:21:00 fmarier: Do you think it should go into 1.4? 09:21:09 dobedobedoh: i think so 09:21:12 good :) 09:21:22 lots of sites are switching to https these days 09:21:27 thanks to firesheep 09:21:37