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
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:
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