...
...
...
Draft proposal, until agreed on and joined by members from at least three Samvera Partners.
Scope & Objectives
Community members who work on Hyrax development and maintenance have identified several chronic issues that must be addressed to protect both Hyrax community code and those who dedicate time and energy to maintaining it:
A perception that contributing fixes upstream to Hyrax community code is difficult and time-consuming
A lack of support by local institutional leadership for turning local fixes into community code
A large and complex codebase seeing a decline in contributors
A history of burnout amongst Community members who take on technical leadership roles
This group will develop deliverables to address these issues from several angles including new and increased community engagement strategies; recommended best practices, commitments, and actions for Partners; training and development opportunities for the Community; and recommendations for ways to better care for Community-based technical leadership.
Deliverables & Timeframe
The group should produce the following deliverables by the beginning of Samvera Connect, October 2021:
A process and schedule for multiple Development Congresses to be held at regular intervals every
...
year – completed by April 1, 2021
New contributor support practices, including new practices for highlighting successful contributions and contributors and regular opportunities for new contributor
...
support – completed by May 1, 2021
An evaluation of current contribution culture strengths and
...
weaknesses – completed by June 1, 2021
A set of recommendations to Partners based on the above work, including but not limited to recommendations for practices and actions that require commitment from the institutional leadership
...
level – completed by August 1, 2021
The group will present their work at Samvera Connect 2021 and sunset after that presentation.
Meeting Times & Communication Channels
Note that following current best practices within Samvera, interest and working groups should use an existing communication channel unless and until it becomes clear that a dedicated channel is needed. This section should specify which existing channel(s) will be used: e.g., samvera-tech, samvera-partners, samvera-community@googlegroups.com. When using a shared channel, individual working groups should start the subject line with their name in []s, such as [archives] for the Archives Working Group. If and when a dedicated channel is needed, the new channel should be well publicized and open to any interested subscribers/participants in the community. Meeting link: https://emory.zoom.us/j/97449753231?pwd=NXZMcWNoMlFISnhuS2dXWjh2Zys5dz09
Meetings are held every other Tuesday at 8AM PT/11AM ET/4PM CET.
Special topic meetings related to Challenges for Developer Participation in Samvera Code Implementation
May 25th topic: one-off contributions
June 8th topic: targeted work in groups
June 22th topic: maintenance work
Meeting agendas and notes
| Child pages (Children Display) | ||||
|---|---|---|---|---|
|
Members
Note that Working Groups must have participants from three different Partners. All members of a working group producing software must be licensed Samvera contributors covered by the appropriate CLAs. Other types of contributions such as requirements, design, best practices, documentation, etc. - do not require CLAs but participants should accept that the materials to which they contribute may be released under a Creative Commons Attribution 4.0 International License..
Heather Greer Klein, facilitator, Samvera
Jeremy Friesen (Notre Dame)
Lynette Rayle (Cornell)
Juliet Hardesty (Indiana University)
your name here (your institution here)
Resources
Meeting Notes
- list of links
- or table of meeting notes