-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update and refactor CoC policy and processes #1135
Conversation
18b023b
to
808ab78
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
b692f74
to
fa51125
Compare
Thank for your thorough review, @eemeli. I think I've answered or addressed the issues you raised. I've now marked them as resolved. Feel free to LMK if you disagree with my responses. Thanks again for chiming in. Much appreciated! |
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
…scalation Allow CoC Team to involve CPC if necessary and project leadership if appropriate.
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Co-authored-by: Eemeli Aro <eemeli@gmail.com> Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Co-authored-by: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com> Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Seems like this PR removed this page: https://github.com/openjs-foundation/cross-project-council/blob/0c30a269acb2cc0b22cf3c62b8389e779bda0101~1/conduct/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md but the link still exists somewhere, so the link checker is failing |
Must have missed this one which is in meeting minutes:
It's kind of weird to be editing minutes years later for this, tbh. |
true, but cool URLs don't change, so the alternative is never fully removing any markdown files :-) |
- Clearly split all CoC related-documents into 4 buckets: 1. The **Code of Conduct** itself, which is also the source of truth for the makeup of the CoC Team, how to contact the CoC Team, and how to report an incident, escalate it, and appeal a decision. 2. The **Code of Conduct Policy**, which defines the higher level aspects of our code of conduct implementation (the _what_). 3. The **CoC Team Charter** which is the mean by which the CPC delegates responsibilities to the CoC Team. 4. Various related **processes** which describe _how_ the policy is implemented. - Replace the Code of Conduct Panel with a Code of Conduct Team instead. - Standardize on the language used in the Contributor Covenant and in the CNCF and use it consistently throughout. - Clarify the escalation and appeal policies. - Be explicit about the projects's freedom to implement moderation policies - Create a placeholder for all of the processes related to the makeup and structure of the CoC Team. - Add an indication at the top of each related file pointing people who just want to report an incident to the right place. - Clean up a number of smaller issues. - Clarify the requirements for projects who opt-in to manage incident reports themselves. Make the policy generic so that it applies both to those projects and to the CoC. --------- Signed-off-by: Tobie Langel <tobie@unlockopen.com> Signed-off-by: Paula <8395352+PaulaPaul@users.noreply.github.com> Co-authored-by: Michael Dawson <mdawson@devrus.com> Co-authored-by: Jordan Harband <ljharb@gmail.com> Co-authored-by: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com> Co-authored-by: Ben Hutton <relequestual@gmail.com> Co-authored-by: Paula <8395352+PaulaPaul@users.noreply.github.com> Co-authored-by: Eemeli Aro <eemeli@gmail.com>
Still to do:
This is now ready to land pending: