We’ve been hard at work behind the scenes over the past few weeks, planning, experimenting, and testing with various protocols and standards. Here are a few updates for those keeping a close eye on the progress of this project:
- Whiteboarding — as you can see from one of the above screenshots, we’re figuring out the components of Project MoodleNet, and how everything will fit together. Initially, we thought there would be six components, but this has grown to eight (as a couple of them needed to be separated-out)
- Testing — again, as you can see from the other two screenshots above, we’ve been experimenting with two open source projects that are compatible with the (newly W3C-recommended) ActivityPub protocol. We want Project MoodleNet to be a decentralised, federated system and these projects may give us a head start — at least for the MVP. You can read more about Mastodon and Hubzilla on project lead Doug Belshaw’s blog. In terms of authenticating into the system, we’re going to be using OpenID Connect in the first instance.
- Compliance — the General Data Protection Regulation (GDPR) comes into force in May, and pertains to every organisation based in the European Union (EU), or processing the data of EU citizens. Moodle has already published a plan for GDPR compliance, but this relates mainly to our learning platform. Project lead Doug Belshaw is blogging his reflections on a GDPR course he is currently undertaking.
Thanks again to those who left comments on v0.1 of the Project MoodleNet white paper. We have now transferred the text from Google Docs to the wiki, and will proceed to make changes based both on community feedback and the discoveries we make as the project progresses.
Next week, Moodle’s team leads are meeting in Perth, Australia, for some days of intensive planning. We intend to have a lot more updates for you over the coming weeks!