Page Comparison

...

Notes

• Hyrax-Valkyrization

  • Held the community sprint

  • Project Board: Hyrax Valkyrization Project Board: https://github.com/samvera/hyrax/projects/20

  • Two weeks in length, there are still some outstanding issues to be fully-resolved

  • Improvements are being made for supporting derivative generation

    • Similarly, there is ongoing progress for integrating the UniversalViewer

  • Nested and shared collections are being advanced

  • Release Management

    • There is still outstanding labor required to support integrating Bootstrap for the latest Blacklight support?

    • Might there be a 4.0.0 and 5.0.0 simultaneously?

    • Valkyrized-Hyrax should not break any of the improvements and upgrades for the 4.0.0 pre-releases

    • Perhaps a single beta might be possible then?

  • 10/03/22 begins the final sprint with Julie as the Product Owner for the Maintenance Group

• Welcome Rebekah!

  • Rebekah will be serving as the new Product Owner for Hyrax

  • Julie will continue to attend as a representative for the Metadata IG

• Future Roadmaps Alignment Group

  • Perhaps this should be a rotating role?

    • There was a consensus for this decision

  • Facilitator would be responsible for ensuring that the agenda is always prepared

  • One person setting the agenda provided the energy needed for this group

  • Heather has volunteered to serve throughout the rest of the 2022 year

    • Planning the rotation for the 2023 year

    • James is available

• Core Components

  • (Notes to be added)

• Updated State of Technology white paper

  • ITHAKA paper and the need to publish a new paper (following version 1 released in 2019)

  • Want to publish a much more updated paper by 2022

  • This updated version must not state that the Valkyrized Hyrax is nearly complete

  • Definitely valuable to discuss, in more abstract terms, that there are efforts for decoupling the persistence backends

  • Publishing a paper in January 2023/Q1 is much more likely to be accurate in describing the state of Hyrax features sets and development progress

  • Avalon on Hyrax

    • There are a number of different strategies being explored

    • Will all development effort be halted on the current Avalon release series to dedicate resources for Hyrax/Valkyrie? Or might this be more modularized?

  • Hyku

    • Pushing to try and ensure that PostgreSQL is adopted as a persistence backend as quickly as possible

    • There exist several projects which require a high degree of data storage which would not be possible with Fedora

  • GitHub Teams

    • James needs to identify who should and should not be provided with membership to the GitHub Organizations for Samvera

  • Development Communication Plan

    • Request updates from members of the Roadmaps Alignment Group to determine if any technology domain requires additional labor (and, if so, determine whether or not a community sprint might be required)

    • There should be a new Rails release in the foreseeable future

      • Rails 7.1 is planned for release

      • Rails 6.0 series would then be end-of-life

        • No major updates are required, unless a new form of JavaScript handling is supported

      • Last of Ruby 2.7.z series is likely to be end-of-life at some point near or on Christmas Day

        • There may well need to be some labor to ensure that Ruby 2.7.z is no longer supported

      • Fewer Gems would actually reduce the amount of labor needed to support each upgrade

Meeting adjourned at 11:52 PDT/14:52 EDT