White paper update: first draft of ‘Access to openly-licensed resources’ and ‘Crowdfunding’ sections

We’re making good progress in our aim to get a complete non-technical first draft of the Project MoodleNet white paper complete before Christmas! This update provides the first draft of the ‘Access to openly-licensed resources’ and ‘Crowdfunding’ sections. You can add your comments and feedback directly on the Google Doc at the following link or discuss via the forum link underneath each update, respectively.

Access and comment on the white paper: https://goo.gl/vwWRVD


Section 4: Access to openly-licensed resources

OER CommonsThe Access to openly-licensed resources section of the MoodleNet white paper gives a very brief overview of copyright in light of the Internet, Creative Commons, and the shift from OER to Open Educational Practices. There’s also a bit in there about ‘GitHub for Education’.

There three recommendations for Project MoodleNet from this section:

  • Recommendation #12: Project MoodleNet should respect copyright law while allowing educators to share their resources as freely and openly as possible. 
  • Recommendation #13: Open Educational Practices should be supported in Project MoodleNet by providing educators with tools to find, create, remix, and share each other’s resources.
  • Recommendation #14: Project MoodleNet should provide educators with powerful functionality that is easy and pleasurable to use.

Is there anything you think should be be in this section that isn’t currently included?

Discuss the Access to openly-licensed resources section in this forum thread: https://moodle.org/mod/forum/discuss.php?d=363180 or or directly on the white paper: https://goo.gl/vwWRVD

 

Section 5: Crowdfunding

Crowdfunding image CC BY-SA Rocío LaraThe Crowdfunding section of the MoodleNet white paper explains the role of crowdfunding and how it is related to membership and subscription options for supporting individuals and organisations providing content, products, and services.

There three recommendations for Project MoodleNet from this section:

  • Recommendation #15: Project MoodleNet should provide a way for educators to be recognised for the contributions they make to the community, including in financial ways.
  • Recommendation #16: To avoid advertising within Project MoodleNet, members should be able to support the development of new features through membership and/or subscription options.
  • Recommendation #17: Project MoodleNet should encourage the development of OERs by educators through easy-to-use crowdfunding options.

Do you agree with the discussion in this section? What should be added or removed?

Discuss the Access to openly-licensed resources section in this forum thread: https://moodle.org/mod/forum/discuss.php?d=363219 or or directly on the white paper: https://goo.gl/vwWRVD


What’s next? We’re going to revisiting the six scenarios outlined at the start of the white paper in light of the 17 recommendations made so far. In early 2018 we’ll then start work on the approach to the design and build of Project MoodleNet, along with a high-level overview of the technical development required.

Crowdfunding image CC BY-SA Rocío Lara

White paper update: further work on ‘Scenarios’, first draft of ‘Messaging’ and ‘News feed’

We’re continuing work on the Project MoodleNet white paper. This update revamps the ‘Scenarios’ section, and provides the first draft of the ‘Messaging’ and ‘News feed’ sections. You can add your comments and feedback directly on the Google Doc at the following link or discuss via the forum link underneath each update, respectively.

Access and comment on the white paper: https://goo.gl/vwWRVD


Scenarios

After discussions with Moodle HQ colleagues last week, we decided that to really make it clear that Project MoodleNet is aimed at educators, this should be reflected in the user personas. As such, we now have six different personas:

Scenario 4

These six personas are now:

  • Educator: Teacher (K12) – Spain
  • Educator: Lecturer (University) – Japan
  • Educator: Trainer (workplace) – Canada
  • Learning technologist (College) – Australia
  • Teaching Assistant (K12) – Brazil
  • Programme co-ordinator (University) – South Africa

It’s important that we get these right, so please do provide your comments, thoughts, and ideas!

Discuss the Scenarios in this forum thread: https://moodle.org/mod/forum/discuss.php?d=361923 or or directly on the white paper: https://goo.gl/vwWRVD

 

Section 2: Messaging

The first draft of the Messaging section of the MoodleNet white paper is now ready for feedback! This part begins to outline how the intention for Project MoodleNet is to foster communities of practice.

The recommendations from this section are currently:

  • Recommendation #6: Project MoodleNet should employ end-to-end encryption on all messages sent through the system. It should also be clear to users who will be able to see their communications (e.g. public / group / one-to-one)
  • Recommendation #7: To the greatest extent possible, Project MoodleNet should be interoperable with open standards, including the import and export of data to and from other social networks. It should have an API that allows others to build upon the core functionality it offers.
  • Recommendation #8: Project MoodleNet should aim at helping educators create Communities of Practice, adding features and taking UX decisions that help with this (e.g through ‘call to action’ buttons).

Is there anything you think should be added, amended, or removed?

Discuss the Messaging section in this forum thread: https://moodle.org/mod/forum/discuss.php?d=363106 or or directly on the white paper: https://goo.gl/vwWRVD

 

Section 3: News feed

The News feed section of the MoodleNet white paper is now drafted. Please do take a look at it and add your comments and feedback! This part explains how news, status updates, and messaging all got bundled together within algorithmic news feeds, and why that’s a bad thing for democracy

There three recommendations for Project MoodleNet from this section:

  • Recommendation #9: The three elements of news, status updates, and messaging should be controlled by users in Project MoodleNet. They should be separate if the user wishes, and combined if they prefer an approach more like other social networks.
  • Recommendation #10: Project MoodleNet should provide a raw, unfiltered feed to users, and make this available via an API that developers can build upon. Any other views or types of feed should be in addition to this.
  • Recommendation #11: To provide a disincentive for ‘clickbait’ headlines and sensationalist content, Project MoodleNet should provide mechanisms to collaboratively rate the content shared in the network.

What are your thoughts on this section? Do you see Project MoodleNet working differently? How?

Discuss the News feed section in this forum thread: https://moodle.org/mod/forum/discuss.php?d=363108 or or directly on the white paper: https://goo.gl/vwWRVD

White paper updates: ‘Scenarios’ & ‘Identity and reputation’

Work continues on the Project MoodleNet white paper. The latest updates are around the ‘Scenarios’ or the introductory user personas section, and the ‘Identity and reputation’ section. You can add your comments and feedback directly on the Google Doc at the following link or discuss via the forum link underneath each update, respectively.

Access and comment on the white paper: https://goo.gl/vwWRVD


Scenarios

The white paper introduces five scenarios in the way of user personas. These give a brief overview of the lives of different kinds of Moodlers, from learners and educators to developers and system administrators.

Scenario 1

The idea is for the discussion of Project MoodleNet in the white paper to address the issues felt by users in each of the five scenarios. For this to happen, the personas need to be as believable as possible, so please do help them ‘leap off the page’ for readers!

Discuss the Scenarios in this comment thread: https://moodle.org/mod/forum/discuss.php?d=361923

 

Section 1: Identity and reputation

This section is now ready in first draft form. It begins to outline how Project MoodleNet will differ from the major social networks, particularly around use of personal data, identity management, and decentralisation.

As part of this, there are five recommendations, listed below:

  • Recommendation #1: Project MoodleNet should at the very least allow users to create and manage multiple accounts. Serious thought should be given as to the possibility of allowing some interactions to be anonymous, or pseudo-anonymous. This will enable users to reflect different facets of their identity, allowing them to not only conform to how they currently are (and others see them) but grow, both professionally and personally.
  • Recommendation #2: Although easy to join and use, Project MoodleNet should be a robust, decentralised, federated system that does not have on a single point of failure.
  • Recommendation #3: Project MoodleNet should put the user in control of all of her data. All data held about a user should be compliant with the terms of the GDPR and be removable from the system. Users should be given fine-grained controls over who can see personal data and information they have added.
  • Recommendation #4: Project MoodleNet should allow for digital credentials to be created, exchanged, and displayed. These should reflect the diverse and wide-ranging interests of users, and contribute to Moodle’s mission of empowering educators.
  • Recommendation #5: The aim should be for Project MoodleNet portfolios to become the default place for educators to tell the story of their professional lives.

Additional recommendations will feature at the bottom of upcoming sections. We’re particularly interested in whether this feels like the right approach and, if so, if there’s a better way of explaining it? Please do help us pitch the language and tone correctly.

Discuss the the Identity and reputation section in this comment thread: https://moodle.org/mod/forum/discuss.php?d=362850