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

One thought on “Planning for the MoodleNet public beta

Leave a Reply

Your email address will not be published. Required fields are marked *