MoodleNet/Roadmap: Difference between revisions

Latest revision as of 16:01, 25 February 2020

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)

@@ Line 2: / Line 2: @@
 ----
-[[File:tasty-cupcake.png|right|frameless|200px]]
 == Roadmap ==
-'''''Note:''' this is a work in progress to create a high-level overview of the MoodleNet project. For more granular detail, please check out the [https://gitlab.com/groups/moodlenet/-/milestones milestones in our GitLab issue tracker].
+=== 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 [https://blog.moodle.net/2018/retrospective/ 2018 retrospective post] on the MoodleNet blog.
-=== Q1 2018 ===
-Conceive
-In this phase, we researched our options and came up with a high-level goal for a platform that will be of immediate use to educators. This involved talking to a lot of educators and technologists, and looking to other platforms and services for [https://docs.moodle.org/dev/MoodleNet/inspiration inspiration].
-=== Q2 2018 ===
-Plan
-This phase focused on planning how to achieve our high-level goal, deciding on the functionality it should have. We ran a [https://docs.moodle.org/dev/MoodleNet/Design_Sprint design sprint] to ensure we had a coherent plan focused on developing a Minimum Viable Product (MVP). We also hired Mayel, our [https://blog.moodle.net/2018/welcome-mayel/ Technical Architect] to ensure that we make the correct [https://docs.moodle.org/dev/MoodleNet/tech technical decisions].
-=== Q3 2018 ===
-Develop
-In this phase we developed prototypes and worked with [https://outlandish.com Outlandish] on the [https://docs.moodle.org/dev/MoodleNet/Front-end_dev_workshop front-end development]. We hired Alex, a [https://blog.moodle.net/2018/introducing-alex/ backend developer], who built out the crucial plumbing using [https://docs.moodle.org/dev/MoodleNet/tech/stack Elixir].
-=== Q4 2018 ===
+=== 2019 ===
-Iterate
+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.
-This phase was about iterating existing designs and approaches so we could be laser-focused on producing something of value to educators. We onboarded Ivan as our [https://blog.moodle.net/2018/say-hello-to-ivan/ designer and front-end developer], and brought together the front-end and backend development work. We did some early testing around the [https://blog.moodle.net/2018/sign-up-feedback/ sign-up process], and re-imagined it to ensure there's no blockers for testing.
+=== 2020 ===
+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).
------
+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 2019 ===
+==== Q1 ====
-Test
+* Moodle LMS integration
+* Federation testing
+* Resource uploading
+* Moderation by admins
+* [https://ux.stackexchange.com/questions/11998/what-is-a-toast-notification#12000 Toast notifications]
-We're scheduled to launch the first version of MoodleNet to a group of beta testers in January 2019. Our plan is to recruit around 100 existing Moodle users to test the platform, and rapidly iterate the platform based on their feedback. We'll then give them invites to share with friends and colleagues, meaning we grow organically and sustainably.
+==== Q2 ====
+* User testing (on Moodle HQ-run instances) - ''including data export and deletion''
+* Extensible architecture
+* Tagging and categorisation
+* Roles and access controls
+* Push notifications
-In addition, we will be working on testing federation so that MoodleNet instances can communicate with one another. This will involve setting up a HQ-run API-as-a-service, which also needs testing.
+==== Q3 ====
+* Private communities/collections
+* Direct messaging
+* Collaborative blocklists
+* Theming
+* Display Open Badges on user profiles
-=== Q2 2019 ===
+==== Q4 ====
-Beta launch
+* Share resource from Moodle LMS to MoodleNet collection
+* Request resources
+* Moodle HQ provided cloud hosting for MoodleNet
+* Social sign-in
+* User-requested extensions & improvements
-Once we've tested both the value proposition and federation, we'll double-down on fixing bugs and responding to user needs before opening registrations. During this quarter we aim to develop a plugin to allow users to send collections from MoodleNet to courses in Moodle Core.
+=== 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)

Documentation