- 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 CNTI Certification for which certified is being claimed, referenced as the "Certification Version" from hereon.
- Verify that the Certification Version is the current or previous version of CNTI Certification.
- Look at results log, cnf-testsuite-results-YYYY-MMDD-HHMMSS-NNN.yml. Verify that the major.minor component of the CNTI Certification matches the certification version being claimed. The patch version does not matter.
- Verify that the RESULTS SUMMARY section of results log "X of Y essential tests passed". There should be at least 15 essential tests passed.
- Confirm that the vendor is currently a member of LFN. If they are not, request that they obtain membership at LFN Membership Inquiries or reach out to info@lfnetworking.org for more information 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 LFN 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, product version and website_url are listed in the "Qualifying Offerings" section of the vendor's Participation Form.
If the submission doesn't meet all policy requirements, reply with a message indicating "Signed participation form needed", "Files missing from PR", "Membership in LFN or confirmation of non-profit status needed", etc.
- Update the CNTI Certifications spreadsheet to reflect the vendor's certified offering.
- Add the vendor's information to the LFN-CNTI Landing Page.
- Add a comment saying "This product is now "CNTI Certified."
- Merge the PR (eg. Squash and merge).
- Close the PR.