RE: [csaf] E-Mail motion to submit current editor draft as CS 01 / CSPR 01

["Schmidt, Thomas" <thomas.schmidt@bsi.bund.de>]

Dear TC members,

I, Thomas Schmidt, second the motion.

Best regards,
Thomas

> -----Original Message-----
> From: csaf@lists.oasis-open.org <csaf@lists.oasis-open.org> On Behalf Of
> Mr. Stefan Hagen
> Sent: Sunday, October 10, 2021 9:21 PM
> To: csaf@lists.oasis-open.org
> Subject: [csaf] E-Mail motion to submit current editor draft as CS 01 / CSPR 01
> 
> Dear TC members,
> 
> I hereby submit the following motion and request that if seconded and no
> objection received per this list before one week has passed
> on 2021-10-18 18:00 UTC to automatically carry.
> 
> The Chair will of course subsequently state the result per mail to this list
> when the period has passed.
> 
> The base of the promotion from CSDPR01 to CS01 is per the OASIS TC
> Process, section 2.7 at
> https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-
> 26/#committeeSpec (This version of the OASIS TC Process was approved
> by the OASIS Board of Directors on 22 July 2020 and became effective 01
> December 2020.)
> 
> The comment resolution log of the relevant CSDPR01 public review is publicly
> available per issue #366 at https://github.com/oasis-tcs/csaf/issues/366.
> This issue #366 together with the linked issue #360 presents a clear and
> comprehensible summary of the changes made since the last public review.
> 
> Stefan Hagen moves that the TC approve that the CSAF Version 2.0 Working
> Draft and all associated artifacts uniquely identified by
> below listed URLs and packaged together in the zip file at
> (https://github.com/oasis-tcs/csaf/releases/download/cs-01-20210927-
> rc1/cs-01-20210927-rc1.zip)
> as Committee Specification Draft 01 release candidate contain only Non-
> Material changes. For this, and per the TC process, I move
> that the TC members kindly task the Chair to request a Special Majority Vote
> from TC administration.
> 
> Stefan Hagen further moves that the TC approve CSAF Version 2.0 Working
> Draft and all associated artifacts uniquely identified by below listed URLs
> and packaged together in the zip file at (https://github.com/oasis-
> tcs/csaf/releases/download/cs-01-20210927-rc1/cs-01-20210927-rc1.zip) as
> Committee Specification Draft 01 and designate the markdown version of the
> specification as authoritative and direct the Chair supported
> by the Editors to perform any tasks as required by TC Admin to facilitate that
> issuance.
> 
> I additionally move that the TC approve submitting CSAF Version 2.0
> Committee Specification 01 for 15 days public review and direct the Chair
> perform any tasks as required by TC Admin to facilitate that issuance.
> 
> The referenced URLs for the 4 artifacts we submit to TC Admins are:
> 
> * https://github.com/oasis-
> tcs/csaf/blob/55196309458f1385210fa4115d167df4087b0904/csaf_2.0/prose/
> csaf-v2-editor-draft.md
> * https://github.com/oasis-
> tcs/csaf/blob/55196309458f1385210fa4115d167df4087b0904/csaf_2.0/json_s
> chema/aggregator_json_schema.json
> * https://github.com/oasis-
> tcs/csaf/blob/55196309458f1385210fa4115d167df4087b0904/csaf_2.0/json_s
> chema/csaf_json_schema.json
> * https://github.com/oasis-
> tcs/csaf/blob/55196309458f1385210fa4115d167df4087b0904/csaf_2.0/json_s
> chema/provider_json_schema.json
> 
> All the best,
> Stefan