2024-05-29 Nix team meeting minutes #148

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
    1. clean up if you break something
      
      this is the distinguishing property of maintainers; contributors may disappear after any merged PR
    2. 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
@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