project: Moodle Community Sites
summary: Close down existing moodle.net in an orderly, well-communicated way
description: Moodle.net is a service that has been around since 2010. It allows users to search for and download Moodle courses, as well as database presets, quiz questions, and other Moodle-specific content. In addition, Moodle.net functionality is accessible within the Moodle LMS itself. Users can both share content with the service, as well as search and download relevant content. The existing Moodle.net will be sunsetted (i.e. shut down gracefully and with plenty of notice) when the new MoodleNet| is ready to take over the functionality it offers.

1.summary: Moodle links filter updates
description: The Moodle links filter currently links moodle.net to with title text Moodle.net - Courses and content. This needs to be changed to MoodleNet - Connecting and empowering educators worldwide. It would also be cool to add more words to the Moodle links filter: MoodleCloud - linking to Moodle Users Association - linking to MUA - linking to (Edited to amend the moodle.net title text to include Connecting and empowering educators worldwide as stated on
2.summary: Create transition plan for every user-facing subdomain and service on moodle.net
description: Sunsetting moodle.net doc: Delete unused moodle.net subdomains: academy.moodle.net accessibility.moodle.net analyticslrs.moodle.net aws.moodle.net game.moodle.net. gdprdemomaster.moodle.net. gdprdemo.moodle.net. hubzilla.moodle.net. ipv6.moodle.net. learninganalytics.moodle.net. learn-analytics.moodle.net. learn-b.moodle.net. localhost.moodle.net. mec.moodle.net mobile.moodle.net. notify.moodle.net outcomes.moodle.net pinry.moodle.net. prototype.moodle.net. reviews.moodle.net. veronique.moodle.net. www.ipv6.moodle.net| DO NOT TOUCH the following subdomains: app.moodle.net. blog.moodle.net. email.mailg.moodle.net. home.moodle.net. mailg.moodle.net. messages.moodle.net. new.moodle.net. COPY user-facing moodle.net subdomains elsewhere demomaster.moodle.net. master.moodledemo.net demo.moodle.net. moodledemo.net learn.moodle.net learn.moodle.org mary.moodle.net marydev.moodledemo.net qamaster.moodle.net. qamaster.moodle.org qa.moodle.net. qa.moodle.org research.moodle.net. research.moodle.org school.demo.moodle.net. school.moodledemo.net schoolmaster.demo.moodle.net. schoolmaster.moodledemo.net
3.summary: Decide whether we need new domain(s) for moodle.net/sites and moodle.net/stats
description: See comment thread on this GDoc|
4.summary: Archive all existing moodle.net content
description: Wed like to keep the content the community has uploaded to moodle.net but NOT just automatically import it into the new MoodleNet. As a result, we need to plan for a new subdomain (e.g. archive.moodle.net) Steps: Disallow any new content to appear on moodle.net from August 2019 Create archive.moodle.net, transfer content, and make it read-only Take down existing moodle.net and redirect people towards archive.moodle.net (Edited to add steps as mentioned in a comment below.)
5.summary: Figure out everywhere that moodle.net is referenced and how it needs to be updated in Moodle Core
description: We need a list of everywhere that moodle.net is referenced in Moodle Core so we can update the strings for 3.8.
6.summary: Create comms plan for communicating sunsetting of moodle.net
description: This should include Moodle Docs as the single source of truth for the community. Also, lets plan out blog posts and other updates to keep people in the loop.
7.summary: Create plan to redirect registration stats to stats.moodle.org
description: We need to decide on a domain to handle registrations. Moodle.org? Other?
8.summary: Discuss desirability of moving messages.moodle.net elsewhere
description: According to jleyva: "messages.moodle.net| has been used since Moodle 2.4 as the Push backend so we have more than once hundred thousand sites using that address."
9.summary: Create RACI for moodle.net sunsetting
description: 
10.summary: Create plan to change moodle.net functionality in supported versions <3.8
description: Lets discuss this in proposed meeting on 12th June 2019. One for mudrd8mz and others to think about. How can we ensure that users of supported Moodle versions know that existing moodle.net functionality is being/has been deprecated?
11.summary: Perform course housekeeping on Moodle.net
description: Prior to sunetting it would be useful to go through the courses and remove any enrollable courses with past enrolment dates and any downloadable courses with outdated content. That way, the archive will actually contain useful materials.
12.summary: Remove course-sharing functionality
description: Course sharing| on Moodle.net will no longer be possible in Moodle 3.8, so the functionality needs to be removed. The functionality includes: Capabilities moodle/course:publish, moodle/backup:backuptargethub and moodle/restore:restoretargethub Course sharing switch in Advanced features in the Site administration.
13.summary: Delete unused moodle.net subdomains
description: Unused moodle.net subdomains are as follows: academy.moodle.net accessibility.moodle.net analyticslrs.moodle.net aws.moodle.net game.moodle.net gdprdemomaster.moodle.net gdprdemo.moodle.net hubzilla.moodle.net Ipv6.moodle.net learninganalytics.moodle.net learn-analytics.moodle.net learn-b.moodle.net localhost.moodle.net mec.moodle.net mobile.moodle.net notify.moodle.net outcomes.moodle.net pinry.moodle.net prototype.moodle.net reviews.moodle.net veronique.moodle.net www.ipv6.moodle.net
14.summary: Add info to moodle.net informing users it will soon be read-only
description: 
15.summary: Remove course-sharing functionality in Moodle 3.7.2, 3.6.6 and 3.5.8
description: Moodle 3.7.2, 3.6.6 and 3.5.8 are scheduled for release on 9 September 2019. It would be good to remove the course-sharing functionality as in Moodle 3.8 ().
16.summary: Redirect moodle.net subdomains
description: Lets start with: 1. -mary.moodle.net marydev.moodledemo.net- 2. -research.moodle.net research.moodle.org- 3. -prototype.moodle.net -> then: 4. -demo.moodle.net sandbox.moodledemo.net- 5. -demomaster.moodle.net sandboxmaster.moodledemo.net- then check that all is working fine (reset scripts etc), and if so do: 6. -school.demo.moodle.net school.moodledemo.net- color:172b4dcolor:de350b 7. -schoolmaster.demo.moodle.net-colorcolor - schoolmaster.moodledemo.net- Insert from sub ticket - _Remove above list of old user-facing moodle.net subdomains (EXCEPT school.demo.moodle.net as hardcoded into Moodle mobile app and can only update upon release in either August or November 2019 - until Juan Leyva gives go-ahead) and: 8. -qa.moodle.net qa.moodledemo.net- 9. -qamaster.moodle.net qamaster.moodledemo.net- _Note: All the above can be done immediately or at any time before September 2019._ Finally, _to be done after 15 July 2019_: 10. -learn.moodle.net learn.moodle.org- 11. learn.next.moodle.net learn.next.moodle.org Please comment "1, 2, 3 done and ready for checking" etc. before proceeding with further redirects. Note: This issue is only about redirecting subdomains to new subdomains. color:de350bDeletion of moodle.net subdomains will be in another issue (for after we have updated links everywhere). color
17.summary: Split Moodle site registration part of moodle.net to create stats.moodle.org
description: 
18.summary: Split courses and content part of moodle.net to create archive.moodle.net
description: 
19.summary: Code changes required after moving Moodle site registration data to stats.moodle.org
description: Moodle site registration data is being moved from moodle.net to stats.moodle.org (). As a result, changes are required in core code. _Note: needs to be completed before this issue is integrated._ As commented by Marina in : 1. There is one place in core where we store a constant with the "hub" name code define(HUB_MOODLEORGHUBURL, " define(HUB_OLDMOODLEORGHUBURL, " code 2. There was an upgrade script once changing references to -> for sites that were already registered. If we change the value of this variable we will need to repeat it: Note that there are config variables that contain the hub name (from the time when it was possible to register on multiple hubs) (3. removed as it has been done.) 4. There are couple of hardcoded "Moodle.net" strings in core that need to be changed in core, just search the code for them. one of the examples: 5. There are the following "endpoints" on both and that code accesses and that should continue to work with the current URLs: /local/hub/webservice/webservices.php /local/hub/webservice/download.php /local/hub/webservice/upload.php /local/hub/siteregistration.php /privacy Important: the redirection should also redirect POST content, not only GET
20.summary: Remove community finder block
description: When moodle.net is closed down in September 2019, the community finder block will no longer be needed. In addition to the community finder block, the capabilities moodle/community:add, moodle/community:download and block/community:addinstance should be removed. It would be good to remove the block plus caps in 3.7.2, 3.6.6 as well as in 3.8.
21.summary: Provide moodle.net error info for sites which dont upgrade
description: For sites which dont upgrade, we need to provide error info when they attempt to use the course-sharing functionality or the community finder block. Thus, we need to determine what error message is shown and the docs link.
22.summary: Update links on moodle.org/demo
description: should have links as follows: Mount Orange School - Moodle sandbox demo - Also, it would be good if the layout could be improved, as it looks a bit odd on smaller screen sizes (as illustrated in the attached screenshot).
23.summary: Update links to school demo site and sandbox demo in Moodle Docs
description: Mount Orange School - Moodle sandbox demo -
24.summary: Redirect user tours, competency frameworks and Boost presets repository links
description: Currently the links moodle.net/tours, moodle.net/competencies and moodle.net/boost on Moodle site administration pages redirect to database activities on moodle.net moodle.net/mod/data/view.php?id=17 etc. Once archive.moodle.net is set up (), well need to redirect the links to archive.moodle.net as follows: -> -> -> Once the new MoodleNet is available, well hopefully to be able to identify a place on it for sharing user tours, competency frameworks and Boost presets and update the redirects accordingly. Note: We need to keep the links moodle.net/tours, moodle.net/competencies and moodle.net/boost for the foreseeable future so that the links are not broken on Moodle sites which havent upgraded. Thus, there is no point at the moment in changing these links in Moodle 3.8.
25.summary: Keep certain legacy endpoints working on the old moodle.net URLs
description: As noticed in : There are the following "endpoints" on both and that code accesses and that should continue to work with the current URLs: /local/hub/webservice/webservices.php /local/hub/webservice/download.php /local/hub/webservice/upload.php /local/hub/siteregistration.php /privacy /local/sitecheck/check.php Important: the redirection should also redirect POST content, not only GET We need to make sure they keep working - redirecting to the new URLs.
26.summary: Create a temporary moodle.net static page
description: From now (October 2019) until the new MoodleNet is launched (November 2019) rather than redirecting moodle.net to archive.moodle.net, it would be better to have a temporary moodle.net static page with links to archive.moodle.net, stats.moodle.org and
27.summary: Prepare a test client site that we can use as a test client
description: To be able to test and it will help to have a temporary moodle installation on the URL such as that we will be able to use in all the testing scenarios in those two issues. Ill be able to customize the docker part of it (we need a clone of moodle.git). But I have to ask for the kubernates setup and the database (either engine is fine, I prefer postgresql personally) that we could use for this site. It can exist in the staging environment.
28.summary: Create new production pods for the stats.moodle.org
description: We need a new production pod where the stats.moodle.org will be running. eduardcerc s to prepare the kubernates, volumes etc. mudrd8mz will configure the docker part as needed for the data and code conversion. Let us start with the same resources as we currently have for the
29.summary: Make the linkchecker work with the new database location
description: The Python linkchecker config needs to be updated so that it can be used against the new database location. As a partt of it, it would be great to come up with a solution to have a testing linkchecker instance available that would work with the staging DB and could be used for testing.
30.summary: Add the HTTP basic auth back for our next sites
description: As a part of testing the redirects and registrations, we have temporarily switched off the HTTP Basic Auth for some of our staging sites (stats, archive, registration, moodle.net). We should re-add that protection back now, using the same credentials as before.
31.summary: Convert accounts from MNet to manual on archive.moodle.net
description: Follow-up tasks from : Convert accounts from MNet to manual so that previous moodle.net users can request a copy of their data or data deletion Add Is this your first time here? instructions explaining how previous moodle.net users can log in
32.summary: Add favicon for stats.moodle.org
description: 

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: Moodle Community Sites
summary: Close down existing moodle.net in an orderly, well-communicated way
description: Moodle.net is a service that has been around since 2010. It allows users to search for and download Moodle courses, as well as database presets, quiz questions, and other Moodle-specific content. In addition, Moodle.net functionality is accessible within the Moodle LMS itself. Users can both share content with the service, as well as search and download relevant content. The existing Moodle.net will be sunsetted (i.e. shut down gracefully and with plenty of notice) when the new MoodleNet| is ready to take over the functionality it offers.

### Response:
1.summary: Moodle links filter updates
description: The Moodle links filter currently links moodle.net to with title text Moodle.net - Courses and content. This needs to be changed to MoodleNet - Connecting and empowering educators worldwide. It would also be cool to add more words to the Moodle links filter: MoodleCloud - linking to Moodle Users Association - linking to MUA - linking to (Edited to amend the moodle.net title text to include Connecting and empowering educators worldwide as stated on
2.summary: Create transition plan for every user-facing subdomain and service on moodle.net
description: Sunsetting moodle.net doc: Delete unused moodle.net subdomains: academy.moodle.net accessibility.moodle.net analyticslrs.moodle.net aws.moodle.net game.moodle.net. gdprdemomaster.moodle.net. gdprdemo.moodle.net. hubzilla.moodle.net. ipv6.moodle.net. learninganalytics.moodle.net. learn-analytics.moodle.net. learn-b.moodle.net. localhost.moodle.net. mec.moodle.net mobile.moodle.net. notify.moodle.net outcomes.moodle.net pinry.moodle.net. prototype.moodle.net. reviews.moodle.net. veronique.moodle.net. www.ipv6.moodle.net| DO NOT TOUCH the following subdomains: app.moodle.net. blog.moodle.net. email.mailg.moodle.net. home.moodle.net. mailg.moodle.net. messages.moodle.net. new.moodle.net. COPY user-facing moodle.net subdomains elsewhere demomaster.moodle.net. master.moodledemo.net demo.moodle.net. moodledemo.net learn.moodle.net learn.moodle.org mary.moodle.net marydev.moodledemo.net qamaster.moodle.net. qamaster.moodle.org qa.moodle.net. qa.moodle.org research.moodle.net. research.moodle.org school.demo.moodle.net. school.moodledemo.net schoolmaster.demo.moodle.net. schoolmaster.moodledemo.net
3.summary: Decide whether we need new domain(s) for moodle.net/sites and moodle.net/stats
description: See comment thread on this GDoc|
4.summary: Archive all existing moodle.net content
description: Wed like to keep the content the community has uploaded to moodle.net but NOT just automatically import it into the new MoodleNet. As a result, we need to plan for a new subdomain (e.g. archive.moodle.net) Steps: Disallow any new content to appear on moodle.net from August 2019 Create archive.moodle.net, transfer content, and make it read-only Take down existing moodle.net and redirect people towards archive.moodle.net (Edited to add steps as mentioned in a comment below.)
5.summary: Figure out everywhere that moodle.net is referenced and how it needs to be updated in Moodle Core
description: We need a list of everywhere that moodle.net is referenced in Moodle Core so we can update the strings for 3.8.
6.summary: Create comms plan for communicating sunsetting of moodle.net
description: This should include Moodle Docs as the single source of truth for the community. Also, lets plan out blog posts and other updates to keep people in the loop.
7.summary: Create plan to redirect registration stats to stats.moodle.org
description: We need to decide on a domain to handle registrations. Moodle.org? Other?
8.summary: Discuss desirability of moving messages.moodle.net elsewhere
description: According to jleyva: "messages.moodle.net| has been used since Moodle 2.4 as the Push backend so we have more than once hundred thousand sites using that address."
9.summary: Create RACI for moodle.net sunsetting
description: 
10.summary: Create plan to change moodle.net functionality in supported versions <3.8
description: Lets discuss this in proposed meeting on 12th June 2019. One for mudrd8mz and others to think about. How can we ensure that users of supported Moodle versions know that existing moodle.net functionality is being/has been deprecated?
11.summary: Perform course housekeeping on Moodle.net
description: Prior to sunetting it would be useful to go through the courses and remove any enrollable courses with past enrolment dates and any downloadable courses with outdated content. That way, the archive will actually contain useful materials.
12.summary: Remove course-sharing functionality
description: Course sharing| on Moodle.net will no longer be possible in Moodle 3.8, so the functionality needs to be removed. The functionality includes: Capabilities moodle/course:publish, moodle/backup:backuptargethub and moodle/restore:restoretargethub Course sharing switch in Advanced features in the Site administration.
13.summary: Delete unused moodle.net subdomains
description: Unused moodle.net subdomains are as follows: academy.moodle.net accessibility.moodle.net analyticslrs.moodle.net aws.moodle.net game.moodle.net gdprdemomaster.moodle.net gdprdemo.moodle.net hubzilla.moodle.net Ipv6.moodle.net learninganalytics.moodle.net learn-analytics.moodle.net learn-b.moodle.net localhost.moodle.net mec.moodle.net mobile.moodle.net notify.moodle.net outcomes.moodle.net pinry.moodle.net prototype.moodle.net reviews.moodle.net veronique.moodle.net www.ipv6.moodle.net
14.summary: Add info to moodle.net informing users it will soon be read-only
description: 
15.summary: Remove course-sharing functionality in Moodle 3.7.2, 3.6.6 and 3.5.8
description: Moodle 3.7.2, 3.6.6 and 3.5.8 are scheduled for release on 9 September 2019. It would be good to remove the course-sharing functionality as in Moodle 3.8 ().
16.summary: Redirect moodle.net subdomains
description: Lets start with: 1. -mary.moodle.net marydev.moodledemo.net- 2. -research.moodle.net research.moodle.org- 3. -prototype.moodle.net -> then: 4. -demo.moodle.net sandbox.moodledemo.net- 5. -demomaster.moodle.net sandboxmaster.moodledemo.net- then check that all is working fine (reset scripts etc), and if so do: 6. -school.demo.moodle.net school.moodledemo.net- color:172b4dcolor:de350b 7. -schoolmaster.demo.moodle.net-colorcolor - schoolmaster.moodledemo.net- Insert from sub ticket - _Remove above list of old user-facing moodle.net subdomains (EXCEPT school.demo.moodle.net as hardcoded into Moodle mobile app and can only update upon release in either August or November 2019 - until Juan Leyva gives go-ahead) and: 8. -qa.moodle.net qa.moodledemo.net- 9. -qamaster.moodle.net qamaster.moodledemo.net- _Note: All the above can be done immediately or at any time before September 2019._ Finally, _to be done after 15 July 2019_: 10. -learn.moodle.net learn.moodle.org- 11. learn.next.moodle.net learn.next.moodle.org Please comment "1, 2, 3 done and ready for checking" etc. before proceeding with further redirects. Note: This issue is only about redirecting subdomains to new subdomains. color:de350bDeletion of moodle.net subdomains will be in another issue (for after we have updated links everywhere). color
17.summary: Split Moodle site registration part of moodle.net to create stats.moodle.org
description: 
18.summary: Split courses and content part of moodle.net to create archive.moodle.net
description: 
19.summary: Code changes required after moving Moodle site registration data to stats.moodle.org
description: Moodle site registration data is being moved from moodle.net to stats.moodle.org (). As a result, changes are required in core code. _Note: needs to be completed before this issue is integrated._ As commented by Marina in : 1. There is one place in core where we store a constant with the "hub" name code define(HUB_MOODLEORGHUBURL, " define(HUB_OLDMOODLEORGHUBURL, " code 2. There was an upgrade script once changing references to -> for sites that were already registered. If we change the value of this variable we will need to repeat it: Note that there are config variables that contain the hub name (from the time when it was possible to register on multiple hubs) (3. removed as it has been done.) 4. There are couple of hardcoded "Moodle.net" strings in core that need to be changed in core, just search the code for them. one of the examples: 5. There are the following "endpoints" on both and that code accesses and that should continue to work with the current URLs: /local/hub/webservice/webservices.php /local/hub/webservice/download.php /local/hub/webservice/upload.php /local/hub/siteregistration.php /privacy Important: the redirection should also redirect POST content, not only GET
20.summary: Remove community finder block
description: When moodle.net is closed down in September 2019, the community finder block will no longer be needed. In addition to the community finder block, the capabilities moodle/community:add, moodle/community:download and block/community:addinstance should be removed. It would be good to remove the block plus caps in 3.7.2, 3.6.6 as well as in 3.8.
21.summary: Provide moodle.net error info for sites which dont upgrade
description: For sites which dont upgrade, we need to provide error info when they attempt to use the course-sharing functionality or the community finder block. Thus, we need to determine what error message is shown and the docs link.
22.summary: Update links on moodle.org/demo
description: should have links as follows: Mount Orange School - Moodle sandbox demo - Also, it would be good if the layout could be improved, as it looks a bit odd on smaller screen sizes (as illustrated in the attached screenshot).
23.summary: Update links to school demo site and sandbox demo in Moodle Docs
description: Mount Orange School - Moodle sandbox demo -
24.summary: Redirect user tours, competency frameworks and Boost presets repository links
description: Currently the links moodle.net/tours, moodle.net/competencies and moodle.net/boost on Moodle site administration pages redirect to database activities on moodle.net moodle.net/mod/data/view.php?id=17 etc. Once archive.moodle.net is set up (), well need to redirect the links to archive.moodle.net as follows: -> -> -> Once the new MoodleNet is available, well hopefully to be able to identify a place on it for sharing user tours, competency frameworks and Boost presets and update the redirects accordingly. Note: We need to keep the links moodle.net/tours, moodle.net/competencies and moodle.net/boost for the foreseeable future so that the links are not broken on Moodle sites which havent upgraded. Thus, there is no point at the moment in changing these links in Moodle 3.8.
25.summary: Keep certain legacy endpoints working on the old moodle.net URLs
description: As noticed in : There are the following "endpoints" on both and that code accesses and that should continue to work with the current URLs: /local/hub/webservice/webservices.php /local/hub/webservice/download.php /local/hub/webservice/upload.php /local/hub/siteregistration.php /privacy /local/sitecheck/check.php Important: the redirection should also redirect POST content, not only GET We need to make sure they keep working - redirecting to the new URLs.
26.summary: Create a temporary moodle.net static page
description: From now (October 2019) until the new MoodleNet is launched (November 2019) rather than redirecting moodle.net to archive.moodle.net, it would be better to have a temporary moodle.net static page with links to archive.moodle.net, stats.moodle.org and
27.summary: Prepare a test client site that we can use as a test client
description: To be able to test and it will help to have a temporary moodle installation on the URL such as that we will be able to use in all the testing scenarios in those two issues. Ill be able to customize the docker part of it (we need a clone of moodle.git). But I have to ask for the kubernates setup and the database (either engine is fine, I prefer postgresql personally) that we could use for this site. It can exist in the staging environment.
28.summary: Create new production pods for the stats.moodle.org
description: We need a new production pod where the stats.moodle.org will be running. eduardcerc s to prepare the kubernates, volumes etc. mudrd8mz will configure the docker part as needed for the data and code conversion. Let us start with the same resources as we currently have for the
29.summary: Make the linkchecker work with the new database location
description: The Python linkchecker config needs to be updated so that it can be used against the new database location. As a partt of it, it would be great to come up with a solution to have a testing linkchecker instance available that would work with the staging DB and could be used for testing.
30.summary: Add the HTTP basic auth back for our next sites
description: As a part of testing the redirects and registrations, we have temporarily switched off the HTTP Basic Auth for some of our staging sites (stats, archive, registration, moodle.net). We should re-add that protection back now, using the same credentials as before.
31.summary: Convert accounts from MNet to manual on archive.moodle.net
description: Follow-up tasks from : Convert accounts from MNet to manual so that previous moodle.net users can request a copy of their data or data deletion Add Is this your first time here? instructions explaining how previous moodle.net users can log in
32.summary: Add favicon for stats.moodle.org
description: 
