IMPORTANT: Please examine this entire event description for a handy list of resources, responsibilities, and more!
P H O N E, W E B C O N F E R E N C I N G, A N D C H A T R O O M
Due to prankster calls, please contact the co-chairs using your OASIS-registered email address to obtain this information (reference: https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201307/msg00013.html)
*** This meeting will use the phone bridge and web conferencing tool (also the new chatroom URL) specified by the co-chairs privately to all TC members ***
R E C O R D Y O U R O W N A T T E N D A N C E
Participants are responsible to log their attendance on this Kavi calendar entry. When you join the meeting, use this page to record your attendance by clicking "Record My Attendance". If you are not on the internet, you can request the chair to record your attendance on your behalf.
Y O U R S C R I B E R E S P O N S I B I L I T Y
Every person in the TC is asked to take their turn at scribing a meeting. When your name is called by the co-chair, please take your turn. You will use the chat room for the initial scribing.
Scribing is easy:
1. Change your name using setting button in the chat room to "YOUR NAME (Scribe - CO).
2. Record motions/votes and some context in the chat room during the meeting (people will add details and help). You don't have to quote people.
T R A C K Y O U R V O T I N G R I G H T S
Participants are responsible for the state of their voting rights. The co-chairs will endeavor to update the roster at
http://www.oasis-open.org/apps/org/workgroup/tosca/members/roster.php before meetings. Except for leaves of absence, the general rule is that a Voting Member who is absent from two consecutive meetings loses his or her voting rights at the end of the second Meeting missed, and a TC Member who has lost his or her voting rights shall regain them by attending two consecutive meetings after the end of the second Meeting attended. (see the TC Process section 2.4.4 for more details).
O T H E R R E S O U R C E S
TOSCA TC PAGE:
PROPOSALS AND ISSUES:
NOTE: As always, only JIRA issues will be considered by the TC for v1.1 document changes (any TC member can create a JIRA issue. Please contact the co-chairs if you have technical issues or questions)
* Resources
*
TOSCA-108: Catch-all for All Editorial Suggestions That Do NOT Change Semantics, e.g., spelling, grammar, readability, layout (use for all v1.1 documents)
* Editor's Report
* These issues at the discretion of the co-chairs and time permitting. TC members should also feel free to use this opportunity to ask further questions on any of these topics and assignees are free to volunteer further information/discussion at this time, as well.
**
TOSCA-77 (Documentation Attribute Doesn't Specify mime-type)
**
TOSCA-81 (Charter clarification rev2 revisited based on OASIS feedback)
**
TOSCA-12 (Set of Basic Node Types) -- also related is
TOSCA-11 (Set of Fundamental Lifecycle Operations)
The TC will continue development of TOSCA-12 / TOSCA-11 to completion
**
TOSCA-7 (Alternate encodings Service Templates) -- update by ad hoc team lead (Krishna)
**
TOSCA-114 (Composite Capabilities and Requirements)
**
TOSCA-115 (Requirements Capabilities to Provide Interfaces)
* GENERAL REMINDER: While a general approach can be decided by motion, specific concrete/material proposals and contributions need to be JIRA issues