Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document TAG Roles - TAG governance template file #1116

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
104 changes: 103 additions & 1 deletion tags/resources/tag-formation-templates/template-roles.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,105 @@
# Roles within the `<TAG NAME>`

*tbd* - contributions are welcome!
<!--- **How to complete this template.** For each area, select the appropriate roles and responsibilities that align with your TAG's expected operation and adjust the language as necessary. Not all TAGs will need or use all roles, or leverage the time limits suggested, and each TAG may choose to redefine or adjust the scope of responsibilities and activities for a given role. The TOC reserves the right to define what TAG Chairs are responsible for, a sample of which have been provided here. --->

The TAG includes several key roles that are critical to the group's success.
TheFoxAtWork marked this conversation as resolved.
Show resolved Hide resolved
Beyond the roles described in this document the TAG has many contributors, all serving in varying capacities.

- [Roles within the `<TAG NAME>`](#roles-within-the-tag-name)
- [Chairs](#chairs)
- [Technical lead (TL)](#technical-lead-tl)
- [Working Group Chair](#working-group-chair)
- [Working Group technical lead](#working-group-technical-lead)
- [TOC liaison](#toc-liaison)
- [WG TAG Lead Liasion](#wg-tag-lead-liasion)
- [Emeritus Chair](#emeritus-chair)

## Chairs

The TAG Chairs drive, guide, and coordinate the TAG's efforts within the broader CNCF ecosystem and within their TAG's community. They are supported by Technical Leads in the execution of TAG activities
Chairs may be experienced leaders within the CNCF ecosystem and often have specialized domain expertise. Chairs have term limits, most commonly two years. Chairs continue to serve until removed either by an elected replacement or by the TOC.

Chair applications go through an [election process](https://github.com/cncf/toc/blob/master/tags/cncf-tags.md#elections) with a final CNCF TOC vote. The [leadership election process is described here](template-leadership-election-process.md#chair).

Chair responsibilities and expectations may include the following or delegation of the following:
* Manage the operations and governance of the group.
* Organize, host, plan and facilitate TAG meetings and events.
* Reporting to the CNCF TOC on the status of TAG work.
* Encouraging community members to start projects and working groups.
* Resolve technical difficulties and decisions related to multiple sub-projects.
* Remind the community of the scope of the TAG and point out guardrails in discussions, working groups, and projects.
* Serve as TAG leadership representative in CNCF project discussions and at community events.
* Evolve the TAG to reflect ongoing changes in the industry.
* Onboard and mentor new community members.
* Mentor community members in a leadership role within the TAG.
* Enforce and promote the [CNCF CoC](https://www.cncf.io/conduct/) and our shared community values.
* Embody and promote excellent leadership in accordance with the [Technical Leadership principles](https://github.com/cncf/toc/blob/main/PRINCIPLES.md#technical-leadership-principles)

For more information on TAG Chair responsibilities and expectations, please refer the to the TOC's description of [TAG Chairs](placeholder)

## Technical lead (TL)

A technical lead (TL) expands the bandwidth of the leadership team in terms of covering technical areas, growing the community, organizing events or doing TAG communications.
Working Groups must have a TL or Chair working as an active sponsor.
TLs are experienced contributors within TAG, often recognized as successful past project leads, through their triage and planning, content and community management, or other attributes the Chairs determine to be valued for the TAG. TLs may be term limited akin to Chairs, the recommended time-frame is two years, but is dependent upon each TAG to define as their needs and activities warrant. The [leadership election process for TLs is described here](template-leadership-election-process.md#technical-lead) <!-- UPDATE LINK AFTER THE TEMPLATE HAS BEEN COPIED -->.

**A technical lead is expected to**:
* Establish and guide projects and working groups.
* Resolve cross-sub-project technical difficulties and decisions.
* Propose agenda items for meetings to ensure that open issues are discussed with the group when needed.
* Serving as TAG leadership representative in CNCF project discussions and on community events.
* Onboard and mentor new community members.
* Mentor community members in a leadership role within the TAG.
* Enforce and promote the [CNCF CoC](https://www.cncf.io/conduct/) and our shared community values.
* Support the TAG Chairs.

## Working Group Chair

Depending on the nature of the work being pursued by the TAG, the TAG Leadership may determine, with TOC Liaison approval, that a particular project or effort warrants a longer term project.
Working Groups as community governance structure are defined in the [CNCF TOC](https://github.com/cncf/toc/tree/main/workinggroups) repository.

A Working Group technical lead is an experienced contributor to the TAG that volunteers to lead and steer a scoped activity. Each WG has between two and three chairs. The [WG Chair election process is described here](template-leadership-election-process.md). <!-- UPDATE LINK AFTER THE TEMPLATE HAS BEEN COPIED -->

**The tasks of a working group lead or project lead may include the following**:
* Schedule, host, plan and facilitate meetings for the group.
* Provide technical direction unique to the group.
* Plan group deliverables.
* Report to the TAG on the group status.
* Garner active participation.
* Establish documents and correct permissions for contributions to occur.
* Contribute content to the group.
* Onboard and setup a WG Chair successors.

## Working Group technical lead

A Working Group technical lead is an experienced contributor to the TAG that volunteers to lead a scoped activity in support to the WG Chairs.
The number of WG TLs may vary depending on the defined scope and level of effort.
The [WG TL election process is described here](template-leadership-election-process.md). <!-- UPDATE LINK AFTER THE TEMPLATE HAS BEEN COPIED -->

**The tasks of a working group lead or project lead may include the following**:
* Provide technical direction unique to the group.
* Collaborate on group deliverables.
* Report to the TAG on the group status.
* Garner active participation.
* Contribute content to the group.
* Onboard and setup WG TL successors.

## TOC liaison

The [CNCF TAG](https://github.com/cncf/toc/blob/master/tags) process identifies a TOC Liaison.
The TAG Chairs are responsible for establishing effective communication with the TOC liaison, including further communication to the wider TOC upon request.

The TOC Liaison will occasionally prioritize TAG activities, as needed by the TOC, to further the [CNCF mission](https://github.com/cncf/foundation/blob/master/charter.md#1-mission-of-the-cloud-native-computing-foundation).
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved

For more information on TOC Liaisons, their responsibilities and expectations, please refer to the [TOC Liaisons section of CNCF Tags](https://github.com/cncf/toc/tree/main/tags#toc-liaisons).

## WG TAG Lead Liasion

Following the TOC liaison for TAG model, at least one TAG co-chair or/and TL serve as liaison for each TAG WG so the co-chair or/and TL can help resolve any concerns from the WG within the TAG’s own governance. This ensures TAG Leadership remains aware and conscious of the WG’s activities, deliverables, and overall health.

## Emeritus Chair

After a TAG Chair completes their term, they transition into the role of Emeritus Chair.
This role does not impose any obligations on the TAG, but it acknowledges their committed time and effort.
The role also lets them share information about their previous work and contributions to the TAG.
An Emeritus Chair does/does not retain the same rights/access as in their previous role.