Implement CF conformance testing program for certification about community HOT 5 CLOSED

@gberche-orange I'm currently working on a document proposing certification via conformance testing (using CATs to start). I'm going to share this with cf-dev soon, but if you want a look at the work in progress: https://docs.google.com/document/d/1tI2uY7AXmL7ED-FlJLxpuAVBmRr_I11XMm1u68J-6NE/edit?usp=sharing

from community.

Personally, I'm looking forward to a TOC defining explicit API conformance. Tagging @troytop as he might have some thoughts.

from community.

+1 for TOC defining api conformance (such as https://github.com/cloudfoundry/cf-acceptance-tests/ )

The existing certification process was however wider in scope, e.g. aiming at avoiding forks and mandating use of core component binaries, see https://docs.google.com/document/d/1QRtzYcumcNmEiGTmzMjcxnWffcPsu7AyHlReFx5eY7M/edit?ts=5a0277af#heading=h.v1uqb5pkq2ul

Certified offerings are required to use the exact software packaged in specific releases of each of the: Cloud Foundry Elastic Runtime and Developer CLI tool. Details for each component are noted below.

When certifying and during a verification audit, the program participant must provide the Foundation the exact release numbers for each required component.

from community.

The existing certification process was however wider in scope, e.g. aiming at avoiding forks and mandating use of core component binaries, see https://docs.google.com/document/d/1QRtzYcumcNmEiGTmzMjcxnWffcPsu7AyHlReFx5eY7M/edit?ts=5a0277af#heading=h.v1uqb5pkq2ul

Certified offerings are required to use the exact software packaged in specific releases of each of the: Cloud Foundry Elastic Runtime and Developer CLI tool. Details for each component are noted below.
When certifying and during a verification audit, the program participant must provide the Foundation the exact release numbers for each required component.

+1 to the idea that the current model is broader in scope. My suggestion for the "rebooted" technical governance process would be to toss out the old cert goals and refocus on what is best for the project going forward, starting with API conformance first. The whole program should be up for discussion at this point, while we may find value in the past implementation.

from community.

Changed title to accurately reflect this as a TODO for the TOC once we have one.

from community.