No Monetization Plans In Sight, MoodleNet Attempts To Answer The Community’s Pressing Questions

In a commendable effort of transparency, the MoodleNet team updated a Moodle Docs page with questions and concerns arising from the community from the recent MoodleMoot Spain 2018. Sorted in a traffic light-like arrangement, community interactions were sorted as green (praise), yellow (questions), and red (concerns). The green section features a lot of “love,” “greats,” likes and yeses at the purportedly confirmed features.

Post Pages - Post Inline - WIRIS

Previously in MoodleNews: MoodleNet Officially In The Works: Where Is The ‘X’ Factor?

The yellow section lists dozens of practical questions, some of which were answered in a blog post. On sharing, MoodleNet is poised as a replacement for the current repository, which means it is expected to offer importing and exporting functionality. The post confirms that features like MBZ files (the extension for Moodle course packages) and bulk download will be offered, as well as multi-language search and subject group recommendations.

Other features pending confirmation include storage (which the old does offer) and the revenue model. Despite keynotes in which Dougiamas framed MoodleNet as a “marketplace” for content creators. About paid content and services exchange, “I wouldn’t say that this is going to happen any time soon, but it’s a good idea” says Doug Belshaw, MoodleNet lead and blog post author. Spam protection will not be addressed directly by MoodleNet, but rather delegated to community admins.

On compatibility, it seems the first route of action would be MoodleCloud, then sites serviced by Moodle Partners, and eventually a plugin.

Finally, the red section includes concerns, but also more questions, many of which could well belong in the yellow. It is unclear whether they are being addressed, or when they will:

  • Teachers may not be willing to share their content.
  • Copyright issues will get in the way of sharing.
  • Too many communities about the same topics will create confusion about which to join.
  • The site might not reach a critical mass of contributors.
  • The site might not prove to be relevant to be used.
  • The prototype looks too much like Facebook or Twitter, and not in a good way.
  • People don’t really want yet another social network.

See also: Teen Survey Warning for MoodleNet: Think Instagram, Not Facebook.

Regarding future interactions, thanks to GDPR (although some might hold the lawyer responsible) the MoodleNet team had to stop their community calls due to the inability of the team to track data and consent with the tools they were using.

Slides presented at the “Moot” revealed that the “Specification and Planning” stage is currently underway. “Prototyping and testing” is scheduled for the final quarter of 2018, followed with a “Minimum Viable Product” by early 2019.

Visit a MoodleNet project board at

Visit “MoodleNet-MootES18” at

Read “Responding to questions from #MootES18” at

View a presentation.

MoodleNet code repositories in GitHub and Gitlab. ■

ecreators logoThis Moodle Governance related post is made possible by: eCreators. Moodle for the enterprise, K12 and corporate. Australia and Singapore. To learn more about eCreators, click here.

Previous article“Docteur Moodle” And Other Highlights Of MoodleMoot Francophonie 2018
Next articleBreves de Moodle en Español: MoodleMoot España, Moodle Barcelona, Moodler Honoris Causa



Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.