SB monthly call 17th December 2021
Invitees
Carolyn Caizzi (Chair)
Esmé Cowles (Chair-elect)
Hannah Frost
Harriett Green
Nabeela Jaffer
Brian McBride
Rosalyn Metz
Alicia Morris
Simeon Warner
Ex-officio
Heather Greer Klein
Agenda
New Partner letter of intent - El Colegio de México
Unanimous passed vote to welcome as a new Partner. Carolyn will reach out with welcome and Partner agreement.
Repository Management survey results
Indicated high interest in trainings for Samvera Tech 101, Samvera-specific GitHub overview, outside Product Owner training, and Samvera Documentation workshop.
Will pursue the trainings for 2022 and advertise the channel
Should rename to repurpose the repo-mangement channel for use in these trainings
trainings could stimulate a cohort feeling for this part of the community’s work
Heather will follow up in the Community and bring more detailed proposals
Technical coordinator role update and discussion of proposed next steps
Roadmap Alignment Group discussed the document created by the Board subgroup. There was a question/confusion about the. difference between a Hyrax tech lead and a Samvera tech lead as there is an evident need for a Hyrax tech lead. Detailed notes are here.Asked about the difference between Hyrax tech lead and a tech coordinator role. Clear that the Hyrax role had expanded to fill the void of a tech coordinator role. Could a 1-2 year term position in the hyrax role be helpful?
The list is broad and makes sense for a higher level role
Previous conversations about a long term role vs a short term role
Hard to think about a tech coordinator without a Hyrax tech lead, for many in the community
We also have a more concrete notion of the Hyrax role and know we need it – and Hyrax is the basis for Hyku, and potentially for Avalon soon. Hard to sell overall tech coordinator to those who feel Hyrax is in need of a lead
Hard to do and to envision tech coordinator without the Hyrax role. Could grow a Hyrax lead into a tech coordinator role.
Agreement that we present a recommendation to Partners
If the community paid for half time of a partner staff member, that could be the most efficient approach. There are established processes to treat it like a grant. It would be easier to manage as things evolve, and if it doesn’t work out. If we reimburse it is clear that the community priorities would be implemented.
Carolyn and Heather will talk about this in January, how to fund a tech lead as part of a partner institution.
Automated CLA checking progress
Approved, heather and Esme will implement and update the Community
Forum on the report ”The Effectiveness and Durability of Digital Preservation and Curation Systems” (to be released this week) in which Samvera participated
Status checks
Board retreat agenda review
Updating the bylaws – finalize and schedule vote
Dev Congress
Pledge hours for Jan-April 2022
Wings work
Partner contributions
27 paid ($183,125)
2 still to pay ($11,000) both in process
Roadmaps Alignment Group (regular status check)
Want a community review and audit of the Samvera and Samvera Labs teams. Make sure that settings are applied properly, and that those who are no longer members of the community are not IDed as gem owners, etc.
Need to clarify who has access and who to contact to push to Ruby gems and to do releases
Will recommend that Admins must have 2FA enabled
Will notify the community and do this organization discussion and implementation during the next Dev congress.
Misc
Samvera Holiday Card and text – last year sent to Partners list and to Partner institution leadership, then to Community and tech lists
Heather on vacation December 20-27, December 31, January 6-7
Items for next Partner call:
Date of next meeting: Board retreat January 24-25