Generally GoogleDocs are useful especially when comment resolution includes a small note in the comment itself saying âaccepted â see changesâ or ârejected - <reason why>â.
I posted a few comments and saw most of my comments resolved without any note on acceptance or rejection.
Without looking at the text in the doc I have no idea how my comments were resolved or just discarded.
LookingGlass Cyber Solutions
From: <firstname.lastname@example.org> on behalf of Chet Ensign <email@example.com>
Date: Monday, October 21, 2019 at 12:01 PM
To: OASIS Charter Discuss List <firstname.lastname@example.org>
Cc: Carol G <email@example.com>, Dee Schur <firstname.lastname@example.org>, Ryan Hohimer <email@example.com>, JG CTI-TC <firstname.lastname@example.org>, "Eschweiler, Joerg" <email@example.com>, Javier Garcia Robles <firstname.lastname@example.org>, "Bret
Jordan (CS)" <Bret_Jordan@symantec.com>, Anuj Goel <email@example.com>, Avkash Kathiriya <firstname.lastname@example.org>, Shawn Riley <email@example.com>, Robert Keith <Robert_Keith@symantec.com>, Alex Applegate <firstname.lastname@example.org>, Ben Ottoman <email@example.com>,
David Powell <firstname.lastname@example.org>, Rob Arnold <email@example.com>, Andreas Sfakianakis <firstname.lastname@example.org>, Caitlin Huey <email@example.com>, Sergey Polzunov <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>
Subject: [oasis-charter-discuss] Minutes from TAC TC convener call
- Attending: Ryan Hohimer, Jane Ginn, Bret Jordan, Gershon Janssen, Carol Geyer, Dee Schur, Chet Ensign
- Jason corrected my rendering of the name: it is Threat Actor Context TC
- Regarding their experience with the call for comment using a Google Doc, Ryan explained that the feedback was very useful. The process of addressing proposals and handling comments was logistically challenging. Some direction or proposed procedures to follow
would be helpful. Also, the comment resolution log spread sheet was not the best tool.
- AI to Chet: review how GD handles revision history; prepare some suggested procedures for handling feedback in the future.
- The content of the Google Doc is ready for use for the call for participation. Ryan will send the comment log to the oasis-charter-discuss@ mailing list.
- We reviewed the timeline to the first call. Chet clarified for Jane that subcommittees can be set up at any time; the TC doesn't have to approve them at the first meeting.
- Dee went over outreach and promotion. Ryan, Jane, and Bret had suggestions on who might be interested in the work.
- Ryan asked if there is information available to help him get up to speed on OASIS tools. Dee offered to do her training session at his convenience. Chet to send out the list of useful links.
- No other business raised. Meeting adjourned.
Chief Technical Community Steward
OASIS: Advancing open source & open standards for the information society