| 2 May 2024 |
 7c6f434c | This is all about keeping things from blowing up, and valuable. But it is not, on its own, about making (at least) self-coherent decisions in a explicit-value-conflict situation. | 22:05:49 |
| 7c6f434c | It's how not to explode en route, but not how to make sure you arrive anywhere worth being. | 22:06:35 |
 edef | i think that itself is part of the next conversation, maybe? | 22:07:36 |
| 7c6f434c | Yes, sure | 22:07:50 |
 danielle | A decision making framework would fall under the scope of a zulip discussion indeed | 22:07:52 |
| edef | and i'd encourage you to bring it up there | 22:07:55 |
| edef | because i do think it is important | 22:08:02 |
 ronef | In reply to @danielle:fairydust.space
Can you [board hat on] review https://github.com/NixOS/foundation/pull/144 ? Merged | 22:08:04 |
| ronef | Also took most feedback and posted the first update here -> https://discourse.nixos.org/t/board-update-1-starting-process-and-transparent-comms/44735 | 22:08:33 |
 nyanbinary | O | 22:10:08 |
| nyanbinary | What about the suggestions for the coc? | 22:10:18 |
| danielle | nyanbinary: we can open a PR for the last few refinements | 22:10:45 |
| danielle | none of them change meaning or intent | 22:10:45 |
 raitobezarius | I'm logged in, if anyone has issues or concerns about Zulip, please reach out to me. | 22:12:07 |
| raitobezarius | I am caught up with the discussion and I see that folks had the Zulip folks answer them about the invitation limit. | 22:12:27 |
 infinisil | Perfect timing, let's get this Zulip party started! | 22:12:34 |
| raitobezarius | (note that Zulip folks are very easy to reach out to as long as TZ stuff works well) | 22:12:37 |
| danielle | (working on the PR now) | 22:12:46 |
 lovesegfault | itshappening.gif | 22:14:10 |
| infinisil | raitobezarius: I updated https://discourse.nixos.org/t/zulip-for-governance-discussions/44684#moderation-3 with the link to the new zulip CoC, can you do the same for GitHub? | 22:15:10 |
| infinisil | I'll start adding the CoC and deescalation docs to each stream topic | 22:15:38 |
| danielle | https://github.com/NixOS/foundation/pull/145 - Jonas Chevalier / ronef tiny pr with a couple of refinements from suggestions that got missed in 144 | 22:17:08 |
 @zimbatm:numtide.com | updated the foundation statement to point to https://github.com/NixOS/foundation/issues/143 | 22:17:16 |
| raitobezarius | In reply to @infinisil:matrix.org
raitobezarius: I updated https://discourse.nixos.org/t/zulip-for-governance-discussions/44684#moderation-3 with the link to the new zulip CoC, can you do the same for GitHub? done | 22:21:12 |
| infinisil | We should delete comments in https://github.com/NixOS/foundation/issues/143 that were invited already, to avoid leaking the users email addresses forever (it wasn't a great choice to do it this way, but by deleting them we can fix it, and know which ones were already invited!) | 22:21:13 |
| infinisil | Jonas Chevalier: Can you ensure that all the Zulip moderators have write permission to the foundation repo? That's the permission needed to delete comments (obviously we won't abuse this) | 22:22:25 |
| edef | fwiw i think most people used their already-public GitHub email, or a disposable address | 22:24:02 |
 joepie91 🏳️🌈 | infinisil: was the intent not to have a historical record? | 22:24:09 |
| edef | i think people understood they were posting an address publicly | 22:24:35 |
| raitobezarius | worst case, people can censor or remove their address after invite | 22:24:56 |
