Time: 14:00 - 14:30 PM EDT/11:00 - 11:30 AM PDT

Zoom URL: https://princeton.zoom.us/my/jrgriffiniii

Attendees

• @James Griffin (Princeton University Library)

• @Daniel Pierce (Indiana University)

• @Chris Colvard (Indiana University)

• (Additional attendees to be added)

Discussion Items

• Member Updates

• https://samveraconnect2025.sched.com/

• (Additional items to be added)

Notes

• Presentation for Samvera Connect

  • James will deliver these for tomorrow

    • Request feedback from Slack and request improvements and extensions

  • Daniel and Chris propose a chart

  • Try and address RubyGems/GitHub parallel authorization policies before Samvera Connect

    • Pruning for developers who are not actively contributing in the space

    • Perhaps follow the GitHub permissions?

• Synchronizing these is always going to be a challenge

• It is possible to build and push to RubyGems from GitHub using GitHub Actions

  • (James was thinking of this: https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry )

  • Perhaps this could be explored?

  • Daniel: Then the owner could be one account (e. g. “samvera-community”)

  • Chris: It would be good to reduce

  • James: Action Item

    • GitHub Actions for each Core Component

    • Basic GitHub Actions config. just to prototype integration

      • This way, if this if an additional action is needed, these can be extended

      • Perhaps “tag” could trigger the RubyGems release?

• Ensure that 2FA is enabled for GitHub and RubyGems users

•