Move CoC workflow into Community Operations handbook
Why is this change being made?
The Community Advocacy program was retired last year, and the Code of Conduct workflow is still partially used the same way. This MR does the following:
- Move the workflow into Community Operations handbook
- Make the Community Relations team responsible for CoC moderation
- Add redirects and update handbook URLs
- List the workflows in main Community Relations handbook
to ensure we have a stable workflow for CoC violations and enforcements.
More in details Slack (internal).
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what -
Assign this change to the correct DRI - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
-
If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping(this requirement has been removed pending identification of a new DRI for the handbook)@gl-static-site-editor
in a comment for a review and merge. For example changes to.gitlab-ci.yml
, JavaScript/CSS/Ruby code or the layout files.