-
Verify that the list of files matches the expected list.
-
Note the
vX.Y
subdirectory that the PR is in, this is the version of Crossplane 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 Crossplane.
-
Look at
results.log
. Verify that themajor.minor
component of theConformance test version
exactly matches the Conformance Version. The patch version does not matter. -
Verify that the last line of
results.log
saysPASS
. -
Verify that no files outside of the submitted subdirectory are being modified. For example, if a submission is adding files to
v1.2/distribution/coyote/
, ensure that it doesn't changeREADME.md
orv1.2/distribution/roadrunner/
.
- Confirm that the vendor is currently a member of CNCF. If they are not, request that they reach out to [email protected] to become a member in order to complete their certification. (Companies can alternatively pay a certification fee equal to the cost of membership if, for whatever reason, they don't wish to become a CNCF member.) Alternatively, non-profit organizations (including community distributions like Debian) can certify at no cost.
Review the 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
name
andwebsite_url
are listed in the "Qualifying Offerings" section of the vendor's Participation Form, i.e. that thename
andwebsite_url
are listed.
If the submission doesn't meet all policy requirements, reply with a message indicating "Signed participation form needed", "Files missing from PR", "Membership in CNCF or confirmation of non-profit status needed", etc.
- Add a comment saying "You are now Certified Crossplane" and merge the PR.