Samvera Tech Call 2022-04-20

Meeting Logistics:

• Time: 9:00am PDT / Noon EDT

• Zoom Meeting URL: https://princeton.zoom.us/j/7739591625
  (link will launch Zoom client – if you do not have Zoom, expand the instructions below)
  
  

Agenda (meeting notes below)

• Hyrax Maintenance Policy proposal - @Juliet Hardesty

• Request to Review https://github.com/samvera/ldp/pull/136 (@James Griffin)

• CircleCI usage – gathering information to inform our subscription – @Heather Greer Klein

• https://github.com/samvera-labs/active_encode/pull/102

• https://github.com/samvera/questioning_authority/pull/354

• (To be added)

Moderator: @Heather Greer Klein

Notetaker: @James Griffin

Attendees:

• @Juliet Hardesty (Indiana University)

• @Thomas Scherz (University of Cincinnati)

• @Chris Colvard (Indiana University)

• (To be added)

Meeting Process

Notes

• (To be drafted)

• Hyrax Maintenance Policy

  • https://docs.google.com/document/d/1FRRwjk4K3XKJJy58ALTVvLQRpscSWsJTEzzIhvl5ltk/edit#heading=h.6kypcp5ouri7

  • Interested in detailing what it is that is being addressed during Hyrax releases

  • There are going to be two major releases (Blacklight/Bootstrap and Valkyrization, both of which cannot be combined)

    • What is the community supporting? How far back can these go?

  • Data migrations incur a major release

    • This is already the current, standard community practice

  • Path forward for capturing feedback

    • How many versions back should be supported?

    • How are security patches addressed?

    • Hyrax Maintenance WG meeting

    • Partner Meeting on May 2nd addresses this also

      • GitHub issues for addressing outdated Gem versions which are necessary for upgrade

      • Should there be a generic policy for core components?

      • James wants Core Components to provide guidance

      • Hyrax deprecated releases would provide a way of ensuring that community members are not going to be available to actively assist adopters who need to upgrade

• CircleCI Usage Restrictions

  • Heather met with a representative from CircleCI regarding usage by the Samvera Community

  • Starting with March, Samvera usage started to exceed the 80 concurrent job limit

    • This may have been related to the Valkyrization work

    • CircleCI wants to try and move us to the unlimited plan

    • Thursday there is another scheduled meeting

      • Request for attendance

    • Request a trial for CircleCI unlimited

      • If a trial is undertaken, then this should be for the next Hyrax development cycle

    • Annual Cycle

      • Perhaps request these increased resources, one year further might suffice for the required Hyrax cycles

      • Following the completion of these cycles, perhaps it won’t be as necessary

    • History with CircleCI

      • In past events for the Developer Congress, there have been delays for up to 10 minutes

      • This was actually the justification for increasing more of the resources originally

      • Tamsin was involved in the original configuration for CircleCI resources and administration

    • GitHub Actions

      • If CircleCI is becoming cost prohibitive, then perhaps GitHub Actions might provide a more cost-effective alternative

      • Blacklight is currently using GitHub Actions, along with several developers within the community

    •  

• Next Scheduled Samvera Tech Call

  • Moderator: Chris

  • Notetaker: James

Call concluded at 09:30 EDT/12:30 PDT