@zmitchell: population of people knowing Nix enough, and having capacity or interest in working part time even if well paid, is probably very small
@fricklerhandwerk: could leverage some expertise built up through Summer of Nix
should hire for full time work, budget would allow for it
what would we let paid contributors work on? high-value targets?
@proofconstructions: depends on their skill level
may require a lot of additional coordination
@fricklerhandwerk: Summer of Nix is coming up, mob programming thing is coming up, works really well especially for knowledge-sharing. Could be combined with the documentation effort?
@zmitchell: Looking at the Nixpkgs manual; will the recent changes to nixos-render-doc make it possible to split the nixpkgs manual into more than one page?
@fricklerhandwerk: certainly, but this is a minor issue requiring relatively small changes in comparison to content quality
possible topics:
@yuki_is_bored: language-specific sections need much more attention
@proofconstruction: platform-specific stdenv variations such as for Darwin
@nobbz: docs talk about GNU C compiler, though in reality it is system-dependant which compiler is provided
@nobbz: Manual also doesn’t really cover that we have a “default” stdenv that would be system dependant, while there are also “specific” stdenvs you can choose from if you need a newer/older GCC or Clang specifically.
@fricklerhandwerk: contribution guides, currently mostly a pile-up of rules
@zmitchell: agreed, almost useless; no instructions on testing and quality assurance
@zmitchell: Would be a lot easier to work on some of this stuff with funding for it, though it feels weird to say “pay me money!”
@proofconstruction: Certainly easier to imagine dedicating more time to this project, moving other projects to accommodate, etc. if there’s non-token money behind the effort. Only concern is effectively using the funds/being as productive as possible with the time, to maximize the ROI for the project.