Samvera Tech Call 2021-01-06

Owned by Jeremy Friesen
Last updated: Jan 06, 2021 by Chris Colvard (Deactivated)
2 min read

Meeting Logistics:

Agenda

(meeting notes below)

  • <add your agenda item here (your name)>


Moderator: tamsin woo

Notetaker: Chris Colvard (Deactivated)

Attendees:


Meeting Process

 Moderator and Note Taker - click to see 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

(2020-12-18 - This is Jeremy Friesen, I won't be here for the tech call, but feel free to assign me to either moderator or note taker for the Jan 13th call)

  • Hyrax 3.0 release plans
    • Release of 3.0RC3 blocked by not having a deploy environment for testing (nurax)
    • No code blockers right now
    • Open items in Hyrax WG project board can be worked on during RC3 review process and either be fed into a RC4 or a post 3.0 bug fix release

    • Release process: cut RC3, wait 2 weeks for feedback, then cut official if no issues

    • Should 3.0 release should be done before Hyrax WG starts up again? (First sprint starts on 1/25/21)

      • Tom - I don't think it is a requirement

      • Possible first topics for WG:
        • QA: verify old bugs/issues
        • Devs: engage in permissions work being done by hyku
    • GlobalID changes wait until 3.1? Tom thinks yes for safety since there isn't a deploy yet
    • Upgrade won't be too hard: db:migrate will need to be run and the UV install process has changed
  • How are we going to test hyrax?
    • Nurax out of date and needs to be updated with latest
    • Conversation started at end of last year about future of nurax and Continuous Deployment (CD) of Hyrax
    • Not a huge rush but would be good to have soon
    • Nurax discussion continuing in nurax channel on slack with Mark, Max, and Heather