-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promote Bulkrax to Samvera #876
Comments
Closed
@orangewolf There are a few of these im not sure about when it comes to being complete. We're trying to get most of these checked and verified, but could use some support on the last few. |
This project uses github actions to run both continuous integrations and coverage tools. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are working on promoting Bulkrax out of Samvera-Labs and into Samvera. There is a checklist found here: Promoting From Samvera Labs
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
Hierarchy of promises asserted in clearly defined acceptance tests
Documentation Checklist
LICENSE file, Apache 2 (or compatible)
README.md
Statement of purpose
Basic install steps
Identify any volatile/experimental features
How to contribute -> CONTRIBUTING.md
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)
Use Requirements
Community use by three or more institutions
In active use for six months
Has an ongoing maintenance plan.
The text was updated successfully, but these errors were encountered: