Statement on GitLab

The MoodleNet team use products and services from GitLab Inc. to develop the MoodleNet code base. We were therefore disappointed to learn of a recent decision by GitLab Inc. to change their policies around who they will and will not do business with.

"Deciding not to turn down customers on "moral/value" grounds is still a "moral/value" choice. It's just the wrong one. I hope that GitLab employees are furious."
Tweet from Eva Galperin, Director of Cybersecurity for the Electronic Frontier Foundation

As reported in The Register, GitLab Inc. first updated their policies to declare that they “won’t ban potential customers on “moral/value grounds,” and that employees should not discuss politics at work”. However, after a substantial backlash from current and potential customers, they have modified their position to “get rid of the problematic passages put forth in [the] handbook change”.

The internal policies of other companies might seem irrelevant to the work we are doing at Moodle, but it is important that, as a purpose-driven organisation, we use the influence we have to make our world a better place. Our values include integrity (“we employ the highest ethical standards, demonstrating honesty and fairness in every action that we take”) and openness (“we strive to be open in our goals, our tools, our processes and our results, as much as is practical”).

We believe that in order to live up to our values of integrity and openness, we should make decisions of which our community can be proud. While it would appear that GitLab Inc. have partly reversed their decisions based on the firestorm of criticism they have received, we have nevertheless decided to remove the MoodleNet repositories from gitlab.com and move them to a self-hosted solution. We will provide a further update on this after the Global Moot in Barcelona next month.


Note: the MoodleNet project is set up differently to the Moodle LMS and Workplace projects. Last year, we made the pragmatic decision to use gitlab.com (an instance of the GitLab open source software operated by GitLab, Inc.) to ensure that our project was as open to contributors as possible. 

Our intention was always to move the project’s repositories to an even more open and decentralised solution at an appropriate time. Now that time has come, we are evaluating a variety of options, including the ForgeFed project. Although we may decide to mirror our repositories on centralised services such as GitHub, we believe it is important for the canonical location of our code to be under our control.

MoodleNet and ‘free speech’

Network

Background

Moodle’s stated aim is to “empower educators to improve our world”. We do this in alignment with our values:

  • Education – We understand that education is the foundation of making the world a better place. We are always learning, improving how we learn, and helping those around us to learn and to teach.
  • Integrity – We employ the highest ethical standards, demonstrating honesty and fairness in every action that we take.
  • Respect – We treat everyone with respect and sensitivity, recognising the importance of their contributions: team members, customers, partners, suppliers and competitors.
  • Innovation – We encourage a progressive culture of data-driven experimentation and research, where entrepreneurship and prudent risk-taking are encouraged, rewarded and incorporated.
  • Openness –  We strive to be open in our goals, our tools, our processes and our results, as much as is practical.  We encourage team members and our community to communicate freely both internally and externally. We promote accessibility and embrace international cultures across all our products.

Context

MoodleNet is a new open social media platform for educators, focussed on professional development and open content. It sustainably empowers communities of educators to share and learn from each other to improve the quality of education. It is an integral part of the Moodle ecosystem.

As a federated social network using the ActivityPub protocol, MoodleNet will be part of the Fediverse. This means that users can follow accounts on other services such as Mastodon, Pleroma, and Pixelfed. This works both ways, of course, so users on any server using, for example, Pleroma as a basis for their social network, can follow and interact with MoodleNet users.

This is a huge step forward for social networking, as instead of having silos such as Instagram and Twitter, you can follow any account on any other network. You can also maintain different accounts for different facets of your personality, so for example mastodon.art is a community artists, and scholar.social is for academics. But what if there was an instance for… fascists? And what if those users went out of their way to harrass and troll other users?

The wider problem

This is not a hypothetical issue. Since the start of the year, the Fediverse has had to deal with a social network called Gab which claims to be focused on ‘free speech’ but actually contains a disproportionate number of users who identify as Nazi sympathisers. It’s blatant enough for both Apple and Google to have banned Gab’s app from their app stores for contraventions of their policies on ‘hate speech’.

In response, Gab decided to fork Mastodon, an Open Source project. This manoeuvre meant that Gab users could simply install any generic app that was compatible with Mastodon without Apple or Google being able to ban it. An article in The Verge explains the headache that this caused the Fediverse. The important paragraphs are quoted below:

Over the past few years, Mastodon has become the model for a friendlier kind of social network, promising to keep out the hateful or ugly content that proliferates on larger and more centralized networks. Journalists hailed it as “Twitter without Nazis” and for years, it’s generally lived up to that promise. But last week, the social network Gab migrated to Mastodon — and Mastodon’s admins have been forced to deal with the internet’s Nazi problem head-on.

[…]

Some Gab content has crossed the line into criminal activity. The UK jailed two teenage neo-Nazis in June for posting terrorist propaganda. Florida police also arrested a user last month for posting racist threats and possessing a firearm as a convicted felon. And in 2018, a man posted an anti-Semitic Gab message just before killing 11 members of a synagogue in Pittsburgh. Gab denies that it condones hatred — CEO Andrew Torba says it simply allows any speech that’s “legal in the United States” with a few exceptions. It correctly notes that Facebook and Twitter also contain hate speech and violent threats. Gab is far smaller than these sites, however, and its bad posts are particularly concentrated.

When Gab migrated to Mastodon, that content threatened to spill into the larger platform. Mastodon is organized into a “Fediverse,” which means that users on one instance can follow and interact with users from another. It helps make Mastodon feel like a single community, but by default, it could make users from one instance vulnerable to trolls from another. Fortunately, administrators can block instances, too, keeping out any posts or users from that server.

So far, that’s been the default response to Gab. Mastodon’s official site will only list instances that follow the Mastodon Server Covenant. The covenant mandates “active moderation against racism, sexism, homophobia, and transphobia” — which pretty much nixes any contact with Gab. For Rochko, it seems like the clearest way forward. “The software that powers Mastodon is released under an open-source free software license, which means anybody can use it,” he says. “And you know, that offers a great number of benefits — but some disadvantages.”

As you can see, there’s no way to remain neutral here. Developing software is a political act. Most Fediverse administrators seem to have blocked Gab instances, and many app developers have blacklisted all Gab domainsSo how is this going to affect MoodleNet?

Our response

MoodleNet is Free and Open Source Software (FLOSS) that we are developing and releasing under the terms of the AGPL. Anyone can use it for any purpose. However, in addition to MoodleNet, and to improve the user experience, administrators running a MoodleNet instance may apply for an API key to connect to the Moodle HQ ‘mothership’. This means that users on their instance can search all other connected instances to discover new content, follow users and collections, and join communities.

Given what has been going on in the Fediverse, we are going to be very careful in terms of who we hand out API keys to. They can, of course, be revoked, but we want to establish minimum standards, especially as we’re planning on creating a MoodleNet equivalent of the join Mastodon page.

With all this in mind, the MoodleNet team has been working with our Privacy Officer to draft two documents and put them out for community consultation. As outlined in an earlier post, the first of these is a MoodleNet User Agreement, which includes six sections:

  1. Terms
  2. Code of Conduct
  3. Contribution, Use, Modification and Distribution Licenses
  4. Disclaimers
  5. Modifications
  6. Instance Rules

The second is a MoodleNet Covenant for Instance Administrators, which also has six points. Admins running a MoodleNet instance who want to connect to the ‘mothership’ (for search and discoverability) must agree to:

  1. Foster an open and welcoming environment.
  2. Actively moderate their instance
  3. Perform daily backups
  4. Give emergency access to the server infrastructure to at least two people
  5. Give users at least 3 months of advance warning in case of shutting down
  6. Make available the source code of any customisations to your instance, regardless how small

The full version of the first point on this list mandates that administrators contribute to “a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation”. The second that they actively moderate against “racism, sexism, homophobia, transphobia, harassment, defamation, doxxing, sexual depictions of children, and conduct promoting alt-right and fascist ideologies”.

The ‘free speech’ issue

Many people who use FLOSS tend to be those who value their independence and liberty. As a result, we’ve received messages expressing concern that we’re taking a “political stance” which might be inappropriate in an educational setting.

Our response has been to remind the people sending these message that our approach isn’t about restricting the discussion of this kind of stuff, but the promoting of it. We’ve cited the Paradox of Tolerance:

“Unlimited tolerance must lead to the disappearance of tolerance. If we extend unlimited tolerance even to those who are intolerant, if we are not prepared to defend a tolerant society against the onslaught of the intolerant, then the tolerant will be destroyed, and tolerance with them.” (Karl Popper)

To reiterate, we are not specifying how people use MoodleNet. We are setting the minimum standards we expect from administrators (and their users) on instances connected to the MoodleNet mothership. This does not contravene the free software definition, as anyone is free to install and run MoodleNet, as they wish, for any purpose. They are also welcome to contribute to the code base subject to our Community Code of Conduct.

We hope that clarifies a few things. If you’ve got questions/concerns about this, please add a comment below, or email: moodlenet-moderators@moodle.com

MoodleNet overview slide deck (September 2019)

Update: Check out a 10-minute screencast of this slide deck!

Here’s the latest version of the slide deck we use to explain MoodleNet. You are very welcome to use it to introduce MoodleNet to others, personally or professionally.

Access the slides directly here: http://bit.ly/2lvTci5

We’ve completely restructured this slide deck from the one shared in July. It’s now much more focused on MoodleNet functionality, so we’ve moved the more technical aspects to the end.

MoodleNet development timeline
MoodleNet development timeline

Comments? Questions? Add them below!

Late August 2019 update

MoodleNet UI 2.0 — a work in progress
MoodleNet UI 2.0 — a work in progress

Work on MoodleNet continues apace, with the above screenshot no longer being a clickable prototype, but live code on our staging server! Ivan, our talented UX designer and front-end developer, has created a ‘read-only’ version of the new user interface before he heads off on a well-deserved holiday for a couple of weeks.

During that period, James will be finishing off a very necessary refactoring of the core functionality on backend code, Karen is continuing making good progress on federation, and Mayel has submitted a plugin to the Moodle LMS team for their review and (possible) integration into Moodle 3.8.

We’re still on track for a November beta release with everything from the ‘must’ section of our MoSCoW prioritisation grid. However, we’ve had to push back the federation testing until October as we’re a small team working on a complex project, and many things have to come together at the same time!

Thank you to those who have commented (only privately, so far) on our draft MoodleNet User Agreement and Covenant for Instance Administrators. Please do consider giving your feedback — positive or negative!

*DRAFT* MoodleNet User Agreement and Covenant for Instance Administrators

Happy Birthday Moodle! 🎉🎉🎉

As promised in our post about the upcoming federation testing programme, we are now ready to share draft versions of two relevant documents.

While anyone is free to use MoodleNet for any purpose (Freedom 0 of the ‘Four Freedoms‘), in order to connect to the HQ ‘mothership’ for reasons of search and discovery, instance administrators must:

  • Either use the MoodleNet User Agreement as-is, or only add reasonable terms that do not negate any element of the existing agreement.
  • Agree to be bound by the terms of the MoodleNet Covenant for Instance Administrators.

The first is a MoodleNet User Agreement, which includes six sections:

  1. Terms
  2. Code of Conduct
  3. Contribution, Use, Modification and Distribution Licenses
  4. Disclaimers
  5. Modifications
  6. Instance Rules

The second is a MoodleNet Covenant for Instance Administrators, which also has six points. Those admins running a MoodleNet instance who want to connect to the ‘mothership’ (for search and discoverability) must agree to:

  1. Foster an open and welcoming environment.
  2. Actively moderate their instance
  3. Perform daily backups
  4. Give emergency access to the server infrastructure to at least two people
  5. Give users at least 3 months of advance warning in case of shutting down
  6. Make available the source code of any customisations to your instance, regardless how small

To be as clear and direct as possible, the MoodleNet team is committed to fostering an open and welcoming environment, meaning that racism, sexism, homophobia, transphobia, harassment, defamation, doxxing, sexual depictions of children, and conduct promoting alt-right and fascist ideologies will not be tolerated.

We welcome the community’s feedback on these drafts, either as comments directly on the documents, in comments below this post, or on the MoodleNet forum. If you have particular concerns or comments that you like to make more privately, please email: moodlenet-moderators@moodle.com

Planning for the MoodleNet public beta

In the spirit of working openly, we’d like to share a MoSCoW prioritisation grid for the public beta release of MoodleNet in November 2019. While any project is subject to changing priorities as it progresses, this is where we are in early August.

For those that prefer a more accessible text-based version, please see below.


MUST

Instances:

  • Federation with other instances
  • Connect to HQ ‘mothership’
  • Search across federated instances
  • Discover page
  • My MoodleNet
  • Profiles
  • Flags/reporting
  • Moderation tools
  • Sign-up page (username/password)
  • Open to browse without signing in

Communities:

  • Image upload
  • Join/create/edit/leave a community
  • Every @community is hyperlinked

Collections:

  • Category tags
  • Create/edit a collection
  • Every +mention is hyperlinked

Resources:

  • Like resources
  • Add resource via URL
  • Add hashtags to added resources

Profiles:

  • Bio & links
  • Avatar
  • Header image
  • User timeline
  • Joined communities
  • Followed collections
  • Liked resources

Users:

  • Every @username is hyperlinked
  • Unique usernames

Moodle Core integration:

  • Plugin to pull resources from MoodleNet

Misc.

  • Basic security audit

SHOULD

Instances:

  • Help pages
  • Interoperability with other ActivityPub apps
  • Blocklists

Communities:

  • Share link to community 

Collections:

  • Hashtags 
  • Pinned resources
  • Share link to collection

Resources:

  • Upload resources
  • Add licence to uploaded resources

Profiles:

  • Follow other users

Users:

  • Notifications if mentioned within a community
  • Receive weekly emails about recent activity

COULD

Instances:

  • Analytics
  • Sign-up page (social accounts)

Communities:

  • Related communities

Collections:

  • Related collections
  • Sort/filter listed resources

Resources:

  • Auto-complete hashtags

Profiles:

  • Add other users to a contact list
  • Invite other people to create a MoodleNet profile
  • Add interests (based on hashtags)

Users:

  • Sort/filter ‘My MoodleNet’

Misc.

  • In-depth security audit

WON’T

  • Private communities / collections
  • Request a resource
  • Copy/fork a collection into another community
  • Events functionality
  • Emoji ID
  • Open Badges on profiles
  • Query 3rd-party repositories

MoodleNet overview slide deck (July 2019)

Update: we recorded a 13-min screencast version of the slide deck below!


We regularly update the slide deck used to give an overview of MoodleNet. It not only helps us continue to (hopefully!) get better at explaining what MoodleNet is, but is a useful resource for community members who may want to introduce it to others.

Access the slides directly here: http://bit.ly/2OkahJN

What we’ve changed this time around:

  • Removed ‘non-technical’ from the title
  • Replaced references to ‘decentralisation’ with ‘federation’
  • Updated the slide referencing Mastodon with a similar MoodleNet-focused one (see below!)
  • Added slides showing the UI 2.0 clickable prototype
  • Replaced the slide referencing Aha! with one showing Moodle Tracker
It doesn't matter which MoodleNet instance you are a member of - you can join communities, and follow other people and collections fro any other instance!
New MoodleNet federation overview slide

Comments? Questions? Add them below!

An update on sunsetting the existing moodle.net to make way for MoodleNet

As part of the preparations for a new MoodleNet plugin coming in Moodle 3.8, the current sharing site, moodle.net will be closed and its content archived. This means that from August 2019, it will no longer be possible to share courses on moodle.net.

To see what this means for teachers, and to find out what you need to do as an administrator, please see our guide: Sunsetting moodle.net.

If you have any questions about the current moodle.net site being closed, please post in the Moodle community sites forum.

MoodleNet and Free Cultural Works

MoodleNet is a new open social media platform for educators, focused on professional development and open content.

To facilitate the ‘open content’ part of MoodleNet’s mission, we propose that users sharing content via upload may choose from three open licenses, all provided by Creative Commons:

These are Free Culture licenses, defined in the following way: 

  1. the freedom to use the work and enjoy the benefits of using it
  2. the freedom to study the work and to apply knowledge acquired from it
  3. the freedom to make and redistribute copies, in whole or in part, of the information or expression
  4. the freedom to make changes and improvements, and to distribute derivative works

There is more detail about this on the Creative Commons website, which goes into much more detail about Free Cultural Works.

By taking this approach to uploading content to MoodleNet we would be following the lead of Wikimedia Commons, who have a comprehensive page on what is and what is not allowed on their platform. We believe that we can take a simpler approach with MoodleNet, with the added advantage that Creative Commons licences are already translated into most major languages.

Here is a (low-fidelity) wireframe example workflow for a user uploading a resource to MoodleNet:

User chooses the option to upload a resource to a collection
User chooses the option to upload a resource to a collection
User enters title, description, and hashtags
User enters title, description, and hashtags
User can change license from collection default
User can change license from collection default

What do you think of this approach? Is this what you were expecting? What else would you like to see (if anything)?