chet-ensign
commented
3 years ago Thanks Stefan - that motion works perfectly!
On Wed, Jul 28, 2021 at 11:47 AM Stefan Hagen @.***> wrote:
@santosomar https://github.com/santosomar, @chet-ensign https://github.com/chet-ensign I hereby suggest the following motion template in the case the TC likes to initiate the public review of the first CSAF v2.0 Committee Specification Draft in today‘s meeting:
I move that the TC approve CSAF Version 2.0 Working Draft and all associated artifacts packaged together in as a 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 further move that the TC approve submitting CSAF Version 2.0 Committee Specification Draft 01 for 30 days public review and direct the Chair perform any tasks as required by TC Admin to facilitate that issuance.
My suggestion is to agree during the meeting on the URLs by just copying the URL of the editor draft and generate a zipfile of the three schema files and the markdown file as service for TC Admins. The designation of the normative format is relevant when TC Admin adds the generated HTML and PDF variants to the markdown source for publication and review.
The current URLs for the 4 artifacts we submit to TC Admins would be:
- https://github.com/oasis-tcs/csaf/blob/ca2d9a872b3ce7249c41532961507490724158d6/csaf_2.0/prose/csaf-v2-editor-draft.md
https://github.com/oasis-tcs/csaf/blob/ca2d9a872b3ce7249c41532961507490724158d6/csaf_2.0/json_schema/aggregator_json_schema.json
https://github.com/oasis-tcs/csaf/blob/ca2d9a872b3ce7249c41532961507490724158d6/csaf_2.0/json_schema/csaf_json_schema.json
Unfortunately I currently do not have access to a machine to generate a zip archive and upload this here, but any note on the four specific URLs should be sufficiently safe to generate a zip file after the meeting.
Originally posted by @sthagen https://github.com/sthagen in #329 (comment) https://github.com/oasis-tcs/csaf/pull/329#issuecomment-888418320
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/oasis-tcs/csaf/issues/331, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACYUWRPB2SM5VBKZNH7PAJLT2ARB3ANCNFSM5BEULFIQ .
-- Chet Ensign
Chief Technical Community Steward
OASIS Open
+1 201-341-1393 <+1+201-341-1393> @.*** www.oasis-open.org
santosomar
sthagen
tolim
OASIS-OP-Admin
@santosomar, @chet-ensign I hereby suggest the following motion template in the case the TC likes to initiate the public review of the first CSAF v2.0 Committee Specification Draft in today‘s meeting:
My suggestion is to agree during the meeting on the URLs by just copying the URL of the editor draft and generate a zipfile of the three schema files and the markdown file as service for TC Admins. The designation of the normative format is relevant when TC Admin adds the generated HTML and PDF variants to the markdown source for publication and review.
The current URLs for the 4 artifacts we submit to TC Admins would be:
Unfortunately I currently do not have access to a machine to generate a zip archive and upload this here, but any note on the four specific URLs should be sufficiently safe to generate a zip file after the meeting.
Originally posted by @sthagen in https://github.com/oasis-tcs/csaf/issues/329#issuecomment-888418320