/
Samvera Tech Call 2025-02-26

Samvera Tech Call 2025-02-26

Owned by Chris Colvard
Last updated: Feb 26, 2025 by Randall Floyd
2 min read

Meeting Logistics:

Agenda (meeting notes below)

  • Current sprint:

    • Trying to address bugs in Dassie w/Wings on F4 (see notes)

Moderator: @Daniel Pierce

Notetaker: @Randall Floyd

Attendees:

  • you

  • you

  • you!



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: @Randall Floyd

      2. Notetaker: @Daniel Pierce

    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 XXXX-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: 2024

      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. Current sprint:

    • Trying to address bugs in Dassie w/Wings on F4

      • Multiple bugs being caused by FileSets not handled correctly for AF and Valkyrie works in the same Hyrax

      • They are not from the dependency upgrades in main; exists in v5.0.3, not sure how much farther back

      • As Daniel and Heather said, this is why it’s so important to get upgraded and get Wings fully deprecated out of the stack, too many repo/storage scenarios is too costly

      • @Randall Floyd will ping Rob on Slack asking about “Valkyrie Transition mode” to understand it, to see if there’s any help there

    • @Daniel Pierce summarized some findings with billing for our Nurax instances on AWS

      • Cloud Watch is costing us about $150/month, mostly due to heavy log generation and retention

      • Going to set the log levels to be less chatty



Related content