Agreed. I would like to make our discussions more âactionableâ, so they will result in more frequent updates to the spec. We will discuss the process for accomplishing this during next weekâs TC meeting, but hereâs what I have in mind:
- We will maintain a âmaster listâ of these suggestions on the portal.
- Before one of these topics can be discussed in the Language Ad-Hoc, the following should happen:
- An issue should be created on the âtosca-community-contributionsâ github repo.
- Example TOSCA code should be provided (to illustrate shortcomings in the current spec, to suggest new grammar, or both)
- Once we get agreement on grammar, we will âpromoteâ the code example into an area of the repo that can be used to test conformance of various TOSCA implementations.
Please feel free to make additional recommendations for this process before next Thursdayâs meeting.
Thanks,
Chris
From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org>
On Behalf Of Tal Liron
Sent: Friday, December 17, 2021 9:55 AM
To: tosca@lists.oasis-open.org
Subject: [tosca] Re: TOSCA TODO list
Small emphasis that I forgot to add to this list --
It's true that we've "resolved" some of these issues in conversations in the TOSCA TC. But that's not enough, we also have to update the spec. :) So the point is to track all topics until they are "done".
As I said last time, I think we really need to compile a list of everything everyone has brought up and organize it in some kind of spreadsheet or other TODO list.
It doesn't mean we have to resolve all the topics or resolve them for TOSCA 2.0. But I just want to make sure we're keeping track.
This is what I came up with, in no particular order. Feel very free to add more!
|