-
Notifications
You must be signed in to change notification settings - Fork 76
Contributing guide
Michael Baentsch edited this page Jan 22, 2021
·
1 revision
All submissions must meet acceptance criteria given below. Demos may be removed if they no longer meet the acceptance criteria.
- Purpose of integration and upstream (code origin) location must be clearly documented.
- README must contain all steps to build the OQS-enabled code.
- An optional USAGE file must be present if the integration can be built into a docker image.
- If possible, a Dockerfile should be provided such as to automate the integration completely. In this case, a separate USAGE file must be available that shall document usage of the docker file at docker hub.
- If a docker file is provided, it is expected that build-and-test code is added to the continuous integration environment testing (see CCI config).
We hope the contributor will intend to help update the integration over time as the upstream code bases as well as the underlying algorithms and APIs evolve.