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)

• @Chris Colvard (Princeton University Library)

Discussion Items

• Member Updates

  • James: Request to assist with any Pull Request Reviews

  • Daniel and Chris: Nothing is blocked for the GitHub Reorg

  • Next: RubyGems

  • James: Proposes generating a report from the RubyGems API

  • Moving RubyGem pushes to GitHub Actions and thus use GitHub Permissions

    • Setting up a new workflow

    • A list of Core Components would be needed

    • Scoped

  • James: Proposes a GitHub GraphQL API report for auditing GitHub Permissions

  • Daniel and Chris defined the new GitHub Roles

    • Started already adding persons to the Contributors Team

    • But the reorg did achieve the main task of reducing the number of users with Organizational admin privileges (ensured that those who could delete Orgs and Repos)

• Reviewing the Charter

  • Develop a process for tagging, communicating about, and closing long-standing issues and pull request; this includes a proposed window in which issues and pull requests should be marked as stale and undergo evaluation for being closed

    • James can volunteer to look to try and advance this

    • Review the notes from the Samvera Community discussions in Princeton, NJ

      • James can link to the notes here

    • Defining how long PRs should stay open? Propose standard timeframes?

      • Lifecycle automation for communication piece

        • Otherwise, PRs can sit open for too long

      • Perhaps GitHub bots for moving things along?

    • Documentation and policy proposal would be the first step

    •  

  • Create a rubric for identifying core components as candidates for deprecation; this includes explanations for how each data point in the rubric is factored in and should be evaluated

    • Rubric already existed, was reviewed, and consensus was achieved

  • A system for evaluating gem ownership and GitHub permissions so that authors can be onboarded and offboarded smoothly as membership changes

    • GitHub Permissions is completed

    • Core Components in rubygems will have owners removed except for a Samvera service rubygems account.  A gem publishing github action will be setup using rubygem's "trusted publisher" feature.  This workflow will be triggered when version tags are pushed and will require the approval within github of one of the tech leads (as part of a core publishing team) or users added by the tech lead to a publishing github team specific to that gem.

    • Daniel and Chris worked through a proof-of-concept

      • Testing the following of documented tasks for a Gem which is not released as often

• Samvera Maintenance

  • CircleCI Updates

    • Samvera Community is no longer using a paid plan

    • There is still a longer term plan to move off of CircleCI

      • CircleCI Orb is no longer actively maintained

    • Hyrax and Hyku have already moved to GitHub Actions

• Meeting adjourned at 14:24 EDT

Notes