Welcome to the OASIS OpenC2 Technical Committee (TC). This brief document provides some basics about our how our TC operates. First, some useful links:
- An overview of the TC, including our standing rules, can be found at our home page at OASIS.
- General information about OpenC2 can be found at OpenC2.org
- General information about OASIS can be found on the organization's About page
The TC conducts our meetings Wednesdays at 11:00 AM Eastern time ("OpenC2 time"). The monthly meeting schedule is as follows:
| Day | Meeting Type |
|---|---|
| 1st Wednesday | Working Meeting |
| 2nd Wednesday | Working Meeting |
| 3rd Wednesday | TC Meeting (2 sessions) |
| 4th Wednesday | Working Meeting |
| 5th Wednesday (if any) | No Meeting |
We conduct all of our meetings using Lucid Meetings. As the OASIS Kavi system is the system of record for TC activities, we schedule our meetings on both the Kavi and Lucid calendars, but members will only receive one invitation for each meeting series, from Lucid. Meetings are usually scheduled in 6-month blocks (March-September, and October-April). When a new block is scheduled each member receives a brief flurry of email with calendar invitations (5 calendar invites, total).
Our monthly TC meetings on the third Wednesday of each month have an "early" (11:00 AM Eastern) session and a "late" (9:00 PM Eastern) session. The same agenda is used for both sessions, and the two sessions are treated as a single meeting (see Standing Rule #6) for purposes of attendance, voting rights, meeting minutes, motions voted, etc. This also means decisions made at the daytime session are provisional until the evening session is adjourned.
The 1st, 2nd, and 4th Wednesdays of each month are used for working meeting to discuss topics related to TC work products and other technical matters.
- By joining our TC you’re automatically subscribed to the OASIS TC email list.
- Communicationa about Work Products is typically done either:
- in Working Meetings, or
- via GitHub issues and pull requests.
-
At present all of our work product development is happening on GitHub using the Fork & Pull model. There is also a collection of open GitHub repositories with OpenC2 implementations. Links:
-
Work product repos: specifications and related documents
-
Open repos: software contributions
-
-
The TC's Documentation Norms provides a great deal of information regarding our approach to work product development. This includes information on using GitHub if you aren't familiar with it.
-
The TC also has a Google Drive where we did much of our work in the past; you can find a lot of history and reference information there.
If you joined the TC as an Observer, we welcome your interest and just ask that you respect the limits of that role and not try to actively participate in the activities on the resources above.
Please feel free to contact me if you have any questions or concerns.
Email: [email protected]