| 1 Nov 2023 |
|  trinity joined the room. | 11:09:23 |
| 2 Nov 2023 |
|  ris_ joined the room. | 22:53:54 |
| 5 Nov 2023 |
 vcunat | Has date&time been determined yet? Lettuce seems greenest on Wednesday, though. | 11:49:56 |
 fricklerhandwerk | Friday has most participants and I got an invite for friday 9:30 CET. | 20:59:54 |
| fricklerhandwerk | * Friday has most available participants and I got an invite for Friday 9:30 CET. | 21:00:10 |
| fricklerhandwerk | Will there be anyone from the foundation board except Théophane though? | 21:00:33 |
 infinisil | In reply to @fricklerhandwerk:matrix.org
Friday has most available participants and I got an invite for Friday 9:30 CET. That doesn't sound right, Théophane mentioned 21:00 CET, see https://matrix.to/#/!qPyghedoYQUdaSXHnv:hufschmitt.net/$vq3qg4vvjS2j9AlJ0iQG5yDvbxDU5-Ud2y8j88cSWSY?via=nixos.org&via=matrix.org&via=lossy.network <- vcunat | 21:07:08 |
| vcunat | Oh right, now I see I already had it in my calendar 🤦 which is too full now to notice easily. | 21:09:07 |
| fricklerhandwerk | * Friday has most available participants and I got an invite for Friday ~~9:30~~ 9:00 CET. | 21:18:10 |
| fricklerhandwerk | * Friday has most available participants and I got an invite for Friday 9:30 9:00 CET. | 21:18:23 |
| fricklerhandwerk | * Friday has most available participants and I got an invite for Friday 9:30 21:00 CET. | 21:18:36 |
| 7 Nov 2023 |
 @theophane:hufschmitt.net | I've started drafting an agenda for Friday's meeting here. Don't hesitate to suggest anything you think is important to cover (keeping in mind that we're having a 1h meeting, with potentially a fair number of participants, so we'll have to keep the agenda short and actionable to make the best of everyone's time) | 09:36:48 |
| fricklerhandwerk | It turns out I won’t be able to make it, this week has been really stressful for me. I’ll ask @proofconstruction to represent the docs team as an independent mind, but I think @infinisil can do that perfectly as well and there is no hard requirement to have that many people in the call. | 12:04:43 |
 @delroth:delroth.net | did you end up finding a representative for security? can't tell if risicle actually replied / accepted | 16:01:02 |
 raitobezarius | risicle joined but didn't say anything yet | 16:01:23 |
| raitobezarius | ris_: can you confirm you are fine with being named as the representative for the security team? | 16:01:45 |
| 9 Nov 2023 |
| fricklerhandwerk | Regarding the agenda: We can compile the "list of unmaintained things" async, and use the time to discuss questions | 14:52:28 |
| fricklerhandwerk | In other words, please add the stuff you come up with, then we don't have to waste time on what could have been an email | 14:52:58 |
| fricklerhandwerk | @proofconstruction will join | 16:55:25 |
| 10 Nov 2023 |
| fricklerhandwerk | I added a proposal tomberek and me cultivated in the past months which concerns all team members. It's quite a chunk of text already, and as is best practice with executive meetings 😛 , I'd like you to skim it beforehand, and - if you decide to keep it on the agenda - use the time to collect quick feedback and gut reactions, and then decide where to take it next. Thank you very much! | 10:59:01 |
| fricklerhandwerk | You can already add feedback to the document, that will save time in the meeting | 11:01:33 |
| fricklerhandwerk | * I added a proposal tomberek and me cultivated in the past months which concerns all teams. It's quite a chunk of text already, and as is best practice with executive meetings 😛 , I'd like you to skim it beforehand, and - if you decide to keep it on the agenda - use the time to collect quick feedback and gut reactions, and then decide where to take it next. Thank you very much! | 11:02:11 |
| raitobezarius | Théophane: can we put again a link for the call here? | 12:02:49 |
| @theophane:hufschmitt.net | In reply to @raitobezarius:matrix.org
Théophane: can we put again a link for the call here? Certainly:
Meeting link: https://jitsi.lassul.us/nix-team-gathering
Notes and agenda: https://pad.lassul.us/nzIzJ-sVRay17ZOIr1qldA
| 12:33:36 |
| raitobezarius | added some items on the lack of maintenance stuff and a call to action to sunset things in the nixos org | 12:48:15 |
| raitobezarius | Meeting is now, right? | 20:00:35 |
| @theophane:hufschmitt.net | Indeed it is | 20:00:52 |
 figsoda | Sorry guys, I forgot about my timezone change | 20:11:51 |
| @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!
| 20:14:20 |
 @kranzes:matrix.org | Is this being recorded or just meeting notes? I gotta go but would like to follow | 20:17:19 |
