conf call

Host confcall: Fujitsu
US Toll Free: 877-995-3314
US Toll/International: 210-339-1806

(same passcode)

1.  Admin:
1.1 minutes Jan 10, approval
1.2 short action items status
1.3 Miscellaneous Web and collaborative aspects to TAB work (if any)

2. Normative Keyword directives : (quick)
- feedback from review (Martin, J.Borras)
- approval vote for publishing?

3. excellence award (JIRA "Long" Action Items ): (quick)
 - https://tools.oasis-open.org/issues/browse/TAB-424
 - follow-up (email has been sent, acknowledged by Carol, need Scott opinion)

4. PR status. What specs are / have been reviewed, use of JIRA.
- coming PRs: MQTT V3.1.1 .
- categorizing comments (see AI-24), follow-up

5. Conformance Clause guideline:
- make it more than "clause" scope? need to cover how to handle Normative/Non-normative
- review current JIRA issues logged (12)



============================= Action items: ============================
----- Action Items status: those currently open  

----- Action Items status: those currently open + those that just changed

AI-12: [open](in progress) Chet and Patrick: adding comment buttons to HTML specs.
(got it working, still in progress, will send samples for a next PR)

AI-27: [open] (new) ? : deferred PR comments: e.g. TOSCA comments:
how to track those deferred until V1.1? (need to extract a subset of comments)

AI-28: [open] Patrick/Chet: to write up the process:
how issues can be imported in some way under new JIRA
Patrick: importing is possible in curr JIRA but requires administrator roles.
not set up for routine use - more as a system migration process
Suggestion from P: we could post JIRA issues directly into the TC JIRA space
chet: we still need to send these comments on mailing list. We can still move issues from a project to another.
there is a "move" capability for JIRA issues
Will hold open pending Patrick and I documenting our findings

AI-31: [open] Patrick: to see if shopping list and w3c citation builder are concurrent. Answer is “yes”.

AI-32: [open] Jacques: to initiate a new JIRA long AI for guidance to TCs on how to architect their
specs (in case several docs)
- done: https://tools.oasis-open.org/issues/browse/TAB-516

AI-33: [open] (new) Jacques will draft a note to Carol outlining the proposed general model and ask if staff is willing to nominate TCs

AI-34: [open] (new) Jacques will contact Martin and Borras about our disposition of their comments on keywords guidelines.

AI-35: [open] (new) Chet:post approved minutes to Wiki

AI-36: [open] (new) ? assessing the need for a TAB public page.
we have a TAB public Kavi group, though (if not a public page)
P: if we want the TAB to be more visible, removing public page is a step in the wrong direction