Child pages
  • Hyrax Maintenance Working Group
Skip to end of metadata
Go to start of metadata

Scope & Objectives

The Hyrax Maintenance Working Group (formerly the Hyrax Working Group) is charged with supporting core maintenance and development for Hyrax in order to provide a stable base of support for the solution bundle. Work includes addressing bugs and other issues as they arise and reviewing pull requests to Hyrax. This working group is not meant to be a replacement for community-led development efforts and/or contributions, but rather, it is meant to augment such efforts and release community members who are not part of the working group from the responsibilities around maintenance of Hyrax. 

Membership for Core Team

1 product owner: refines backlog, prioritizes stories and creates milestones, consults with Hyrax Interest Group as needed.

4-5 Developers including: Hyrax technical lead, who would be responsible for delivering releases in a timely fashion; 1 developer with UX skills when needed. All will be responsible for communication with Components Maintenance WG as needed.

QA Specialist/Coordinator: brought in during release time to test or coordinate testing and document.

Deliverables & Timeframe

The Hyrax Maintenance Working Group responds to an ongoing need for core maintenance and development of Hyrax. It does not have pre-determined deliverables as such. The charter provisions for a 6 month continuation through December 2020, but will presumably continue indefinitely in 6 month renewals. This cadence allows for participants to make a tenable commitment.  Deliverables include: regular updates when requested at Samvera conferences, partner meetings, etc.; and creation of charters to renew the WG as necessary.

Sprints will continue on the schedule of 2 weeks on and 2 weeks off.  This schedule is not adjusted around holidays and vacations to keep scheduling simple.

Meeting Times & Communication Channels

Team:

July 2020 - December 2020 (Sprints start September 1 and go through December; this will be a 4-month charter in practice, but backdating to July for continuity):

Name

Institution

Role

FTE

Notes

Julie Hardesty

Indiana University

Product Owner

0.2

As part of overall 0.2 FTE as product owner. JH begins role October 2020.

Tom Johnson

UC Santa Barbara

Technical Lead

0.2

As part of overall 0.5 FTE as tech lead

Jessica Hilt

UC San Diego

Projects Lead

0.2




QA Lead 

0.5


Brian KeeseIndiana University

Developer

0.5


Jeremy FriesenNotre Dame

Developer

?

I have confirmation that I can work 3 sprints on this and provide async consultation during the other sprints. I can also likely attend all sprint planning meetings, but not necessarily daily stand-ups. Depending on projects, I may have personal time I might commit.


Developer

0.5


July 2019 - December 2019:

NameInstitutionRoleFTENotes


Product Owner0.2as part of overall 0.2 FTE as product owner
Tom JohnsonUC Santa BarbaraTechnical Lead0.2as part of overall 0.5 FTE as tech lead
Jessica HiltUC San DiegoProjects Lead0.2
Kelly ChessNotch8QA Lead 



Daniel Lewis PierceIndiana UniversityDeveloper

0.5


Jose Blano / Fritz FreiheitUMichDeveloper0.5
Dananji WithanaIndiana UniversityDeveloper


January 2020 -June 2020:

NameInstitutionRoleFTENotes


Product Owner0.2as part of overall 0.2 FTE as product owner
Tom JohnsonUC Santa BarbaraTechnical Lead0.2as part of overall 0.5 FTE as tech lead
Jessica HiltUC San DiegoProjects Lead0.2
Crystal RichardsonNotch8QA Lead 

0.5


Brian KeeseIndianaDeveloper0.5


Developer0.5


Developer0.5


Agendas and Meeting Notes:

Release Notes (Working Drafts):

Previous WG Teams:

  • No labels