=============================================================
Minutes TAB call (September 5, 2014)
=============================================================


Info
Time: 11amPT
Dial:
Host confcall: Fujitsu
US Toll Free: 877-995-3314
US Toll/International: 210-339-1806


Agenda

1. Admin and general status:
- Minutes Aug 15, 22
- Conformance Clause guideline submission status, follow-up plans
2. Review of short action items, move to Kavi. (see below)
- In particular, TAB public page
3. PRs: status, process and outputs.
- current PR pipeline (latest SMP,...),
- facilitating public feedback (inline comment links, etc)
- TAB PR process
- PR checklist follow-up: latest update with JIRA-aligned severity fields, possible values per check item.


Roll:

Patrick Durusau (individual)
Jacques Durand (Fujitsu)
Ashok Malhotra (Oracle)
Chet Ensign (staff)


Minutes:

1. Admin and general status:
- Minutes Aug 15, 22: approved unan
- Conformance Clause guideline submission status, follow-up plans:
J: we still need to cover non-machine processable specs:
(1) ref architectures, (2) human-driven administrative processes
- patrick: ISO terminology. Different conf clause issues.
E.g. what does it mean "to have representation of all stakeholders" (in a non-machine processable spec)? need some tangible benchmarks.
- Patrick: One reference on frameworks: https://lists.oasis-open.org/archives/tab/201408/msg00139.html
- other candidate new content for conf guidelines:
conformance clause templates (in appendix)

2. Review of short action items, move to Kavi. (see below)
Action items: https://www.oasis-open.org/apps/org/workgroup/tab/members/action_items.php?sort_field=status

#0287: close? (moderating the list is still TBD)
keep open to resolve moderating point

#0288 Fix the link to the FAQ from the TAB public page
- open

#0289 Ask Carol about reorganizing the PnG page to separate TAB-published documents
- open

#0290 Develop a schedule for meetings that work with Gershon's schedule
- open

#0291 Experiment with using Kavi action items to track our short-term AIs
- close

#0292 Schedule a review and discussion of current TAB charter for an upcoming meeting
- open

#0294 Set up process for sending a welcome message from the TAB to new TCs
- New A item for Chet: see if the convener call announce can be CCed to TAB list.

#0295 Document the process that the TAB is following to perform public reviews
- open

#0296 Implement a way to monitor that TCs are providing comment resolution logs before their next stage in the workflow
- close - no solution.

- New A Item [J] : How to verify comment resolution logs of 2nd+ PRs, assign process for TAB member? How to find the previous PR export spreadsheet?

#0297 Ask Carol to update the current TAB page off the main OASIS homepage
- open

#0298 Submit revised conformance clauses doc to Board for approval
- closed

New A Item: the "Press" link in TAB public page needs updated content. For Carol (Chet)

new A Item: (Chet) to add TAB list to CC in every new PR public announce.

3. PRs: status, process and outputs.

PR checklist: https://www.oasis-open.org/apps/org/workgroup/tab/download.php?document_id=53616
-J: uploaded file: TAB-ReviewChecklist-rev8.doc

- Severity levels: Blocker/Critical/Major-Minor.
o Minor ( formerly Low) severity means that failing the item does not require a correction in the specification although that would be preferable.
o Major (formerly Medium) means that failing the item might be an issue for some reviewers, when membership approval is needed. The failure should be corrected.
o Critical: serious flaw that makes it very difficult if not impossible for implementers to develop an implementation or claim conformance, even if not violating the TC process rules. The OASIS TC admin may decide to not process further such a specification. It is strongly recommended to correct the failure.
o Blocker (formerly High )means that the item is required by the OASIS TC Process and failing the item imperatively requires to be addressed by editors.

Some values may be predefined for the item, meaning the reviewer can only pick one of them. If none are specified, the reviewer can label a failing item according to his/her judgment.

- Patrick: "Minor should not hint that TC could ignore
- Patrick: means that the item should be corrected, conveying the TC's concern for accuracy and readable prose.
- Patrick: major - means the item is likely to confuse standard consumers and must be corrected to avoid differing implementations.
- Jacques will upload rev9 of PR checklist with above fixes.

- next regular full meeting Sept 19.

Meeting adjourned.

20140905 (last edited 2014-10-03 21:38:58 by chet.ensign)