|
|
| (9 intermediate revisions by the same user not shown) |
| Line 4: |
Line 4: |
|
| |
|
| == Roadmap == | | == Roadmap == |
|
| |
| '''''Note:''' this is a work in progress to create a high-level overview of the MoodleNet project. For more granular detail, please check out the [https://bit.ly/epic-MN Moodle Tracker] (you must be logged-in to view).''
| |
|
| |
|
| === 2018 === | | === 2018 === |
| 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 [https://blog.moodle.net/2018/retrospective/ 2018 retrospective post] on the MoodleNet blog. | | 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 [https://blog.moodle.net/2018/retrospective/ 2018 retrospective post] on the MoodleNet blog. |
| -----
| |
|
| |
|
| === 2019 === | | === 2019 === |
| ==== Q1+2 ====
| | Our main aim for 2019 was to ensure that we carry out extensive testing of both MoodleNet's value proposition and ability to set up federated instances, before delivering a version of MoodleNet for internal testing. |
| 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.
| | === 2020 === |
| # Easily find out when something has changed within a community they’ve joined, or a collection they’re following.
| | This year, we aim to build out the functionality and features of MoodleNet based on the recommendations from the original [https://docs.moodle.org/dev/MoodleNet_whitepaper white paper], feedback from the community (via [https://changemap.co/moodle/moodlenet Changemap], and our [https://blog.moodle.net/2019/planning-for-the-moodlenet-public-beta/ prioritisation grid] (August 2019). |
| # 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.
| | 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. With our current budget and resourcing, we are prioritising: |
|
| |
|
| As a result of all this activity, we did a deep dive into [search https://blog.moodle.net/2019/search-in-moodlenet/] 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.
| | ==== Q1 ==== |
| | * Moodle LMS integration |
| | * Federation testing |
| | * Resource uploading |
| | * Moderation by admins |
| | * [https://ux.stackexchange.com/questions/11998/what-is-a-toast-notification#12000 Toast notifications] |
| | |
| | ==== Q2 ==== |
| | * User testing (on Moodle HQ-run instances) - ''including data export and deletion'' |
| | * Extensible architecture |
| | * Tagging and categorisation |
| | * Roles and access controls |
| | * Push notifications |
|
| |
|
| ==== Q3 ==== | | ==== 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.
| | * Private communities/collections |
| | | * Direct messaging |
| 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.
| | * Collaborative blocklists |
| | | * Theming |
| 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.
| | * Display Open Badges on user profiles |
| | |
| 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 ==== |
| 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.
| | * Share resource from Moodle LMS to MoodleNet collection |
| | | * Request resources |
| '''Must-have''' functionality still to deliver from our [https://blog.moodle.net/2019/planning-for-the-moodlenet-public-beta/ prioritisation grid] includes the following, which are all works-in-progress:
| | * Moodle HQ provided cloud hosting for MoodleNet |
| | |
| Instances:
| |
| * 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
| |
| | |
| Communities:
| |
| * Image upload
| |
| * Every @community is hyperlinked
| |
| | |
| Collections:
| |
| * Category tags
| |
| * Every +mention is hyperlinked
| |
| | |
| Resources:
| |
| * Like resources
| |
| * Add hashtags to added resources | |
| * Liked resources
| |
| | |
| Users:
| |
| * Every @username is hyperlinked
| |
| | |
| Moodle Core integration: | |
| * Finalise plugin to pull resources from MoodleNet
| |
| | |
| Misc.
| |
| * Basic security audit
| |
| | |
| === 2020 ===
| |
| Based on our [https://blog.moodle.net/2019/planning-for-the-moodlenet-public-beta/ prioritisation grid] (August 2019) we are planning the following post-beta functionality and features.
| |
| | |
| ==== Q1+2 ====
| |
| * Analytics for instance administrators
| |
| * Social sign-in | | * Social sign-in |
| * Related communities/collections | | * User-requested extensions & improvements |
| * Sort/filter listed resources
| |
| * Auto-complete hashtags
| |
| * Add other users to a contact list
| |
| * Invite other people to create a MoodleNet profile
| |
| * Add interests (based on hashtags)
| |
| * Sort/filter ‘My MoodleNet’ page
| |
| * In-depth security audit
| |
|
| |
|
| ==== Q3+4 ==== | | === 2021 === |
| * Unsplash integration | | * Events/meet-ups |
| * Private communities/collections | | * Communities can define their own taxonomies |
| * Copy/fork a collection into another community | | * Crowdfunding resources into existence |
| * Events functionality
| | * Version control for OER (incl. forking and merging) |
| * [https://blog.moodle.net/2018/what-is-emoji-id/ Emoji ID] | | * Uploading videos (integration with third-party services) |
| * Query 3rd-party repositories | |
| * Request a resource
| |
| * Open Badges on profiles
| |
