@zmitchell: Created documentation categories (PR not yet created). Not sure about what goes where, a lot of loosely categorized tutorials, making the tree deeper would be a better
@infinisil: Should tutorials be linear or graph-based? How to integrate with the tree structure?
@khaled: Linear might not make sense, some people e.g. don’t care about NixOS
@zmitchell: Imo the first steps should be linear, but after that it’s more free form.
@infinisil: Flakes still indirectly uses channels via the e.g. nixos-22.11 branch which Hydra updates on successful channel evaluations
@infinisil: Maybe channels should be introduced before this tutorial? nix-shell -p → channels → shell.nix with channel:...
DetSys installer leaves NIX_PATH empty, but <nixpkgs> is still available, making nix-shell -p work
@infinisil: Common grounds is that every installation has a <nixpkgs> available, can use that
@zmitchell: Where it comes from should also be documented
@infinisil: Currently it sucks because nix-channel is being deprecated, but the Flake registry has similar impurities
@infinisil: We could use nix-shell -p hello -I nixpkgs=channel:nixpkgs-unstable
@khaled: Flake registries seem bad, only the CLI should have it
Conclusion (@zmitchell, @infinisil, @khaled): Let’s go with the assumption that <nixpkgs> works in a Nix installation without going into details how it works
@zmitchell: Just cargo and rustc works fine for a Rust project without managing deps with Nix
Removed the learning journey project board by merging it into the documentation team project board using a new field “Subgroup”, a new view was created to filter just for learning journey issues: Nix documentation · GitHub