From its inception as Hydra, Samvera has been designed to provide a generalizable, portable framework that would meet the needs not only of the three original institutions, but also those of a wider community. Originating as a multi-institutional project spanning three universities (Hull, Stanford and Virginia), and with support from Fedora Commons, Samvera has since expanded to include like-minded institutions with similar needs, technical infrastructures and complementary systems.
...
Partners sign a formal one page Letter of Agreement (LoA) in support of the formal, legal Memorandum of Understanding (MoU) signed by the Steering Group in April 2012, and each Partner is asked at the time of joining the group to write a brief letter of intent indicating why they want to become a Samvera Partner and what they intend to contribute to the Community. (Note that we post these letters publicly in the wiki.) Partners are also required to file a corporate Contributor License Agreement (see Samvera Community Intellectual Property Licensing and Ownership page) to ensure that the Community can accept code and other intellectual contributions from the Partner institution. A composite document comprising the 2012 MoU, amendments made to it in 2018 to reflect the name change from Hydra to Samvera, a version of the MoU showing the effect of these amendments, and a blank Letter of Agreement can be found here.
...
Electing representatives to the Steering Group
Community maintenance and growth
Collaborative roadmapping (technical & community)
Samvera application development
Governance of, maintenance of and code contribution to the core components
Design contribution: UI's, API's, data models, et al.
Documentation and sharing of contributions, eg. through http://samvera.github.io/
Community infrastructure provisioning & support (Bug trackers, Continuous Integration Servers, Web site, Wiki, etc.)
Maintenance of the official Samvera website
Resource coordination
Recruiting
Communityadvocacy (e.g., public speaking, writing articles)
Participation and leadership in "Interest Groups" and "Working Groups" within the Samvera Community
Meeting organization & planning
Determining Community strategy
...
The current set of Bylaws governing the operation of the Steering Group can be found here.
Samvera Code Development
...
Our code development is overseen and coordinated by a number of groups. The Roadmap Council exists to align the roadmaps of the various Samvera code initiatives where this makes sense. The council comprises the product owners of the core Samvera components and Solution Bundles and of representatives from relevant Interest or Working Groups. The essential elements of the Samvera code are maintained by the Core Components Maintenance Group which is devoted to the ongoing maintenance of identified core components via planned sprints organized in communication with the product owners. Hyrax, the repository toolkit that underpins other solution bundles has two key working groups: one for coordinating development, and another for its roadmap. Our solution bundles (Hyku and Avalon) each have their own development teams responsive to the needs of, and advised by, their users.
...