| 2 May 2024 |
 joepie91 🏳️🌈 | and this is causing confusion | 19:29:22 |
 infinisil | Jonas Chevalier: How about this: Let's just put the CoC and deescalation documents in the stream topics and sign up as many users as we can for now, while I contact chat support to ask for increasing the number of users per day | 19:29:48 |
 edef | worst case: it's 60 people, i'm happy to send out emails by hand if need be | 19:29:53 |
| edef | i'm fine with a little RSI if it gets things moving | 19:30:28 |
| infinisil | In reply to @joepie91:pixie.town
infinisil: the signup post on discourse has a rather serious error; it references the contributor covenant, rather than the CoC for the governance zulip We don't have an accepted CoC yet: https://github.com/NixOS/foundation/pull/144 | 19:30:43 |
| edef | okay, in that case we should clarify that | 19:31:08 |
| edef | rather than linking to one that is controversial among a decently sized crowd | 19:31:26 |
| edef | we wrote this one specifically with that in mind | 19:31:37 |
| joepie91 🏳️🌈 | In reply to @infinisil:matrix.org
We don't have an accepted CoC yet: https://github.com/NixOS/foundation/pull/144 then it should not reference any at all, or reference the future CoC | 19:31:48 |
 @zimbatm:numtide.com | Ok. Who is the coordinator? | 19:31:49 |
| joepie91 🏳️🌈 | right now it is simply wrong | 19:31:52 |
| edef | In reply to @infinisil:matrix.org
Jonas Chevalier: How about this: Let's just put the CoC and deescalation documents in the stream topics and sign up as many users as we can for now, while I contact chat support to ask for increasing the number of users per day okay, easy mode: we invite people to a read-only stream that just has an announcement message, with links to the other streams | 19:32:25 |
| infinisil | Or both! | 19:32:55 |
| edef | just want to have a bit of a turnstile | 19:33:10 |
| edef | i think that would cover all of my concerns | 19:33:28 |
| edef | and i can throw this pile of code in the trash :) | 19:33:39 |
| infinisil | Honestly this isn't that big of a problem, we tried to make it work nicely, but the board is right in that it would take too long. We've gotten this far with setting up Zulip, let's just start using it, with all of the non-ideal suggestion for pointing out the CoC | 19:33:46 |
| edef | yeah | 19:33:58 |
| edef | this was just the do-it-in-Zulip suggestion | 19:34:10 |
| infinisil | Yeah let's do a read-only stream, subscribed by default, with the CoC, plus the CoC in the topic of each stream | 19:34:31 |
| infinisil | Plus link to it in the GitHub/Discourse threads | 19:34:44 |
| edef | by the way, is the Zulip UI convenient enough for mass sending out of invites? | 19:35:50 |
| edef | idk who is doing validation | 19:35:59 |
| infinisil | But actually, the most blocking thing right now is https://github.com/NixOS/foundation/pull/144 | 19:36:19 |
| edef | oh that has a lot of clicks | 19:36:23 |
| @zimbatm:numtide.com | Is it possible to make streams read-only by default, but invite people for read-write? | 19:36:30 |
| infinisil | In reply to @edef1c:matrix.org
by the way, is the Zulip UI convenient enough for mass sending out of invites? Yes, it's super easy :) | 19:36:37 |
| edef | ack | 19:37:19 |
| infinisil | In reply to @zimbatm:numtide.com
Is it possible to make streams read-only by default, but invite people for read-write? Not sure why we'd want that? But I think it only works based on roles. E.g. giving only moderators write access | 19:37:22 |
| @zimbatm:numtide.com | Otherwise we can do GitHub Auth to read-only. And then promote people manually to the discussion | 19:37:39 |
