For members (TODO: link) of the Open Container Initiative, there is no charge for certification. There is also no charge for non-profit organizations. For commercial organizations that wish to certify but don’t want to become an OCI member, the fee is the same as joining (TODO: link) the OCI.
A community distribution does not have a company behind it. For the purposes of certification, we treat community distributions as non-profit organizations, so there is no charge. However, we do require an individual to complete the certification agreement so that we have an official contact (or multiple contacts) if your software falls out of compliance.
You can certify the currently released version of each spec and the two versions before that. The currently released version is the latest stable tag in each spec repo. Already certified implementations remain certified as long as a newer version is certified at least once a year after the initial certification.
From the bottom of the OCI Distributions & Platforms spreadsheet (TODO: link):
No. If the software is the same, and just the name has changed, you just need to submit a revised Participation Form available at https://github.com/opencontainers/oci-conformance/blob/main/participation-form/OCI_Certified_Form.md that includes the new name. Please also open a pull request to update the name in your PRODUCT.yaml file. We do ask that you send us the new Participation Form prior to announcing the name change. You can submit the pull request after the announcement, if necessary.
Per product. Each separate product (i.e., different product name) from your company requires a different participation form. We don’t need a new form for new versions of an existing product.
Yes. First, we need it in SVG, AI, or EPS format. If you don’t have a product-specific logo, it is fine to reuse your company one. However, we have a set of requirements (TODO: link) including that it incorporate the name of the product or company in English (it’s fine to also include text in other languages) and that the logo not be reversed.
Second, your logo can’t be derivative of or include portions of the OCI logo (TODO: link), in order to preserve the value of the OCI logo. Of course, under the terms of the OCI Certified agreement, you’re welcome and encouraged to use the OCI Certified logo to indicate that your product is OCI Certified.
No. We need the Readme of your conformance submission to contain more detailed directions on how to install and configure your OCI implementation. The reason is that we need your users to be able to replicate the installation so that they can re-run the tests in the same environment and confirm that they get the same conformance results. We’re trying to minimize link rot (i.e., the installation directions moving or changing) and we’re requesting that you include sufficient detail (particularly around flags and permissions) such that an informed user will be able to replicate your results.
When a product fails certification, the issue could be in the implementation or in the conformance tests. We use a tracking issue (TODO: link) to record issues with the tests.
You can, but it requires membership in OCI. Instead, you may be able to accomplish your goal of ensuring conformance simply by running the conformance tests on your private cloud. As long as you pass, your implementation is conformant. It can’t be certified unless you complete the participation form, but certification (and the ability to use the OCI Certified mark) is probably unnecessary for an internal-only product.
Yes. Please email us at email@example.com.