summaryrefslogtreecommitdiff
path: root/CodeOfConduct
diff options
context:
space:
mode:
authorkarolherbst <karolherbst@web>2024-05-16 13:42:14 +0200
committerIkiWiki <ikiwiki.info>2024-05-16 13:42:14 +0200
commitd913ebb56f5303ec0b24e9159c0a622409826141 (patch)
tree0ac901cafcc8258537d8863e9dd517a9ea8d2670 /CodeOfConduct
parent26fa071bf20700b0b59d83c773c16673f8d8985e (diff)
Diffstat (limited to 'CodeOfConduct')
-rw-r--r--CodeOfConduct/Guidlines.mdwn53
1 files changed, 53 insertions, 0 deletions
diff --git a/CodeOfConduct/Guidlines.mdwn b/CodeOfConduct/Guidlines.mdwn
new file mode 100644
index 00000000..ab5cfe5c
--- /dev/null
+++ b/CodeOfConduct/Guidlines.mdwn
@@ -0,0 +1,53 @@
+## Guidelines for Project Maintainer moderation
+
+Remember these aren't rules, there's simply suggestions project maintainers are
+free to use when moderating projects on Freedesktop - especially when using
+Gitlab.
+
+### Dealing with Spam
+
+If possible or unless told otherwise, don't report spam through Gitlab's
+reporting system. Because of how much spam we get, we've setup a spam bot
+that project maintainers can use instead to prevent the pipes from getting
+clogged up - and get a much faster response. When you see spam:
+
+* If it's an issue or a merge requeest, add the "spam" label to it on Gitlab.
+ This will hide the comment immediately
+* If it's a comment, react with the do not litter emoji 🚯 and the bot will
+ do its civic duty
+
+Note that the bot isn't setup by default, but can be setup for any project
+on freedesktop's gitlab. See
+https://gitlab.freedesktop.org/freedesktop/damspam for information on how
+to do this
+
+### Documenting incidences
+
+Document things first and foremost, such as with screenshots
+
+The biggest reason for this: Gitlab *does not* keep an edit history for
+comments, nor does it keep track of deleted comments. Once something has
+been removed or edited it's gone. Taking record of incidents can help the
+CoC team act on those when/if you reach out to them - as it makes it much
+easier to spot repeated patterns of behavior.
+
+### Inappropriate comments
+
+If you come across a comment that feels inappropriate or hinders a healthy discussion, consider one of the following actions:
+
+* Editing the comment with a canned response such as:
+ * "This comment has been removed as discussion about Foo is off-topic,
+ and should be discussed in its own issue"
+ * "This comment has been hidden due to inflammatory language, please
+ assume good faith when participating in discussions."
+* You can also delete the comment
+* You can also add a spoiler tag when editing the comment, to keep the body
+ of the comment intact - but collapse it by default.
+
+### Limit engagement with problematic comments to moderating them
+
+Trying to argue with someone or accuse them of wrongdoing will many times
+make a situation worse, and can also complicate things from the perspective
+of the CoC team. When problematic behavior occurs, it's recommended to keep
+responses brief and to the point - and to reach out to the code of conduct
+team if moderating the discussion fails.