Page History

...

• Org Structure and Work Streams https://github.com/cntt-n/CNTT/blob/master/doc/gov/chapters/chapter03.md
• Nomination and Selection https://github.com/cntt-n/CNTT/blob/master/doc/gov/chapters/chapter04.md
• Concensus-based Decision Making https://github.com/cntt-n/CNTT/blob/master/doc/gov/chapters/chapter05.md

Formal Definitions (from Github https://github.com/cntt-n/CNTT/blob/master/doc/gov/chapters)

• Technical Steering Committee
  • The Technical Steering Committee (the “TSC”) is responsible for general oversight of the CNTT Projects (aka Workstreams).
  • The TSC is responsible to meeting one of CNTT's core principals is to stay current with new and emerging trends in the industry, including how to integrate new technologies and processes. In pursuit of this Goal the TSC approves:
    • the creation of a new CNTT Release and Milestones
    • new Workstreams (WS),
    • termination of a WS, and
    • the creation of any short-term teams focused on an emerging technology or field of interest to CNTT
  • The TSC is led of a Lead and up to 2 (two) Co-Leads and are elected as per CNTT election policies. The Nomination and Selection document defines the process for selecting the TSC Leads and Co-Leads. The document also specifies the Length of Term which is 12 calendar months and will start typically in February each year and end around the same time the year after. The exact dates and timing might vary to accommodate CNTT releases and workshops.
  • The TSC is composed of Workstream Leads/Co-Leads (Nomination and Selection specifies the process for selecting the WS Leads and Co-Leads).
  • The TSC Lead/Co-Leads are responsible for arranging and leading regular TSC meetings with a formal agenda and published minutes.
  • The TSC is open to all but formally participants belong only to CNTT member companies.
  • The TSC and constituent WSs follow Concensus-based Decision Making
  • The TSC Lead is responsible for monitoring progress of the projects and their activities (Github Issues and Pull Requests (PR) for inactivity. Any inactivity is pointed to the WS Leads and if not addressed are brought for discussion at the regular TSC Meetings.
  • The TSC Lead is the Code Owner in Github of all Technical Workstreams and hence is authorized for final approval and merger of completed PRs. Since the WS Leads are Code Owners of the activities for their WS, the TSC Lead will normally only act on a PR whose author is the WS Lead (and hence cannot approve and merge) or where exceptional circumstance require the TSC Lead to approve the activities.
  • The TSC resolves any inter-WS issues following a consensus-based approach.
  • The TSC defines policies or changes to existing policies that affect multiple WSs.
• Technical Workstream
  • Workstreams (WS) are responsible for all technical activities related to their approved nature of work.
  • Workstreams are responsible to define the work to be performed for a particular CNTT release, and the management and tracking of progress of the work.
  • Workstream Leads (WSLs) have responsibilities and perform functions similar to the TSC Lead for their Workstreams including holding WS Meetings, approval and merge of technical content changes for their WS.