/
Samvera Tech Call 2021-01-13

Samvera Tech Call 2021-01-13

Apr 14, 2021

Meeting Logistics:

Agenda

(meeting notes below)



Moderator: @tamsin johnson

Notetaker: @Chris Colvard (Deactivated)

Attendees:

  • @Jeremy Friesen (Notre Dame)

  • @Collin Brittle (Emory)

  • @Chris Colvard (Deactivated) (Ubiquity Press)

  • @Juliet Hardesty

  • @tamsin johnson (UC Santa Barbara)

  • @Lynette Rayle (Cornell)

  • Anna Headley (Princeton)

  • @Rob Kaufman (Notch8)

  • you!



Meeting Process

  1. Standing pre-agenda items (moderator)

    1. Welcome

      • "Welcome everyone, please add your name to the Attendees list.  If you are unable to do so, please let us know, and someone will add you. To any newcomers, Welcome, and please feel free to ask questions. Likewise for all attendees. We strive for an open and accessible conversation around Samvera technology."

    2. Call for new agenda items

  2. Follow Agenda from above (facilitated by moderator) and record notes in Notes section below (note taker)

  3. Standing post-agenda items (moderator)

    1. call for next moderator and note taker (moderator)

      1. Moderator:

      2. Notetaker:

    2. Samvera help follow-up (moderator)

    3. Pull request review (moderator)

  4. Post-meeting action (note taker)

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

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

      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. 



Notes

  • Is it time to move on from GitHub?

    • Samvera has used GitHub for many years

    • GitHub corporate practices have caused times to pause and think about continued use of GitHub:

    • Jeremy has written to helpers channel about this conversation and how it appears to run counter to community values

    • How to make voice heard?

      • Email GitHub as an individual

      • Ask your institution to talk with GitHub

      • Voices at all levels will help bring accountability

    • What do we do as a community?

      • Bring it to partners

        • Get community to talk to GitHub

        • What does with mean with respect to Code of Conduct?

        • Next partner call is February 12th

      • What should developers recommend we do?

    • What alternatives exist?

      • GitLab

      • Codeberg

    • How do we do due diligence on what we'd move to?

    • Is there anything that GitHub could do that would make us not want to move?

    • Working group to explore this and provide messaging to help bring community along with process

      • Similar to Branch Renaming WG

    • Jeremy will send an email to Samvera email lists; will not write up WG charter

  • Hyrax 3.0.0 rc3 and release plans

    • Version bump merged yesterday

    • Release will be cut shortly

    • 1-2 weeks for testing

    • If all looks good then it will be Hyrax 3.0.

    • Nurax?  QA Process?

      • Will try to deploy somewhere for testing

      • Not full QA process but at least a quick test of things already fixed

  • StaleBot

    • Will be discussed over email or next tech call

  • Next meeting in 2 weeks:

    • Moderator: @Lynette Rayle

    • Notetaker: @tamsin johnson