Scope & Objectives
The Hyrax Maintenance 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.
1 Projects Lead: Serves as Scrum Master for sprints.
4-5 Developers: Includes Hyrax Technical Lead, who is responsible for delivering releases in a timely fashion; Developer with UX skills when needed. All will be responsible for communication with Components Maintenance WG as needed.
1-2 Quality Assurance (QA) Specialists/Coordinators: Testing issue backlog and brought in during release time to test or coordinate testing and documentation.
All code contributors must have an Individual Contributor License Agreement (iCLA) on file with the Samvera Steering Group. If the contributor works for an institution, the institution must have a Corporate Contributor License Agreement (cCLA) on file. See Samvera Community Intellectual Property Licensing and Ownership for more information.
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
- The call for participation will be sent to samvera-partners@googlegroups.com, samvera-community@googlegroups.com, and samvera-tech@googlegroups.com, as well as through appropriate slack channels.
- Regular meetings (for sprint planning, stand-ups, etc.) will be held remotely, and will be scheduled at a time and frequency that works best for WG members.
- WG notes and activity, including working drafts of Release Notes, will be documented on the Hyrax Maintenance Working Group wiki page.
Team:
July 2021 - December 2021:
Name | Institution | Role | FTE | Notes |
---|---|---|---|---|
Julie Hardesty | Indiana University | Product Owner | 0.2 | as part of overall 0.2 FTE as product owner |
tamsin johnson Note: only through September 2021 | 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 | |
Github issues tester (QA) | 0.5 | |||
Rebekah Kati | UNC Chapel Hill | Github issues tester (QA) | 0.25 | |
Github issues tester (QA) | 0.25 | |||
Daniel Pierce | Indiana University | Developer | 0.5 | |
Developer | 0.5 |
January 2021 - June 2021:
Name | Institution | Role | FTE | Notes |
---|---|---|---|---|
Julie Hardesty | Indiana University | Product Owner | 0.2 | as part of overall 0.2 FTE as product owner |
tamsin 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 | |
Diem Tran | Notch8 | Github issues tester (QA) | 0.25 | |
Crystal Richardson | Notch8 | Github issues tester (QA) | 0.25 | |
Rebekah Kati | UNC Chapel Hill | Github issues tester (QA) | 0.25 | I have confirmation that I can work one week of each sprint. |
Daniel Pierce | Indiana University | Developer | 0.5 | |
Developer | 0.5 | |||
Jeremy Friesen | University of Notre Dame | Developer | 0.2 | 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. |
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. |
tamsin 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 Keese | Indiana University | Developer | 0.5 | |
Jeremy Friesen | Notre 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 |
January 2020 -June 2020:
Name | Institution | Role | FTE | Notes |
---|---|---|---|---|
Product Owner | 0.2 | as part of overall 0.2 FTE as product owner | ||
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 | |
Crystal Richardson | Notch8 | QA Lead | 0.5 | |
Brian Keese | Indiana | Developer | 0.5 | |
Developer | 0.5 | |||
Developer | 0.5 |
July 2019 - December 2019:
Name | Institution | Role | FTE | Notes |
---|---|---|---|---|
Product Owner | 0.2 | as part of overall 0.2 FTE as product owner | ||
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 | |
Kelly Chess | Notch8 | QA Lead | ||
Daniel Lewis Pierce | Indiana University | Developer | 0.5 | |
Jose Blano / Fritz Freiheit | UMich | Developer | 0.5 | |
Dananji Withana | Indiana University | Developer |
Agendas and Meeting Notes:
- Planning Meeting - June 2018
- Valkyrie Discussion - 2018-10-04
- WG Breakout and Valkyrie Discussion at Samvera Connect
- Hyrax QA Lead Bookmarks
Release Notes (Working Drafts):
Previous WG Teams:
The Hyrax Maintenance Working Group was formerly known as the Hyrax Working Group.