diff options
author | Eddie Arrage <eddie.arrage@huawei.com> | 2018-01-23 16:39:55 -0800 |
---|---|---|
committer | Dan Xu <xudan16@huawei.com> | 2018-02-01 02:56:31 +0000 |
commit | 0780202ed6a1521a4c43aaaa6f0407b6f8633b08 (patch) | |
tree | d0c2dcc3428e8ce7a01706002c76ff2ad7c3c310 /docs | |
parent | d864c18501dfc4f44a0d2d434fe3c45beef9ceff (diff) |
Update OVP workflow document
- Fix typos and word changes
- Remove editor's note
- Adopt rewording suggestions
- Add back toc that was inadvertently deleted
- Modify to reflect process used during beta and current OVP web portal
usage
- Remove reference to application form and use online participation form
instead. Add new fields required in participation form
Change-Id: Ia51b7674315467e01081015b3aa780ec03652ebd
Signed-off-by: Eddie Arrage <eddie.arrage@huawei.com>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/testing/user/certificationworkflow/ApplicationForm.rst | 2 | ||||
-rw-r--r-- | docs/testing/user/certificationworkflow/index.rst | 101 |
2 files changed, 53 insertions, 50 deletions
diff --git a/docs/testing/user/certificationworkflow/ApplicationForm.rst b/docs/testing/user/certificationworkflow/ApplicationForm.rst index 247167d8..aac9a46e 100644 --- a/docs/testing/user/certificationworkflow/ApplicationForm.rst +++ b/docs/testing/user/certificationworkflow/ApplicationForm.rst @@ -2,8 +2,6 @@ .. http://creativecommons.org/licenses/by/4.0 .. (c) OPNFV, Intel Corporation and others. -.._ovp-application-form: - ======================================= OPNFV Verified Program Application Form ======================================= diff --git a/docs/testing/user/certificationworkflow/index.rst b/docs/testing/user/certificationworkflow/index.rst index 36346215..e0273601 100644 --- a/docs/testing/user/certificationworkflow/index.rst +++ b/docs/testing/user/certificationworkflow/index.rst @@ -4,28 +4,28 @@ .. _dovetail-certification_workflow: -============================================= -OPNFV Verified Program certification workflow -============================================= +=============================== +OPNFV Verified Program Workflow +=============================== Introduction ============ -This document provides guidance for testers on how to obtain OPNFV compliance -certification. The OPNFV Verified Program (OVP) is administered by -the OPNFV Compliance and Certification (C&C) committee. +This document provides guidance for prospective participants on how to obtain 'OPNFV Verified' +status. The OPNFV Verified Program (OVP) is administered by the OPNFV Compliance and Certification +(C&C) committee. For further information about the workflow and general inquiries about the program, please check out the `OVP web portal`_, or contact the C&C committee by email address verified@opnfv.org. This email address should be used for all communication with the OVP. -Step 1: Applying -================ +Step 1: Participation Form Submission +===================================== -A tester should start the process by completing an application. -The application form can found on the `OVP web portal`_ and the following -information should be provided: +A participant should start the process by submitting an online participation form. The participation +form can found on the `OVP web portal`_ or directly at `OVP participation form`_ and the +following information must be provided: - Organization name - Organization website (if public) @@ -35,7 +35,7 @@ information should be provided: - Product categories, choose one: (i) software and hardware (ii) software and third party hardware (please specify) - Primary contact name, business email, postal address and phone number - Only the primary email address should be used for + Only the primary contact email address should be used for official communication with OPNFV OVP. - User ID for OVP web portal The OVP web portal supports the Linux Foundation user ID in the current release. @@ -45,16 +45,15 @@ information should be provided: - If the test is to be conducted by a third-party lab, please specify name and contact information of the third-party lab, including email, address and phone number. +- OVP software version for compliance verification +- Testing date -Please email the completed application using the primary contact email -account in order to establish identity. - -Once the application information is received and in order, an email response will be -sent to the primary contact with confirmation and information to proceed. +Once the participation form information is received and in order, an email response will be +sent to the primary contact with confirmation and information to proceed. The primary contact +specified in the participation form will be entered into OVP web portal back-end by the program +administrator and will be permitted to submit results for review on behalf of their organization. -[Editor's note: -No fee has been established at this time for OVP applications. Recommend -we skip fee for the initial release of OVP.] +There is no fee at this time for participation in the OVP. Step 2: Testing =============== @@ -65,55 +64,61 @@ The following documents guide testers to prepare the test environment and run te - :ref:`dovetail-test_case_specification` - :ref:`dovetail-testing_user_guide` -A unique Test ID is generated by the Dovetail tool for each test run. Please take a note -of this ID for future reference. +A unique Test ID is generated by the Dovetail tool for each test run and can only be +submitted to the OVP web portal once. Step 3: Submitting Test Results =============================== -Testers can upload the test results to the `OVP web portal`_. -By default, the results are visible only to the tester who uploaded the data. +Users/testers other than the primary contact may use the OVP web portal as a resource to upload, +evaluate and share results in a private manner. Testers can upload the test results to the +`OVP web portal`_. By default, the results are visible only to the tester who uploaded the data. Testers can self-review the test results through the portal until they are ready to ask -for OVP review. They may also update with or add new test results as needed. +for OVP review. They may also add new test results as needed. -Once the tester is satisfied with the test result, the tester grants access to the test result -for OVP review via the portal. The test result is identified by the unique Test ID. +Once the tester is satisfied with the test result, the primary contact grants access to the test +result for OVP review using a 'submit for review' operation via the portal. The test result is +identified by the unique Test ID and becomes visible to a review group comprised of OPNFV +community members. -When a test result is made visible to the reviewers, the web portal will notify -verified@opnfv.org and Cc the primary contact email that a review request has been made and reference -the Test ID. This will alert the C&C Committee to start the OVP review process. +When a test result is made visible to the reviewers, the program administrator will ask for +volunteers from the review group using the verified@opnfv.org email and CC the primary contact +email that a review request has been made. The program administrator will supply the Test ID +and owner field (primary contact user ID) to the reviewers to identify the results. Step 4: OVP Review =================== -Upon receiving the email notification and the Test ID, the C&C Committee conducts a -peer based review of the test result. Persons employed by the same organization that submitted -the test results or by affiliated organizations will not be part of the reviewers. +Upon receiving the email request from the program administrator, the review group conducts a +peer based review of the test result using reviewer guidelines published per OVP release. +Persons employed by the same organization that submitted the test results or by affiliated +organizations will not be part of the reviewers. -The primary contact may be asked via email for any missing information or -clarification of the application. The reviewers will make a determination and recommend -compliance or non-compliance to -the C&C Committee. Normally, the outcome of the review should be communicated -to the tester within 10 business days after all required information is in order. +The primary contact may be asked via email for any missing information or clarification of the +test results. The reviewers will make a determination and recommend compliance or non-compliance +to the C&C Committee. A positive review requires a minimum of two approvals from two distinct +organizations without any negative reviews. The program administrator sends an email to OVP/C&C +emails announcing a positive review. A one week limit is given for issues to be raised. If no +issue is raised, the C&C Committee approves the result and the program administrator sends an +email to OVP/C&C emails stating the result is approved. -If an application is denied, an appeal can be made to the C&C Committee. +Normally, the outcome of the review should be communicated to the primary contact within 10 +business days after all required information is in order. -Step 5: Grant of Use of Logo -============================ +If a test result is denied, an appeal can be made to the C&C Committee for arbitration. -If an application is approved, further information will be communicated to the tester -on the guidelines of using OPNFV OVP logos and the status of compliance for promotional purposes. +Step 5: Grant of Use of Program Marks +===================================== - -Appendix -======== +If an application is approved, further information will be communicated to the primary contact +on the guidelines of using OVP Program Marks (including OVP logo) and the status of compliance +for promotional purposes. .. toctree:: :maxdepth: 2 - ApplicationForm - .. References .. _`OVP web portal`: https://verified.opnfv.org +.. _`OVP participation form`: https://na3.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=e03e78d7-c32e-47d3-8292-350b747a0105 |