copyleft-next/code-of-conduct
1
1
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

initial changes to the Contributor Covenant Code of Conduct for copyleft-next project adaptation. #1

Open
bkuhn wants to merge 13 commits from bkuhn/initial-coc-modifications into main
pull from: bkuhn/initial-coc-modifications
merge into: copyleft-next:main
Conversation 3 Commits 13 Files changed 1 +37 -10
bkuhn commented 2026-06-16 03:35:17 +00:00
Owner
Copy link

These are the initial changes that should adequately tailor the Contributor Covenant Code of Conduct 3.0 for the copyleft-next project.

Sending this to review by Richard Fontana, the Community Moderators volunteers, and the copyleft-next mailing list.

These are the initial changes that should adequately tailor the Contributor Covenant Code of Conduct 3.0 for the copyleft-next project. Sending this to review by Richard Fontana, the Community Moderators volunteers, and the copyleft-next mailing list.
The guide for using this Code of Conduct recommends writing your own
section here.
This is the only place the phrase “Community Managers” is used, so it
could surely be “Community Moderators”
The HBR is a guideline but not a specific code of conduct or covenant
from contributors.  However, we should note this here for avoidance
of any doubt, as many may already see HBR as the CoC of copyleft-next
— even though it was never intended to be.
bkuhn force-pushed bkuhn/initial-coc-modifications from c32b4c5ac6 to 14b26fa2a8 2026-06-17 00:34:44 +00:00 Compare 
The preceding paragraph clarifies that HBR infractions are not “read
into” this Covenant as violations.

However, a tangential problem is addressed herein: this Covenant must
operate independently of HBR, and when in conflict, the Covenant
supersedes.
Of course, with an “including but not limited to”.
bkuhn force-pushed bkuhn/initial-coc-modifications from 0b104f0ca4 to 9ba7fff94a 2026-06-17 01:12:44 +00:00 Compare
ref commented 2026-06-17 03:20:05 +00:00
First-time contributor
Copy link

Looks good to me.

Looks good to me.
jwheel commented 2026-07-01 06:44:25 +00:00
First-time contributor
Copy link

Sorry I have been dragging my feet here. I have had it on my to-do list since some of my work travel ended in June… but I promise, this is on my list. Going to try and make a thorough pass before the end of this week.

Sorry I have been dragging my feet here. I have had it on my to-do list since some of my work travel ended in June… but I promise, this is on my list. Going to try and make a thorough pass before the end of this week.
jwheel approved these changes 2026-07-08 01:04:03 +00:00
jwheel left a comment
Copy link

Overall, LGTM. No blocking feedback, but I have some thoughts.

I left in-line comments for a vocabulary nitpick I had and an open-ended question on from what authority the CoC is empowered to act under in the project.

The Interaction with HBR is a non-conventional addition but it reads how I would hope it would read when comparing with the guideline document. Overall, the changes from the original Contributor Covenant v3.0 make sense to me.

Overall, LGTM. No blocking feedback, but I have some thoughts. I left in-line comments for a vocabulary nitpick I had and an open-ended question on from what authority the CoC is empowered to act under in the project. The _Interaction with HBR_ is a non-conventional addition but it reads how I would hope it would read when comparing with the guideline document. Overall, the changes from the original Contributor Covenant v3.0 make sense to me.
CODE_OF_CONDUCT.md Outdated
@ -47,3 +51,3 @@
Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
When an incident does occur, it is important to report it promptly. To report a possible violation, **[NOTE: describe your means of reporting here.]**
Report an alleged violation under this Covenant to the Community Moderation Committee ("Community Moderators"). The committee is comprised of three individuals; the individuals are chosen by the following criteria:
jwheel commented 2026-07-08 00:56:00 +00:00
First-time contributor
Copy link

I'm finding "Community Moderation Committee" and "Community Moderators" to be distracting here. I would personally distinguish it clearly as Code of Conduct Committee Members and use this vocabulary consistent throughout.

The reason I point this out is that community moderation can be a wide, general effort. In a healthy community, there might be many different people performing a moderator-type role. However, a Code of Conduct Committee is more than just everyday moderation; it is a pathway of escalation when other pathways are exhausted. I think distinguishing the three named people in this document as Code of Conduct Committee Members is better to avoid confusion, now or in the future. Not just anyone can raise their hand to join a CoC Committee.

I'm finding "Community Moderation Committee" and "Community Moderators" to be distracting here. I would personally distinguish it clearly as Code of Conduct Committee Members and use this vocabulary consistent throughout. The reason I point this out is that community moderation can be a wide, general effort. In a healthy community, there might be many different people performing a moderator-type role. However, a Code of Conduct Committee is more than just everyday moderation; it is a pathway of escalation when other pathways are exhausted. I think distinguishing the three named people in this document as Code of Conduct Committee Members is better to avoid confusion, now or in the future. Not just anyone can raise their hand to join a CoC Committee.
bkuhn marked this conversation as resolved
CODE_OF_CONDUCT.md Outdated
@ -75,3 +89,3 @@
3) Repair: There is no possible repair in cases of this severity.
This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
This enforcement ladder is intended as a guideline. It does not limit the ability of Community Moderators to use their discretion and judgment, in keeping with the best interests of our community.
jwheel commented 2026-07-08 00:57:43 +00:00
First-time contributor
Copy link

As far as authorities for appeal, I wonder if the CoC Committee "reports" to anyone. Who gives the Committee a wide-reaching mandate, charter, and authority to uphold the CoC? Maybe it doesn't matter at the current scale of operation, but might be something to think about in a future updated version.

As far as authorities for appeal, I wonder if the CoC Committee "reports" to anyone. Who gives the Committee a wide-reaching mandate, charter, and authority to uphold the CoC? Maybe it doesn't matter at the current scale of operation, but might be something to think about in a future updated version.
bkuhn commented 2026-07-22 15:52:07 +00:00
Author
Owner
Copy link

@jwheel , this is indeed the meta “Quis custodiet ipsos custodes?” problem, but I think we should table that. Would you mind opening a separate issue against this repositroy for this (I don't think I can move this into a new issue, at least I don't know how to with Forgejo. It should be a standing item open, but at this point, the fact that Richard and I have someone who is watching us, the guards for the meta-guards probably isn't urgent, and this is why I've invited people who care about copyleft-next but aren't planning to be heavily involved to be the initial CoC Committee.

@jwheel , this is indeed the meta “Quis custodiet ipsos custodes?” problem, but I think we should table that. Would you mind opening a separate issue against this repositroy for this (I don't think I can move this into a new issue, at least I don't know how to with Forgejo. It should be a standing item open, but at this point, the fact that Richard and I have someone who is watching *us*, the guards for the meta-guards probably isn't urgent, and this is why I've invited people who care about copyleft-next but aren't planning to be heavily involved to be the initial CoC Committee.
The original version of this patch was posted to the mailing list,
and there were no objections, and some endorsements.

Goal here is to handle that the Fediverse platforms generally require
more aggressive moderation and banning than other types of platforms.
jwheel was right that the entire text was muddled as I'd carried
forward the terms “Community Managers” and “Community Moderators”
from upstream — which were *not* presented upstream as defined terms
and therefore were confusing from the start of this drafting.

We can always add roles of those names as the project becomes larger
and such are needed.

Forgejo-Comment: #1 (comment)
These three have agreed to serve on our CoC Committee.  They are all
three excited and interesting in copyleft-next, but are great choices
for the CoC Committee as they don't plan to have time available to do
extensive work directly on the project — giving them a good distance
to make good decisions.

“Illi sunt custodes qui alios custodes custodiunt.”
“Member” is not a defined term so shouldn't be capitalized.

“Committee” was used by itself in various places, but the defined
term is “CoC Committee”
bkuhn changed title from WIP: initial changes to the Contributor Covenant Code of Conduct for copyleft-next project adaptation. to initial changes to the Contributor Covenant Code of Conduct for copyleft-next project adaptation. 2026-07-23 00:47:45 +00:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin bkuhn/initial-coc-modifications:bkuhn/initial-coc-modifications
git switch bkuhn/initial-coc-modifications

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff bkuhn/initial-coc-modifications
git switch bkuhn/initial-coc-modifications
git rebase main
git switch main
git merge --ff-only bkuhn/initial-coc-modifications
git switch bkuhn/initial-coc-modifications
git rebase main
git switch main
git merge --no-ff bkuhn/initial-coc-modifications
git switch main
git merge --squash bkuhn/initial-coc-modifications
git switch main
git merge --ff-only bkuhn/initial-coc-modifications
git switch main
git merge bkuhn/initial-coc-modifications
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
jwheel
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
copyleft-next/code-of-conduct!1
No description provided.