...
Attendees: Jeremy Friesen
Agenda:
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
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.
The opening process worked well:
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
Right now Nurax is pinned to 3.0.0.pre.rc3. We’re not pushing updates current work to Nurax.
The Roadmap is Juliet Hardesty 's suggestion, she needs to vet this with tamsin johnson .
Julie’s been working through what needs testing for rc2 to rc3. Juliet Hardesty will be drafting a community ask for testing. Heather Greer Klein will make sure it makes it through all the channels.
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).