Codeberg/Documentation
43
151
Fork
You've already forked Documentation
128

Contact: Add 'Community channels' section to Abuse #685

Merged
Gusted merged 1 commit from n0toose/abuse-community-spaces into main 2025年10月26日 13:30:42 +01:00 AGit
  • 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.
- 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.
@ -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)
Author
Owner
Copy link

(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).

(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).
n0toose force-pushed n0toose/abuse-community-spaces from ccd29cf7f0
Some checks failed
ci/woodpecker/pr/build Pipeline failed
ci/woodpecker/pr/lint Pipeline failed
ci/woodpecker/pr/deploy-preview Pipeline failed
to 480d3d1910
Some checks failed
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/lint Pipeline failed
ci/woodpecker/pr/deploy-preview Pipeline was successful
2025年10月20日 08:07:24 +02:00
Compare

Surge PR preview deployment was removed

<!--woodpeckerci-plugin-surge-preview--> 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.
Author
Owner
Copy link

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.

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.
n0toose force-pushed n0toose/abuse-community-spaces from 480d3d1910
Some checks failed
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/lint Pipeline failed
ci/woodpecker/pr/deploy-preview Pipeline was successful
to 2e441446f3
Some checks failed
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/lint Pipeline failed
ci/woodpecker/pr/deploy-preview Pipeline was successful
2025年10月20日 08:19:51 +02:00
Compare
Author
Owner
Copy link

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.
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.
n0toose force-pushed n0toose/abuse-community-spaces from 2e441446f3
Some checks failed
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/lint Pipeline failed
ci/woodpecker/pr/deploy-preview Pipeline was successful
to 9b9713a183
All checks were successful
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/lint Pipeline was successful
ci/woodpecker/pr/deploy-preview Pipeline was successful
2025年10月20日 08:24:01 +02:00
Compare
Gusted left a comment
Owner
Copy link

Sounds great.

Sounds great.
n0toose force-pushed n0toose/abuse-community-spaces from 9b9713a183
All checks were successful
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/lint Pipeline was successful
ci/woodpecker/pr/deploy-preview Pipeline was successful
to c55c3fd142
All checks were successful
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/lint Pipeline was successful
ci/woodpecker/pr/deploy-preview Pipeline was successful
ci/woodpecker/pull_request_closed/deploy-preview Pipeline was successful
2025年10月20日 21:27:58 +02:00
Compare
Author
Owner
Copy link

@gusted force-pushed to fix the conflict, mind doing the honors? :D

@gusted force-pushed to fix the conflict, mind doing the honors? :D
Sign in to join this conversation.
No reviewers
Labels
Clear labels
Codeberg Pages

Issues affecting Codeberg Pages
Documentation Usability

Issues related to using and reading docs.codeberg.org
Forgejo
Good First Issue! 👋
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Question
Kind: Security
Licensing
Part: Generator

This is related to the generation of the documentation, not to the content itself
Priority: High

The priority is high
Priority: Low

The priority is low
Priority: Medium

The priority is medium
Reviewed: Confirmed

Something has been confirmed
Reviewed: Duplicate

Something exists already
Reviewed: Invalid

Something was marked as invalid
Reviewed: Wontfix

Something won't be fixed
Status: Blocked
Status: Help wanted

Contributions are welcome!
Status: In progress

Work is in progress
Status: Needs feedback

Feedback is needed
Status: Ready for Review

Work is completed
Status: Review

Review is in progress / Reviewers wanted
Status: Stale
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
Codeberg/Documentation!685
Reference in a new issue
Codeberg/Documentation
No description provided.
Delete branch "n0toose/abuse-community-spaces"

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?