Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Date

2-3PM EST

Call-in Info

BlueJeans: https://bluejeans.com/223781975

Wiki: https://wiki.duraspace.org/pages/viewpage.action?pageId=90976017

Goals

  • Understanding of State of Hyrax Roadmap
  • Identification of Possible roles/ outcomes
  • Identification of Meeting schedule

Discussion items

TimeItemWhoNotes
Start

Status of Hyrax Roadmap and whats next

  • What is finished?
  • What is happening now?
  • What is planned?
  • How do we get to the 3.0 release?

Steve Van Tuyl; Michael Joseph Giarlo



Governance Discussion Input - does SIGAHR have specific feedback?

Steve Van Tuyl



Hyrax issue review club

  • would be useful to have a subgroup of SIGAHR to periodically (monthly? weekly?) review Hyrax issues for labeling, prioritization, etc.
  • volunteers?!

Steve Van Tuyl



Backporting - how far back do we want to support Hyrax?

Steve Van Tuyl; tamsin woo


Towards the End


Action items

  • @


NOTES

Steve - go over agenda

status update for where we are on the Hyrax Roadmap - Hyrax issues review club and back porting and previous solutions

COllections extension work is nearing the end.  2.1 release - Lynette - not a lot of issues (< 30).  Get resources on cranking on issues.  

Shake the tree for folks who can help resolve issues for 2.1 release.  About 1/2 the issues are general Hyrax issues and don't need C.E. knowledge, but Lynette will get people up to speed.

Looking for 1-2 people who can jump on for rest of March to finish up ANALYTICS.  Don't have to talk about it now, but get people in touch with Van Tuyl.

Group in responsibility MGMT.  Addressing that set of issues - LaRita from Notre Dame is watching that.  How roles and groups are managed or not.

Accessibility 360 call.  Contracted for an accessibility audit in Hyrax.  Write up report of findings, 140 issues to resolve.  Indicated that Hyrax is in decent shape, work to be done.  Follow up for next steps.  GitHub project for accessibility issues, decide method for tackling issues.  Not a huge amount of work.  

Start building out documentation for how we address accessibility up front.

New life in Bulk Import/ Export/ Edit convo - Tom Johnson put together a working group to hash out requirements.  Needed batch functionality.  

Swappable back-end/ Valkyrie - Trey led a 3rd dev effort - what does it mean to finish that work?  How do we make that happen?

Community exhaustion for dev efforts?  Fatigue from CE stuff, analytics has a hard time bringing people in.  Guess:  Valkyrie work and bulk/ import/ export - maybe summer?

There's continued interest in Vaklyrie in Slack - start soon, plan, line-up resources.  Maybe start work in early summer.  Lots of work left, get 6-8 week effort spun up.  (Justin Coyne was lead on last 2 efforts)





Action Items:



  • No labels