update matrix moderation guidelines based on infra-team discussion #181

Merged
lilly merged 1 commit from lilly/moderation-guidelines into main 2026-11-01 22:58:51 +01:00
Owner
No description provided.
update matrix moderation guidelines based on infra-team discussion
Some checks failed
/ build (pull_request) Successful in 29s
/ Ansible Lint (push) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
aaf8c7d064
You can view your changes at https://staging.infra-docs.hamburg.ccc.de/pr181/
lilly force-pushed lilly/moderation-guidelines from aaf8c7d064
Some checks failed
/ build (pull_request) Successful in 29s
/ Ansible Lint (push) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
to 00586e21cd
Some checks failed
/ build (pull_request) Successful in 29s
/ Ansible Lint (pull_request) Has been cancelled
/ Ansible Lint (push) Has been cancelled
2026-11-01 19:49:46 +01:00
Compare
lilly force-pushed lilly/moderation-guidelines from 00586e21cd
Some checks failed
/ build (pull_request) Successful in 29s
/ Ansible Lint (pull_request) Has been cancelled
/ Ansible Lint (push) Has been cancelled
to 46a1bbc8da
Some checks failed
/ build (pull_request) Successful in 28s
/ Ansible Lint (push) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
2026-11-01 19:52:25 +01:00
Compare
lilly force-pushed lilly/moderation-guidelines from 46a1bbc8da
Some checks failed
/ build (pull_request) Successful in 28s
/ Ansible Lint (push) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
to 5c639ebc31
Some checks failed
/ build (pull_request) Successful in 28s
/ Ansible Lint (push) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
2026-11-01 19:53:38 +01:00
Compare
lilly force-pushed lilly/moderation-guidelines from 5c639ebc31
Some checks failed
/ build (pull_request) Successful in 28s
/ Ansible Lint (push) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
to 51f66e9958
All checks were successful
/ build (pull_request) Successful in 29s
/ Ansible Lint (push) Successful in 2m21s
/ Ansible Lint (pull_request) Successful in 2m24s
2026-11-01 19:55:16 +01:00
Compare
lilly force-pushed lilly/moderation-guidelines from 51f66e9958
All checks were successful
/ build (pull_request) Successful in 29s
/ Ansible Lint (push) Successful in 2m21s
/ Ansible Lint (pull_request) Successful in 2m24s
to ecafe6a4e7
Some checks failed
/ build (pull_request) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
/ Ansible Lint (push) Has been cancelled
2026-11-01 19:59:11 +01:00
Compare
lilly force-pushed lilly/moderation-guidelines from ecafe6a4e7
Some checks failed
/ build (pull_request) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
/ Ansible Lint (push) Has been cancelled
to e60a27be20
Some checks failed
/ Ansible Lint (push) Has been cancelled
/ build (pull_request) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
2026-11-01 19:59:42 +01:00
Compare
lilly force-pushed lilly/moderation-guidelines from e60a27be20
Some checks failed
/ Ansible Lint (push) Has been cancelled
/ build (pull_request) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
to ece5df20b8
All checks were successful
/ build (pull_request) Successful in 30s
/ Ansible Lint (push) Successful in 4m14s
/ Ansible Lint (pull_request) Successful in 4m26s
2026-11-01 19:59:57 +01:00
Compare
lilly changed title from WIP: update matrix moderation guidelines based on infra-team discussion to update matrix moderation guidelines based on infra-team discussion 2026-11-01 20:02:54 +01:00
stb requested changes 2026-11-01 20:25:13 +01:00
stb left a comment

Have to break for dinner, I'll continue later

Have to break for dinner, I'll continue later
@ -7,2 +9,3 @@
All Matrix rooms created around CCCHH and which are considered *official* are subject to centralized moderation.
This moderation is enforced by a [Draupnir](https://github.com/the-draupnir-project/Draupnir) bot on a techincal level and operated by a dedicated sub-team of the Infra Group.
This moderation is enforced by a [Draupnir](https://github.com/the-draupnir-project/Draupnir) bot on a techincal level and operated by a dedicated team of CCCHH people on an organisational one.
Owner

The end of the sentence appears to be mangled?

The end of the sentence appears to be mangled?
lilly marked this conversation as resolved
@ -7,2 +10,3 @@
All Matrix rooms created around CCCHH and which are considered *official* are subject to centralized moderation.
This moderation is enforced by a [Draupnir](https://github.com/the-draupnir-project/Draupnir) bot on a techincal level and operated by a dedicated sub-team of the Infra Group.
This moderation is enforced by a [Draupnir](https://github.com/the-draupnir-project/Draupnir) bot on a techincal level and operated by a dedicated team of CCCHH people on an organisational one.
The team is mixed but represents at least our [Vorstand](https://wiki.hamburg.ccc.de/verein:vorstand:start), [Vertrauenspersonen](https://wiki.hamburg.ccc.de/verein:offizielles:vertrauenspersonen) and the [Infra-Team](https://wiki.hamburg.ccc.de/intern:infra-team).
Owner

The team consists of representatives of at least our...

The team consists of representatives of at least our...
lilly marked this conversation as resolved
@ -18,3 +22,3 @@
- Prohibited content includes spam, pornography, harassment, and fascist-like behavior. We remove such content and subsequently ban the user responsible (see [Matrix: Taking Moderation Action](../guides/matrix-taking-moderation-action.md)).
- The CCCHH admin account may be used under special circumstances to issue warnings and explain the moderation team’s decisions in general terms. It does not respond to DMs and does not engage in discussions. If moderation action is to be discussed, people are referred to the moderation team at [matrix-moderation@hamburg.ccc.de](mailto:matrix-moderation@hamburg.ccc.de) instead.
- The moderation team discusses and chooses an approprite moderation action for questionable behavior together. While crass breach of our rules can result in swift action (e.g. porn bots) social dynamics are discussed internally and a decision which the whole team can defend should be reached.
Owner
  • chooses an appropriate moderation action (typo)
  • While egregious breaches (style)
  • Comma after porn bots
  • social dynamics are discussed internally in the team, and
* chooses an appropriate moderation action (typo) * While egregious breaches (style) * Comma after porn bots * social dynamics are discussed internally in the team, and
lilly marked this conversation as resolved
@ -20,1 +24,3 @@
- The CCCHH admin account may be used under special circumstances to issue warnings and explain the moderation team’s decisions in general terms. It does not respond to DMs and does not engage in discussions. If moderation action is to be discussed, people are referred to the moderation team at [matrix-moderation@hamburg.ccc.de](mailto:matrix-moderation@hamburg.ccc.de) instead.
- The moderation team discusses and chooses an approprite moderation action for questionable behavior together. While crass breach of our rules can result in swift action (e.g. porn bots) social dynamics are discussed internally and a decision which the whole team can defend should be reached.
- The moderation team has at their disposal a few technical and social tools and options. Importantly the chosen tool must be suitable to enforce our rules (i.e. not be ineffective), necessary to accomplish so (i.e. a more mild choice would not work), and appropriate (i.e. the downsides for anyone invovled do not stand in stark contrast with rule enforcement). Notably, disregard for the moderation teams decision (e.g. ban evasion or not accepting a written warning) can lead to harder measures.
Owner
  • i.e. be effective: avoid the double negative
  • accomplish them (the rules)
* i.e. be effective: avoid the double negative * accomplish them (the rules)
Author
Owner

I wouldn't say we accomplish our rules but rather that the aforementioned enforcement is accomplished. Otherwise thanks for the pointers.

I wouldn't say we accomplish our rules but rather that the aforementioned enforcement is accomplished. Otherwise thanks for the pointers.
max approved these changes 2026-11-01 20:31:42 +01:00
Dismissed
lilly force-pushed lilly/moderation-guidelines from ece5df20b8
All checks were successful
/ build (pull_request) Successful in 30s
/ Ansible Lint (push) Successful in 4m14s
/ Ansible Lint (pull_request) Successful in 4m26s
to 5f19629480
All checks were successful
/ build (pull_request) Successful in 29s
/ Ansible Lint (push) Successful in 5m14s
/ Ansible Lint (pull_request) Successful in 5m47s
2026-11-01 20:45:26 +01:00
Compare
lilly dismissed max's review 2026-11-01 20:45:26 +01:00
Reason:

New commits pushed, approval review dismissed automatically according to repository settings

june approved these changes 2026-11-01 21:48:19 +01:00
Dismissed
june left a comment

Seems reasonable with no obvious complaints, but am also rather tired right now.

Seems reasonable with no obvious complaints, but am also rather tired right now.
stb requested changes 2026-11-01 22:07:12 +01:00
stb left a comment

Otherwise fine. Thank you!

Otherwise fine. Thank you!
@ -20,1 +24,3 @@
- The CCCHH admin account may be used under special circumstances to issue warnings and explain the moderation team’s decisions in general terms. It does not respond to DMs and does not engage in discussions. If moderation action is to be discussed, people are referred to the moderation team at [matrix-moderation@hamburg.ccc.de](mailto:matrix-moderation@hamburg.ccc.de) instead.
- The moderation team discusses and chooses an appropriate moderation action for questionable behavior together. While egregious breaches of our rules can result in swift action (e.g. porn bots), social dynamics are discussed internally, and a decision which the whole team can defend should be reached.
- The moderation team has at their disposal a few technical and social tools and options. Importantly the chosen tool must be suitable to enforce our rules (i.e. be effective), necessary to accomplish so (i.e. a more mild choice would not work), and appropriate (i.e. the downsides for anyone invovled do not stand in stark contrast with rule enforcement). Notably, disregard for the moderation teams decision (e.g. ban evasion or not accepting a written warning) can lead to harder measures.
Owner
  • "necessary to accomplish so" is weird. I think a single "necessary" is fully sufficient and less confusing (and "accomplish so" is not really a thing in English).
  • "involved" (typo)
* "necessary to accomplish so" is weird. I think a single "necessary" is fully sufficient and less confusing (and "accomplish so" is not really a thing in English). * "involved" (typo)
lilly marked this conversation as resolved
lilly force-pushed lilly/moderation-guidelines from 5f19629480
All checks were successful
/ build (pull_request) Successful in 29s
/ Ansible Lint (push) Successful in 5m14s
/ Ansible Lint (pull_request) Successful in 5m47s
to 04bb14c6f4
All checks were successful
/ build (pull_request) Successful in 29s
/ cleanup-staging (pull_request) Successful in 32s
/ build (push) Successful in 27s
/ Ansible Lint (pull_request) Successful in 2m31s
/ Ansible Lint (push) Successful in 4m42s
2026-11-01 22:58:32 +01:00
Compare
lilly dismissed june's review 2026-11-01 22:58:32 +01:00
Reason:

New commits pushed, approval review dismissed automatically according to repository settings

lilly merged commit 04bb14c6f4 into main 2026-11-01 22:58:51 +01:00
lilly deleted branch lilly/moderation-guidelines 2026-11-01 22:58:52 +01:00
Sign in to join this conversation.
No description provided.