2026-06-16 Documentation Interest Group Meeting Notes

🔗 Links

• Zoom link

• Documentation GitHub Board

• Documentation Interest Group Confluence Page

 Participants

• @Sarah Proctor - notetaker

• @Morgan McKeehan - facilitator

•  

 Goals

• Any questions from DocIG participants?

• Agenda items

  • reminder about: likely no Docs priorities for Community sprint in June. Also probably no DocDays of Summer this year.

  • look at figma diagram, for Admin Sets ticket: Admin Sets: Create beginner-friendly graphics to introduce the concept of Admin Sets · Issue #2698 · samvera/hyku

  • collect ideas for 1-pager (Action item from May 19)

    • gist of the 1-pager: a super simple public-facing overview page about the Samvera documentation organization overall/where to find different kinds of docs. consensus yes - this could be useful, potential future mini-project for a couple folks to contribute to. Could maybe link from the Samvera main page. HGK goes through the Samvera main page every December to update it.

      https://samvera.atlassian.net/wiki/spaces/samvera/overview?homepageId=405210583. can also access it via shortcut : wiki/samvera.org

  • Board organizing tickets if time

• Categorizing/prepping tickets in Documentation Tasks Board

  •  Overall - any issues folks want to discuss, and/or that need coordination/feedback with other groups? 

  • Check the Board’s Workflow columns:

    • “Questions/blockers”

      • Check in comments threads, if there’s anything we can do to help resolve the Qs/blocks.

      • [if any tickets to discuss, can add here]

    • “inProgress”

      • Check for issues that are not-assigned to anyone?

    • “Ready”

      • Confirm that everything here is an “issue” (ie all drafts have been converted to issues, assigned to a repo.)

    • “Todo” column -

      • In the Todo column overall - are there any in “todo” that are higher-priority/DocIG should look at 1st?

      • Prep tickets so that they are “Ready to work”.

        • Ready to work =

          • all required tags are assigned (see below for required).

          • Add clarifying info to description if needed.

          • Generally check if there’s any quick improvements you can make so it’s easy for someone to pick up the ticket & work.

          • Then, convert the draft to an issue in a gh-repo, & move it to the “Ready” column.

      • About the tags:

        • Required tags: Audience, doc-location, SamveraProject (dropdowns with CVs)

        • Optional tags: workflow (IGdiscuss, triage); events (if good for a DocSprint, etc.)

 Discussion Notes

 Action Items

 Decisions