The samvera-labs Github repository is for Samvera Experiments, Works-in-progress, and Beta versions of gems and apps. Projects here may be suitable for production use, but awaiting broader adoption.
Requirements for creating a project
The samvera-labs repository is meant to be a true lab, and experimentation is to be encouraged as much as possible. The committers may accept any any contributions to samvera-labs by any Samvera Licensed Contributors wishing to offer their work.
Guidelines for Promotion to Samvera from Labs
You may utilize this template to display how your repository meets each criteria
To move from samvera-labs to the core samvera code organization, the following requirements must be met:
Code must be released at version >= 1.0
Good unit test coverage measured by community (e.g. 100% or 75% of what’s important)
uses CI (Preferably CircleCI, unless there is a compelling reason to do something else)
uses Coverage tool (coveralls or simplecov)
Show compatibility with current Rails versions and other dependencies, when was it last tested; note compatibility with prior versions when available. Compatibility can be specified in the gemspec(s) or verified via CI matrix.
How/Who to contact for help -> push out to all gems like CONTRIBUTING.md
Known issues documented in github Issues tickets (not just listed in text)
Tutorial / Walkthrough / Example usage
Resolve TODO items in documents and remove them
All Contributors should have signed Hydra Contibutor License Agreement (CLA)
Community use by three or more institutions
In active use for six months
Has an ongoing maintenance plan.
Mechanism for Promotion
As needed or requested, code repositories are reviewed for promotion / deprecation. To start this process, email the Samvera Tech list with a request. Provide documentation that all of the above requirements have been met. Ask for a spot on the next developer’s call to discuss the issue. Once the promotion has been decided, another email should go out to the list with an announcement.