SIG: Documentation meeting on 2024-08-17
Attendees:
- Skyler Grey (@minion)
- Olly (@dfh)
- Florian (@liketechnik)
Agenda
- Approval/Revision of Agenda
- @minion: buildbot
- @minion: Buildbot up and working, executes ‘flake checks’ to check automatically
- @minion: downsides Cache missing, only 1 worker that also handles forgejo, possibly more workers from tc424
- @dfh: Can we have a set of criteria and modules that implement a secure worker? Possibly have some checkmarks of what makes a trustable community member.
- @minion: Good idea, but dont let theoretical/ trust aspects block having workers available.
- @dfh: Possibly ask Jake for guidance on trust.
- @dfh: We currently don’t have any critical packages we build, this might leave us with more space for technical experimentation right now. With the goal to see/ prove that it’s technically feasible.
- @dfh: Can we have a set of criteria and modules that implement a secure worker? Possibly have some checkmarks of what makes a trustable community member.
- @minion: network access hidden behind a headscale instance
- @minion: Looking at hosting websites from the builder, like pyroxs docs-site
- @minion: Upstream PR w/ buildbot to add a kinda ‘result’ like symlink to checks output → hope this could help with hosting via, e.g. nginx
- feat!: Update output path writing by Minion3665 · Pull Request #243 · nix-community/buildbot-nix · GitHub
- @dfh: Do we have forgejo workers then?
- @minion: No, buildbox links as a bot account into PRs, is not triggered by forgejo CI functions
@pyrox: This week in https://docs.auxolotl.org- @dfh: .editorconfigs and treefmt
- @dfh: With @minions help sorted it out.
- @dfh: Is docs authoritative on style and formatting, can we send PRs to other teams to fix their repos?
- @minion: Yes and Yes, I talked to Steering and they said to pick a standard and enforce it.
- @dfh: Where are all the place to implement that?
- Each git repo on https://git.auxolot.org/auxolotl
- All of the templates in https://git.auxolotl.org/auxolotl/templates
- Possibly move ‘c’ to ‘lang/c’
- Have some proper instructions on the wiki
- Fill the ‘treefmt’ placeholders in the wiki
- @dfh: Where are all the place to implement that?
- @minion: Yes and Yes, I talked to Steering and they said to pick a standard and enforce it.
- @dfh: Should we do direnv + devshells per default for all flakes?
- @dfh, @minion: email
- @minion: Mail is not yet routed to the new server due to MX priorities + mailgun not excepting incoming emails
- @dfh: Only mail, no calendar or contacts for now, can do jmap though
- @dfh: No webmail right now, but I’m thinking about roundcube{,-jmap}. they now have commercial backing by nextcloud. One can possibly use the gmail IMAP import as frontend too (still to be tested).
- @dfh git workflow examples to do PRs w/ forgejo properly
Action Items
- @minion + @dfh: Look at headscale networking issue
- @dfh: Send PRs for .editorconfig + treefmt to other aux repos + templates
- @dfh: Add treefmt instructions to wiki
- @dfh: Add direnv + devshell to docs repo
- @minion: Work out MX priorities with Jake
- @dfh + @minion: Figure out date & time to get started on git workflow docs
Standing reminders
- Next meeting will be at the same time next week!