2025-04-15 Documentation Interest Group meeting notes

Zoom link

 Participants

• @Kiah Stroud

• @Heather Greer Klein

• @Sudha Anand

• @Rebekah Kati

• @Morgan McKeehan

• Dona

• Sarah Proctor

• @Nic Don Stanton-Roark

• @Christine Peterson

 Goals

• Discuss documentation needs

• Mark tickets that can be worked on at Virtual Connect as “ready” on the board

 Discussion notes

• Any documentation needs from participants?

  • No

• Suggestion: create a doc that captures and lays out how this IG operates

  • https://docs.google.com/document/d/1BukNDRa7IjXEZwpfWrcLinGz8X1LOdW4daIUyYsV7SA/edit?tab=t.0#heading=h.5f0h4qwwamw2

• Criteria to be ready to be picked up in the sprint:

  • Link to page or pages to be updated

  • Describe what’s necessary for the ticket to be considered “done”

    • Either phrasing this as a problem (e.g. “this page lacks Valkyrie info”) or as a suggestion (e.g. “consider adding a table with these columns”) leaves room for the person working on the ticket to make decisions or ask questions

  • Documentation type is defined, and the audience is defined - is this for a developer, is this for an admin, is this for an end user, etc.

    • The following three ticket fields should be used to accomplish this:

      • Related tech/tools

      • Documentation location

      • Doc type

• What would be helpful to kick off the Documentation working group? i.e., Github access; GitHub training?

  • Heather is working on this and will be asking for feedback in the #documentation Slack channel

 Action items

 Decisions

1. Create a document to represent how this IG operates