diff options
Diffstat (limited to '3rd_party/static/testapi-ui/components/about/templates/README.html')
| -rw-r--r-- | 3rd_party/static/testapi-ui/components/about/templates/README.html | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/3rd_party/static/testapi-ui/components/about/templates/README.html b/3rd_party/static/testapi-ui/components/about/templates/README.html index 538ffb8..4be7c8d 100644 --- a/3rd_party/static/testapi-ui/components/about/templates/README.html +++ b/3rd_party/static/testapi-ui/components/about/templates/README.html @@ -38,12 +38,12 @@ defined by the community under the oversight of the Technical Steering Committee <p>Please note that these sources are subject to further revisions and may be updated at some future time. The current compliance verification procedures are published by OPNFV.</p> -<h2>Program Management & Maintenance</h2> +<h2>Program Management & Maintenance</h2> -<h3>Role of C&C Committee</h3> -<p>The OPNFV Certification & Compliance (C&C) Committee, hereafter referred to as the Committee, serves as the CVP -administrator on behalf of the OPNFV Board of Directors. The Committee is responsible for defining program governance, -compliance verification strategy, and the overall scope of the compliance verification procedures.</p> +<h3>Role of C&C Committee</h3> +<p>The OPNFV Certification & Compliance (C&C) Committee, hereafter referred to as the Committee, serves as the +CVP administrator on behalf of the OPNFV Board of Directors. The Committee is responsible for defining program +governance, compliance verification strategy, and the overall scope of the compliance verification procedures.</p> <h3>Maintenance of Program Documents</h3> <p>Program documents, such as this document, produced by the Committee will be labeled using semantic versioning. @@ -90,9 +90,9 @@ endorse any products or appear to endorse any products.</p> <li>Readiness for commercial deployment</li> </ul> </ul> -<p>The OPNFV C&C Committee on behalf of the Board of Directors can award a product “OPNFV Ready” status. “OPNFV Ready”, -therefore, may not be used in relation to a vendor’s product without first having met the requirements outlined in this -document.</p> +<p>The OPNFV C&C Committee on behalf of the Board of Directors can award a product “OPNFV Ready” status. +“OPNFV Ready”, therefore, may not be used in relation to a vendor’s product without first having met the requirements +outlined in this document.</p> <p>Use of “Ready” must be used in conjunction with the OPNFV release name under which the product was verified (e.g., “OPNFV Colorado Ready”). This allows the OPNFV compliance/qualification standard to evolve over time as the OPNFV platform matures.</p> @@ -125,7 +125,7 @@ respect to the confirmed category.</p> Logo/Trademark, program documents, or compliance verification procedures.</p> -<h2>Compliance Verification & Application Requirements</h2> +<h2>Compliance Verification & Application Requirements</h2> <h3>Compliance Verification Procedures Requirements</h3> <p>CVP compliance verification procedures leverage tests, compliance verification tools, test infrastructure and compliance verification program infrastructure defined and maintained by OPNFV projects which are included in an OPNFV @@ -170,8 +170,8 @@ and validity. Based on the determination of the Committee, a recommendation will regarding the approval of the granting of permission to use an OPNFV Logo/Trademark.</p> <p>The Committee may request additional information regarding the application for use of an OPNFV Logo/Trademark.</p> <p>OPNFV may charge a reasonable fee for reviewing results. Reviews will be conducted by OPNFV member companies -participating in the review committee (a C&C subcommittee). No member company may review its own compliance verification -results.</p> +participating in the review committee (a C&C subcommittee). No member company may review its own compliance +verification results.</p> <p>In the event of a dispute, the submitting organization has a right to appeal the decision with the OPNFV Board of Directors. An appeals process is documented in the Escalation Process below.</p> @@ -180,7 +180,7 @@ Directors. An appeals process is documented in the Escalation Process below.</p> <h3>Similarity Policy</h3> <p>Hardware platforms identified as similar to platforms that have passed CVP compliance verification procedures may -apply to use the OPNFV Ready trademark. The C&C Committee can decide to grant “OPNFV Ready” to products designated +apply to use the OPNFV Ready trademark. The C&C Committee can decide to grant “OPNFV Ready” to products designated “under similarity”. The Committee will consider similarity in the following areas (for example):</p> <ul> <li>Compute</li> |