...
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. 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.
Team:
The team for the first 6 months (July 2018-December 2018)January. 2019-June 2019:
Name | Institution | Role | FTE | Notes | ||
---|---|---|---|---|---|---|
Steve Van Tuyl | Oregon State University | Product Owner | 0.2 | as part of overall 0.2 FTE as product owner | ||
Tom JohnsonData | Curation ExpertsUC Santa Barbara | Technical Lead | 0.2 | as part of overall 0.5 FTE as tech lead | ||
Jessica Hilt | UC San Diego | Facilitator/Project Manager/Scrum Master | 0.2 | |||
Daniel Lewis Pierce | Indiana University | Developer | 0.5 | |||
LaRita Robinson | University of Notre Dame | Developer | 0.5 | possibly higher FTEKaren Didrickson | ||
Jose Blanco | NorthwesternUniversity of Michigan | Developer | 0.5 | Adam Arling | Northwestern University | Front Endwill be replaced mid-way through the 6 month period by another UMich developer |
Julie Allinson | CoSector | Developer | 0.5 | |||
Chris Diaz | Northwestern University | QA Specialist | --- | as part of overall FTE towards Hyrax QA Coordination | ||
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