Samvera Tech Call 2020-07-29

How to connect: https://notredame.zoom.us/j/94030214208 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)

Time: 9:00am PDT / Noon EDT

Moderator: @Jeremy Friesen(University of Notre Dame)

Notetaker: @James Griffin (Princeton University Library)

Attendees:

• @Collin Brittle (Emory)

• @Jeremy Friesen (Notre Dame)

• @Chris Colvard (Deactivated) (Ubiquity Press)

• @tamsin woo (UC Santa Barbara)

• @Lynette Rayle (Cornell University)

Agenda

1. Roll call by timezone per following order - ensure notetaker is present (moderator)

   1. folks outside North and South America

   2. Eastern timezone

   3. Central timezone

   4. Mountain timezone

   5. Pacific timezone

   6. folks who were missed or who dialed in during roll call

   7. Remind everyone to sign in on agenda.

   8. Welcome all newcomers!

2. Agenda (moderator)

   1. Call for new agenda items (moderator)

   2. Hyrax tags, all 300+ of them. How can we wrangle with this? @Jeremy Friesen

   3. <add open agenda items here>

   4. Samvera help follow-up

   5. Pull request review

3. Moderator & notetaker for next time

   1. Moderator:

   2. Notetaker:

4. After call, this week's notetaker should create the agenda for the next call:

   1. Open template agenda titled "Samvera Tech Call 2020-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: 2020

   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.

5. PR Review

   1. Review issues:

   2. PR review coordinator for next time: 

Notes

• Hyrax GitHub Repository Tags

  • Quite a number of Tags exist

  • Tag cleanup requires coordination from the community

    • Perhaps this could be proposed as a Dev. Congress activity?

    • There is effort involved in squashing Tags which needs to be considered

  • There are collisions between version numbers for Hyrax and Sufia in the past

    • Perhaps remove Tags from Sufia which are invalid now (as they don't reference any Hyrax releases)

    • There would be a way through RubyGems to find all of the Hyrax-referencing Tags

    • Scripting against the API might support querying this and doing this in batch

  • Is it possible to limit push Tag permissions in GitHub?

    • Tom could not find any setting for this

    • It might not be realistic to assume that we can purge these Tags continuously without restricting the ability for contributors to push Tags

    • Perhaps engage with contributors and ask them to delete any existing `git checkouts`, as the Tags can be pushed

    • Hence, we would need to restrict `git push` rights for a small number of contributors

  • GitHub Actions does provide a hook for tagging

    • Maybe there is some automation here?

  • Clarification: It's people's `git push` behavior which leads to these problems

  • Maintainers have deleted Tags, and they have reappeared

    • Perhaps there is some way of listening for new pushes with Tags, and intercepting this

  • GitHub Tag Collisions

    • If Alice and Bob both push with the same Tag name, how is this conflict resolved?

    • If the person minting a Hyrax version needs to perform Tag cleanup locally, then that new version Tag won't be getting obliterated is the desirable behavior

  • Tag Confusion

    • People think that 2.5.2 is a Tag which doesn't reference a valid release

      • This did not even come from the Sufia merge

  • Annotated Tags

    • These are full commits associated with the Tag

    • Does `rake release` include this functionality?

      • Tom did perform a `rake release` with an annotation and with signing the Tag

      • This should be a strongly recommended practice

  • GitHub Actions

    • Can we, through Actions and RubyGems API, clean up on `git push`?

    • Concern: It would be preferred to explore supporting this in CircleCI, as otherwise GitHub Actions would conflate multiple CI platforms

  • Generating a list of the Tags which we've generated from RubyGems

    • This would provide us with a means of providing a chronology between the Tags and the releases

  • We definitely need a document describing the release process

    • If Tag annotations are going to be supported, we should no longer use `rake release`

    • We should still explore whether or not `rake release` supports annotating Tags

    • Those releasing should also sign each release

  • Plans

    • Carry on, when you release, if there is a Tag in the way, this gets clear

    • Future practice: When a collision occurs, bump the Hyrax patch version, and start with a clean slate

      • People are still going to be confused regarding which Tags reference valid releases

      • If this is a small, restricted group of people getting confused, then perhaps this could just be added to the README

        • This could be a warning with a list of the releases from RubyGems

  • Action Items

    • Jeremy volunteers to provide a PR for improving the README discussing points of potential confusion with regards to Tagging

    • Tom volunteers to provide instructions for releasing Gems and improve the README

      • This will include the expectation that releases should be signed

    • Releases Page

      • Releases appear to be valid after 1.0.5

      • Scrolling after January 2015, there are problematic releases

    • Jeremy will request a review from Lynette in order to ensure that questions related to working directly off of Tags are addressed

• Community Manager Position

  • (Please check Slack for an update on the process of the Community Manager interview process)

• Next Scheduled Tech. Call

  • Moderator: Chris Colvard

  • Notetaker: Lynette Rayle

• Call concluded at 09:31 PDT/12:31 EDT