Versions Compared

Old Version 1

changes.mady.by.user Bradley Watson

Saved on

compared with

New Version 2

changes.mady.by.user Chris Colvard

Saved on

Key

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

...

...

Notetaker: Chris Colvard

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. Core Components support for Rails 7.2 / Ruby 3.3

    1. Jonathan Rochkind merged PRs for questioning authority and browse-everything

    2. Trey merged a PR for Rails 7.1 support in hydra-derivatives

    3. Also existing PRs for Rails 7.1 merged for active_fedora and hydra-head

    4. Chris and Avalon team are working on PRs for Rails 7.2 support in active_fedora, hydra-head, noid_rails, and other gems used by Avalon

    5. When cutting new releases check that rubygems two-factor is enabled

  2. Avalon is continuing work on moving to Fedora 6 with ActiveFedora

    1. Where best to store the code to be accessible and not break things?

      1. has been in maintenance mode for a while

      2. major breaking change would be fine if cutting new major release

      3. wait until after release for Rails 7.2 / Ruby 3.3 support

      4. Future Fedora 4 releases could come as minor/patch releases cut off of branch

  3. Emory - performance testing non-pair-tree Fedora storage

    1. loading a bunch of things and then testing performance

    2. increasing size of test: 100,000 file sets → 1,000,000

    3. looking to see if okay to proceed without pair-tree since project doesn't want to wait

  4. Daniel - looking into failures in sirenia possibly due to valkyrie inverse member lookup (when in pair-tree mode)

  5. Next call: 8/29/2024

    1. Moderator: rob

    2. Notetaking: Daniel