...
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
...
January -
...
April 2023
Name | Institution | Role | FTE | PledgedHours | Notes |
---|
Rebekah Kati |
UNC-Chapel Hill | Product Owner | 0.2 | as part of overall 0.2 FTE as product owner | ||
Daniel Pierce | Indiana University | Technical Lead |
0.2
as part of overall 0.5 FTE as tech lead
Jessica Hilt
UC San Diego
Projects Lead
0.2
Rebekah Kati (through October)
Julie Hardesty (starting November)
UNC Chapel Hill
Indiana University
Github issues tester (QA)
0.25
Gabriela Montoya
Github issues tester (QA)
0. |
Joining sprints in November and December
Developer
5 |
May - August 2022
Name
Institution
Role
FTE
PledgedHours
Notes
Julie Hardesty
Indiana University
Product Owner
0.2
Technical Lead
0.2
as part of overall 0.5 FTE as tech lead | |||
Jessica Hilt | UC San Diego | Projects Lead | 0.2 |
UNC Chapel Hill
Github issues tester (QA) | 0.25 |
Indiana University
Developer | 0.5 |
became Technical Lead July 1, 2022
Tao Zhao
Federal Reserve Bank of Minneapolis
Github issues tester (QA)/Developer
0.5
Brad Watson
Emory University
Developer
Joining sprints in May and June
Ayoub Belemlih
Emory University
Developer
Joining sprints in May and June
Emily Porter
Emory University
Github issues tester (QA)
Joining sprints in May and June
January - April 2022
...
Name
...
Institution
...
Role
...
FTE
...
PledgedHours
...
Notes
...
Julie Hardesty
...
Indiana University
...
Product Owner
...
0.2
...
as part of overall 0.2 FTE as product owner
...
Technical Lead
...
0.2
...
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
...
Daniel Pierce
...
Indiana University
...
Developer
...
0.5
...
Tao Zhao
...
Federal Reserve Bank of Minneapolis
...
Github issues tester (QA)
...
0.5
...
filing iCLA so can also do dev work
...
Adam Arling 🌟
...
Northwestern University
...
Developer
...
20 - completed!
...
Bootstrap and related front end maintenance
...
Mat Jordan 🌟
...
Northwestern University
...
Developer
...
20 - completed!
...
Bootstrap and related front end maintenance
...
University of Michigan
...
Developer
...
80 - completed!
...
February 21 - March 4 sprint
...
Conor O’Malley 🌟
...
University of Michigan
...
Developer
...
80 - completed!
...
February 21 - March 4 sprint
...
Brad Watson 🌟
...
Emory University
...
Developer
...
160 - completed!
...
March 21 - April 1 and April 18-29 sprints
...
Ayoub Belemlih 🌟
...
Emory University
...
Developer
...
160 - completed!
...
March 21 - April 1 and April 18-29 sprints
...
Emily Porter 🌟
...
Emory University
...
Github issues tester (QA)
...
160 - completed!
...
March 21 - April 1 and April 18-29 sprints
Past Members
Hyrax Maintenance Working Group Members 2022
Joining a sprint or work cycle
...
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
...