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.
...
Community Structure and Responsibilities
Adopters
Samvera is committed to free and open source software. Adopters are members of the Samvera Community who use the software. The Community would not be what it is without adopters. Adoption, and all kinds of contributions big and small, can build toward Partnership.
Partnership
Samvera Partners are institutions, corporations or other groups that have formally committed to contributing to the Samvera Community. Samvera Partners collectively advance the project and the Community for the benefit of all participants.
...
Electing representatives to the Steering Group Samvera Board
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
Recruitment
Community advocacy (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
...