project: MoodleNet
summary: Help pages and other documentation for and of MoodleNet
description: Help pages and other documentation for and of MoodleNet

1.summary: Create blog post for v0.9 alpha release
description: List of v0.9 features (Thurs): Colour scheme / dark theme New UI New homepage (communities/collections) Bug fixing Timelines (profiles, instance, user inbox on home page)
2.summary: Create slides for MoodleMoot UK & Ireland presentation
description: Adapt existing slide decks for 20 minute presentation at the Moot.
3.summary: Plan UK & Ireland MoodleMoot 2019 workshop
description: 14:30-17:00, Wednesday 17th April MoodleNet: Share. Curate. Discuss. Facilitated by: Doug Belshaw, Moodle HQ Come and get started with MoodleNet, the new resource-centric social network for educators! In this workshop, you will have the opportunity to get started with the much-anticipated MoodleNet! Come along to be one of the first users of this exciting new environment, ask questions, suggest features, and earn a rare badge in the process! Participants of all user levels welcome. Please bring a laptop and/or smartphone.
4.summary: Create Fediverse account for MoodleNet
description: We need a Fediverse account for two reasons: Now: so we can toot like we tweet Future: so we can talk about any issues with MN in future
5.summary: Review options for fork/remix/share approach in MoodleNet
description: As discussed, we need to revisit the option for versioning in MoodleNet. In particular: Whats the smallest possible thing we could do which would be of value? Whats the most full-featured thing we could do to delight users? What are our options in terms of technologies?
6.summary: Create onboarding overview doc for Karen and James
description: We need a Google Doc to share with Karen and James to give them an overview of the team and what to pay attention to:
7.summary: Document backend code
description: . Some guidelines about what/how to document The MoodleNet backend needs to be documented. The point isnt to have super extensive and verbose documentation, but at the very least to provide new backend devs coming to the project (including future contributors & instance admins) an overview of the projects architecture and hints to help them quickly add/modify/tweak functionality, with the readme as a starting point, as well as detailed inline documentation (used to auto-generate online docs). When possible, our docs can simply link to relevant sections of external docs. . Describe in the readme Setting up a dev environment General code structure (directories/applications/modules) List of external dependencies and what theyre needed/used for (dev & prod) How to run tests How to deploy (to both staging & prod) How to run migrations when deploying How to encapsulate strings for localisation How GraphQL pagination works (both from backend point of view, and how to use by API client) How to view (and generate) docs from inline documentation (eg. with ExDoc| Any important implementation details . Inline documentation Document the internals of Makefile & Dockerfile & docker-compose Add descriptions to GraphQL endpoints ( Document the functional code (using the standard | & Brief description of what each function is for Why it does it this way| (when relevant) Expected or optional parameters/arguments What the function returns Examples (doctests| when possible, or pointing to existing tests)
8.summary: Create transactional email copy for reset password
description: We need the copy for emails to be sent out to users who forget their passwords.
9.summary: Create list of activities for MoodleNet community management
description: marycooch and tsala have kindly offered to help with some of the community management side of things for MoodleNet. This issue is to capture and discuss some of these, including: Regularly creating new content to seed MoodleNet (i.e. adding resources to collections) Providing feedback from a Moodle users perspective on potential directions for MoodleNets user interface Encouraging existing Moodlers to use MoodleNet (requesting an account if necessary) Updating the list of feature communities and collections for each release (example) Responding to MoodleNet questions via Twitter Assisting with the sunsetting of the existing moodle.net Responding to and curating feedback from users on Changemap Posting and responding to toots on MoodleNets account(s) on the fediverse Suggesting demo content for mockups and clickable prototypes What else could/should we add? :)
10.summary: Research other federated networks r.e. MoodleNet user agreement
description: For example:
11.summary: Scope out federation testing programme
description: To do: Blog post: Google Form: User agreement: Covenant for instance administrators:
12.summary: Add info to MoodleNet combined data register
description: Carlos asked us to complete this combined data register from a users perspective:
13.summary: Define support workflow for users requiring assistance with MoodleNet
description: We need to ensure that our users are supported. Theyll be able to use Changemap to log things that need fixing/upgrading, but for general support queries we need a solution. Other Moodle products use Zendesk via support.moodle.com. We should consider doing the same, after talking with Terri Ann and others.
14.summary: Prototype user tour for first run of MoodleNet after sign-up
description: Some resources:

Below is an instruction that describes a task, paired with an input that provides an epic with this format: 
"project": "Name of the project" 
"summary": "Summary of the epic user story" 
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Help pages and other documentation for and of MoodleNet
description: Help pages and other documentation for and of MoodleNet

### Response:
1.summary: Create blog post for v0.9 alpha release
description: List of v0.9 features (Thurs): Colour scheme / dark theme New UI New homepage (communities/collections) Bug fixing Timelines (profiles, instance, user inbox on home page)
2.summary: Create slides for MoodleMoot UK & Ireland presentation
description: Adapt existing slide decks for 20 minute presentation at the Moot.
3.summary: Plan UK & Ireland MoodleMoot 2019 workshop
description: 14:30-17:00, Wednesday 17th April MoodleNet: Share. Curate. Discuss. Facilitated by: Doug Belshaw, Moodle HQ Come and get started with MoodleNet, the new resource-centric social network for educators! In this workshop, you will have the opportunity to get started with the much-anticipated MoodleNet! Come along to be one of the first users of this exciting new environment, ask questions, suggest features, and earn a rare badge in the process! Participants of all user levels welcome. Please bring a laptop and/or smartphone.
4.summary: Create Fediverse account for MoodleNet
description: We need a Fediverse account for two reasons: Now: so we can toot like we tweet Future: so we can talk about any issues with MN in future
5.summary: Review options for fork/remix/share approach in MoodleNet
description: As discussed, we need to revisit the option for versioning in MoodleNet. In particular: Whats the smallest possible thing we could do which would be of value? Whats the most full-featured thing we could do to delight users? What are our options in terms of technologies?
6.summary: Create onboarding overview doc for Karen and James
description: We need a Google Doc to share with Karen and James to give them an overview of the team and what to pay attention to:
7.summary: Document backend code
description: . Some guidelines about what/how to document The MoodleNet backend needs to be documented. The point isnt to have super extensive and verbose documentation, but at the very least to provide new backend devs coming to the project (including future contributors & instance admins) an overview of the projects architecture and hints to help them quickly add/modify/tweak functionality, with the readme as a starting point, as well as detailed inline documentation (used to auto-generate online docs). When possible, our docs can simply link to relevant sections of external docs. . Describe in the readme Setting up a dev environment General code structure (directories/applications/modules) List of external dependencies and what theyre needed/used for (dev & prod) How to run tests How to deploy (to both staging & prod) How to run migrations when deploying How to encapsulate strings for localisation How GraphQL pagination works (both from backend point of view, and how to use by API client) How to view (and generate) docs from inline documentation (eg. with ExDoc| Any important implementation details . Inline documentation Document the internals of Makefile & Dockerfile & docker-compose Add descriptions to GraphQL endpoints ( Document the functional code (using the standard | & Brief description of what each function is for Why it does it this way| (when relevant) Expected or optional parameters/arguments What the function returns Examples (doctests| when possible, or pointing to existing tests)
8.summary: Create transactional email copy for reset password
description: We need the copy for emails to be sent out to users who forget their passwords.
9.summary: Create list of activities for MoodleNet community management
description: marycooch and tsala have kindly offered to help with some of the community management side of things for MoodleNet. This issue is to capture and discuss some of these, including: Regularly creating new content to seed MoodleNet (i.e. adding resources to collections) Providing feedback from a Moodle users perspective on potential directions for MoodleNets user interface Encouraging existing Moodlers to use MoodleNet (requesting an account if necessary) Updating the list of feature communities and collections for each release (example) Responding to MoodleNet questions via Twitter Assisting with the sunsetting of the existing moodle.net Responding to and curating feedback from users on Changemap Posting and responding to toots on MoodleNets account(s) on the fediverse Suggesting demo content for mockups and clickable prototypes What else could/should we add? :)
10.summary: Research other federated networks r.e. MoodleNet user agreement
description: For example:
11.summary: Scope out federation testing programme
description: To do: Blog post: Google Form: User agreement: Covenant for instance administrators:
12.summary: Add info to MoodleNet combined data register
description: Carlos asked us to complete this combined data register from a users perspective:
13.summary: Define support workflow for users requiring assistance with MoodleNet
description: We need to ensure that our users are supported. Theyll be able to use Changemap to log things that need fixing/upgrading, but for general support queries we need a solution. Other Moodle products use Zendesk via support.moodle.com. We should consider doing the same, after talking with Terri Ann and others.
14.summary: Prototype user tour for first run of MoodleNet after sign-up
description: Some resources:
