Actions

Difference between revisions of "Developer Area/Developer Meetings/29"

From Mahara Wiki

< Developer Area‎ | Developer Meetings
 
Line 22: Line 22:
 
### Dinamical "Progress bar" based on Institution selected preferences
 
### Dinamical "Progress bar" based on Institution selected preferences
 
### "Cookie directive" plugin, possibly merged into core
 
### "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
+
### 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)
Second part of above bug uld 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
 
### 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