Developer Area/Developer Meetings/31

From Mahara Wiki

< Developer Area‎ | Developer Meetings
Revision as of 08:01, 24 March 2014 by Anzeljg (talk | contribs)

Agenda for the 31st Mahara developer meeting on Thursday, 27 March 2014 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: Kristina Hoeppner


  1. Items from last meeting
  2. Whitespace changes in patches (kabalin)
  3. Usability (anzeljg)
    1. Choose internal image in TinyMCE without attaching it first. (See related bugs: Bug #1038580 and Bug #1235569) This applies to:
      • Adding images from Mahara to Journal posts
      • Adding attached images to Textboxes: if user adds an image and want to embed that image into a textbox content he/she is unable to do so.
    2. Display name on publicaly available pages: don't show "by" or don't show name at all. (See similar bug: Bug #548021)
    3. Group journals vs. ability for users to sheir their journals with the group. (See related bugs: Bug #833583 and Bug #547332)
    4. Multilinguality of Mahara
    5. Finding or searching for pages shared with me (if there are thousands of those pages and posiblly a lot of pages have the same title)
    6. Copying of Textboxes should create real copies not only linked texboxes
    7. Better tag support:
      1. On the blocktype level: For example, when adding images it would be nice if user could select tag and all images that contain that tag they would be displayed (added to page) or the user would have the possibility to choose among taged ones, which of them to add to page
      2. On the page level: When creating new page, if user could select existing tag, all the artefacts (matching blocktypes) that contain that tag would be randomly (or in some order) added to the page. Then the user would rearrange them or delete them.
    8. Creating groups:
      1. There are a lot of settings even for experienced users? Is it possible to give users some simple group definition on buttons (e.g. Create closed group, Create open group, Create semi-open group, etc.). Upon clicking the button relevannt check boxes would be already ticked or un-ticked...
      2. Creating groups without e.g. group pages, group files, etc. Sometimes those are not needed (especially with younger students).
    9. Members of the group should be listed as admin (first), tutors (second) and members (last). Currently tutors and members are mixed up...
  4. Core developer applications: Jono Mingard, Yuliya Bozhko, Ghada El-Zoghbi
  5. Next meeting and chair
  6. Any other business