#mahara-dev Meeting
Meeting started by rkabalin at 20:03:47 UTC
(full logs).
Meeting summary
-
- anitsirk is Kristina Hoeppner, Catalyst IT,
Wellington, NZ (anitsirk,
20:04:12)
- Andrew Nicols, Lancaster University, UK
(dobedobedoh,
20:04:28)
- Ruslan Kabalin - Lancaster University,
UK (rkabalin,
20:04:33)
- richardm Richard Mansfield, Catalyst IT
(richardm,
20:04:37)
- is Melissa Draper, Catalyst IT (elky,
20:04:48)
- Items from last meeting (rkabalin, 20:05:29)
- 3. melissa/elky to publish a dev forum post
about the 6 monthly release cycle (rkabalin,
20:06:55)
- https://mahara.org/interaction/forum/topic.php?id=4547
(anitsirk,
20:08:12)
- AGREED: Mahara
release cycle is set to fixed period of 6 month (rkabalin,
20:24:25)
- the first release in the new shedule will be in
October (rkabalin,
20:25:12)
- AGREED: minor point
release after security fix or major bug (rkabalin,
20:32:43)
- Discuss/decide on style guidelines for CSS https://reviews.mahara.org/#/c/1098/ Melissa/Hugh (rkabalin, 20:35:09)
- Google Apps block in Mahara 1.6? cf. https://mahara.org/interaction/forum/topic.php?id=4641 (Kristina) (rkabalin, 20:37:31)
- : the gist: i was wondering if we still need
the google apps block in 1.6 now that we have the safeiframe feature
and the admin interface to easily add any iframe base url (1.6
feature). (anitsirk,
20:38:35)
- is Hugh Davenport, Catalyst IT Ltd (hughdavenport,
20:49:26)
- ACTION: elky look
into removing google apps block from the core (rkabalin,
20:51:21)
- https://developers.google.com/safe-browsing/
(elky,
20:57:50)
- ACTION: safeiframe
xss vulnerabilities discussion move to next meeting (rkabalin,
21:00:05)
- Continued: Discuss/decide on style guidelines for CSS https://reviews.mahara.org/#/c/1098/ Melissa/Hugh (rkabalin, 21:00:51)
- we need volunteers to edit the code guidelines
wiki page for other langs (rkabalin,
21:05:54)
- http://en.wikipedia.org/wiki/Rules_lawyer
(elky,
21:07:48)
- ACTION: elky/hughdavenport update code guidelines and extend
it to other than php (rkabalin,
21:09:56)
- hughdavenport: Discuss how long we support releases for and/or the posibility of a LTS release (rkabalin, 21:10:47)
- discussing possibility to support release for 2
years, will be phased in from next release. Re. existing, we drop
1.4 when 1.6 comes, 1.5 stays 2 years, 1.6 2 years, etc, optinally
1.5 can stay for 18 months (rkabalin,
21:21:44)
- AGREED: support 3
versions back, 1.4 will go with 1.6, 1.5 will go with 1.8, 16 with
1.9 (rkabalin,
21:30:30)
- next meeting / Chair (rkabalin, 21:30:52)
- AGREED: next dev
meeting Tuesday, July 31st, 7:30 UTC (rkabalin,
21:41:11)
- http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120731T0730
(hughdavenport,
21:42:52)
- AGREED: elky chair
the next meeting (to be safe) (rkabalin,
21:46:09)
- any other business (rkabalin, 21:46:28)
Meeting ended at 21:53:18 UTC
(full logs).
Action items
- elky look into removing google apps block from the core
- safeiframe xss vulnerabilities discussion move to next meeting
- elky/hughdavenport update code guidelines and extend it to other than php
Action items, by person
- elky
- elky look into removing google apps block from the core
- elky/hughdavenport update code guidelines and extend it to other than php
- hughdavenport
- elky/hughdavenport update code guidelines and extend it to other than php
People present (lines said)
- elky (126)
- rkabalin (109)
- anitsirk (79)
- hughdavenport (68)
- dobedobedoh (37)
- richardm (12)
- maharameet (3)
Generated by MeetBot 0.1.4.