Difference between revisions of "MoodleNet/Roadmap"

Jump to: navigation, search
Line 13: Line 13:
=== 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 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.
==== Q1+2 ====
The first half of 2019 was focused on the '''Test''' and '''Iterate''' parts of the Product Lifecycle. We launched the first version of MoodleNet to a group of beta testers (~100 English-speaking, ~100 Spanish-speaking). The [https://blog.moodle.net/2019/why-test-moodlenet/ value proposition] we were testing was, ''“Do educators want to join communities to curate collections of resources?”''. By listening to users and [https://blog.moodle.net/2019/evolving-the-moodlenet-ui/ evolving the user interface] based on their input, we received useful feedback. The [https://blog.moodle.net/2019/what-we-learned-from-testing/ value proposition was validated], the tagline of '''Share. Curate. Discuss''' was chosen, and we understood the top 10 priorities from testers:
# Search for specific keywords and topics of interest.
# Easily find out when something has changed within a community they’ve joined, or a collection they’re following.
# Sort lists of communities and collections by more than ‘most recent’ (e.g. by number of collections or discussion threads)
# Tag communities, collections, and profiles, to make it easier to find related content.
# Upload resources to MoodleNet instead of just adding via URL.
# Indicate ‘resource type’ (e.g. ‘course’, ‘presentation’ or ‘plugin’)
# Send resources they discover on MoodleNet to their Moodle Core instance
# Add copyright information to resources and collections
# Easily rediscover useful resources they’ve discovered in collections they’re not following
# Access MoodleNet on their mobile devices
After the testing period, we [https://blog.moodle.net/2019/thanks-alex/ said goodbye] to our previous backend developer, and [https://blog.moodle.net/2019/welcome-karen-and-james/ welcomed two new members] to our team. We ran a workshop at the [https://blog.moodle.net/2019/what-we-learned-by-running-a-workshop-at-mootieuk19/ UK & Ireland MoodleMoot] where we received some extremely useful feedback, and attended the [https://blog.moodle.net/2019/ccsummit/ Creative Commons Summit] where we found links between our work and that of allies in the Open Education movement.
As a result of all this activity, we did a deep dive into [https://blog.moodle.net/2019/search-in-moodlenet/ search] in MoodleNet, as well as [https://blog.moodle.net/2019/rating-systems/ rating systems] and [https://blog.moodle.net/2019/voodoo-categorisation/ categorisation] of resources.
==== Q3 ====
The third quarter of 2019 has been focused on the '''Iteration''' part of the Product Lifecycle. There was some meta-level things to deal with in the form of planning to [https://blog.moodle.net/2019/update-sunsetting-moodle-dot-net/ sunset the existing moodle.net], work with the marketing team on a [https://blog.moodle.net/2019/new-moodlenet-page-at-moodle-com/ new MoodleNet page for moodle.com], and finalising the first version of MoodleNet's [https://blog.moodle.net/2019/dpia-consultation/ Data Protection Impact Assessment (DPIA)] for a community consultation.
More practically, the [https://blog.moodle.net/2019/user-agreement-covenant/ draft User Agreement and Covenant for Instance Administrators] helped us draw a line in the sand based on [https://www.theverge.com/2019/7/12/20691957/mastodon-decentralized-social-network-gab-migration-fediverse-app-blocking some issues] that the wider 'Fediverse' was having. In addition, we decided that MoodleNet would be focused on [https://blog.moodle.net/2019/free-cultural-works/ free cultural works] which differentiates it from other options.
We shared a [https://blog.moodle.net/2019/clickable-prototype/ clickable prototype] of a new user interface with the community for their feedback, and created a [http://bit.ly/2Z83Gr3 lightweight spec] based on it. A [https://blog.moodle.net/2019/late-august-update/ read-only version] of the basic features in the new UI is now live on our staging server. Our small, part-time team has been punching above its weight to get [https://blog.moodle.net/2019/planning-for-the-moodlenet-public-beta/ a long list of features] ready for a beta release in November. Before that, we will be running a [https://blog.moodle.net/2019/federation-testing-programme/ federation testing programme], which we announced during this quarter, receiving a good number of sign-ups.
Working with [https://eummena.org/blog/2019/eummena-moodle-partnership/ Eummena], a new Moodle Partner, we have developed a Moodle LMS plugin which allows users to search MoodleNet and import resources to courses. After review and and any further work, we envisage this will be made available first via the [https://moodle.org/plugins/ Moodle plugins directory], and then integrated as core Moodle LMS functionality in a future release.
==== Q4 ====
==== Q4 ====

Latest revision as of 14:23, 2 December 2019

<< Back to MoodleNet index


MoodleNet loadmap (Sept 2019).png


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.


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 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.

Must-have functionality still to deliver from our prioritisation grid includes the following, which are all works-in-progress:


  • 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


  • Image upload
  • Every @community is hyperlinked


  • Category tags
  • Every +mention is hyperlinked


  • Like resources
  • Add hashtags to added resources
  • Liked resources


  • Every @username is hyperlinked

Moodle Core integration:

  • Finalise plugin to pull resources from MoodleNet


  • Basic security audit


In 2020 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.


  • Upload resources
    • Add license to uploaded resources
  • Private communities/collections
  • More fine-grained user privacy controls and export functionality
  • An API for others to build upon MoodleNet’s core functionality
  • The ability to pay for a MoodleNet instance, hosted on MoodleCloud
  • Enhanced admin tools
    • 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


  • Unsplash integration
  • Private messaging
    • End-to-end encryption
    • In-depth security audit
  • Copy/fork a collection into another community
  • Events functionality
  • 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


  • Multiple accounts on a single instance (admin setting)
  • Fine-grained control over the user interface and notifications
  • Crowdfunding