terminology
A configuration file for in-solidarity-bot that flags some of the terms in the NIST Technical Series Publications Author Instructions and the IETF's list of problematic terminology. (by ietf)
contributor_covenant
Pledge your respect and appreciation for contributors of all kinds to your open source project. (by ContributorCovenant)
terminology | contributor_covenant | |
---|---|---|
2 | 17 | |
61 | 1,813 | |
- | 0.7% | |
0.0 | 7.3 | |
almost 2 years ago | 11 days ago | |
CSS | ||
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terminology
Posts with mentions or reviews of terminology.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Companies use dark patterns to keep you subscribed
The IETF for one https://github.com/ietf/terminology/pull/9
My intent wasn't to appeal to authority though. I think it's a better term.
-
Why I'm losing faith in UX
You can propose to https://github.com/ietf/terminology
contributor_covenant
Posts with mentions or reviews of contributor_covenant.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-25.
-
Qilin: A Starter Project Template For Every Open Source Project
While you are free to write your own or adopt one from another repository, project, or organization you respect, there exists a code of conduct written and maintained by the community known as the Contributor Covenant.
-
Get People Interested in Contributing to Your Open Project
Many Open Source projects have adopted the Contributor Covenant as their code of conduct. Check this page to see a list of adopters.
-
Hyprland Is a Toxic Community
https://www.contributor-covenant.org/ is (was?) the most widely adopted code of conduct in FOSS, initially drafted by a Ruby contributor, who also happens to be transgender if that's pertinent information to you. It's the genesis seed from which all this code of conduct madness stems from. Personally I'd stick with "be excellent to each other" or "say what you want, just don't insult other contributors" or something vague, ambiguous and universally understood as that. I'm not really a fan of rigorous social rules, so my view on this starts from that position.
-
Setting up your GitHub Repository for Open Source Development
You can adapt the guidelines provided by https://www.contributor-covenant.org/ to create your guideline.
-
PrismLauncher (the replacement for PolyMC) is now on flathub
The Contributor Covenant that the maintainer removed to "reclaim polymc from the leftoids" was added in February: https://github.com/PolyMC/PolyMC/pull/178. You can view a list of other communities that have adopted the covenant on their website.
-
What's going on with PolyMC being declared compromised?
For reference, the Code of Conduct they used is basically the same as this one: https://www.contributor-covenant.org/
-
cppfront: meta
Please follow the Contributor Covenant
-
How to Open Source Your Project
As your audience grows, it is vital that you define clear rules to create a safe environment for everyone to participate. A common way of doing this is to define a code of conduct (CoC), which sets some basic guidelines on what kind of community interaction will not be tolerated. We decided to stick to well-established frameworks and based our CoC on the Contributor Covenant.
- The SQLite Code of Ethics
-
Introducing OpenSourceLaw
Those aren't the only ways I could see things happen, but that represents a few points on the spectrum. Having been participating in the English Wikipedia community since the early days, I know that collaborative writing on a worldwide scale is hard, and leads to misunderstandings and hurt feelings. Hence the reason why things like the Contributor Covenant came out, and why Linus Torvalds took such a long time accepting something. Note, things labeled "Code of Conduct" and "Contributor Covenant" are one small slice of governance. Dealing with things like the ideal public transit system create a massive extra layer of complexity. Governance, in general, is difficult.
What are some alternatives?
When comparing terminology and contributor_covenant you can also consider the following projects:
i-d-template - A template for IETF internet draft git repositories
cortx - CORTX Community Object Storage is 100% open source object storage uniquely optimized for mass capacity storage devices.