Orientation Meeting: Doc IG Co-Facilitators + Samvera Community Manager
Samvera Community Manager Office Hours/Orientation meeting for new DocIG co-facilitators
Tuesday Aug 12, 2025 ⋅ 11-11:30 am PT/ 2pm – 2:30pm (Eastern Time - New York)
all DocIG participants are also welcome to join! In this call, we’ll be learning from HGK more about how the various Samvera Community projects and groups are organized, so we can keep this in mind for planning the DocIG’s work.
Participants
@Heather Greer Klein
@Sarah Proctor
@Morgan McKeehan
Goals
Orientation questions from new co-facilitators for Doc IG:
Samvera projects covered by Documentation Interest Group:
Current: Hyku, Hyrax, Bulkrax
The documentation group can cover any topic under the Samvera Community umbrella that is needed. The group’s focus areas tend to be shaped by whoever shows up. If there is a need that is not being met by the group, the facilitators can flag it and pass it along to Heather.
Sometimes there is a need to balance what gets documented vs not documented. Things that change quickly can be hard to maintain. But as a rule, a barebones version is better than nothing.
Could also include:
Any projects that the Samvera Community wants to work on. Such as:
possible future AI projects that grow out of/in relation to H/H
currently separate:
Valkyrie - is separate from H & H. This is a related but sep tool.
Valkyrie is also pretty stable/done at this point. Most Valkyrie doc is in the readme in Valkyrie gh repo. Valkyriedocs are dev-oriented.
Valkyrie is mostly Hyku-oriented.
Avalon - has more staff, so they tend to do their own docs.
others? - not currently, but might be in future if projects grow out of/in relation to H/H
What is the “tree structure”/overall organization of the projects in relation to each other?
diagram!! The Hyrax and Hyku Technology Stack
Hyku will be the most unique - has the most-developed feature set, vs. Hyrax is pretty bare-bones OOTB. So Hyku has more detailed workflows/functionality that could potentially be documented
Who are the product owners?
Hyku - Nick Don PO - contract position thru grant
This is 1st year for Hyku to have a PO. Previously, had only a TechLead.
TechLead: Rob K. at Scientist, prev. Notch8
Sustaining Hyku - has 1 more year in grant.
term of current team: thru Dec.2026
Hyrax - Nick Homenda PO, volunteer service thru Tufts.
TechLead: Randall, volunteer service
on calendar year schedule
term of current team: thru Dec.2025, or 2nd year Dec.2026
Bulkrax - had a PO previously, but does not currently.
under purview of H/H (both teams)
Avalon - Jon Cameron, is both PO+TL - and is staff/Indiana
Future for H/H PO and TL-
minimum need is for 2 roles: PO and TL.
Communication: OK to ping PO and/or TL in hyrax or hyku channels
Doc Tasks board setup and process
Labels - (non-dropdowns) not working for tables/filtering?
Ok to experiment with config of tickets/labels
Doc Locations
Morgan to update values, based on current locations from H/H docs structures/frameworks pages
Drafts vs. Issues
We will convert drafts to issues when ready to work!!
Moving issues to Done
will document process: ticket-assignee gets to decide/move to done. They can add comments/Qs + move to blocker column if they want to, but otherwise the regular process is for assignee to move to done.
Logistics
Zoom meeting: zoom link in the current invite should work - co-Facils OK to join on their own, etc
Calendar invitation - there have been problems with sharing the invite w/ folks using Outlook
co-Facils OK to add participants to the invite
Discussion notes