MoodleNet project community call (May 2018)


Next Wednesday, we’re hosting our MoodleNet project community call for May. We’ve got some updates to share, and we’d also very much appreciate your input for an upcoming design sprint.

The call will kick off, as usual, with a brief update about the current status of Project MoodleNet, and then we will collaborate on the data and inputs required for the design sprint we’re running later this month.

We’re alternating the times of each monthly call, so apologies to those who live in timezones that make it difficult to join this time around. We record each one, and you’re welcome to add your thoughts to the etherpad-based agenda asynchronously.

Image by Dafne Cholet used under a Creative Commons license

Mid-April 2018 round-up of project activity

This is a quick progress report since our last update in early February. A reminder that the canonical home page of this project can be found at

Doug Belshaw, MoodleNet project lead, as been meeting with lots of people and making notes of what was discussed. That has led to a shift away from the ‘start with a social network’ approach hinted at in the last update.

In the presentation and workshop Doug led at MoodleMoot UK & Ireland, he explained how such a potentially large and complex project needs a concrete starting point. Using the metaphors of cupcakes (always a favourite!) he introduced three different approaches:

CC BY-ND Bryan Mathers

Instead of starting with social networking, we’d instead add that and professional development to a platform that would initially focus on resource curation.

Participants who attended the first monthly community call discussed the pros and cons of starting off in this way, but all agreed that it would be something immediately useful to educators. Doug is now putting together a list of different types of resource-centric social media platforms, for inspiration.

While the white paper needs further work to update it in light of the slight change of direction, we have tidied it up and added new faces to scenarios section

We’ve been doing a whole host of work, including putting together a job landscape for a Technical Architect to join the team at some point in the near future. We’ll also be engaging a design and development agency to help us with design sprint / prototyping / MVP.  More on that in the next update!

Related posts on Doug’s blog:


Meet us at the OER18 conference (Bristol, UK) this week, or OE Global 2018 (Delft, Netherlands) next week!

Recording of first Project MoodleNet community call now available!

Project MoodleNet community call (4th April 2018)

Many thanks to the 20+ who joined us for the first Project MoodleNet community call. Despite some technical difficulties towards the end, it proved to be a great, positive discussion!

The (now very colourful and annotated) agenda can be found here. The video and audio recording, along with a backup of the agenda, and visual notes from Bryan Mathers and Adam Procter, can be found at

Update: further to a discussion with Moodle’s DPO & Legal Advisor, we have removed the agenda and recording of previous community calls. We are now in the process of creating a GDPR-compliant workflow.

Community call: save the date!


Right now, we’re deep in planning mode for Project MoodleNet. This includes putting together documentation (most of which is publicly available here), sorting out resourcing, and talking to people who have valuable insights which will help us with the road ahead.

We’re keen to involve the community in this process as soon as it makes sense to do so, which is why we’re announcing the first Project MoodleNet community call for early April!

The call will kick off with a brief presentation about the current status of Project MoodleNet, and then will take questions and have a discussion about what should be in/out of scope for the project.

Apologies to those who live in timezones that make it difficult to join this time around. We’ll be sure to record this one, and will attempt to accommodate different timezones in future calls.

Image by Dafne Cholet used under a Creative Commons license

Early February 2018 round-up of project activity

Project MoodleNet planning/experimentation screenshots

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:

  1. 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)
  2. 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.
  3. 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!

Introducing Project MoodleNet (Jan 2018 slide overview)

In accordance with our principle of transparency for Project MoodleNet, we’re sharing the slides from a recent All-Hands meeting. You should see them embedded below but, if not, please click through!

Comments? Questions? Add them below!

Principles underpinning Project MoodleNet: 6. ‘Connected’

Photo by Federico Beccari on Unsplash

The principles underpinning Project MoodleNet are:

  1. Open
  2. Safe
  3. Private
  4. Ethical
  5. Transparent
  6. Connecte​d

But what do these mean in practice? In this sixth (and final) in a series of posts, we explore what ‘connected’ means as regards this project.

Project MoodleNet is described by Martin Dougiamas, CEO of Moodle as, “a new open social media platform for educators, focused on professional development and open content”. Therefore, when we talk about one of the principles underpinning the project being ‘connected’ it is obvious that we are connecting people with people. We have grown used to these platforms over the last decade, discussing a whole range of things on social networks such as Facebook, Twitter, and Instagram.

What is different about Project MoodleNet is that it will have an explicit focus on educators, connecting them together to share openly-licensed resources and provide professional development.  We will design the system to respond to their needs, ensuring that they are not limited by the constraints of more generic social networks, and can help shape its future direction.

When we connect with other people, we are connecting as something or someone: perhaps a daughter, a husband, or a teacher. In the Project MoodleNet white paper we explore the ways in which identity plays an important role online as well as offline, so we want to ensure that when an educator uses Project MoodleNet, they have a choice of how to portray themselves. We will experiment with a number of ways of doing this.

In addition to connecting people to people, Project MoodleNet will also connect people with resources, news, and members of our partner network. We will provide a lightweight, contextually-focused dashboard which can be curated by users to provide, amongst other things:

  • Up-to-date information about openly-licensed content they may be interested in
  • Questions from the community that they may be able to answer (and answers in which they may be interested)
  • News from accounts they have chosen to follow

In an age of algorithmic curation and fake news, we want to empower educators to quickly and easily ‘tune their feeds’ in ways that help them teach and help others learn.

Project MoodleNet will be API-based. In layperson’s terms that means ‘Application Programming Interface’ and is a “set of subroutine definitions, protocols, and tools for building application software” (Wikipedia). They are a powerful way of building applications and services:

“On the Web, APIs make it possible for big services like Google Maps or Facebook to let other apps “piggyback” on their offerings. Think about the way Yelp, for instance, displays nearby restaurants on a Google Map in its app, or the way some video games now let players chat, post high scores and invite friends to play via Facebook, right there in the middle of a game.


APIs simplify [things] by limiting outside program access to a specific set of features—often enough, requests for data of one sort or another. Feel free to think of them as doors, windows or levers if you like. Whatever the metaphor, APIs clearly define exactly how a program will interact with the rest of the software world—saving time, resources and potentially nasty legal entanglements along the way.” (ReadWrite)

It will be simple and straightforward for users to both put information into Project MoodleNet, and to get it out. We will be building upon open standards and protocols, and using well-documented APIs to make this seamless. Moving between different elements of Project MoodleNet, for example search, user profiles, the OER repository, help forum, and crowdfunding area, will be seamless due to the APIs we both use and write.

Moodle’s learning platform uses APIs provided by Google Drive, Dropbox, and Microsoft OneDrive so that users can bring in files they have stored on those services. In turn, Moodle provides a number of APIs meaning that there are thousands of plugins available to extend the learning platform’s core functionality. Well-documented, open APIs encourage greater connection between people, resources, and other web services, so Project MoodleNet will build upon these.

By connecting users with other users, by connecting them with openly-licensed content, and by leveraging the power of APIs, Project MoodleNet will, we believe, empower educators to improve our world.

Principles underpinning Project MoodleNet: 5. ‘Transparent’

Photo by Aleks Dahlberg on Unsplash

The principles underpinning Project MoodleNet are:

  1. Open
  2. Safe
  3. Private
  4. Ethical
  5. Transparent
  6. Connecte​d

But what do these mean in practice? In this fifth of a series of posts, we explore what ‘transparent’ means as regards this project.

Whether in the media or in our own organisations, we’ve all experienced calls for ‘greater transparency’. This is usually an encouragement for those with the necessary power to increase the frequency or quality of communication with those to whom they’re accountable.

As Wikipedia puts it:

“Transparency is operating in such a way that it is easy for others to see what actions are performed. It has been defined simply as “the perceived quality of intentionally shared information from a sender”.”

In the first post of this series on the principle of openness, we explored open as an ‘attitude’. When it comes to the transparency of Project MoodleNet, this involves two factors:

  1. Sharing information about the status and decision-making of the project while it is being built
  2. Being open and honest with users about the ways their data is being used once the project is up-and-running

Right now, we’re being as open and transparent as possible about the project as it’s being scoped out. There are some things (for example project risks) which we may choose to limit to Moodle HQ, but we are defaulting to sharing everything as quickly and openly as possible.

The canonical URL for this project is By this we mean that this is the project’s home, and that you should be able to navigate to every part of it from that link. In addition, we are endeavouring to make this project as ‘legible’ as possible, in the sense that we want it to be easy to keep up-to-date with progress. There are a number of ways of doing this, including this blog, a Telegram channel, and a discussion forum, all linked to from the web address given above.

Ultimately, the success of Project MoodleNet depends on Moodle’s competitive advantage around working closely with partners and community members in an open, transparent trusted way. We are confident that doing so will build trust and increase the chances of project success.