[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cacao] Re: Method of work and Comments
Sorry, partial email sent because left tab for paragraph was interpreted as send from within the browser... Please ignore and use the following...
===
We are entering a more formal part of the OASIS process. We have a Public Review outstanding, and we have received comments.Â
Â
Under the Oasis process, all comments must be tracked and their disposition recorded. These comments and dispositions mut be publicly reviewable.Â
Â
A brief oversight of this process can be read atÂhttps://www.oasis-open.org/resources/toolsÂ
Â
The result of this is that informal group editing of Google Docs is no longer appropriate. One big reason is versioning. There must be formal versions for comments to be linked to formal versions.Â
Â
I am aware of two ways this is done in OASIS.ÂÂ
1) Each working draft from here on out must be properly tracked within KaviÂ
At least once a month (unless no work has been done), and prior to each TC meeting at which one or more draft documents will be discussed,ÂWorking DraftÂlevel material for any/all such documents must be uploaded to theÂTC document repository, properly identified according to theÂOASIS Naming Directives; links to the non-Kavi publication venues are insufficient
Under this model, comments are tracked in OASIS Jira. All comments are entered there, assigned as necessary, and potentially the resolution is voted on. (Most issues do not require committee votes, but some do, and it is often considered good practice to have a formal vote accepting all the Kavi managed issues in advance of the next publication.)ÂAs far as I can tell, no Jira project for Cacoa has been created, so there are definitely no issues.Â
Â
2) Working Drafts move into Github. Working Drafts must still be released as if it were in Kavi. There are a host of other procedures which, in the spirit of specifications, I reference rather than incorporate here.Â
If managed in GitHub, each comment is entered as a Pull Request. Pull Requests can be worked as any other issue, and may require TC votes to resolve.Â
Â
I raise the issue now because I see that nothing has been done in the git for CACAO for more than eight months. (https://github.com/oasis-tcs/cacao). Again, we have issues and comments but they are not being logged.Â
Â
Have we, as a TC decided on which path to use, yet?Â
If the path is in Github, as hinted at by the existence of the repository, then some work needs to be done including but no limited to:Â
- Enter the CSD01 into Github as a releaseÂ
- Initiate a working branch (WD04?) from CSD01Â
- Begin entering the comments as pull requests, linked to the appropriate text as appropriateÂ
Â
I have numerous comments from the ongoing Public Review. I need to know if I shouldÂ
- Write them all up, and submit them as one massive multi-part comment to CACAO-commentsÂ
- Start entering Jira IssuesÂ
- Begin entering Pull Requests, which requires that the branch described above be created.Â
Â
If this was decided previously, and I missed it, my apologies. Â
Â
ThanksÂ
Â
tcÂ
From: cacao@lists.oasis-open.org <cacao@lists.oasis-open.org> on behalf of Considine, Toby <Toby.Considine@unc.edu>
Sent: Sunday, September 13, 2020 3:14 PM
To: cacao@lists.oasis-open.org <cacao@lists.oasis-open.org>
Subject: [cacao] Method of work and CommentsÂWe are entering a more formal part of the OASIS process. We have a Public Review outstanding, and we have received comments.
Under the Oasis process, all comments must be tracked and their disposition recorded. These comments and dispositions mut be publicly reviewable.
A brief oversight of this process can be read atÂhttps://www.oasis-open.org/resources/tools
The result of this is that informal group editing of Google Docs is no longer appropriate. One big reason is versioning. There must be formal versions for comments to be linked to formal versions.
I am aware of two ways this is done in OASIS.Â1) Each working draft from here on out must be properly tracked within KaviAt least once a month (unless no work has been done), and prior to each TC meeting at which one or more draft documents will be discussed,ÂWorking DraftÂlevel material for any/all such documents must be uploaded to theÂTC document repository, properly identified according to theÂOASIS Naming Directives; links to the non-Kavi publication venues are insufficient
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]