Verify that the list of files matches the expected list.
$spec/vX.Y subdirectory that the PR is in, this is the spec and
version of OCI for which conformance is being claimed, referenced as the
“Conformance Version” from hereon.
Verify that the Conformance Version is the current or previous two versions of the OCI spec.
report.html. Verify that the
major.minor version defined
in the report summary both exactly match the Conformance Version.
The patch version does not matter.
report.html. Verify that the summary contains the text “All tests passed”.
PRODUCT.yaml file, and:
Verify that there is a Participation Form on file for the
vendor, and that
the vendor is in good standing in the program.
Verify the product
website_url are listed in the
“Qualifying Offerings” section of the vendor’s Participation Form, i.e. that
website_url are listed.
name. The name should not contain the term “OCI”.
If the submission doesn’t meet all policy requirements, reply with a message indicating “Signed participation form needed”, “Files missing from PR”, “Membership in OCI or confirmation of non-profit status needed”, etc.
Update the OCI Distributions & Platforms spreadsheet (TODO: link) to reflect the vendor’s certified offering.
Add the vendor’s information to the OCI landscape (TODO: link), which also causes them to appear on (TODO: link) and (TODO: link).
Add a comment saying “You are now OCI Certified” and merge the PR.