Agenda
- triage board items
- team process (10 min)
- content (20 min)
- infrastructure (15 min)
- writing standards (10 min)
Notes
-
@fricklerhandwerk: @henrik-ch’s improved help command listing. by henrik-ch · Pull Request #7661 · NixOS/nix · GitHub will auto-merge when CI passes
-
@fricklerhandwerk: Can close documentation team: project board structure and function · Issue #470 · NixOS/nix.dev · GitHub now that we can filter by topic
- Does Learning Journey tutorial - "nix-shell -p" · Issue #498 · NixOS/nix.dev · GitHub need to be on the board?
-
@fricklerhandwerk: @Ericson2314 is blocked on Documentation: list experimental features in manual by peeley · Pull Request #7798 · NixOS/nix · GitHub.
- There’s some things to discuss, see review, could use some more eyes
-
@j-k: Could look at that
- What about daemon-only vs CLI flags?
-
@fricklerhandwerk: Got green light by the Nix team for Remove Package Management chapter · Issue #7769 · NixOS/nix · GitHub, consisting of a bunch of sub-tasks good for a first issue.
- How could we encourage people to tackle these?
-
@j-k: Tag tickets as
good-first-issue, link to filter
-
@infinisil: Could have a weekly Discourse post listing all the new issues that week
-
@infinisil: Less indirection is good, but means more work on our part
-
@zmitchell: Auto-generating markdown is easy using the github API
-
@fricklerhandwerk: Prepare filter queries, add to the monthly posts, “if you wanna help out, look at these issues”.
- Maybe tracking issues could be announced separately
-
@fricklerhandwerk: No cross-repo filters
-
@infinisil: Could have a separate board view with the filter
-
@fricklerhandwerk: Seems like it works, though can’t see all issues, needs to be added to the board
-
@infinisil: Could use the GitHub API to automatically add all
good-first-issue
-
@fricklerhandwerk: Now that we have smaller tasks, need a lot of volunteers for this; can encourage people to come to the meetings, should be announced
-
@zmitchell: Maybe have people leave a comment on the issue instead, asynchronous is often preferred.
-
@fricklerhandwerk: Can still encourage meeting participation when necessary
-
@zmitchell can pick up Section headings from comments at top of files · Issue #19 · nix-community/nixdoc · GitHub, knows Rust
-
@Ericson2314: Almost done with some listing shuffling around of experimental features
-
@fricklerhandwerk: Maybe we should follow up on the original announcement to get more people working on No Status tasks
-
@zmitchell: Where are things supposed to end up?
- Let’s prioritize the docs restructuring issues
-
@henrik-ch: Regarding removing installation instructions by henrik-ch · Pull Request #206 · NixOS/nix-pills · GitHub, should we go after maintaining the Nix Pills?
- Do we have permissions to change nix pills?
-
@Ericson2314: Has been given to the org a long time ago, should be fine
-
@zmitchell: Who should have access to nix.dev? Would be useful to have for me, but don’t want others to blow up the labels.
-
@infinisil: GitHub Subteams should work well for that
-
@fricklerhandwerk: Status of ease onboarding of contributors · Issue #333 · NixOS/nix.dev · GitHub?
-
@infinisil: General idea: Read more documentation ourselves
-
@fricklerhandwerk: Shouldn’t have to read all the docs to understand where to put stuff
- Learning Journey WG’s objective is to make that easier
-
@zmitchell: Created project board for the learning journey WG, but not public yet
- Moving the work meeting on Tuesday, when2meet not filled out by many yet: Nix documentation team weekly working session - When2meet
Action items
Hosted by Flying Circus.