Meeting Notes from 06/30/25

Meeting Notes from 06/30/25

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)

  • @Heather Greer Klein (Samvera Community)

  • @Daniel Pierce (Indiana University)

  • @Chris Colvard (Indiana University)

  • @Shana Moore (Notch8)

 

Discussion Items

  • Member Updates

  • Samvera GitHub Organization

    • Auditing Owners and GitHub Permissions/Privileges/Authorizations for Samvera Organizations

    • Explore for actionable, iterative work for the next meeting?

      • Who should and should not have the Owner level of permission

      • Samvera Board can be consulted

        • Offer options:

          • Here are the roles which are currently offered, and here are the past practices

          • How best to identify the appropriate roles moving forward?

      • Heather requires documentation in order to advance this

      • We currently have a legacy setup with Members and Owners

        • Next Partners meeting: 07/10

        • Next Board meeting: 07/18

      • Can we develop a small framework by the next Partners Meeting?

        • Try and deliver this before the 07/10

  • RubyGems Permissions

    • Can we request guidance from the Board simultaneously?

    • Heather does not object

    • Can these authorizations be synchronized?

      • Perhaps enquire with other open source communities?

      • How often authorizations should be audited?

      • Blacklight is not very well structured about these types of permissions

      • James can look to enquire with members of DSpace

    • James can work in parallel on RubyGems permissions

    • Managing Gem Releases

      • Perhaps using GitHub Actions for releases instead of RubyGems?

      • For now, should still definitely audit RubyGems permissions, but should not rule out GitHub Actions for future possible releases

  • Any Other Topics before the next Partners or Board Meeting?

    • Referencing the Charter…

    • Rubric for identifying Core Components as candidates for deprecation

      • Perhaps wait for the survey?

      • Discuss the rubric at the next meeting of this Group

  • (Please add additional items)