| 18 Oct 2023 |
 @delroth:delroth.net | FWIW I do think there's likely still value in "forcing" people from all these separate efforts to have general awareness of what's going on in other work tracks. This usually leads to good feedback from people that have a different view of the problem space, and it might accelerate situations where a team is blocked on another. Currently I'd expect this is happening to some extent due to the overlap in membership of the teams, but I don't know whether that's true of all the teams (I suspect some are more isolated than others). | 20:56:36 |
| @delroth:delroth.net | (Some of this "awareness spreading" also happens by virtue of having #dev be used to talk about ~everything once in a while...) | 20:56:58 |
 @theophane:hufschmitt.net | * Hey everyone,
In line with our ongoing efforts to strengthen and empower the NixOS community, numerous discussions have taken place recently, including those at NixCon, focusing on improving the structure and governance of our community.
A recurring theme in these conversations is the need for greater clarity. Questions frequently arise about who can make specific decisions, the current status of various projects, and who holds responsibility for different aspects of the ecosystem. Partially continuing on the initial threads of empowering the Nix teams.
I think a good and easy first step towards solving that would be to just gather leads/representatives from each team on a regular basis. That would allow people to talk to each other in a slightly more structured fashion, and help to unblock all the rest. So if you're OK with that idea, I've made a poll to find a first timeslot: https://lettucemeet.com/l/9KNXn.
The goal is to have one representative from each team, if possible the team lead for the teams which have one.
Taking the list of team leads from whatever is on https://nixos.org/community/, this gives:
- Security: ??
- Build-Infra: ??
- Infra: Julien
- NixOS release: @figsoda
- NixCon: ??
- RFC steering committee: ??
- Marketing: @rok
- Moderation: ??
- Nix team: @edolstra
- Documentation: @fricklerhandwerk
- Nixpkgs architecture: @infinisil
- foundation board: ??
A rough agenda for the first call could be:
Presentation of each team: goal and areas of responsibility
Listing the main points in the ecosystem which are lacking.
Does that sound like a good plan to everyone? If so, let’s roll!
| 20:57:14 |
| @delroth:delroth.net | But it's easy for me to say that as someone who's not leading anything and would likely not be taking active participation :P | 20:57:24 |
 raitobezarius | I think the biggest problem is that #dev is a black hole for information | 20:58:31 |
| raitobezarius | And this channel may or may not change that much this issue | 20:58:44 |
| @delroth:delroth.net | part of the solution would also be to have weekly notes from more than just the few teams that are currently doing it :) | 21:05:16 |
| @delroth:delroth.net | (I really appreciate reading these, btw. All of them, at least all the ones I spot on Discourse :) ) | 21:05:56 |
 infinisil | Again I think this needs some streamlining, so all teams use the same processes, take meeting notes, post them to the same place, etc. | 21:07:40 |
|  @cole-h:matrix.org joined the room. | 21:12:27 |
| raitobezarius | In reply to @delroth:delroth.net
part of the solution would also be to have weekly notes from more than just the few teams that are currently doing it :) This is true but also this works for formal team, for informal teams, there needs to be awareness that this info goes to blackhole and someone has to post it and as it is usually a flow of continuous information, I find it hard to do cutoffs but you're right that things could be done in that area | 21:31:18 |
| raitobezarius | (and I am culprit of pushing info in the blackhole a lot of times) | 21:31:36 |
|  ronef joined the room. | 22:00:14 |
| 19 Oct 2023 |
|  tomberek joined the room. | 00:56:43 |
| @theophane:hufschmitt.net changed 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.
https://matrix.to/#/!qPyghedoYQUdaSXHnv:hufschmitt.net/$lmbsV4lGtAwatn8prBSx3J-64dgBr6niYolQDdLjHyY?via=nixos.org&via=matrix.org&via=hufschmitt.net" from "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.". | 08:37:23 |
|  Robert Hensing (roberth) joined the room. | 10:42:07 |
| 20 Oct 2023 |
| @theophane:hufschmitt.net | * Hey everyone,
In line with our ongoing efforts to strengthen and empower the NixOS community, numerous discussions have taken place recently, including those at NixCon, focusing on improving the structure and governance of our community.
A recurring theme in these conversations is the need for greater clarity. Questions frequently arise about who can make specific decisions, the current status of various projects, and who holds responsibility for different aspects of the ecosystem. Partially continuing on the initial threads of empowering the Nix teams.
I think a good and easy first step towards solving that would be to just gather leads/representatives from each team on a regular basis. That would allow people to talk to each other in a slightly more structured fashion, and help to unblock all the rest. So if you're OK with that idea, I've made a poll to find a first timeslot: https://lettucemeet.com/l/9KNXn.
The goal is to have one representative from each team, if possible the team lead for the teams which have one.
Taking the list of team leads from whatever is on https://nixos.org/community/, this gives:
A rough agenda for the first call could be:
Presentation of each team: goal and areas of responsibility
Listing the main points in the ecosystem which are lacking.
Does that sound like a good plan to everyone? If so, let’s roll!
| 07:26:38 |
|  proofconstruction joined the room. | 13:52:57 |
| 21 Oct 2023 |
|  @bb010g:matrix.org joined the room. | 04:54:22 |
| 23 Oct 2023 |
|  IdaBzo joined the room. | 07:55:37 |
| 24 Oct 2023 |
|  @gdesforges:matrix.org joined the room. | 20:29:53 |
| 26 Oct 2023 |
| @theophane:hufschmitt.net | * Hey everyone,
In line with our ongoing efforts to strengthen and empower the NixOS community, numerous discussions have taken place recently, including those at NixCon, focusing on improving the structure and governance of our community.
A recurring theme in these conversations is the need for greater clarity. Questions frequently arise about who can make specific decisions, the current status of various projects, and who holds responsibility for different aspects of the ecosystem. Partially continuing on the initial threads of empowering the Nix teams.
I think a good and easy first step towards solving that would be to just gather leads/representatives from each team on a regular basis. That would allow people to talk to each other in a slightly more structured fashion, and help to unblock all the rest. So if you're OK with that idea, I've made a poll to find a first timeslot: https://lettucemeet.com/l/9KNXn.
The goal is to have one representative from each team, if possible the team lead for the teams which have one.
Taking the list of team leads from whatever is on https://nixos.org/community/, this gives:
A rough agenda for the first call could be:
Presentation of each team: goal and areas of responsibility
Listing the main points in the ecosystem which are lacking.
Does that sound like a good plan to everyone? If so, let’s roll!
| 09:01:47 |
| @theophane:hufschmitt.net | Hey all, it would be nice to get more team represented.
figsoda, niksnut are you OK with representing NixOS and Nix? If so, can you fill the poll?
There's still no one from Security, Build-infra, NixCon, RFC and Moderation. How about (semi randomly):
Security: grahamc (he/him)
Build-infra: Jonas Chevalier
NixCon: raitobezarius
RFC: tomberek
?
Are you OK with joining?
| 09:05:58 |
| raitobezarius | I'd rather be part of a Nixpkgs team than NixCon, I tried to invite hexchen which is also co-project lead with me and I think she would be an excellent representative of NixCon, unfortunately invitation failed | 09:08:18 |
 vcunat | It's hard for me to plan for that week, as I'm at IETF. | 09:08:19 |
| @theophane:hufschmitt.net | I can try if you have her handle | 09:13:23 |
| @theophane:hufschmitt.net | (as for a Nixpkgs team, 💯times yes) | 09:14:13 |
| raitobezarius | @hexchen:colon.at | 09:14:29 |
| @theophane:hufschmitt.net | Thanks | 09:15:20 |
| @theophane:hufschmitt.net invited  hexchen. | 09:15:32 |
