| 3 Nov 2021 |
@ryblade:matrix.org | In reply to @gallantchef:matrix.foxears.life But a CoC for a CoC's sake that touches enough of the points that are desired may be a good middle way that kind of reminds me of stallman's reasons for creating the GPL, even though he fundamentally disagrees with the concept of software licenses entirely. in a world where licenses are a reality, having one you can agree with is better than having none at all. i suppose the same can be said about CoCs. | 19:42:43 |
@gallantchef:matrix.foxears.life | That's a decent perspective | 19:43:30 |
@gallantchef:matrix.foxears.life | I don't typically see eye to eye with rms, but I definitely agree with that | 19:43:51 |
@ryblade:matrix.org | same | 19:44:16 |
@gallantchef:matrix.foxears.life | So based on your post there, I think the main safeguards that could be implemented are:
- Clearly scoping what the powers of the moderation team are
- Coming up with a way to select for staff
- Enumerating what is or isn't an actionable offense in unambiguous language
- Use non-partisan language in the CoC that can't be interpreted with a slant
| 19:46:13 |
@gallantchef:matrix.foxears.life | * So based on your post there, I think the main safeguards that could be implemented are:
- Clearly scoping what the powers of the moderation team are
- Coming up with a way to select for staff
- Enumerating what is or isn't an actionable offense in unambiguous language
- Use non-partisan language in the CoC that can't be interpreted with a slant
- Providing transparency for said processes (bans, elections/appointment, etc.)
| 19:46:58 |
@jonringer:matrix.org | In reply to @gallantchef:matrix.foxears.life
So based on your post there, I think the main safeguards that could be implemented are:
- Clearly scoping what the powers of the moderation team are
- Coming up with a way to select for staff
- Enumerating what is or isn't an actionable offense in unambiguous language
- Use non-partisan language in the CoC that can't be interpreted with a slant
- Providing transparency for said processes (bans, elections/appointment, etc.)
The first 2 I'll do in the moderation RFC, the last two will be part of the CoC RFC. The 3rd should be satisfied by the CoC as well | 19:47:46 |
@ryblade:matrix.org | ... and perhaps a brief mention on how a user can take their own action to curate their environment (blocking, etc.)? perhaps worded in a way that sounds more... i dunno... "empowering", rather than dismissive. if that makes sense. | 19:48:01 |
@gallantchef:matrix.foxears.life | That's brilliant, actually | 19:48:13 |
@gallantchef:matrix.foxears.life | Here in the Nix community, we encourage contributors to be empowered and take control of their environment thru such and such | 19:48:40 |
@gallantchef:matrix.foxears.life | [demonstrative/pronoun] likes that sort of rhetoric | 19:48:56 |
@ryblade:matrix.org | though perhaps if necessary, a clear delineation of where your responsibilities end and the moderators' responsibilities begin might also help. this sort of thing could be easily represented in a table. | 19:50:12 |
@gallantchef:matrix.foxears.life | Second, tables are good | 19:50:23 |
@gallantchef:matrix.foxears.life | Basically it could read as "when to contact a moderator" | 19:50:39 |
@gallantchef:matrix.foxears.life | Or "when to escalate" | 19:50:43 |
@ryblade:matrix.org | tables would be best | 19:51:02 |
@jonringer:matrix.org | In reply to @ryblade:matrix.org ... and perhaps a brief mention on how a user can take their own action to curate their environment (blocking, etc.)? perhaps worded in a way that sounds more... i dunno... "empowering", rather than dismissive. if that makes sense. I think the best solution is that anyone within the nix community can step in and help arbitrate minor miscommunications. However, that puts more responsibility on everyone. And not everyone wants to step up. which is why a moderation team should still be around | 19:51:25 |
@gallantchef:matrix.foxears.life | Self-moderation is truly ideal | 19:51:41 |
@ryblade:matrix.org | using fluffy, long paragraphs makes it easy to gloss over the details, and makes it much easier to sneak vague, weasily content into updates to the document. the bigger the document, the bigger the pork. | 19:51:50 |
@ryblade:matrix.org | tables all the way | 19:52:05 |
@gallantchef:matrix.foxears.life | tfw clear, concise, correct documentation | 19:52:16 |
@gallantchef:matrix.foxears.life | But yes, simpler and more unambiguous language is better, especially if this is going to be something translated or presented to an international community | 19:52:59 |
@gallantchef:matrix.foxears.life | It's paramount that it's easy to understand | 19:53:06 |
@ryblade:matrix.org | too bad it probably can't be simple enough to represent in pictograms, like those ikea furniture instructions :D | 19:55:00 |
@ryblade:matrix.org | but we should do our best all the same | 19:55:22 |
@ryblade:matrix.org | with regards to adapting this CoC to the rust one, i think even from line one, it's got that problem of having a huge laundry list of subgroups listed as examples of people you're supposed to be sensitive towards. that list is already enormous and it will always require updating. can't we just say "everyone" instead of having to point out all kinds of specific examples? otherwise it might make listed groups feel more entitled to moderator intervention than people who are not mentioned specifically. | 20:02:42 |
@gallantchef:matrix.foxears.life | I second that | 20:02:57 |
@ryblade:matrix.org | being so specific about each and every type of group we're supposed to respect might also make it impossible for members of the international community to participate, because they may have internet filters or laws against accessing material that is seen as promoting "western values". if anyone with the talent to contribute to nixos is among them, they might get arrested for helping a group of people with very clearly and objectively stated goals towards providing a safe environment for what their countries may perceive as sinners or criminals. that puts them in danger. and it robs us of potential talent, creating a lose-lose situation for all of us. | 20:03:12 |
@gallantchef:matrix.foxears.life | My thoughts on how to better write a line like that involves something to the effect of welcome all based on the contents of their character and not their phenotype | 20:04:10 |
@ryblade:matrix.org | YES. | 20:04:21 |