- Mention where reports should be made.
- Mention expectations regarding propagation of bans and provide context.
- Provide additional means of recourse in cases of interpersonal conflicts
between a participant and a moderator. - Explain that moderation standards can be stricter (and not ToU-only)
at the behest of a moderator.
Contact: Add 'Community channels' section to Abuse #685
@ -88,0 +92,4 @@
If you witness abusive behavior in our channels, please report it to its active moderators
directly (and, if appropriate, privately).
If you wish to complain about the moderation of our channels, please [contact the e. V.](#email)
(either specific moderators or the lack of said moderation)
Keep in mind that I have been in a dispute over my moderation with a participant at least once. In such cases, I would like to provide an additional means of recourse (or at least have a third person get in between).
We should probably make "points of contact" with the option to directly contact in the future (not necessarily an awareness team, but would be a neat first step).
ccd29cf7f0
480d3d1910
Surge PR preview deployment was removed
@ -88,0 +100,4 @@
To ensure the community's health and foster a friendly and welcoming climate, a channel's
moderators can apply stricter moderation standards as they deem fit.
For instance, they can warn or exclude (i.e. mute, kick, ban) individuals over disruptive behavior
(e.g. trolling, [sealioning]) temporarily or permanently, proactively or reactively.
We have banned people (i.e. known bad faith actors) preemptively from our Matrix chats before. We have banned people that received repeated warnings over concern trolling, sarcastic and otherwise toxic behavior - but did not ban their Codeberg.org account with, idk, 2-3 random repositories.
Some people just don't work well in places with other people (or they might be annoying/disruptive) - but that alone may not be reason enough to exclude them from all repositories hosted on Codeberg.org.
This principle may also apply to Codeberg.org services as well: Someone may abuse our CI (or otherwise violates the terms for using it), and we may simply prevent them from using our CI. Or, depending on the severity and if it's a matter beyond reasonable doubt, the action taken might be stricter.
480d3d1910
2e441446f3
Some further motivations behind this change are:
- Explain the moderation team's modus operandi and better clarify "our responsibility" depending on where something took place.
- Find the opportunity to mention how "users/organizations can work in isolation from each other".
- Explain what the reporter should expect when reporting something or someone.
- Explain the standards that should be expected from the moderation of our discussion rooms on e.g. Matrix, including that "something doesn't have to be strictly in our Terms of Use" to warrant a ban/kick/etc.
2e441446f3
9b9713a183
Sounds great.
9b9713a183
c55c3fd142
@gusted force-pushed to fix the conflict, mind doing the honors? :D
Issues affecting Codeberg Pages
Issues related to using and reading docs.codeberg.org
This is related to the generation of the documentation, not to the content itself
The priority is high
The priority is low
The priority is medium
Something has been confirmed
Something exists already
Something was marked as invalid
Something won't be fixed
Contributions are welcome!
Work is in progress
Feedback is needed
Work is completed
Review is in progress / Reviewers wanted
No due date set.
No dependencies set.
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?