Simplify CoC page (#782)

* Simplify CoC page

Closes #781.

* Make handling CoC violations the responsibility of the CPC for project which don't have a documented process

Author: tobie

.remarkrc

@@ -5,6 +5,7 @@
     ["remark-lint-list-item-bullet-indent", false],
     ["remark-lint-no-literal-urls", false],
     ["remark-lint-no-shortcut-reference-link", false],
+    ["remark-lint-no-auto-link-without-protocol", false],
     ["remark-lint-no-undefined-references", false]
   ]
 }

CODE_OF_CONDUCT.md

@@ -1,66 +1,41 @@
 # Code of Conduct
 
-The OpenJS Foundation and its member projects use [Contributor Covenant v2.0](https://contributor-covenant.org/version/2/0/code_of_conduct) as their code of conduct. The full text is included [below](#contributor-covenant-code-of-conduct) in English, and translations are available from the Contributor Covenant organisation:
-
-- [contributor-covenant.org/translations](https://www.contributor-covenant.org/translations)
-- [github.com/ContributorCovenant](https://github.com/ContributorCovenant/contributor_covenant/tree/release/content/version/2/0)
-
-Refer to the sections on reporting and escalation in this document for the specific emails that can be used to report and escalate issues.
-
-## Reporting
-
-### Project Spaces
-
-For reporting issues in spaces related to a member project, please use the email provided by the project for reporting which has been provided below. Projects handle CoC issues related to the spaces that they maintain. Projects maintainers commit to:
-
-- maintain the confidentiality with regard to the reporter of an incident
-- to participate in the path for escalation as outlined in
-  the section on Escalation when required.
-
-#### Project Reporting Emails
-
-* AMP Project - `[email protected]`
-* Appium - [email maintainers]
-* Architect - 
-* Dojo - `[email protected]`
-* Electron - `[email protected]`
-* ESLint - `[email protected]`
-* Esprima - 
-* Express.js - `[email protected]`
-* Fastify - `[email protected]` or `[email protected]`
-* Grunt - 
-* HospitalRun - `[email protected]`
-* Interledger.js - 
-* Intern - 
-* JerryScript - 
-* jQuery - 
-* libuv - 
-* LoDash - 
-* messageformat - 
-* Marko - 
-* Mocha - `[email protected]`
-* Moment.js - 
-* Node.js - `[email protected]`
-* Node-RED - `[email protected]`
-* nvm - 
-* Pep - 
-* QUnit - 
-* Webdriver.io - [contact TSC reps](https://github.com/webdriverio/webdriverio/blob/HEAD/AUTHORS.md)
-* Webhint - `[email protected]`
-* webpack - [redirects here]
-
-### Foundation Spaces
-
-For reporting issues in spaces managed by the OpenJS Foundation, for example, repositories within the OpenJS organization, use the email `[email protected]`. The Cross Project Council (CPC) is responsible for managing these reports and commits to:
-
-- maintain the confidentiality with regard to the reporter of an incident
-- to participate in the path for escalation as outlined in
-  the section on Escalation when required.
-
-## Escalation
-
-The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a foundation-wide team established to manage escalation when a reporter believes that a report to a member project or the CPC has not been properly handled. In order to escalate to the CoCP send an email to `[email protected]`.
+The OpenJS Foundation and its member projects use [Contributor Covenant v2.0](https://contributor-covenant.org/version/2/0/code_of_conduct) as their code of conduct. The full text is included [below](#contributor-covenant-code-of-conduct) in English, and [translations](https://www.contributor-covenant.org/translations) are available on the Contributor Covenant website.
 
+## Commitment
+
+All recipients of reports commit to:
+
+- maintain the confidentiality with regard to the reporter and victim of an incident, and
+- participate in the path for escalation as outlined in the section on Escalation when required.
+
+## Report an issue in a project
+
+1. To report an issue in one of the projects listed below, please use the method provided. The project itself is responsible for managing these reports.
+    * **AMP Project:** <[email protected]>
+    * **Appium:** email maintainers
+    * **Electron:** <[email protected]>
+    * **Express.js:** <[email protected]>
+    * **Fastify:** <[email protected]> or <[email protected]>
+    * **HospitalRun:** <[email protected]>
+    * **Node.js:** <[email protected]>
+    * **Node-RED:** <[email protected]>
+    * **Webdriver.io:** [contact TSC reps](https://github.com/webdriverio/webdriverio/blob/HEAD/AUTHORS.md)
+    * **Webhint:** <[email protected]>
+2. For every other OpenJS Foundation project, please email <[email protected]>. The Cross Project Council (CPC) is responsible for managing these reports.
+
+
+## Report an issue in a space managed by the foundation
+
+For reporting issues in spaces managed by the OpenJS Foundation, for example, repositories within the OpenJS organization or an live event such as a conferences, email <[email protected]>. The Cross Project Council (CPC) is responsible for managing these reports.
+
+## Escalate an issue
+
+The OpenJS Foundation maintains a [Code of Conduct Panel (CoCP)](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md#code-of-conduct-panel). This is a foundation-wide team established to manage escalation when a reporter believes that a report to a member project or the CPC has not been properly handled.
+
+In order to escalate to the CoCP, email <[email protected]>.
+
+## More Info
 
 For more information, refer to the full
 [Code of Conduct governance document](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md).

CPC-CHARTER.md

@@ -181,6 +181,7 @@ Subject to such policies as may be set by the Board, the CPC is responsible for:
    1. Shared resources, tooling and funding for projects (Collaborator Summit Events, Travel fund).
    1. Supporting projects in their enforcement of Code of Conduct
       violations and escalation.
+   1. Handling Code of Conduct violations for projects which do not have a documented process to do so.
    1. Developing a framework for community end-user feedback.
    1. Managing programs to offer mentorship to external individuals.
    1. Managing developer outreach programs.