Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

MoodleNet/Roadmap: Difference between revisions

From MoodleDocs
No edit summary
No edit summary
Line 4: Line 4:


== Roadmap ==
== Roadmap ==
[[File:MoodleNet_loadmap_(Sept_2019).png|650px]]


=== 2018 ===
=== 2018 ===
Line 12: Line 10:


=== 2019 ===
=== 2019 ===
Our main aim for 2019 is to ensure that we carry out extensive testing of both MoodleNet's value proposition and ability to set up federated instances, before delivering a public beta.
Our main aim for 2019 was to ensure that we carry out extensive testing of both MoodleNet's value proposition and ability to set up federated instances, before delivering a version of MoodleNet for internal testing.


==== Q4 ====
=== 2020 ===
Our plan for the final quarter of 2019 is to focus on the '''Launch''' part of the Product Lifecycle. At the Global Moot in Barcelona at the end of November we will announce the beta version of MoodleNet, ready for early adopters to start using.
This year, we aim to build out the functionality and features of MoodleNet based on the recommendations from the original [https://docs.moodle.org/dev/MoodleNet_whitepaper white paper], feedback from the community (via [https://changemap.co/moodle/moodlenet Changemap], and our [https://blog.moodle.net/2019/planning-for-the-moodlenet-public-beta/ prioritisation grid] (August 2019).
 
'''Must-have''' functionality still to deliver from our [https://blog.moodle.net/2019/planning-for-the-moodlenet-public-beta/ prioritisation grid] includes the following, which are all works-in-progress:
 
Instances:
* Federation with other instances
* Connect to HQ ‘mothership’
* Search across federated instances
* Flags/reporting
* MVP admin dashboard
* Sign-up page (username/password)
* Open to browse without signing in
 
Communities:
* Image upload
* Every @community is hyperlinked
 
Collections:
* Category tags
* Every +mention is hyperlinked


Resources:  
We need to be responsive to users while thinking strategically about the order in which to build the following. We need to balance features that users demand and functionality that ensure MoodleNet is sustainable. With our current budget and resourcing, we are prioritising:
* Like resources
* Add hashtags to added resources
* Liked resources


Users:
==== Q1 ====
* Every @username is hyperlinked
* Moodle LMS integration
* Federation testing
* Resource uploading
* Moderation by admins
* [https://ux.stackexchange.com/questions/11998/what-is-a-toast-notification#12000 Toast notifications]


Moodle Core integration:
==== Q2 ====
* Finalise plugin to pull resources from MoodleNet
* User testing (on Moodle HQ-run instances) - ''including data export and deletion''
* Extensible architecture
* Tagging and categorisation
* Roles and access controls
* Push notifications


Misc.
==== Q3 ====
* Basic security audit
 
-----
 
=== 2020 ===
In 2020 we aim to build out the functionality and features of MoodleNet based on the recommendations from the original [https://docs.moodle.org/dev/MoodleNet_whitepaper white paper], feedback from the community (via [https://changemap.co/moodle/moodlenet Changemap], and our [https://blog.moodle.net/2019/planning-for-the-moodlenet-public-beta/ prioritisation grid] (August 2019).
 
We need to be responsive to users while thinking strategically about the order in which to build the following. We need to balance features that users demand and functionality that ensure MoodleNet is sustainable.
 
==== Q1+2 ====
* Upload resources
** Add license to uploaded resources
* Private communities/collections
* Private communities/collections
* More fine-grained user privacy controls and export functionality
* Direct messaging
* An API for others to build upon MoodleNet’s core functionality
* Collaborative blocklists
* The ability to pay for a MoodleNet instance, hosted on MoodleCloud
* Theming
* Enhanced admin tools
* Display Open Badges on user profiles
** Analytics for instance administrators
* UX
** Social sign-in
** Related communities/collections
** Sort/filter listed resources
** Auto-complete hashtags
** Invite other people to create a MoodleNet profile
** Sort/filter ‘My MoodleNet’ page


==== Q3+4 ====
==== Q4 ====
* Unsplash integration
* Share resource from Moodle LMS to MoodleNet collection
* Private messaging
* Request resources
** End-to-end encryption
* Moodle HQ provided cloud hosting for MoodleNet
** In-depth security audit
* Social sign-in
* Copy/fork a collection into another community
* User-requested extensions & improvements
* Events functionality
* [https://blog.moodle.net/2018/what-is-emoji-id/ Emoji ID]
* Query 3rd-party repositories
* Request a resource
* Build out user profiles, including the ability to display digital credentials
** Add interests (based on hashtags)
** Open Badges on profiles
** Add other users to a contact list


=== 2021 ===
=== 2021 ===
 
* Events/meet-ups
* Multiple accounts on a single instance (admin setting)
* Communities can define their own taxonomies
* Fine-grained control over the user interface and notifications
* Crowdfunding resources into existence
* Crowdfunding
* Version control for OER (incl. forking and merging)
* Uploading videos (integration with third-party services)

Revision as of 16:01, 25 February 2020

<< Back to MoodleNet index

Roadmap

2018

The first year of the MoodleNet project focused on the Conceive, Plan, and Develop parts of the Product Lifecycle. An overview of what we achieved can be found in this 2018 retrospective post on the MoodleNet blog.

2019

Our main aim for 2019 was to ensure that we carry out extensive testing of both MoodleNet's value proposition and ability to set up federated instances, before delivering a version of MoodleNet for internal testing.

2020

This year, we aim to build out the functionality and features of MoodleNet based on the recommendations from the original white paper, feedback from the community (via Changemap, and our prioritisation grid (August 2019).

We need to be responsive to users while thinking strategically about the order in which to build the following. We need to balance features that users demand and functionality that ensure MoodleNet is sustainable. With our current budget and resourcing, we are prioritising:

Q1

  • Moodle LMS integration
  • Federation testing
  • Resource uploading
  • Moderation by admins
  • Toast notifications

Q2

  • User testing (on Moodle HQ-run instances) - including data export and deletion
  • Extensible architecture
  • Tagging and categorisation
  • Roles and access controls
  • Push notifications

Q3

  • Private communities/collections
  • Direct messaging
  • Collaborative blocklists
  • Theming
  • Display Open Badges on user profiles

Q4

  • Share resource from Moodle LMS to MoodleNet collection
  • Request resources
  • Moodle HQ provided cloud hosting for MoodleNet
  • Social sign-in
  • User-requested extensions & improvements

2021

  • Events/meet-ups
  • Communities can define their own taxonomies
  • Crowdfunding resources into existence
  • Version control for OER (incl. forking and merging)
  • Uploading videos (integration with third-party services)
Retrieved from "https://docs.moodle.org/dev/index.php?title=MoodleNet/Roadmap&oldid=56956"
Powered by MediaWiki