Actions

Developer Area/Developer Meetings/29: Difference between revisions

From Mahara Wiki

< Developer Area‎ | Developer Meetings
No edit summary
No edit summary
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Agenda for the 29th Mahara developer meeting on [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131205T08&p1=1440 Thursday, 5 December 2013 at 8:00 UTC]
Agenda for the 29th Mahara developer meeting on [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131205T08&p1=1440 Thursday, 5 December 2013 at 8:00 UTC]
The developer meetings are held on IRC in the #mahara-dev channel. An IRC bot will be used to take minutes of these meetings and agendas made available on these pages before-hand.
'''If you don't have an IRC client, you can [http://webchat.freenode.net/?channels=mahara-dev join us using your web browser].'''


Chair: Aaron Wells
Chair: Aaron Wells
Line 9: Line 13:
# Drop support for MySQL 5.1 in Mahara 1.9
# Drop support for MySQL 5.1 in Mahara 1.9
## For 1.8 we claim to support MySQL 5.1 or later, but all the devs are actually running 5.5 or later. So, since 5.5 will have been in a stable release for 4 years by the time 1.9 comes out, we should just raise the minimum supported version to 5.5.
## For 1.8 we claim to support MySQL 5.1 or later, but all the devs are actually running 5.5 or later. So, since 5.5 will have been in a stable release for 4 years by the time 1.9 comes out, we should just raise the minimum supported version to 5.5.
## If we don't want to drop 5.1 completely, we should consider requiring 5.1.6 or later, because 5.1.6 makes the trigger creation permissions a bit more sensible: https://bugs.launchpad.net/mahara/+bug/1237198/comments/8
# Plans & priorities for Mahara 1.9
# Plans & priorities for Mahara 1.9
## Some of the things the Catalyst team is looking at for 1.9 are:
## Some of the things the Catalyst team is looking at for 1.9 are:
Line 14: Line 19:
### Accessibility (though after consulting with our accessibility tzar we've determined that non-JS operation is not required by modern accessibility standards)
### Accessibility (though after consulting with our accessibility tzar we've determined that non-JS operation is not required by modern accessibility standards)
### Upstreaming third-party "Sent Messages" and Inbox improvements
### Upstreaming third-party "Sent Messages" and Inbox improvements
## Features funded by Arnes which could go into 1.9 (anzeljg):
### Dinamical "Progress bar" based on Institution selected preferences
### "Cookie directive" plugin, possibly merged into core
### Social site addresses in user's profile (e.g.: Facebook, Twitter, LinkedIn, Pinterest, Instagram, Foursquare, etc.): https://bugs.launchpad.net/mahara/+bug/605749 Second part of above bug could address new Europass HeadlineTypeLabelType element (see: http://interop.europass.cedefop.europa.eu/data-model/xml-resources/v3.0.1/schema/europass-xml-schema-doc-v3.0.1.pdf - end of page 37, beginning of page 38)
### Adding functionality to place comment/feedback on each individual block on a page
# Next meeting and chair
# Next meeting and chair
# Any other business
# Any other business

Latest revision as of 09:03, 3 December 2013

Agenda for the 29th Mahara developer meeting on Thursday, 5 December 2013 at 8:00 UTC

The developer meetings are held on IRC in the #mahara-dev channel. An IRC bot will be used to take minutes of these meetings and agendas made available on these pages before-hand.

If you don't have an IRC client, you can join us using your web browser.

Chair: Aaron Wells

Agenda:

  1. Items from last meeting
    1. The "Choose a skin" contest
  2. Drop support for MySQL 5.1 in Mahara 1.9
    1. For 1.8 we claim to support MySQL 5.1 or later, but all the devs are actually running 5.5 or later. So, since 5.5 will have been in a stable release for 4 years by the time 1.9 comes out, we should just raise the minimum supported version to 5.5.
    2. If we don't want to drop 5.1 completely, we should consider requiring 5.1.6 or later, because 5.1.6 makes the trigger creation permissions a bit more sensible: https://bugs.launchpad.net/mahara/+bug/1237198/comments/8
  3. Plans & priorities for Mahara 1.9
    1. Some of the things the Catalyst team is looking at for 1.9 are:
      1. Automated testing
      2. Accessibility (though after consulting with our accessibility tzar we've determined that non-JS operation is not required by modern accessibility standards)
      3. Upstreaming third-party "Sent Messages" and Inbox improvements
    2. Features funded by Arnes which could go into 1.9 (anzeljg):
      1. Dinamical "Progress bar" based on Institution selected preferences
      2. "Cookie directive" plugin, possibly merged into core
      3. Social site addresses in user's profile (e.g.: Facebook, Twitter, LinkedIn, Pinterest, Instagram, Foursquare, etc.): https://bugs.launchpad.net/mahara/+bug/605749 Second part of above bug could address new Europass HeadlineTypeLabelType element (see: http://interop.europass.cedefop.europa.eu/data-model/xml-resources/v3.0.1/schema/europass-xml-schema-doc-v3.0.1.pdf - end of page 37, beginning of page 38)
      4. Adding functionality to place comment/feedback on each individual block on a page
  4. Next meeting and chair
  5. Any other business
Retrieved from ‘https://wiki.mahara.org/index.php?title=Developer_Area/Developer_Meetings/29&oldid=4931’