Hyrax Product Owner

Refines backlog, prioritizes stories and creates milestones for Hyrax Maintenance Working Group, consults with Hyrax Interest Group as needed. Shapes and maintains Hyrax Roadmap. Facilitates Hyrax Interest Group and Hyrax Maintenance Working Group. In consultation with the Samvera Community Manager, creates communications about Hyrax and related topics for distribution in the Samvera Community.

Product Owners

@Juliet Hardesty 2020 - 2022

@Rebekah Kati 2022 - 2024

@Nicholas Mark Homenda 2024 - 2025

Resources

• Hyrax Github repository

  • Issue reports with projects, milestones, and labels applied for organization and prioritization

  • Wiki with documentation contributed over time

• Hyrax product site - Information about Hyrax for interested developers/managers

• Nurax - demo implementations maintained by Samvera community. These sites moved from being hosted by DCE to Samvera and the Tech Lead has permission to make changes to the servers. All nuraxes are on AWS.

  • https://pg.nurax.samvera.org/ (Valkyrized Hyrax on Postgres, auto-deployed from Hyrax “main” branch)

  • https://dev.nurax.samvera.org/ (Valkyrized Hyrax on Fedora 4 with ActiveFedora, auto-deployed from Hyrax “main” branch)

  • https://stable.nurax.samvera.org/ (last “stable” release. Currently several releases behind because it needs to be manually deployed. We intend to repurpose for Valkyrized Hyrax on Fedora 6 in the near future)

• Hyrax Interest Group

  • also Hyrax Interest Group Google Shared Drive via Samvera (ask Community Manager for access)

• Hyrax Roadmap

Meetings

• Hyrax Interest Group (facilitator) - monthly

• Samvera Roadmaps Alignment Group - biweekly

• Samvera Tech Call (? maybe more Hyrax Tech Lead) - weekly

• Regular meeting with Community Manager and Hyrax Tech Lead - weekly

• Hyrax Maintenance Working Group standups (facilitator) – daily during Hyrax Maintenance Working Group sprints

  • The Product Owner may be asked to facilitate Developer Congress sessions, which overlap with one week of the maintenance sprints, usually in January, May and October.

  • Occasionally, the Maintenance Working Group will hold themed sprints (such as the Hyrax-Fedora 6 and Accessibility sprints in Fall 2024) to attract contributors outside of the normal maintenance group membership. The Product Owner will need to facilitate these sessions, create milestones, etc.

  • The Product Owner and Tech Lead typically present an update on Hyrax at Samvera Connect and Virtual Connect. The Product Owner also presents an update on the Hyrax Interest Group and Maintenance Working Group at these meetings.

• Other groups as assigned. The Product Owner may be asked to join other working or interest groups if needed. Rebekah served on the Hyrax-Fedora 6 Working Group, the Repository Managers Interest Group and attended a few virtual Samvera Partners meetings during her tenure.