Past due
Milestone
expired on Jun 30, 2020
Federation testing (v1.1)
Federation testing is our name for a round of testing focused on new MoodleNet administrators. The aim is to ensure that admins can:
- Set up MoodleNet and experience no major blockers in doing so
- Connect to the MoodleNet ‘mothership’ via a provided API key (after accepting the relevant terms and conditions)
- Configure their instance, including:
- Allowlisting domains and email addresses for users they want to allow to register
- Creating sample communities and collections
- Featuring communities and collections across the MoodleNet network to their instance’s users
- Moderate any flagged content on their instance
- Report any bugs and problems they discover
Ongoing Issues (open and assigned)
10
- server-client api protocol: error definitions
- ADMIN - Can report a bug from admin interface
- REFACTOR - The search page needs to be integrated in storybook and in the new FE architecture
- Allow late binding SQL queries
- Add fields in DB, API, and AP for resources' content/mime/file type
- develop application top-level template containers
- ADMIN - Can configure information about the instance
- Decide on quotas / rate limiting for user and community actions
- MOTHERSHIP: view list of API keys, with option to revoke a key
- HQ: Backend should record whether user agreed to privacy notice and user agreement
Completed Issues (closed)
46
- ADMIN - Can delete anything on instance
- Fix resource link
- Create list of required toast messages
- USER - Can receive toast messages confirming interactions
- Resources should indicate whether they have been added via upload or link
- USER - Can send resources to Moodle LMS course
- GET MOODLENET READY FOR FEDERATION TESTING
- Add logic to detect (from added URLs and uploaded files) resources' content/mime/file type
- Allow pagination of resources in a collection
- Allow pagination of collections in a community
- Allow pagination of global collections list
- Allow pagination of global communities list
- Allow pagination of feeds
- You must be a member of the community a collection is in to add a resource
- ADMIN: Can block remote users and instances
- USER - Can follow other users
- Activity should embed enough data for infering possible user actions
- Fix last activity dates
- Implement pagination
- Decide how mothership handles API keys
- Decide on approach for pushing content to Algolia after it is received via AP by the mothership
- Public content should get bcc'd to mothership if admin has opted in
- Admin can add domains & emails that are allowed to register
- Write blog post about year ahead for MoodleNet
- Finish styleguide
- Define spec for 'send to Moodle LMS' button in MoodleNet
- Admins can remove a community/collection from featured list
- Admins can add collection to featured list
- Admins can add community to featured list
- Admins can delete communities and collections
- Admins can block an external instance
- Admins can suspend/block users at the instance-level
- USER: Can edit their MoodleNet profile
- Access your likes
- Flag/unflag community
- Flag/unflag collections
- Flag/unflag resources
- Flag/unflag comments
- Flag/unflag the user
- Access (federated) user's followed collections
- Access (federated) user's joined communities
- Newly-created communities and collections should be indexed by the HQ mothership
- Collections should display number of followers
- Display members of each community
- Users can reset their password
- Users can interact with remote communities/collections.