Nix Documentation team meeting #8

2022-08-25

Attendees: @olaf Luc (DetSys) @infinisil @fricklerhandwerk @edolstra @domenkozar (@jonringer @nrdxp arrived later)

Notes: @infinisil

  • @fricklerhanderk: Anything we should be aware of?
    • @Olaf: How much work is it to discuss nix.dev CLA assigning copyright to NixOS foundation? When to put it on the agenda?
      • @fricklerhandwerk: Has a PR for assigning copyright to NixOS foundation
      • @domenkozar: Often required by book publishers. Originally it was all me writing it. Should changed in the future to be legally correct.
      • @olafklingt: Too early?
        • @domen: Yes
      • @fricklerhandwerk: Should be discussed with the board, but how to reach them?
        • @edolstra: We have an issue tracker
        • @fricklerhandwerk: Can we link that more visibly?
          • @domenkozar: Should first make it work well before announcing it too much, very new
        • @fricklerhandwerk: I've got a couple blocking issue that need the board's decision
          • @domenkozar: Creating issues is fine, but don't announce it yet
    • @fricklerhandwerk: Finished Nix language tutorial draft (original issue), did two walk-throughs with beginners. Doesn't cover everything, but gives roadmap for learning not just Nix, but ecosystem. Feel free to review it or test on beginners.
    • @fricklerhandwerk: I'd like commit access for Nix
      • @eelco: I only have push access. I'd like to review PRs for the manual
      • @fricklerhandwerk: I only want to make issue and PR labels, and establish CODEOWNERS.
      • @eelco: Will add you
  • discussed proposal for binding terminology (40 min)
    • decision: Nix package manager, Nix language, Nixpkgs (the package collection, read: Nix packages) and nixpkgs (GitHub repository with Nixpkgs and NixOS).
  • explored how to accomodate Nix book project by @jonringer and @nrdxp (15 min)
    • decision: should eventually merge efforts after agreeing on outline (proposal)
Select a repo