Attendees: @edolstra @roberth @fricklerhandwerk @ericson2314 @raitobezarius
Notes: @fricklerhandwerk
Triaging
LocalStore does not set up or sanitize its build environment correctly · Issue #10798 · NixOS/nix · GitHub
- good issue, needs more investigation
Poor performance of `nix build --debugger` · Issue #10796 · NixOS/nix · GitHub
- needs reproducer
SSL certificate path does not propagate to builds during `nix-build` · Issue #10783 · NixOS/nix · GitHub
- documentation issue, assigned to @fricklerhandwerk
Have our cake and eat it too derivation metadata · Issue #10780 · NixOS/nix · GitHub
- to discuss
Build error: no matching conversion for functional-style cast from 'std::string' · Issue #10774 · NixOS/nix · GitHub
- @roberth will fix
`fetchGit` with a fixed rev and no ref repeatedly hits the network · Issue #10773 · NixOS/nix · GitHub
- looks like a regression related to changes to the fetcher cache, @edolstra will look into it
Crash with static nix if HOME is owned by a different user · Issue #10772 · NixOS/nix · GitHub
- assigned to @Ericson2314
`nix build --system` don't use remote builder · Issue #10762 · NixOS/nix · GitHub
- may be a documentation issue
Discussion
- Shoutout @abathur who tirelessly triages installer issues!
-
@fricklerhanderk: maybe we should introduce labels such as
needs reproducer
- @roberth: we should try
- @fricklerhandwerk: generally need more diligent triaging, have to think about it a bit
-
@fricklerhandwerk: discussed adding more committers with @roberth and @silvan at the Zurich ZHF hackathon, and clarified the ideas together with @tfc.
- conclusion:
- double down on handing on merge permissions
- two strict requirements
-
clean up if you break something
this is the distinguishing property of maintainers; contributors may disappear after any merged PR
-
align with the maintainer who invited you
you’re responsible for technical correctness, but make sure changes take the right direction
-
- we don’t have too strong interfaces yet, but new maintainers can already take moral ownership and help strengthen the in-code boundaries
- @Ericson2314: new maintainers should also communicate a lot. if you can’t make the meetings, write on Matrix, Discourse, GitHub
- @Raitobezarius: it’s also a pending discussion at Lix, but it’s likely people will take a “lock” on particular aspects and lead/own them
- conclusion:
-
@Raitobezarius: Lix found an issue with flake tarballs, the headers don’t follow the HTTP standard
- @fricklerhandwerk: this would be something for @edolstra to check
-
@fricklerhandwerk: STF offered in-kind contributions (recently mentioned on Matrix), concretely developer time to work on Nix (not clear yet how much exactly)
- had an exchange with the contractor, will meet next week to discuss details
- @fricklerhandwerk @Ericson2314 @roberth are up for shepherding them if it comes together