About the Committees category

(Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters.)

Use the following paragraphs for a longer description, or to establish category guidelines or rules:

  • Why should people use this category? What is it for?

  • How exactly is this different than the other categories we already have?

  • What should topics in this category generally contain?

  • Do we need this category? Can we merge with another category, or subcategory?

  • Hey @jakehamilton, really excited to see the committees and wondering if we can have one for documentation… here’s why we think it’s needed and what we think people would do:
  • Aux has excellent ideas, and we want people to understand them. People have struggled with learning Nix, so we’d love to have an extensive set of docs and guides to refer to when you get stuck!
  • This is a new committee, we’d expect people to discuss ways to improve the docs as well as share the work they’ve been doing. We also wondered about having weekly documentation calls, and would post the minutes in the category.

(CC: @coded)


I completely agree and the omission of such a group is my mistake! I think the best way to organize this is as a SIG focused on documentation.
I’ve created a new category and group for it: SIG Documentation - Aux

May I add you @minion and @coded as members so you can begin posting in that category?

Yes, please do. We’re on call and @coded has said that is a good idea too. Thanks!

1 Like