Actions

Difference between revisions of "Proposals"

From Mahara Wiki

Line 19: Line 19:
 
{| width="100%" border="1" cellspacing="0" cellpadding="5" align="left" class="sortable"
 
{| width="100%" border="1" cellspacing="0" cellpadding="5" align="left" class="sortable"
 
|'''Features'''||'''Comments'''||'''Projected effort'''
 
|'''Features'''||'''Comments'''||'''Projected effort'''
 
 
|-
 
|-
 
|TinyMCE selector for choosing portfolio pages for linking them in the text||||small
 
|TinyMCE selector for choosing portfolio pages for linking them in the text||||small
Line 31: Line 30:
 
|Reduce number of clicks||ongoing||
 
|Reduce number of clicks||ongoing||
 
|-
 
|-
|Print to PDF||Formatting is the difficulty; side-effect: we would get thumbnails of pages that could be used for other purposes||medium to big
+
|Timeline / Page versioning||i.e. like a wiki so you can go back to previous versions of a page / entire portfolio; this is probably what is needed rather than implementing a wiki because a Mahara page could just be one page and doesn't have to consist of multiple columns||big to huge
|-
 
|Page versioning||i.e. like a wiki so you can go back to previous versions of a page / entire portfolio; this is probably what is needed rather than implementing a wiki because a Mahara page could just be one page and doesn't have to consist of multiple columns||big to huge
 
 
|-
 
|-
 
|Re-design of the page builder||(long-term) style changes, page itself as rich-text area and then drop blocks into that; make page layouts into a plugin type, i.e. have a traditional Mahara page, a blog page, etc.||huge
 
|Re-design of the page builder||(long-term) style changes, page itself as rich-text area and then drop blocks into that; make page layouts into a plugin type, i.e. have a traditional Mahara page, a blog page, etc.||huge
|-
 
|Drop-down menu as default||instead of tabbed navigation as default for the main menu - Abandonded in favor of re-designing the menu navigation in general||tiny
 
|-
 
|Re-designing the menu navigation||||big
 
 
|-
 
|-
 
|Etherpad  functionality||i.e. editing text collaboratively simultaneously||medium
 
|Etherpad  functionality||i.e. editing text collaboratively simultaneously||medium
Line 48: Line 41:
 
|-
 
|-
 
|[https://bugs.launchpad.net/mahara/+bug/1185188 "Copy page/collection" button] for users without an account to create a Leap2A file||||
 
|[https://bugs.launchpad.net/mahara/+bug/1185188 "Copy page/collection" button] for users without an account to create a Leap2A file||||
|-
 
|MNet service migration||to [[Developer_Area/Specifications_in_Development/MNet_replacement | replace Mnet]] with web services and a more modern authentication protocol; incl. bringing the web services plugin into core Mahara and implementing a [[Developer_Area/Specifications_in_Development/MNet_replacement/Connection_manager | connection manager]] to easily manage sites connecting to Mahara||big to huge
 
 
|-
 
|-
 
|Skin previewer||Switch between skins and quickly preview your page with the skin||medium
 
|Skin previewer||Switch between skins and quickly preview your page with the skin||medium
|-
 
|Integrate SAML SSO into Mahara||so that all necessary packages are installed and don't need to be set up separately||medium
 
 
|-
 
|-
 
|journal entry prompts||to facilitate scaffolding||medium
 
|journal entry prompts||to facilitate scaffolding||medium
Line 66: Line 55:
 
|-
 
|-
 
|Tag recommendations||tag recommendations based on what's on your page||big to huge
 
|Tag recommendations||tag recommendations based on what's on your page||big to huge
|-
 
|Implement patternlab.io or something similar||To have a living style library available for designers and developers to use to stay consistent||Done in Mahara 16.04 with the [http://manual.mahara.org/en/16.04/administration/styleguide.html#index-0 style guide]||
 
 
|-
 
|-
 
|performance profiling||Nigel already started on that||
 
|performance profiling||Nigel already started on that||
 
|-
 
|-
|More authentication plugins||see Janrain plugin; need to be able to limit e.g. GoogleApps domain||
+
|More authentication plugins||see Janrain plugin; need to be able to limit e.g. GoogleApps domain (maybe)||
|-
 
|Improve tagging UI||Done. use the “Auto-select” UI interface that we use for selecting multiple recipients of a message also for tags||small to medium
 
|-
 
|TinyMCE button to embed media from your portfolio||Done||small
 
|-
 
|Auto-select everywhere||Done, i.e. where it could replace more cumbersome interfaces, e.g. see tag selection||tiny
 
|-
 
|[https://bugs.launchpad.net/mahara/+bug/1408473 Upload a site logo]||Done; for “No institution”; already exists for other institutions, just not the site level||tiny
 
|-
 
|[https://bugs.launchpad.net/mahara/+bug/1385037 Mobile specific HTML tags]||Done. e.g. opens camera app, gallery app without needing mobile app||small
 
|-
 
|More responsive and updated themes||Done in Mahara 16.04||medium
 
|-
 
|Copy page button||Done, [https://bugs.launchpad.net/mahara/+bug/745418 copy pages, collections]||small
 
|-
 
|Drag and drop on mobile||Done||small
 
|-
 
|Sticky filters||[https://bugs.launchpad.net/mahara/+bug/1360535 '''Done'''] i.e. choose a setting on a page, e.g. wanting to filter your portfolio pages according to the last modified date and when you refresh the page that selection is still there and not reset||tiny
 
 
|}
 
|}
  
Line 106: Line 75:
 
* [[Developer_Area/Specifications_in_Development/Localised_Icons_Buttons|Localised Icons and Buttons]] (partially implemented in 1.6)
 
* [[Developer_Area/Specifications_in_Development/Localised_Icons_Buttons|Localised Icons and Buttons]] (partially implemented in 1.6)
 
* [[Developer_Area/Specifications_in_Development/Metadata_for_views_and_artefacts|Metadata for views and artefacts]]
 
* [[Developer_Area/Specifications_in_Development/Metadata_for_views_and_artefacts|Metadata for views and artefacts]]
* [[Developer_Area/Specifications_in_Development/Moodle_LTI_integration|Moodle LTI integration]]
 
 
* [[Developer_Area/Specifications_in_Development/More_flexible_use_of_profile_information|More flexible use of profile information]] - partly implemented in [[Developer_Area/Specifications_in_Development/More_flexible_use_of_profile_information_proposal_2|More flexible use of profile information proposal2]]
 
* [[Developer_Area/Specifications_in_Development/More_flexible_use_of_profile_information|More flexible use of profile information]] - partly implemented in [[Developer_Area/Specifications_in_Development/More_flexible_use_of_profile_information_proposal_2|More flexible use of profile information proposal2]]
 
* [[Developer_Area/Specifications_in_Development/Multipage_Views|Multipage Views]]
 
* [[Developer_Area/Specifications_in_Development/Multipage_Views|Multipage Views]]
Line 116: Line 84:
 
* [[Developer_Area/Specifications_in_Development/Objectionable_content_reporting|Objectionable content reporting]]
 
* [[Developer_Area/Specifications_in_Development/Objectionable_content_reporting|Objectionable content reporting]]
 
* [[Developer_Area/Specifications_in_Development/Page layout plugin type|Page layout plugin type]]
 
* [[Developer_Area/Specifications_in_Development/Page layout plugin type|Page layout plugin type]]
* [[Developer_Area/Specifications_in_Development/PDF_Export|PDF Export]]
 
 
* [[Developer_Area/Specifications_in_Development/Resume_and_CPD_integration|Resume and CPD integration]]
 
* [[Developer_Area/Specifications_in_Development/Resume_and_CPD_integration|Resume and CPD integration]]
 
* [[Developer_Area/Specifications_in_Development/Scheduled_Bulk_Feedback|Scheduled Bulk Feedback]]
 
* [[Developer_Area/Specifications_in_Development/Scheduled_Bulk_Feedback|Scheduled Bulk Feedback]]
Line 148: Line 115:
 
* [[Developer_Area/Specifications_in_Development/Acceptance_testing|Acceptance testing]]
 
* [[Developer_Area/Specifications_in_Development/Acceptance_testing|Acceptance testing]]
 
* [[Developer_Area/Specifications_in_Development/Search_2.0|Search 2.0]] (fulltext search implemented via Elasticsearch)
 
* [[Developer_Area/Specifications_in_Development/Search_2.0|Search 2.0]] (fulltext search implemented via Elasticsearch)
 +
* Re-designing the menu navigation (17.04)
 +
* MNet service migration: Implementation of LTI for SSO (17.04)
 +
* [[Developer_Area/Specifications_in_Development/Moodle_LTI_integration|Moodle LTI integration]]
 +
* Web services in core
 +
* Integrate SAML SSO into Mahara (16.10)
 +
* Print (to PDF) (17.04)
 +
* Implement patternlab.io or something similar (style guide in 16.04)
 +
* Improve tagging UI
 +
* TinyMCE button to embed images from your portfolio
 +
* Auto-select everywhere (where it could replace more cumbersome interfaces)
 +
* [https://bugs.launchpad.net/mahara/+bug/1408473 Upload a site logo]
 +
* [https://bugs.launchpad.net/mahara/+bug/1385037 Mobile specific HTML tags], e.g. opens camera app
 +
* More responsive and updated themes (16.04)
 +
* Copy page button
 +
* Drag and drop on mobile
 +
* [https://bugs.launchpad.net/mahara/+bug/1360535 Sticky filters]

Revision as of 06:03, 20 November 2017

This section contains specifications that are currently in development.  Once they are finalised, they should be moved either into the Roadmap temporarily, until the new feature is released, and then into User documentation.

What might be coming to Mahara

The Mahara project does not have a set roadmap for each release as that depends largely on features that the community implements and those that are being funded to implement, e.g. via a Mahara support company. Nevertheless, the Mahara release team at Catalyst has some items that it wishes to take a closer look for upcoming releases. You can view these items in the table below.

The items are listed more or less according to priority. Some items are fairly small whereas others are large pieces of work that may need to be split up over several releases once the specifications are clearer. The effort that is displayed is just an indication as the eventual implementation may be larger or smaller depending on the finalized specifications.

The list was inspired by the existing Mahara wishlist and the Blue sky thinking.

If you wish to contribute to funding any of these features, please let us know.


Features Comments Projected effort
TinyMCE selector for choosing portfolio pages for linking them in the text small
TinyMCE button for embedding iframes small
Default skins medium
Rethinking groupings of pages and collection organisation for yourself as well as grouping of pages for others to see huge
Reduce number of clicks ongoing
Timeline / Page versioning i.e. like a wiki so you can go back to previous versions of a page / entire portfolio; this is probably what is needed rather than implementing a wiki because a Mahara page could just be one page and doesn't have to consist of multiple columns big to huge
Re-design of the page builder (long-term) style changes, page itself as rich-text area and then drop blocks into that; make page layouts into a plugin type, i.e. have a traditional Mahara page, a blog page, etc. huge
Etherpad functionality i.e. editing text collaboratively simultaneously medium
Make the end-rendered Mahara pages prettier so that they don't look so blocky medium
“Like” button for pages medium
"Copy page/collection" button for users without an account to create a Leap2A file
Skin previewer Switch between skins and quickly preview your page with the skin medium
journal entry prompts to facilitate scaffolding medium
Export pages and collections on all levels i.e. group, institution, site and not only individual portfolio pages / collections small
Forum posts by email Moodle got it in 2.8 medium
AJAX preloading pages i.e. make front-end faster
Config file generator for easier way of setting up Mahara
Tag recommendations tag recommendations based on what's on your page big to huge
performance profiling Nigel already started on that
More authentication plugins see Janrain plugin; need to be able to limit e.g. GoogleApps domain (maybe)

 

Not done

Done