-
Notifications
You must be signed in to change notification settings - Fork 225
Update COC to CC 3.0 #1724
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
base: main
Are you sure you want to change the base?
Update COC to CC 3.0 #1724
Conversation
356b38f to
ec50cf4
Compare
|
To me, this PR qualifies as changing governance so we will leave open for 14 days before merging. |
joesepi
left a comment
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. Thanks!
mcollina
left a comment
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.
Adding a soft block because I don't see an explanation on how the objections were resolved
|
@mcollina Good call out. The objection from @tobie is raised in this comment and is pasted below: For context, the sentence in question was point 5 of the restricter behaviors: "Violating confidentiality. Sharing or acting on someone’s personal or private information without their permission." As discussed during the CPC call, the intention of that language isn't to prevent information sharing when enforcing the CoC, but the language is confusing and creates opportunities for contesting CoC Team decisions. imho, it should be clarified. I believe this is addressed in the section under Reporting an Issue: Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. If this is not adequate we have the ability to clarify by customizing language in sections if appropriate. @tobie can you advise on if the language is sufficient or if you would like clarification and if so, what text do you suggest? |
|
If @tobie is ok, I'm ok. |
|
Mr. @tobie your expertise is required. |
Fixes #1457
I think the questions/concerns folks had with an earlier revision of the contributor covenant are no longer present. This PR updates our COC documentation to reference the 3.0 version of the contributor covenant.