1. a directory of contributing docs

2. markdown, same format as our other docs

3. nix code blocks are syntax-checked

1. one file per common pattern, potentially with examples

2. a list of useful tools and when to use them

1. explicitly document what we expect from

1. where/how to find

1. a directory of contributing docs

2. markdown, same format as our other docs

3. nix code blocks are syntax-checked

1. one file per common pattern, potentially with examples

2. a list of useful tools and when to use them

1. explicitly document what we expect from

1. where/how to find

1. a proper style guide

-  a directory of contributing docs
-  markdown, same format as our other docs
-  nix code blocks  are syntax-checked
  - bonus point if nix code blocks are reasonably easy to eval in a repl to poke somehow
-  one file per common pattern, potentially with examples
-  a list of useful tools *and when to use them*
  - `git-merge-base master staging`
  - tell people to STOP WASTING COMPUTE with `nixpkgs-review` without thinking
  - tell people to think? XD
-  explicitly document what we expect from
  - a new contributor
  - a new package/module
  - exiting packages/modules
  - existing contributors/committers
  - how to do (good) reviews that are useful, even if the reviewer is not a committer
  - includes security considerations
-  where/how to find
  - help
  - examples
  - "inspiration" from how other distros do things (and how that translates to nix)
-  a proper style guide