| 2 May 2024 |
 @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 |
| @zimbatm:numtide.com | Different angle | 19:38:03 |
| infinisil | I think the manual invite process should work out just fine really | 19:38:27 |
| infinisil | Tasks:
- Get https://github.com/NixOS/foundation/pull/144 merged
- Link these documents everywhere
- Open participation for everybody, and maybe create some streams for different topics
- Invite everybody
| 19:39:53 |
| infinisil | * Tasks (in this order)
- Get https://github.com/NixOS/foundation/pull/144 merged
- Link these documents everywhere
- Open participation for everybody, and maybe create some streams for different topics
- Invite everybody
| 19:40:01 |
| edef | 
Download image.png | 19:40:06 |
| edef | this could be the welcome intro, and people can sub to the other streams after they've read the message | 19:40:29 |
| edef | just join people to one read-only thing by default, basically | 19:40:45 |
| edef | (not trying to hammer on this, and not insistent on this particular approach, just making sure my earlier suggestion is conveyed effectively) | 19:41:23 |
| edef | anyway, that's my proposed colour for the bikeshed, onwards | 19:41:33 |
