Discussed the overall structure of the Docs effort
Dificulty of merging, lack of contributors, spending a lot of time collaborating but not getting the velocity we want/need
@roberth: We’re (currently) trying to write documentation like we write software
@proofconstruction: Some concerns around getting blocked on code style/approach; re: nix-build -E [expr] -A … vs making a default.nix and just nix-build -A attrname
@zmitchell: Need a style guide for how to write Nix
Broadly all agree it would be better to have faster merging and more PR activity than keeping PRs sitting while they’re under indefinite review.
@zmitchell: On duplication: need a section of the tutorials as an entrypoint/managed experience for learning (the Learning Journey). It’s fine to move some First Steps tutorials to LJ.
Examples: Nix language tutorial, pinning nixpkgs
Pinning Nixpkgs tutorial; why not use import <nixpkgs>?
Progressive disclosure, fine to use not-best-practices from the beginning.