| 2 May 2024 |
 infinisil | In reply to @infinisil:matrix.org
We could have a stream for the CoC and one for deescalation, only admins have write access, everybody's subscribed by default This? | 17:36:12 |
 edef | mm, the best shot i have left is "really really pin a message in a way you can't avoid" | 17:36:27 |
| edef | maybe pin it to every channel | 17:36:38 |
 joepie91 🏳️🌈 | infinisil: complaint about broken code of conduct link in the discourse signup thread | 17:37:50 |
| edef | well, at least a sign people are reading it :p | 17:38:06 |
| joepie91 🏳️🌈 | (it is indeed broken but their suggestion of where it is meant to point, is wrong) | 17:38:07 |
| joepie91 🏳️🌈 | In reply to @edef1c:matrix.org
if anyone has proposals for how we make it abundantly clear that the rules of engagement for this venue are Very Specific and you actually have to read them, speak now I mean, the only thing I can think of is "get explicit agreement by e-mail before creating their account for them" but this does introduce an extra roundtrip | 17:39:01 |
| infinisil | The link will be valid once https://github.com/NixOS/foundation/pull/144 is merged :) Ron told me he's pinged the foundation channel, just waiting for upvotes | 17:39:26 |
| joepie91 🏳️🌈 | it is not mentioned in the public foundation room fwiw | 17:40:01 |
| edef | In reply to @joepie91:pixie.town
I mean, the only thing I can think of is "get explicit agreement by e-mail before creating their account for them" but this does introduce an extra roundtrip i guess we can send a ~manual email alongside the invitation | 17:40:18 |
| edef | "READ THIS FIRST: Rules of Engagement" | 17:40:28 |
| joepie91 🏳️🌈 | that is possible | 17:40:35 |
| edef | but feels prone to getting lost in people's email streams | 17:40:39 |
| joepie91 🏳️🌈 | yeah that was my concern with that | 17:40:47 |
| joepie91 🏳️🌈 | an explicit acknowledgment would be very helpful | 17:40:54 |
| edef | i'm too ADHD and i'm subscribed to too many email things | 17:41:10 |
| joepie91 🏳️🌈 | I am inclined to say that it is maybe worth the extra roundtrip | 17:41:15 |
| edef | so i literally just fish the relevant thing out of my email when necessary | 17:41:22 |
| edef | does the API let us send out invites? | 17:41:33 |
| infinisil | Honestly I don't think that's feasible to keep track of | 17:41:33 |
| edef | i could cook up a clickthrough | 17:41:59 |
| infinisil | In the "training in zulip" I just added a markdown link to the topic | 17:42:07 |
| joepie91 🏳️🌈 | if you mention the github username in the outgoing e-mail (subject) and use a shared e-mail account then that will show up as a list of "people you have contacted" and their replies will be associated with that | 17:42:20 |
| infinisil | We can add these documents to the topic of every channel | 17:42:21 |
| edef | manual email -> link to clickthrough -> API-driven invite | 17:42:43 |
| edef | that's my best remaining shot at getting it to actually be read before you are capable of interacting with chat | 17:43:10 |
| edef | like, we have two purposes here: a) not giving people the excuse that they were not aware b) not catching out people who genuinely managed to miss it | 17:43:39 |
| infinisil | I don't think we should be blocked on this, this might take like another day to figure, but we should open Zulip today | 17:43:57 |
| joepie91 🏳️🌈 | I do not feel strongly about the exact mechanism but I do feel strongly about presenting these rules to people on an individual and deliberate basis in some way | 17:44:09 |
| infinisil | * I don't think we should be blocked on this, this might take like another day to figure out, but we should open Zulip today | 17:44:13 |
