11 Oct 2024 |
emily | FWIW a maintainer team to list in packages / ci/OWNERS seems like a good idea but I don't think we can really give them concrete authority absent SC decisions about how decision-making should be structured | 17:36:02 |
emily | and it's unclear to me if that would want, e.g. a general core team, a core Linux team specifically, or a more focused stdenv team, or what | 17:36:20 |
emily | right now, I don't know if it makes sense to have the same people listed on both Darwin and Linux stdenvs, because their de facto maintainers are almost entirely disjoint | 17:36:44 |
emily | though | 17:36:50 |
emily | again it depends on what you count as stdenv | 17:36:53 |
Alyssa Ross | wouldn't this be more about codifying existing practice? | 17:37:11 |
emily | the shared code and the platform bootstraps are pretty different things | 17:37:06 |
Tristan Ross | My main thing is just to form an stdenv team from people who have had a stake in it's development. Once the SC is ready, they would be responsible for fine tuning things. | 17:37:11 |
emily | I am in favour of codifying existing practice | 17:37:35 |
emily | just want to make sure that's what we're actually doing | 17:37:39 |
Alyssa Ross | like, de facto certain stdenv changes do get blocked on waiting for somebody authoratative (via their expertise) to check it | 17:37:49 |
emily | right | 17:37:55 |
emily | (I mostly think we should make sure the structure maps to that de facto practice) | 17:38:36 |
Tristan Ross | I'm mostly looking for:
- Better communication
- Getting more PR's and issues figured out and resolved
| 17:39:51 |
Tristan Ross | My hope is that by having a central stdenv team, people would be on board to know what sort of changes that would affect nixpkgs as a whole. | 17:40:23 |
Tristan Ross | Like let's say if there was work that is wanted to rework how hardening works, that affects both darwin and linux. Everyone should be on the same page with that. | 17:41:09 |
13 Oct 2024 |
Tristan Ross | The stdenv team now exists on GitHub. | 02:45:03 |
Tristan Ross | The next steps are to get the CI to pass for the PR and merge it. | 02:46:18 |
Tristan Ross | CI is passing, probably could use a couple reviews if people have any last suggestions. Once there's like 2 or 3 approvals then it should be good to merge. | 16:43:37 |
emily | Artturin: trofi: did you not want to be on the team? I'd consider you both far more qualified than myself :) | 21:10:38 |
Artturin | In reply to @emilazy:matrix.org Artturin: trofi: did you not want to be on the team? I'd consider you both far more qualified than myself :) I requested to join now | 21:12:47 |
Tristan Ross | Download tenor_gif8551597978747056409.gif | 21:14:18 |
Tristan Ross | In reply to @artturin:matrix.org I requested to join now Will add you to the PR after work tonight | 21:14:32 |
trofi | I'll pass. I'd prefer to stay out of NixOS org. | 21:20:11 |
Tristan Ross | That's fine | 21:20:26 |
Tristan Ross | If you ever change your mind, there's an opening for you heh. | 21:20:46 |
15 Oct 2024 |
| Atemu joined the room. | 07:59:58 |
16 Oct 2024 |
| yannis changed their display name from yannis|pto back oct 16 to yannis. | 06:59:07 |
18 Oct 2024 |
| @sammy:cherrykitten.dev left the room. | 08:37:45 |
19 Oct 2024 |
| jwillikers joined the room. | 12:08:03 |