Remove communities wherever they appear (#331)

We're retiring the community docs here in favour of the Sharepoint docs
that are internally visible. We don't want to double up the
documentation and have more than one place to update, and the
communities aren't relevant to a public audience.

Author: regularfry

CONTRIBUTING.md

@@ -23,6 +23,6 @@ When committing your changes, please reference the issue they're resolving, so i
 * Preview your Markdown code to make sure the format is not broken.
 * Check grammar, spelling and punctuation, no one wants to look pedantic by requesting changes due to typos or inconsistent grammar/syntax, but it's only fair to keep this tidy.
 * The framework is open to the world. This has a few implications:
-  * Nothing in it should be confidential, private to NHSD or include any personal data.
+  * Nothing in it should be confidential, private to NHSE or include any personal data.
   * All links in framework pages should be public.
 * Use [inclusive language](inclusive-language.md): avoid terms which cause hurt and offence, including if they have historically been considered industry-standard terms.

README.md

@@ -42,11 +42,6 @@ The framework consists of:
 
 * [Engineering principles](principles.md) and [blueprints](blueprints.md)
 * [Engineering quality review tool](insights/review.md)
-* [Communities of practice guidelines](communities/communities-of-practice.md) and active communities:
-  * [Product Development Test Automation Working Group](communities/pd-test-automation-working-group.md)
-  * [Product Development Engineering CoP](communities/pd-engineering-cop.md)
-  * [Product Development Cloud PaaS Working Group](communities/pd-cloud-working-group.md)
-  * [Secure Engineering CoP](communities/security-cop.md)
 * Guidance on how to practice [continuous improvement](continuous-improvement.md)
 
 ## Contributing

communities/communities-of-practice.md

@@ -19,7 +19,6 @@
 
 - These notes are part of a broader set of [principles](../principles.md)
 - This is related to [Engineering quality checks](../quality-checks.md)
-- Related community of practice: [Test Automation Working Group](../communities/pd-test-automation-working-group.md)
 - See also:
   - [Quality Metrics](../quality-checks.md)
   - [Continuous integration](continuous-integration.md)

communities/pd-cloud-working-group.md

@@ -15,7 +15,6 @@
 ## Context
 
 - These notes are part of a broader set of [principles](../principles.md)
-- Related community of practice: [Test Automation Working Group](../communities/pd-test-automation-working-group.md)
 - See also:
   - [Continuous integration](continuous-integration.md)
   - [Governance as a side effect](../patterns/governance-side-effect.md)

communities/pd-engineering-cop.md

@@ -46,8 +46,4 @@ Create branches and submit Pull Requests to add your own content, or improve exi
 
 [Raise an Issue](https://github.com/NHSDigital/software-engineering-quality-framework/issues/new) for things you would like us to add or amend.
 
-Join the [Communities of Practice](communities/communities-of-practice.md) that jointly input into the Framework.
-
-Join weekly knowledge-sharing meetings, focused on building shared solutions.
-
 Ask for a Technical Coach to help guide your team. You can also offer yourself up as a coach to help other teams.