...
Hyrax Maintenance Working Group update - tamsin johnson and Julie Hardesty
Hyrax 3.0 release update (Hyrax Roadmap) - Julie Hardesty
Topics and Projects
Hyrax policies
Browser support - Proposal: Support the latest browser versions for Chrome, Firefox, Edge, and Safari.
Abandoned browsers like IE are no longer supported
Accessibility considerations
Current Hyrax QA Testing coverage (Chrome, Safari, and Firefox on following OS: Windows, Mac, Android, and iOS)
Cloud storage service support (Box, Dropbox, etc) - is this Hyrax or Core Component (BrowseEverything)?
Where should policies like these live?
Hyku news
Questions?
Next meeting: Monday, March 8, 11:30am Eastern
Notes
Hyrax
The Hyrax Maintenance WG completed its first sprint. There are ~400 issues, we closed out 14 issues in this sprint. We no longer have any issues labeled as blockers. We are working through those labeled as bugs. We had two developers, one triage person, one QA person.
...
Here’s what we’re working on
A non-developer verified that this is or isn’t still broken
And a developer can pick it up knowing that this is a problem
One observation is that the developer work was easier to approach and then resolve. In particular with the documentation for Containers and testing using those containers.
Right now Nurax is pinned to 3.0.0.pre.rc3. We’re not pushing updates current work to Nurax.
...
In the ask, we need a testing coordinator with a deeper knowledge of Hyrax. Ideally this would be someone from the repository managers group. (Juliet Hardesty and Moira Downey (Deactivated) will connect to coordinate). We have an aspirational end
REMINDER: Hyku 3.0 is not on Hyrax 3.0. Hyku 3.0 brought changes to the user model, requiring a migration. Also, there’s a 3.0.1 release that patches a minor security vulnerability.
The Valkyrie dates in the documentation are not up to date. The roadmap is a work in progress, and not current.
Hyrax Policies
When we publish a release, we should declare what versions we used for testing. We can adopt a policy around the browsers we support. Samvera will not be supporting IE 11.
We need a place to articulate what browsers we support. A recommended place is in the Requirements in the README; it lives closer to the code.
Similar, we have challenges with cloud storage service report. Keeping these working is an effort of will. We may want to explore writing specs that consider the API’s of these services as untrustworthy (e.g. subject to arbitrary change). This is conversation Hyrax’s WG/IG should have with James Griffin.
The very specific problem around Browse Everything is on Notch8’s radar (because of a current project structure to contribute back to the community); One of the goals of this project is to improve the documentation for wiring up Browse Everything. There’s a distinct challenge in the volatility of our API.
We’re going to move this into an interest group discussion, and we’ll review if this should move into a working group.