2022-02-11 Partner Call

Facilitator: @Heather Greer Klein

Note Taker: @Esmé Cowles

Recording: https://samvera.atlassian.net/l/c/v1E0o87h

Attendees

• @Esmé Cowles

• @Rosalyn Metz

• @Jim Halliday

• @Rick Johnson

• @Robin Lindley Ruggaber

• @Margaret Mellinger

• @Jon Dunn

• @Karen Cariani

• @Tim Lepczyk

• @Rachel Lynn

• @Brian McBride

• @Nora Zimmerman

• @Harriett Green

• @Thomas Scherz

• @Chris Awre

• @Kevin Kochanski

• @Nabeela Jaffer

• @Alicia Morris

Agenda & Notes

1. Any other items for the agenda? 
   
   

2. Hyrax Update – @Juliet Hardesty

   1. Julie’s presentation is being recorded

   2. Hyrax this year

      1. Developer Congress in January, coinciding with first Hyrax Maintenance WG sprint, which worked out well. Major work on Hyrax Valkyrization and Bootstrap/Blacklight upgrade (both are not completely finished, but good progress was made). Both of these would be good things to work on to meet your pledge hours. Infrastructure update work (e.g., making releases, publishing Helm charts) and getting Docker setup working on M1 Macs. Released Hyrax 3.3.0, including analytics work.

      2. Hyrax Maintenance WG: schedule will continue (two weeks on, two weeks off, regardless of holidays, etc.). Three cycles (Jan-Apr, May-Aug, Sep-Dec). Pledges are open, the more upfront pledges, the better the planning can be. Happy to schedule pledged work as needed to meet what people can contribute. Whole-cycle contributors are Jessica Hilt (UCSD), Rebekah Kati (UNC), Daniel Pierce (Indiana), and Tao Zhao (Federal Reserve Bank of Minneapolis) (thank you!). Adam Arling and Mat Jordan from Northwestern completed their pledged hours during the Dev Congress. University of Michigan has scheduled their pledged hours as two developers joining the next Maintenance WG sprint.

      3. Remaining major areas of work: Blacklight/Bootstrap/Rails upgrade (need to complete ASAP because current version of Rails is EOL this summer), Hyrax Valkyrization (scheduled for March 7-18, Lynette is organizing this sprint with Princeton developers, WG will do feature testing in advance to establish issues to work on). There are also 387 other open issues, some triage/verification work before most of these are workable.

      4. Challenges as Hyrax PO:

         1. not having a tech lead (releases are hard, worried about losing track of who’s working on what, how things fit together)

         2. pledges are working, but doesn’t necessarily completing things, so need to figure out how to get pledged hours to get things completed

         3. Julie is stepping down from PO this fall, want next PO identified by this summer (important to have this roll over and have time to transition to another person)

      5. Joys of being Hyrax PO:

         1. Samvera is an amazing community: there’s always someone who can help, and does help

         2. Learning experience about how different institutions use Hyrax, being confident enough to own the role

         3. More comfortable working with and talking about Hyrax

         4. Feel like Hyrax is worth the effort

   3. Links:

      1. Samvera Developer Congress, January 2022 Project Board - https://github.com/orgs/samvera/projects/8
         Samvera Pledge Drive - 2022 Samvera Technology Maintenance Hours Pledge Drive
         Hyrax Maintenance Working Group - Hyrax Maintenance Working Group
         Blacklight upgrade remaining work - Add support for Blacklight 7 · Issue #3271 · samvera/hyrax
         Bootstrap upgrade remaining work - Support Bootstrap 4 · Issue #5276 · samvera/hyrax
         Hyrax-Valkyrization Developer Congress, March 7-18 - Hyrax-Valkyrization Community Effort - March 7-18, 2022
         Hyrax Maintenance Working Group current project board - https://github.com/samvera/hyrax/projects/25

   4. Hyrax tech lead position: Samvera Board will spend time considering how to make this position more sustainable going forward

   5. Alberto (COLMEX): concerned about language barrier, and would like a roadmap to guide our developers in their work? The project board is probably the best place to look: https://github.com/samvera/hyrax/projects/25 . Happy to talk over email to help figure things out.

3. Other Updates:

   1. Proposed bylaw changes vote reminder – closes February 14th; ballots sent to Partner primary contacts

   2. Maintenance pledge work

      1. Going well, would be a good place to devote any developer effort you’d like to contribute (to Hyrax or other parts of the codebase)

   3. Save the date for Virtual Connect 2022 (May 4 - 5) and Spring virtual Partner Meeting (May 2 - 3) Partner meeting unordered agenda

      1. No May partner call on the usual date/time (second Friday/May 13th)

      2. Call for Virtual Connect program committee: sign up here

   4. Sign up for 2022 Partner call demos

   5. Sign up to join the Hyrax-Valkyrization Community Effort - March 7-18, 2022

      1. This work has been ongoing for a long time, but we hope this focused work will make significant progress to bring this to completion
         
         

4. Anything for the Samvera Board? (Standing item)
   
   

5. Date of next call: March 11th, 2022
   
   

6. Notetaker for next call: