Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
Meta
Meta
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 125
    • Issues 125
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • MoodleNet
  • MetaMeta
  • Wiki
  • HQ user testing plan

Last edited by Doug Belshaw Mar 30, 2020
Page history

HQ user testing plan

Note: this plan will increase in specificity once we have completed Federation testing


Once we have completed the Federation testing and have both fixed any technical issues and ensured admin-based moderation is working properly, our full focus will be on the HQ user testing milestone.

By 'HQ user testing' we mean that we will be testing with end users on MoodleNet instance(s) run by Moodle HQ. We want to test, at the very least, the following:

  • Integration with Moodle LMS
  • Moderation of communities (i.e. by mods not admins)
  • Notifications
  • Exporting personal data
  • Tagging collections and resources

We need to decide whether we want to connect this milestone to the crowdfunding plan. If so, then backing MoodleNet at a particular tier would mean early access to HQ-run instance(s).

Either way, we need to ensure that there is content available when people first use MoodleNet, perhaps via the Moodle LMS integration. Once we've decided on the link between the crowdfunder and this milestone, then we can plan out a focused period of time to get that content added/created.

Broadly, there are several ways of doing this, including making it into a competition, gamifying it, or deputising people to be in charge of different subject areas. We should ask the community for their ideas, too.

Clone repository
  • Federation testing plan
  • HQ user testing plan
  • How to file bugs
  • List of intentions of MoodleNet users (verb based)
  • Localisation
  • OER metadata
  • Policies by user "rank"
  • Taxonomies and common metadata values
  • activitypub and activitystreams
  • apis
  • backends and controllers
  • databases and models
  • discussions
  • elixir app structure
  • front ends
View All Pages