.png?version=1&modificationDate=1629919347853&cacheVersion=1&api=v2&width=510)
.png?version=1&modificationDate=1629919347853&cacheVersion=1&api=v2&width=453)
| Table of Contents | ||||
|---|---|---|---|---|
|
Common Questions
Who will be determining what maintenance work is done?
Pledged hours will inform priorities for all the Community groups responsible for maintenance, including:
The Core Components Maintenance Working Group
The Hyrax Maintenance Working Group
The Avalon User Group
The Hyku Development Group
Any other groups that form to prioritize documentation and/or training needs
In addition, the Roadmap Alignment Group will work with all these groups to coordinate cross-technology priorities and planning for updates that impact more than one codebase.
Will developers have a say in what they work on?
Absolutely! Developers will work collectively, with and within the Maintenance Groups to determine how best they can contribute based on their skills and interests and the maintenance priorities.
Are Partners required to contribute?
Pledging is completely voluntary and open to any institution that has or wants to implement Samvera technologies. It would be excellent to see all Partners pledge to contribute to maintaining the software that is so important to all of us.
Is there a minimum or maximum number of hours to pledge?
There is no minimum or maximum number of hours expected, and no expectation that anThe Samvera Community is asking Partners, adopters, and all users of Samvera technology to commit to technical maintenance in 2022.
The Samvera Community is asking Partners, adopters, and all users of Samvera technology to commit to technical maintenance in 2022.
| Tip |
|---|
If 40 institutions each pledge 20 hours to support Samvera maintenance for 2022, we will exceed our goal! |
Predictable maintenance commitments will allow for better and more efficient planning across all Samvera technologies. It will allow both Community maintenance groups to prioritize and plan their work, and present is an opportunity for developers at all levels to contribute to the maintenance of code, documentation, and training materials across all technologies: Avalon, Hyku, Hyrax, Samvera Core Components, and Valkyrie.
How This Commitment Works
Maintenance will be planned and scheduled within three timeframes:
Section 1 (January 1 - April 30, 2022)
Section 2 (May 1 - August 31, 2022)
Section 3 (September 1 - December 31, 2022)
Institutional decision-makers and individual contributors can pledge any number of developer hours within any Section of 2022.
There is no minimum or maximum number of hours expected, and no expectation that an institution can contribute to every Section. Plan to allocate staff time in the Section(s) that are best for your organization.
Developers at any level are welcome, as is anyone who can contribute to technical documentation and/or technology training.
Providing this commitment well ahead of time will ensure that institutions, developers, and the Community know who will be available to contribute to maintenance work, for how long, and when the work will occur.
How to Pledge:
Determine the number of developer hours your institution, organization, or yourself as an individual contributor can commit in each Section of 2022.
Determine who will fulfill the hours. Committed hours can be assigned to any developer(s) at any level, as long as they are willing to contribute to code maintenance, training, and/or documentation.
Select from three scheduling options for the hours of each individual developer who will be contributing to maintenance:
Maintenance Working Group option: An individual is committed at .5 or .25 FTE (320 hours or 160 hours), scheduled in 2 week sprints (2 weeks on, 2 weeks off), for a full four month Section.
Sprint option: An individual is committed at 1 or .5 FTE for 2 weeks (80 or 40 hours), coinciding with Maintenance Working Group sprint(s) in a given Section. Individuals new to the Community should plan to also participate in Onboarding and Orientation, which will be scheduled for the beginning of each Section.
Flexible Hours option: A developer will contribute for a set number of hours in a Section (every Monday, two afternoons per week, etc.) to work independently on maintenance tasks in coordination with maintenance groups (this could be work on training, documentation, PR review, bug fixes, etc).
Fill out this form to register your contributions:
If you have any questions please reach out to Heather Greer Klein, Samvera Community Manager, on Slack or heather@samvera.org.