Planning for the MoodleNet public beta

In the spirit of working openly, we’d like to share a MoSCoW prioritisation grid for the public beta release of MoodleNet in November 2019. While any project is subject to changing priorities as it progresses, this is where we are in early August.

For those that prefer a more accessible text-based version, please see below.


MUST

Instances:

  • Federation with other instances
  • Connect to HQ ‘mothership’
  • Search across federated instances
  • Discover page
  • My MoodleNet
  • Profiles
  • Flags/reporting
  • Moderation tools
  • Sign-up page (username/password)
  • Open to browse without signing in

Communities:

  • Image upload
  • Join/create/edit/leave a community
  • Every @community is hyperlinked

Collections:

  • Category tags
  • Create/edit a collection
  • Every +mention is hyperlinked

Resources:

  • Like resources
  • Add resource via URL
  • Add hashtags to added resources

Profiles:

  • Bio & links
  • Avatar
  • Header image
  • User timeline
  • Joined communities
  • Followed collections
  • Liked resources

Users:

  • Every @username is hyperlinked
  • Unique usernames

Moodle Core integration:

  • Plugin to pull resources from MoodleNet

Misc.

  • Basic security audit

SHOULD

Instances:

  • Help pages
  • Interoperability with other ActivityPub apps
  • Blocklists

Communities:

  • Share link to community 

Collections:

  • Hashtags 
  • Pinned resources
  • Share link to collection

Resources:

  • Upload resources
  • Add licence to uploaded resources

Profiles:

  • Follow other users

Users:

  • Notifications if mentioned within a community
  • Receive weekly emails about recent activity

COULD

Instances:

  • Analytics
  • Sign-up page (social accounts)

Communities:

  • Related communities

Collections:

  • Related collections
  • Sort/filter listed resources

Resources:

  • Auto-complete hashtags

Profiles:

  • Add other users to a contact list
  • Invite other people to create a MoodleNet profile
  • Add interests (based on hashtags)

Users:

  • Sort/filter ‘My MoodleNet’

Misc.

  • In-depth security audit

WON’T

  • Private communities / collections
  • Request a resource
  • Copy/fork a collection into another community
  • Events functionality
  • Emoji ID
  • Open Badges on profiles
  • Query 3rd-party repositories

MoodleNet 0.3 alpha update

Update: check out this five-minute overview video on YouTube!

This slideshow requires JavaScript.

As MoodleNet progresses and the team get into more of a rhythm, we’ve started working in two-week sprints. For the next few weeks, up to the beta release at the UK & Ireland MoodleMoot, we have plenty to do!

Earlier this week we released MoodleNet v0.3 alpha in preparation for inviting a new cohort of testers. It includes the following new functionality, UI tweaks, and bug fixes:

Functionality added

  • Collection-level discussions
  • ‘Profile & settings’ to update name, description, and avatar
  • Guide to Markdown next to text input boxes

UI tweaks

  • Tweaks to fonts and colours to improve accessibility
  • New approach to discussions, which now act more like threads
  • List of communities indicates number of collections contained by each

Bug fixes

  • No longer have to refresh to see added community/collection
  • Can see all communities again (fixed pagination)

We’ve removed edit functionality from MoodleNet at the moment in preparation for moderation. In future, you’ll be able to edit and delete comments and resources you add, or those in a community you moderate.

Given the amount of time between now and the beta launch at the UK Moot, we’re going to focus on what we consider to be essential to the core value proposition of MoodleNet:

  1. Federation — the ability to have separate instances of MoodleNet that can communicate with one another.
  2. Mobile view — MoodleNet accessible and usable on mobile devices.
  3. Moodle Core integration — add a resource from MoodleNet to a course in a Moodle course.

Thank you to our testers, who are doing a great job of asking questions, reporting bugs, suggesting functionality, and filling in surveys!