This same content is captured in https://github.com/oslc-op/oslc-specs/issues/56but is included in an email to the oslc-op mailing list to ensure wider distribution:

Here's a summary of an OP project specification lifecycle:
        1        PGB can with 14 day notice vote to create a Project Specification Draft (PSD) revision anytime, and simply tags it in the repo, nothing is published
        2        Project Specification Draft can with 14 day notice be promoted to Project Specification (PS) by PGB Special Majority Vote, subject to specification conformance review by OASIS OP Admin
        3        Project Specification can be promoted to OASIS Standard
        i        With 3 statements of use, Submission of a Candidate OASIS Standard (COS) to the TC Administrator,
        ii        Completion of a public review lasting a minimum of 60 days, and
        iii        A call for consent to approve the COS as OASIS Standard.
        iv        A potential single, second call for consent after addressing negative comments.
See https://www.oasis-open.org/policies-guidelines/open-projects-process#project-specificationsfor details.

In order to proceed we need to do the following:
        1.        
Finish any document edits and ReSpec changes
        2.        
Produce HTML and PDF documents and review for template conformance with Chet
        3.        
Schedule a PGB vote to create Project Specification Drafts (PSD) for all documents
        4.        
Schedule Special Majority Vote two weeks later to promote PSDs to Project Specifications (PS) and publish PS HTML and PDF revisions to OASIS Library
        5.        
For Core, AM, CM, QM and RM specs, collect 3 statements of use and schedule Special Majority Vote to promote those Project Specifications to COS and submit to 60 day public review
        6.        
Respond to review and Call for Consent issues as needed to progress to OASIS Standard

--
Jim Amsden, Senior Technical Staff Member
ELM Quality Manager
919-525-6575

Thanks! I would expect we produce only one PS in the end?

--

/Andrew

(from phone)

On Thu, Jun 27, 2019 at 8:24 PM +0200, "Jim Amsden" <jamsden@...> wrote:

This same content is captured in https://github.com/oslc-op/oslc-specs/issues/56but is included in an email to the oslc-op mailing list to ensure wider distribution:

Here's a summary of an OP project specification lifecycle:
        1        PGB can with 14 day notice vote to create a Project Specification Draft (PSD) revision anytime, and simply tags it in the repo, nothing is published
        2        Project Specification Draft can with 14 day notice be promoted to Project Specification (PS) by PGB Special Majority Vote, subject to specification conformance review by OASIS OP Admin
        3        Project Specification can be promoted to OASIS Standard
        i        With 3 statements of use, Submission of a Candidate OASIS Standard (COS) to the TC Administrator,
        ii        Completion of a public review lasting a minimum of 60 days, and
        iii        A call for consent to approve the COS as OASIS Standard.
        iv        A potential single, second call for consent after addressing negative comments.
See https://www.oasis-open.org/policies-guidelines/open-projects-process#project-specificationsfor details.

In order to proceed we need to do the following:
        1.        
Finish any document edits and ReSpec changes
        2.        
Produce HTML and PDF documents and review for template conformance with Chet
        3.        
Schedule a PGB vote to create Project Specification Drafts (PSD) for all documents
        4.        
Schedule Special Majority Vote two weeks later to promote PSDs to Project Specifications (PS) and publish PS HTML and PDF revisions to OASIS Library
        5.        
For Core, AM, CM, QM and RM specs, collect 3 statements of use and schedule Special Majority Vote to promote those Project Specifications to COS and submit to 60 day public review
        6.        
Respond to review and Call for Consent issues as needed to progress to OASIS Standard

--
Jim Amsden, Senior Technical Staff Member
ELM Quality Manager
919-525-6575

Wow, it took 3 hours for this email to hit the list! What’s wrong with this mailing list?

--

/Andrew

(from phone)

On Thu, Jun 27, 2019 at 11:47 PM +0200, "Andrii Berezovskyi" <andriib@...> wrote:

Thanks! I would expect we produce only one PS in the end?

--

/Andrew

(from phone)

On Thu, Jun 27, 2019 at 8:24 PM +0200, "Jim Amsden" <jamsden@...> wrote:

This same content is captured in https://github.com/oslc-op/oslc-specs/issues/56but is included in an email to the oslc-op mailing list to ensure wider distribution:

Here's a summary of an OP project specification lifecycle:
        1        PGB can with 14 day notice vote to create a Project Specification Draft (PSD) revision anytime, and simply tags it in the repo, nothing is published
        2        Project Specification Draft can with 14 day notice be promoted to Project Specification (PS) by PGB Special Majority Vote, subject to specification conformance review by OASIS OP Admin
        3        Project Specification can be promoted to OASIS Standard
        i        With 3 statements of use, Submission of a Candidate OASIS Standard (COS) to the TC Administrator,
        ii        Completion of a public review lasting a minimum of 60 days, and
        iii        A call for consent to approve the COS as OASIS Standard.
        iv        A potential single, second call for consent after addressing negative comments.
See https://www.oasis-open.org/policies-guidelines/open-projects-process#project-specificationsfor details.

In order to proceed we need to do the following:
        1.        
Finish any document edits and ReSpec changes
        2.        
Produce HTML and PDF documents and review for template conformance with Chet
        3.        
Schedule a PGB vote to create Project Specification Drafts (PSD) for all documents
        4.        
Schedule Special Majority Vote two weeks later to promote PSDs to Project Specifications (PS) and publish PS HTML and PDF revisions to OASIS Library
        5.        
For Core, AM, CM, QM and RM specs, collect 3 statements of use and schedule Special Majority Vote to promote those Project Specifications to COS and submit to 60 day public review
        6.        
Respond to review and Call for Consent issues as needed to progress to OASIS Standard

--
Jim Amsden, Senior Technical Staff Member
ELM Quality Manager
919-525-6575