Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Notetaker: Rebekah Kati

Attendees:


...

Meeting Process

Expand
titleModerator and Note Taker - click to see meeting process...
  1. Standing pre-agenda items (moderator)

    1. Welcome

      • "Welcome everyone, please add your name to the Attendees list.  If you are unable to do so, please let us know, and someone will add you. To any newcomers, Welcome, and please feel free to ask questions. Likewise for all attendees. We strive for an open and accessible conversation around Samvera technology."

    2. Call for new agenda items

  2. Follow Agenda from above (facilitated by moderator) and record notes in Notes section below (note taker)

  3. Standing post-agenda items (moderator)

    1. call for next moderator and note taker (moderator)

      1. Moderator:

      2. Notetaker:

    2. Samvera help follow-up (moderator)

    3. Pull request review (moderator)

      1. Recent Samvera PR list

  4. Post-meeting action (note taker)

    1. After call, this week's notetaker should create the agenda for the next call:

      1. Open template agenda titled "Samvera Tech Call 2023-xx-xx"

      2. Click on ... in the top right corner, and select copy.

      3. Popup will open for location. It should contain:

        1. Space: Samvera

        2. Parent page: 2023

      4. Select copy. New page should be created.

      5. Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish. 


...

Notes

  1. Next maintenance group sprint will focus on dependency updates, specifically bootstrap and rails

    1. September 30-October 11, 2024

    2. Goals are to get rails to 7.2, which matches core components. Chris may be able to help.

    3. Samvera regional meetings are around this time and folks in the developer meet ups could also work on this.

    4. Thomas' colleagues have done bootstrap 4 → 5 upgrades for smaller projects, but not Hyrax yet. Seems to be going smoothly so far

  2. Current maintenance sprint is focused on hyrax-fedora 6

    1. Working through failing specs

    2. Randall fixed pair tree issues, which turned out to be an issue in valkyrie

      1. Chris and Randall have had conversations about pair tree support and whether it is needed

    3. Any updates on Emory’s performance testing?

      1. Still investigating as far as we know.

      2. Performance is slightly better regarding collection types but more testing is needed

  3. Avalon/fedora 6 is working through migrations and testing code this week and next.

  4. Cincinnati is working on upgrading Hyrax from 2.x to 3.x.

    1. Open questions: blocker in sipity, navigating components that are end of life, focus on upgrading or do a fresh install?

    2. These are good topics for the Midwest Regional Meeting unconference sessions

  5. FYI: SAML vulnerability via omniauth was announced

  6. Daniel will address Margaret’s question