Samvera Tech Call 2025-12-03

Samvera Tech Call 2025-12-03


Meeting Logistics:

Agenda (meeting notes below)

  • @Mark Bussey needs a re-review of a Hyku PR because he didn’t merge it fast enough after review & approval. What’s the convention for merging PRs after they’ve been approved? Example PRs below:

  • Github Roles and RubyGems Trusted Publisher proposals from WG (@Chris Colvard and @Daniel Pierce)

  • Community Sprint update - folks are joining the tech call and will stay on to give updates.

  • outstanding PRs/slack support

  • notetaker/moderator volunteer

Moderator: @Shana Moore

Notetaker: @Mark Bussey

Attendees:

  • @Juliet Hardesty

  • @Nicholas Mark Homenda

  • @Chris Colvard

  • @Daniel Pierce

  • @Sarah Cogley

  • @Tracy McCormick

  • @Bradley Watson

  • @Eleni Castro

  • @Randall Floyd

  • @Praneeth Byna

  • @Rebekah Kati

  • @Nic Don Stanton-Roark


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 XXXX-XX-XX"

      2. Click on ... in the top right corner, and select “Duplicate”.

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

        1. Space: Samvera

        2. Parent page: (Verify value is current year)

      4. Select “Duplicate”. New page should be created.

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




Notes

  • PR Merge Process -

    • Submitter should generally shepherd their PRs through and may merge their own PR once approved

    • Approver can merge after approval (if tests are complete)

    • Tech Call should review for outstanding approved PRs when time permits

    • Rob Kaufman agrees that we should align with Hyrax - Hyku approvers should also merge PRs

 

  • Github Roles & RubyGems trusted publisher

    • Github

      • Proposal from Working Group: See #4 in notes for 2025-11-13 Partner Call
        Summary: restrict owner role in repos to a fairly short group of people, require secure 2-factor for all users

      • WG will circulate proposal via slack & e-mail with a review and comment

      • Any users losing access will be notified

      • Timeline: TBD

    • RubyGems

      • PROPOSAL: Set up github action to publish new releases to rubygems (as a trusted publisher), potentially on events like new version tag being minted in Github.

      • TODO: Set up workflow in core components

      • EXAMPLE GEM: Hyrax IIIF AV

      • Feedback & Questions: Join the #github-processes-and-permissions-wg Github Processes and Permissions Working Group Charter

 

  • Moderator: @Daniel Pierce

  • Notetaker: @Randall Floyd