Documentation team meeting 2025-11-13

Join via https://meet.google.com/zih-cgjz-czo

Community demo

Have we recently merged any documentation worth highlighting in the next community demo? If so, can someone present it?

General

Agenda for our open docs meeting. Please add comments under this post to propose your topic.

Triage

Anything updated within the past week can be ignored during triage.

Feel free to join or reach out to us on matrix.

@aneta-petrova Would you be willing to talk about upstream AI tools?

It was discussed yesterday and I don’t think there will be much more to share on Thursday. At this stage, using Investigate options for automated PR reviews · Issue #4462 · theforeman/foreman-documentation · GitHub for a discussion should IMO be sufficient.

Proposed topic: From @ekohl - Indicate a document’s persona/target audience in the repo itself so that writers can see the information without having to go through the modules.

I’d like to discuss Add section "Boot loader management and file structure" by spesnova717 · Pull Request #4422 · theforeman/foreman-documentation · GitHub, how we approach the review and if the format is OK.

Triage

  • Anet will ask Eric as theforeman org owner to enable the AI feature on GH
  • Idea: one small readme per guide? Avital will create a small PoC
    • README in guides/doc-X/ would be rendered by GH
    • lines in master.adoc would be more visible to writers
  • PR 4422
    • merge to “master” after tech ACK
    • focus on style and conventions afterwards so that we do not block it forever
    • thanks to the original contributor
    • Jan will take over from there