open-slopware/GOVERNANCE.md
cerox 6e34b6b06c fix spelling (#1029)
### Description of Changes

This PR fixes spelling throughout the CoC, Governance doc and Contributing doc.

Reviewed-on: https://codeberg.org/ethical-foss/open-slopware/pulls/1029
Reviewed-by: Ethical FOSS admin <ethical-foss-admin@noreply.codeberg.org>
2026-06-22 07:39:22 +02:00

4.3 KiB

Who does What

This repo wouldn't exist without the hundred or so people who contribute to it. We value everyone's contributions, but for certain tasks, we have a structure on who can do what.

So it is clear: This is not anyone's full time job. Everyone is an unpaid volunteer working in their free time, including the owners.

Owners

This is mainly @ethical-foss-admin which is an account that is run by multiple people who initially forked this repo. They have the ability to make new rules or tags and updates to the code of conduct. They have full approval and merge rights. If they've approved any PR, Team Human Made can pop in and merge that PR at their leisure. If you're asking for a new rule, tag, or major change to the repo in some way, you need to tag this account. This is also the account you should tag should you need moderation help in any capacity, as they have the authority to ban people from the repo, as well as lock a conversation if it gets too heated or has the potential to drive a rude atmosphere.

If future owners appear, the tag to get them involved would be @ethical-foss/owners.

Team Human Made

This is a special team of collaborators that have been vetted over time via their kind attitudes and continued contributions to the repo. When they show up in the repo, they will have a "member" tag on all their posts to distinguish them. They have the ability to speak on behalf of the repo when it comes to already established rules, and are frequently tagged on matters of discussion. They can also approve PRs, and it carries weight, but does not count towards the official approval required to allow a merge (something that may change in the near future). They can also merge anything that was already approved by the Owners.

If they ask you to update something, or make a suggestion to improve something, please engage kindly.

The entire team can be tagged with @ethical-foss/team-human-made. Please prefer tagging Team Human Made instead of a specific member, as to not weigh down one particular collaborator as, again, they all work on this in their free time.

How to Become a Member of Team Human Made

When positions on Team Human Made are available, we'll create an Issue asking for people to apply and/or nominating specific people. You should not feel pressure to accept a position if you do not want it. We are still happy to have you as a contributor.

We vet collaborators over a period of a couple of months of continued contributions. Provided you:

  • are kind and take feedback well
  • have participated in either PRs or Issues semi-regularly
  • have no Code of Conduct strikes (warnings can be OK depending on the warning, how you reacted, and how long it has been since your warning)
    • do not have a visible history of behavior that would violate our Code of Conduct (even outside of this repo)

There is no time requirement for how much you need to do in the repo once you're made a collaborator. Everyone should operate to the best of their ability. If you need time off for personal life, don't sweat it.

Contributors

These are people who contribute to the repo. They have no special access. Anyone can be a contributor. They cannot approve or merge PRs, and they are not allowed to speak on behalf of the repo. If they would like to give an opinion on a discussion, they're free to do so, but if answering a question, they should state that they're not official maintainers, then tag in @ethical-foss/owners and/or @ethical-foss/team-human-made for an official response.

Vacations

This repo gets put into "vacation mode" periodically through out the year. We do this because we need time away from the repo, and during that time, we can't guarentee any moderation, so for safety, no commenting on the repo can be allowed during that time.

During vacation mode, we will disable Issues and Pull Requests and will not actively work on the repo in any way. The repo will still be public. There will be a notice at the top of README explaining that we're in vacation mode and when we will be back. When the vacation is over, the Issues and Pull Requests will be re-enabled.

Vacations typically last anywhere from 3 days to 2 weeks depending on the owner's schedule, and are announced in advance.

The owners reserve the right to put the repo into vacation mode if they are unwell and unable to tend to the repo.