| Table of Contents | ||||
|---|---|---|---|---|
|
Scope & Objectives
The Hyrax Maintenance Working Group (HMWG) 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.
Meeting Schedule
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.
Our current meeting time is 1:00 to 1:15 PM Eastern time
Roles for Core Team
1 Product Owner: Refines backlog, prioritizes stories and creates milestones, consults with Hyrax Interest Group as needed.
...
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. 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.
...
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.
Current Year Teams
...
Membership
Name | Institution | Role | FTE | PledgedHours | Notes |
|---|
Rebekah Kati
Nick Homenda | Tufts University | Product Owner | 0.2 | as part of overall 0.2 FTE as product owner | |
Daniel Pierce | Indiana University | Technical Lead | 0.5 | as part of overall 0.5 FTE as tech lead |
Jessica Hilt
UC San Diego
Projects Lead
0.2
Rebekah Kati | UNC-Chapel Hill | Github issues tester (QA) | 0.25 |
Fritz Freiheit
University of Michigan
Developer
February and March sprints only
Jose Blanco
University of Michigan
Developer
February and March sprints only
Past MembersPast Members
Joining a sprint or work cycle
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.
Sprints occur on a 2 weeks on and 2 weeks off cycle, regardless of calendar, holidays, or planned time off.
Use the #hyrax-wg channel on Slack to communicate with other HMWG members. You can check in Slack to find out when the next sprint is scheduled to begin.
During a 2 week sprint, daily stand-up occurs via Zoom at 1pm Eastern each weekday of the 2 week sprint (Monday-Friday). Zoom connection info is pinned in the #hyrax-wg Slack channel.
There is a project board in Github that tracks the issues for a sprint and/or work cycle. The current project board is also pinned in the #hyrax-wg Slack channel but should be identifiable by name at https://github.com/samvera/hyrax/projects .
Schedule
2023 Hyrax Maintenance Working Group Schedule
Preparing for HMWG sprint work
Hyrax code is managed in Samvera's Hyrax git repo on Github. Fork that repository and however you prefer, clone that code for working locally (command line checkout, Github Desktop, download a zip).
Make sure Docker is installed locally to contain and manage a local build for running a local Hyrax application.
The following instructions guide you through installing a Hyrax application using Docker: https://github.com/samvera/hyrax/blob/main/CONTAINERS.md
...