| 18 Oct 2023 |
|  @admin:nixos.orgchanged room power levels. | 13:01:38 |
 @theophane:hufschmitt.net | Yes | 13:02:26 |
| @theophane:hufschmitt.net | Any way I can copy the entire list of users? Everyone currently here should be able to talk | 13:02:50 |
 Alyssa Ross | don't know | 13:02:58 |
| @theophane:hufschmitt.netchanged room power levels. | 13:03:57 |
| @theophane:hufschmitt.netchanged room power levels. | 13:04:19 |
| @theophane:hufschmitt.netchanged room power levels. | 13:05:53 |
| Alyssa Ross | Looks like that's done, so I can re-enable the restriction on who can speak now. But before I do, does anybody think we should not do that? | 13:07:21 |
 infinisil | Sounds a bit odd to have two channels mostly about the same thing, but one limits speaking to a certain group. Though I do remember thinking of that too in the governance room | 13:09:28 |
| @admin:nixos.orgchanged room power levels. | 13:09:43 |
| infinisil | But having these two rooms like that probably means people that can't speak in this one would just reply to the person in the other room | 13:10:12 |
| infinisil | Which then splits the discussion | 13:10:55 |
| infinisil | Oh also, the docs team is actually a bunch larger than on the website: https://github.com/NixOS/nix.dev/tree/master/maintainers#members
(It should really be put on the website though) | 13:16:58 |
| infinisil | And what about all the Nixpkgs teams? https://github.com/NixOS/nixpkgs/blob/master/maintainers/team-list.nix
Or https://github.com/orgs/NixOS/teams/ | 13:17:48 |
| Alyssa Ross | I think I'm just going to enable the restriction, since that unblocks making the room public, and then other people can see what's being discussed. | 13:18:48 |
| Alyssa Ross | It sounds like there's not consensus for whether this room should even exist, but if we decide that it shouldn't, we can just get rid of it again, and in the meantime it'd be good if people could at least read this discussion. | 13:19:16 |
| @admin:nixos.orgchanged room power levels. | 13:19:35 |
| @admin:nixos.org set the room topic to "Collaboration room for all the members of a Nix community team.
Anybody can join this room and read the history, but only members of community teams can post here. Moderators can give people permission to post by granting them powerlevel 10.". | 13:20:12 |
| @admin:nixos.org changed the join rule to "public" from "invite". | 13:20:18 |
| Alyssa Ross | room is now public | 13:20:32 |
| @admin:nixos.orgchanged room power levels. | 13:20:59 |
| @admin:nixos.org left the room. | 13:21:11 |
| infinisil | Also, it's really not well defined what it means to be listed on the website. All it means is that somebody made a PR to the website and somebody from the marketing team merged it, there's no requirements that need to be met for that afaik.
Directly relates to the question of what is official, previously discussed in the other channel | 13:25:39 |
|  @andi:kack.it joined the room. | 13:32:34 |
| @theophane:hufschmitt.net | Woops, I had to drop unexpectedly because I had forgotten a meeting. I've manually privileged folks, I hope I haven't forgotten anyone | 13:36:40 |
 @delroth:delroth.net | In reply to @infinisil:matrix.org
And what about all the Nixpkgs teams? https://github.com/NixOS/nixpkgs/blob/master/maintainers/team-list.nix
Or https://github.com/orgs/NixOS/teams/ unstructured train of thought: I think a factor to take into account is whether a team "has cross-functional scope/impact" or not - this currently applies to ~all of the teams that have been listed so far, but less so to e.g. GNOME or Emacs maintenance teams (tighter scoped). That still leaves a few edge cases to consider: for example, what about Reproducible Builds, or Cross Compiling "teams"? (the former has a github team, the latter not) | 13:39:13 |
| @delroth:delroth.net | In reply to @infinisil:matrix.org
And what about all the Nixpkgs teams? https://github.com/NixOS/nixpkgs/blob/master/maintainers/team-list.nix
Or https://github.com/orgs/NixOS/teams/ * unstructured train of thought: I think a factor to take into account is whether a team "has cross-functional scope/impact" or not - this currently applies to ~all of the teams that have been included so far, but less so to e.g. GNOME or Emacs maintenance teams (tighter scoped). That still leaves a few edge cases to consider: for example, what about Reproducible Builds, or Cross Compiling "teams"? (the former has a github team, the latter not) | 13:39:19 |
| @delroth:delroth.net | (I can't trivially figure out objective differentiating factors that would make Security something to be included here but not Repro, but maybe someone has ideas :p) | 13:40:54 |
| @delroth:delroth.net | I'll say that another big omission I see from this list is our favorite wallet, aka. the Foundation | 13:44:45 |
| infinisil | Is the intention to also make the meeting read-only for people that aren't invited? (that also feels weird to me) | 13:53:09 |
