# 2023-04-27 Documentation team meeting notes #44

**URL:** https://discourse.nixos.org/t/2023-04-27-documentation-team-meeting-notes-44/27694
**Category:** Documentation
**Created:** [April 28, 2023, 3:40pm UTC](https://discourse.nixos.org/t/2023-04-27-documentation-team-meeting-notes-44/27694 "2023-04-28T15:40:21Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![fricklerhandwerk](https://discourse.nixos.org/user_avatar/discourse.nixos.org/fricklerhandwerk/32/2029_2.png) [@fricklerhandwerk](https://discourse.nixos.org/u/fricklerhandwerk)
#### Post date: [April 28, 2023, 3:40pm UTC](https://discourse.nixos.org/t/2023-04-27-documentation-team-meeting-notes-44/27694/1 "2023-04-28T15:40:21Z")

</div>

- [Video conference](https://meet.jit.si/nix-documentation)
- [GitHub project board](https://github.com/orgs/NixOS/projects/15)
- [Team details](https://github.com/NixOS/nix.dev/tree/master/maintainers)
- [Past meeting notes](https://discourse.nixos.org/search?q=documentation%20team%20meeting)
- Attendees: @infinisil @fricklerhandwerk @zmitchell @asymmetric @spacekookie @henrik-ch
- Notes by: @infinisil

## Agenda

- Updates
- Documentation project

## Updates

- @asymmetric:
  - [add section on how to get help by asymmetric · Pull Request #504 · NixOS/nix.dev · GitHub](https://github.com/NixOS/nix.dev/pull/504)
  - Maintaining Nixpkgs Rust chapter
  - Nixdoc work with @pennae
  - Intend to look at [https://github.com/NixOS/rfcs/pull/145](https://github.com/NixOS/rfcs/pull/145)

- @zmitchell:
  - [Add issue templates by zmitchell · Pull Request #501 · NixOS/nix.dev · GitHub](https://github.com/NixOS/nix.dev/pull/501)
  - [Switch from poetry to nixpkgs by zmitchell · Pull Request #515 · NixOS/nix.dev · GitHub](https://github.com/NixOS/nix.dev/pull/515#issuecomment-1525768884)
  - Asked around for applicants for documentation project, no results

- @henrik-ch:
  - Got some help on Nix hacking on Monday
  - Want to focus on the [Nix Pills](https://github.com/NixOS/nix-pills/)
    - update some information, fill gaps
    - @zmitchell: opens the question if we want to maintain them or restructure according to Diataxis
      - [Should we update Nix Pills or translate content to Diataxis framework? · Issue #212 · NixOS/nix-pills · GitHub](https://github.com/NixOS/nix-pills/issues/212)

- @spacekookie:
  - [Module system documentation refactor by spacekookie · Pull Request #526 · NixOS/nix.dev · GitHub](https://github.com/NixOS/nix.dev/pull/526)
    - a couple of open questions around scope
    - apparently the module system as an A-B-A problem (with cyclical dependencies between sections)
    - will probably have to create an overview of what is there to be known and how to sequence the information
    - should discuss this once it’s ripe
    - @infinisil wants to get involved and provide feedback

- @infinisil:
  - did a mob programming session on Monday with @zmitchell and others: [2023-04-24 Documentation team meeting notes #43](https://discourse.nixos.org/t/2023-04-24-documentation-team-meeting-notes-43/27558)
    - could still continue, did not upstream the package yet
    - may actually be a couple of more episodes until it’s done
    - @zmitchell: still have to figure out how to do testing

- @fricklerhandwerk:
  - Maintaining the Nix manual
  - Talked to a lot of people
  - Have 18k in the documentation project sponsorship fund
    - Posted [job announcement](https://github.com/nix-community/developer-workshop) last week

  - Preparation for [ZHF hackathon and developer workshop in Zurich](https://github.com/nix-community/developer-workshop). If you have tasks you would like hackathon participants to work on, drop them in the scatchpad
    - [Nix ZHF 25.05 - HedgeDoc](https://pad.lassul.us/hbEwem2tS6mWjDM9WhDCpA#)

## Documentation project

- Who wants to be involved in the project? Starting end of May
  - @infinisil: Can provide Nix help
  - @zmitchell: Will definitely be involved, as a writer too
  - @asymmetric: Want to be involved, but constrained on time

- How can we onboard the editorial lead effectively, providing all the needed context?
  - Could we e.g. provide help by looking through documentation team logs.
  - Have tasks like these for e.g. an hour a week for volunteers

- Goal is to keep focus while the two people are paid for it, they shouldn’t be blocked.
- @zmitchell: Let’s announce the call more, do our due diligence as a sponsored project
- Decision on the application process:
  - @zmitchell will have the final call as the Learning Journey Working Group lead
  - Documentation team members’ input will be considered for the decision