[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Motion for OpenC2 Language Specification CSD
-------- Original Message --------
Subject: [openc2] Re: OpenC2 Language Spec ification draft for appr
From: "Mr. Stefan Hagen" <email@example.com>
Date: Thu, October 12, 2017 1:45 pm
To progress a working draft to CSD a simple motion suffices and triggers the public review for people outside of the TC like so (in the suggested
It is for CS where a ballot is required.
Sample motion in the current case could be:
"I move that the TC approve the OpenC2 Language Specification V1.0 Working Draft 03 and all associated artifacts packaged together in https://www.oasis-open.org/committees/download.php/61772/oc2ls-v1.0.0-wd03.zip as a Committee Specification Draft 01 and designate the PDF version of the specification as authoritative.
I further move that the TC approve submitting the aforementioned Committee Specification Draft 01 for 30 days of public review and direct the Chair perform and tasks as required by TC Admin to facilitate that issuance."
On 12/10/17 18:51, Jason Keirstead wrote:
> Just my opinion - I think one of the things not being considered here is
> how long it takes for a ballot.
> While there is no official oasis rule on the time-frame, a ballot for a
> CSD has to be open for a *reasonable* period of time to allow TC members
> to vote. Given the importance of a CSD, that time-frame should be at
> least in the two week range to account for people's schedules and
> vacations etc.
> If you are pre-planning to do 4 CSDs, you're basically pre-writing-off 2
> months of time waiting for ballots, as you can't make any material
> changes to the document while people are voting.
> Jason Keirstead
> STSM, Product Architect, Security Intelligence, IBM Security Systems
> Without data, all you are is just another person with an opinion - Unknown