Present: @ekohl, @Lennonka, @adamlazik1, @maximilian, @asteflova
This week I forgot to post an agenda, so these are just the notes.
Mini retrospective conclusion
Last week we agreed to have it offline by posting replies to Documentation team meeting 2023-09-25.
Overall everyone was happy with how it went, with some minor practical comments.
- Screensharing while triaging: this will probably always be an issue and you can’t expect everyone to read along. It’s agreed to keep it short. If it’s a lot of reading to summarize we assign it to someone who will prepare it for the next meeting. These will be added to the meeting notes and the agenda of next week.
- Time slot: it’s agreed that there’s a preference to keep the meeting at half an hour and weekly, so we’ll look for another time slot that better accommodates people. We tried to do it online, but that was difficult, so we’ll find a new slot offline. For next week we’ll keep the current slot.
- To advertise the meeting more openly the one making the agenda will add it to Events - TheForeman
Chat discussion
In light of Proposal on consolidation our chat platforms the question was raised if we need a separate Matrix room for documentation. @ekohl suggested to first start in the general foreman developers room and only if it becomes high traffic to start a new one, to avoid fragmenting the discussion.
Triage
After going through the open PRs and issues, these are the action items.
- Draft: Fixes Foreman Support #22332 - document multiple pxdns by pcfe · Pull Request #2007 · theforeman/foreman-documentation · GitHub is stuck, @ekohl will take a better look
- Refs #36697 - Use installer to modify Candlepin logging by ekohl · Pull Request #2471 · theforeman/foreman-documentation · GitHub will be reviewed by @maximilian
- Add info about expected interface names · Issue #73 · theforeman/foreman-documentation · GitHub @ekohl will investigate it for next week
- Look into improving this sentence of all provisioning procedures · Issue #50 · theforeman/foreman-documentation · GitHub @maximilian will see if the issue is still relevant