1
0
Fork
You've already forked template
0

Add a code of conduct #2

Open
opened 2026年06月20日 14:02:56 +02:00 by MultisampledNight · 2 comments
No description provided.

Specifically, write a CONTRIBUTING.md covering both our standards and shared constraints

Specifically, write a `CONTRIBUTING.md` covering both our standards and shared constraints
- Why? At the *very* least, to avoid a [contempt culture](https://blog.aurynn.com/2015/12/16-contempt-culture/) and [negative moral licensing](https://nonzerosum.games/morallicensing1.html) - Inspiration - CoC set up by Safe the Dance, an agency for awareness on events: https://safethedance.de/en/coc/ - CoC of the Tor Project: https://community.torproject.org/policies/code_of_conduct/ - CoC of postmarketOS: https://docs.postmarketos.org/policies-and-processes/community/code-of-conduct.html - CoC of MetaBrainz: https://metabrainz.org/code-of-conduct - Feels substantially different than the others. Covers less "obvious" things, perhaps? Expects neutrality while acknowledging subjectivity. - The manifesto for radical software development: http://cryto.net/~joepie91/manifesto.html - Other thoughts - Acknowledge that mistakes *in general* are inevitable and opportunities to learn; so that mistakes *in specific* are avoided - Resolve zero-sum games into solidarity (de-escalate early and preemptively) - We should optimize for a [positive double standard](https://nonzerosum.games/positivedoublestandard.html): While the CoC is read by an individual, it reflects shared values - Tor and pmOS both have transparency reports and dedicated code of conduct teams. Maybe this template needs some "bootstrapping" logic in assigning responsibility - The transparency reports could be in-repo - Link to the CoC right in the README - Reflect that every tech has political implications and that every change of tech has social implications > Dangerous is the theory that continues to run without being noticed. (https://die-architekt.net/zeit-der-monster/) - Problem factors - Length. Drive-by contributions are a symptom of a culture that does not reward longer-term involvement, not the problem. We still want them, hence keep the total reading time below 10 minutes at most - Nuance and positivity. Avoid writing down specific patterns to avoid, rather show the behavior we *want*.
Sign in to join this conversation.
No Branch/Tag specified
next
release
No results found.
Labels
Clear labels
0-Status
0-Backlog
Can be picked up if so desired.
0-Status
1-Blocked
Cannot progress at the moment due to an external dependency (outside of this repository).
0-Status
2-Planned
Aim to do next sprint.
0-status
3-Todo
Aim to do this sprint.
0-Status
4-Progressing
Working on that in this very moment.
0-Status
5-Feedback desired
Please take a look and review. Can be done by anyone, including you!
0-Status
Needs triage
Please assign more fitting labels and give an initial response.
1-Priority
0-Frozen
Not a factor right now.
1-Priority
1-Low
Keep on radar, do if enough time emerges.
1-Priority
2-Medium
Want to do this in the mid-term.
1-Priority
3-High
Do this in the short-term.
1-Priority
4-Critical
Do this as soon as possible.
2-Complexity
1-Low
Should not have any complications. Straightforward. Often "dull" chores.
2-Complexity
3-High
Deeply intertwined and nested.
3-Area/Code
3-Area/Communication
Exchanging information and talking with others. Beep boop.
3-Area/Design
Planning and thinking about user interactions.
3-Area/Documentation
Writing down processes and emergence of the status quo.
3-Area/Meta
Informative (not actually an issue).
4-expertise/Accessibility
Removing barriers, comprehending the intricacies of interfaces.
4-expertise/Security
Catching assumptions and fixing loopholes.
5-stakeholder/Add a stakeholder here
5-type
Bug
Something doesn't work as expected.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
MultisampledNight/template#2
Reference in a new issue
MultisampledNight/template
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?