Actions

Developer Area/Developer Meetings/77: Difference between revisions

From Mahara Wiki

< Developer Area‎ | Developer Meetings
No edit summary
No edit summary
Line 47: Line 47:
     <!-- Peter's items -->
     <!-- Peter's items -->
     <li>
     <li>
         <h5><u>Testing of trigger patches</u><i>Pushed to next meeting (awaiting Peter)</i></h5>
         <h5><u>Testing of trigger patches</u></h5>
 
        <i>Pushed to next meeting (awaiting Peter)</i>
     </li>
     </li>


Line 57: Line 57:
             <li>There is a wiki for a dedicated highlight plugin.</li>
             <li>There is a wiki for a dedicated highlight plugin.</li>
             <li>
             <li>
                 <b>Background</b>: He developed a plugin as part of a masters project completed for the University of Birkbeck. London. As part of the project, a lot of design documentation was generated to do plugin development and how it fits into the framework of Mahara.
                 <b>Background</b>: Guillaume developed a plugin as part of a masters project completed for the University of Birkbeck. London. As part of the project, he generated a lot of design documentation to do plugin development and how it fits into the framework of Mahara. This documentation could be submitted into the Mahara community.
                <li>Would like to submit this generated documentation to the Mahara community</li>
            </li>
            <li>
                Experience: The initial first step was well documented, but after that it was more complicated where it was required to select and unpick an existing plugin to understand how it worked first.
             </li>
             </li>
             <li>Generation of a lot of design documentation for creating plugins that could be submitted into the Mahara community. Might put something into Mahara.org.</li>
             <li>Note: Gregor had begun documentation for how to write third-party plugins as he wrote most of the plugins for Mahara. With the documentation, Gregor could review and even add to it. </li>
            <li>Commented that the first bit of Mahara was alright to understand but then had to unpick and would have appreciated more support documentation.</li>
         </ul>
         </ul>
     </li>
     </li>
    <li><h5><u>Documentation for writing 3rd party plugins(Gregor)</u></h5></li>
    <ul>
        <li>Started writing documentation for writing 3rd party plugins.</li>
        <li><u>TODO: </u>Catalyst to review Guillaume's design documentation.</li>
    </ul>


     <!-- Gridstack -->
     <!-- Gridstack -->
     <li><h5><u>Gridstack: exports and imports (Cecilia)</u></h5></li>
     <li><h5><u>Gridstack: What happens during export when page hasn't been converted yet? (Cecilia)</u></h5></li>
     <ul>
     <ul>
         <li>Mahara keeps the old layout when exporting  page that didn't use Gridstack.</li>
         <li>The new GridStack layout - A page with the old layout stays the same when exported. Upon importing, the page converts into the new layout.</li>
         <li>Upon importing that export, it will be installed and convert to work with Gridstck.</li>
         <li><h6>IE 11 - not compatible with GridStack</h6></li>
        <ul>
            <li>After regression testing, we encountered some issues with IE 11 not playing nice with new tech like Gridstack.</li>
            <li>We investigated a couple of issues and created patches for them. Those patches are in the next minor point release (date TBC). The code is already in the repository.</li>
            <li>Because IE 11 is on its way out and Microsoft Edge taking its place, we are thinking of removing the support for IE 11 in Mahara 20.04 onwards.</li>
            <li>
                <i>Matomo statistics for September 2019 to January 2020 on the demo site:</i>Chrome ( 46.5%), Chrome mobile (15%), Firefox (11%), Safari (9.7-7%), Microsoft Edge (3.9%), Internet Explorer (2.5%), another site: Chrome (67.3% ), Safari (4%),  Edge (4%), IE (1.1%)
            </li>
            <li>Internet explorer is the lesser-used browser. It seems that people use Microsoft Edge more than Internet explorer. It is trickier to work with standardised desktops.</li>
            <li>Standard universities seen over the past year use Chrome as their standard, IE and Edge are often still there on the Window Machine.</li>
        </ul>
     </ul>
     </ul>


Line 86: Line 92:
     <ul>
     <ul>
         <li>Usability improvements</li>
         <li>Usability improvements</li>
         <ul>
         <ol>
             <li>Language Switcher</li>
             <li>Language Switcher (already in Mahara core) - when you have several languages installed in your Mahara instance and also logged in, you can very quickly change the language. </li>
             <li>Group labelling for sorting -SWITCH (in testing stage)</li>
             <ol>
             <li>SmartEvidence</li>
              <li>Good Feedback: Mits, our Japanese partner, loves this feature and believes it is beneficial in his context</li>
         </ul>
            </ol>
            <li>Labels used to sort groups more quickly (in the last phase in testing) - functionality sponsored by SWITCH portfolio and one of the universities.</li>
             <li>Fixes to SmartEvidence editor - Cecilias has made some improvements and some in reviews, ready to test. We are removing some items to make it easier to look into the individual sections.</li>
         </ol>


         <li>Tech update</li>
         <li>Technical Updates: these are updates of libraries or need to change to a different library for technical reasons because of the ending of support or a better alternative for workflows or to keep up with new technology. </li>
         <ul>
         <ol>
            <li>Updating/switching libraries appropriately, keeping up to date</li>
          <li>One new technology is Mahara Mobile, which Doris is leading to refactor the app to React Native instead of React JS due to some technical problems that we had come across. Also, iOS wasn't supporting something that Cordova requires, therefore making it impossible to update our current app.</li>
            <li>End support for IE 11</li>
          <ul>
             <li>Mahara Mobile</li>
             <li>The aim is for feature parity and in the Mahara 20.04 release.</li>
            <li>20.04 + feature parity</li>
          </ul>
             <li>Library updates: Gulp, PHP 7.3 -> 7.4 (Rebecca), MySQL</li>
             <li>Library upgrades: Gulp, PHP 7.3 -> 7.4 (worked on by Rebecca), MySQL8 upgrade.</li>
             <li>Evonne is working to consolidate elements to improve consistency in styling</li>
             <li>Our designer Evonne is consolidating the elements in Mahara for more efficient themeing.</li>
             <li>Improving accessibility</li>
             <li>Heading doubles for accessibility</li>
         </ul>
         </ol>


         <li>New features (including usability):</li>
         <li>New features (including usability):</li>
Line 127: Line 136:


<h4>Action items</h4>
<h4>Action items</h4>
<ul>
    <li><b>ACTION: </b>Guillaume to submit documentation for 3rd party plugins for Mahara.org.</li>
</ul>

Revision as of 22:44, 14 February 2020

Agenda for the 77th Mahara developer meeting on Wednesday. 29 January 2019, 7:30 UTC

We will meet using Meet.Catalyst (a Catalyst staff member will initiate the call).

Our #mahara-dev channel on Freenode IRC will be our backup or in case there are problems with the web conferencing tool and we'll need to chat to resolve it. If you don't have an IRC client, you can join us using your web browser.

  • Chair: Cecilia Vela
  • Minute taker: Doris Tam

Agenda

  1. Items from the last meeting
    • Catalyst looking at possibilities of posting audio recordings of meetings online
    • Peter using Docker with Selenium to run Behat tests
    • Peter testing of trigger patches
    • Guillaume: Share plugin documentation with the Catalyst team for review. Best to send it to [email protected].
    • Kristina: Ask Cecilia what happens during export when page hasn't been converted yet
  2. Mahara 20.04 progress
  3. Next meeting and chair
  4. Any other business

Minutes

  1. Attendees
    • Cecilia Vela Gurovic from Catalyst IT in Wellington(meeting chair)
    • Doris Tam from Catalyst IT in Wellington (minute taker)
    • Ghada El-Zoghbi from Catalyst IT Australia in Sydney
    • Gregor Anzelj, Computer Science teacher, Mahara community member working on isolated institutions and portfolio moderation, Slovenia, Europe
    • Guillaume Nerzic, independent (HSBC) contribute plugins to Catalyst
    • Kristina from Catalyst IT in Wellington
    • Rebecca Blundell from Catalyst IT in Wellington
    • Robert Lyon from Catalyst IT in Wellington
  1. Catalyst looking at possibilities of posting audio recordings of meetings online
           Pushed to next meeting (awaiting Bob's feedback)
  2. Testing of trigger patches
           Pushed to next meeting (awaiting Peter)
  3. Share plugin documentation with the Catalyst team for review (Guillaume)
    • There is a wiki for a dedicated highlight plugin.
    • Background: Guillaume developed a plugin as part of a masters project completed for the University of Birkbeck. London. As part of the project, he generated a lot of design documentation to do plugin development and how it fits into the framework of Mahara. This documentation could be submitted into the Mahara community.
    • Experience: The initial first step was well documented, but after that it was more complicated where it was required to select and unpick an existing plugin to understand how it worked first.
    • Note: Gregor had begun documentation for how to write third-party plugins as he wrote most of the plugins for Mahara. With the documentation, Gregor could review and even add to it.
  4. Gridstack: What happens during export when page hasn't been converted yet? (Cecilia)
    • The new GridStack layout - A page with the old layout stays the same when exported. Upon importing, the page converts into the new layout.
    • IE 11 - not compatible with GridStack
      • After regression testing, we encountered some issues with IE 11 not playing nice with new tech like Gridstack.
      • We investigated a couple of issues and created patches for them. Those patches are in the next minor point release (date TBC). The code is already in the repository.
      • Because IE 11 is on its way out and Microsoft Edge taking its place, we are thinking of removing the support for IE 11 in Mahara 20.04 onwards.
      • Matomo statistics for September 2019 to January 2020 on the demo site:Chrome ( 46.5%), Chrome mobile (15%), Firefox (11%), Safari (9.7-7%), Microsoft Edge (3.9%), Internet Explorer (2.5%), another site: Chrome (67.3% ), Safari (4%), Edge (4%), IE (1.1%)
      • Internet explorer is the lesser-used browser. It seems that people use Microsoft Edge more than Internet explorer. It is trickier to work with standardised desktops.
      • Standard universities seen over the past year use Chrome as their standard, IE and Edge are often still there on the Window Machine.
  5. Mahara 20.04 progress (Kristina) Roadmap-[1]
    • Usability improvements
      1. Language Switcher (already in Mahara core) - when you have several languages installed in your Mahara instance and also logged in, you can very quickly change the language.
        1. Good Feedback: Mits, our Japanese partner, loves this feature and believes it is beneficial in his context
      2. Labels used to sort groups more quickly (in the last phase in testing) - functionality sponsored by SWITCH portfolio and one of the universities.
      3. Fixes to SmartEvidence editor - Cecilias has made some improvements and some in reviews, ready to test. We are removing some items to make it easier to look into the individual sections.
    • Technical Updates: these are updates of libraries or need to change to a different library for technical reasons because of the ending of support or a better alternative for workflows or to keep up with new technology.
      1. One new technology is Mahara Mobile, which Doris is leading to refactor the app to React Native instead of React JS due to some technical problems that we had come across. Also, iOS wasn't supporting something that Cordova requires, therefore making it impossible to update our current app.
        • The aim is for feature parity and in the Mahara 20.04 release.
      2. Library upgrades: Gulp, PHP 7.3 -> 7.4 (worked on by Rebecca), MySQL8 upgrade.
      3. Our designer Evonne is consolidating the elements in Mahara for more efficient themeing.
      4. Heading doubles for accessibility
    • New features (including usability):
      • SAML improvements (auto-assign roles based on IDP, auto-setup of an institution on IDP login
      • Default login for auto admin on Mahara site
      • PDF exports: comine all exports into one
    • Issue resolution
    • Infrastructure updates - some already processed:
      • Proof of concept for testing in the cloud (Aatharsh, Mahara intern)that allows testers to get set up quickly.
      • Manual updated to Python 3 to generate manual files.
      • Improvement in the running of Behat in Jenkins to run the entire suite only overnight and process parts of it for more quick and efficient testing
  6. Changing 'Users' ->'People'(Kristina)
    Translators: translations may not always be needed as the word doesn't have the same connotations in other languages than English.

Action items

  • ACTION: Guillaume to submit documentation for 3rd party plugins for Mahara.org.
Retrieved from ‘https://wiki.mahara.org/index.php?title=Developer_Area/Developer_Meetings/77&oldid=11006’