2024-01-18 Hyrax Fedora 6 Working Group

 Date

Jan 18, 2024@11am Eastern

 Participants

• @Jon Dunn

• @Randall Floyd

• @Daniel Pierce

• @Juliet Hardesty

• @Collin Brittle

• @Ayoub Belemlih

• @Bradley Watson

• @Kevin Kochanski

• @Emily Porter

• @Dan Field

• @Rebekah Kati

• @Heather Greer Klein

 Goals

• Updates

• Collaborative work on re-writing WG Scope & Objectives

 Discussion topics

Notes

Previous Action Items:

• Sent overview document in December that listed interests of different institutions.

• Finalized working group in community

• Created a page to document, eg. performance testing

Updates:

Hyrax:

• Working on resolving last few failing tests for Valkyrie-only test suite copy (30-something or less)

• Next week’s maintenance sprint should get a Hyrax 5 release out

• Status of Sirenia will be fully supported; currently experimental but seems to work well

  • Sirenia testing: https://docs.google.com/spreadsheets/d/1cBmqnbwWvpKLPOehpKBzuPZo1W1dYo7Y/edit#gid=202333338

  • More retesting of failures and investigating what is Fedora-related would be good (Dev Congress)

  • If we find these are Fedora 6 related, then we don’t have a connector that’s ready for release

• Performance testing - after we get the connector solid, we’ll move forward with performance testing and identifying final adjustments

  • @Juliet Hardesty proposes working with this group for performance testing

• Would be good to get Nurax updated

Fedora 6.5:

• Out by the end of February

Valkyrie:

• Samvera Board has funded SoftServ work for migrating a Hyku instance into Valkyrie/Postgres

  • This was begun over the holiday’s but Kevin didn’t gather an update before this call

• PALNI/PALCI have finalized plans to migrate to Postgres via Valkyrie, which SoftServ has started

Maintenance WG

• We need to leverage the Maintenance WG for resolving

• @Daniel Pierce can’t be the only person contributing to this work

  • We need to do a call to source more dev hours for this work in the Maintenance WG

  • Do this after the dev congress so we can be specific about what work needs to be done

  • Volunteers:

    • @Ben Pennell volunteers to help some depending on the nature of the issues found

    • @Emily Porter and @Collin Brittle said Emory may be able to help, at least with testing

WG Scope and Objectives - https://docs.google.com/document/d/1abE8z8tl0s0SWOewt4zzDGgTB0iqXKp3agtmzVbMXbo/edit#heading=h.j3278pwce3hl

• Originally slated for 3 months

  • This was focused on scoping work, but we should move beyond and expand the scope of the group

• Who sources the dev work for resolving Fedora 6 connection issues that come out of the dev congress?

• @Juliet Hardesty will still consider chairing this group, cannot yet commit

• Future work for this group, as a Part Two (out of scope for this WG):

• A migration to Fedora 6

Revising Deliverables and Timelines:

• We need to revise the language to change from planning to doing

  • Suggest instead of changing the scope, to organize the Planning as a completed milestone, and the Doing as a Phase 2 milestone

• Anything missing as “Deliverables?”

  • Finalize Fedora connector

  • Document migration effort and monitor the need to get others involved

 Action items

 Decisions

1. Will continue with this group, not changing original scope but adding to the charter a second Phase or Milestone (Planning being the initial scope, now considered Phase or Milestone 1)