Skip to content

Commit 4490fd8

Browse files
leonardpahlkeleonardpahlke
committed
add tag roles governance template
Signed-off-by: leonardpahlke <[email protected]>
1 parent 8551be6 commit 4490fd8

File tree

2 files changed

+113
-1
lines changed

2 files changed

+113
-1
lines changed

Diff for: ‎tags/resources/tag-formation-templates/template-leadership-election-process.md

+12
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,15 @@
11
# Leadership election process within the `<TAG NAME>`
22

33
*tbd* - contributions are welcome!
4+
5+
## Chair
6+
7+
*tbd* - contributions are welcome!
8+
9+
## Technical Lead
10+
11+
*tbd* - contributions are welcome!
12+
13+
## Working Group Lead
14+
15+
*tbd* - contributions are welcome!

Diff for: ‎tags/resources/tag-formation-templates/template-roles.md

+101-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,103 @@
11
# Roles within the `<TAG NAME>`
22

3-
*tbd* - contributions are welcome!
3+
The TAG includes several key roles that are critical to the group's success.
4+
Beyond the roles described in this document the TAG has many contributors, all serving in varying capacities.
5+
6+
- [Roles within the `<TAG NAME>`](#roles-within-the-tag-name)
7+
- [Chair](#chair)
8+
- [Technical lead](#technical-lead)
9+
- [Working Group Lead](#working-group-lead)
10+
- [Project Lead](#project-lead)
11+
- [TOC liaison](#toc-liaison)
12+
- [Emeritus Chair](#emeritus-chair)
13+
14+
## Chair
15+
16+
A Chair drives the CNCF community efforts of the TAGs domain.
17+
Chairs are experienced leaders within the CNCF community with rooted expertise in the TAG area. Chairs serve a two-year term but may renew their term by submitting a follow-up application.
18+
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.
19+
The [leadership election process is described here](template-leadership-election-process.md#chair).
20+
21+
* Manage the operations and governance of the group.
22+
* Organize, host, plan and facilitate TAG meetings and events.
23+
* Reporting to the CNCF TOC on the status of TAG work.
24+
* Encouraging community members to start projects and working groups.
25+
* Resolve technical difficulties and decisions related to multiple sub-projects.
26+
* Remind the community of the scope of the TAG and point out guardrails in discussions, working groups, and projects.
27+
* Serve as TAG leadership representative in CNCF project discussions and at community events.
28+
* Evolve the TAG to reflect ongoing changes in the industry.
29+
* Onboard and mentor new community members.
30+
* Mentor community members in a leadership role within the TAG.
31+
* Enforce and promote diversity in TAG work.
32+
* Enforce and promote good communication in TAG efforts in accordance with the [CNCF CoC](https://www.cncf.io/conduct/)
33+
34+
## Technical lead
35+
36+
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.
37+
Proposals must have a TL or Chair working as an active sponsor.
38+
TLs are experienced contributors within the CNCF community with rooted expertise in the TAG area. TL serve a two-year term but may renew their term by submitting a follow-up application.
39+
Technical leads go through an [election process](https://github.com/cncf/toc/blob/master/tags/cncf-tags.md#elections) with a final CNCF TOC vote.
40+
The [leadership election process is described here](template-leadership-election-process.md#technical-lead).
41+
42+
**A technical lead is expected to**:
43+
* Establish and guide projects and working groups.
44+
* Resolve cross-sub-project technical difficulties and decisions.
45+
* Propose agenda items for meetings to ensure that open issues are discussed with the group when needed.
46+
* Serving as TAG leadership representative in CNCF project discussions and on community events.
47+
* Onboard and mentor new community members.
48+
* Mentor community members in a leadership role within the TAG.
49+
* Enforce and encourage diversity in the TAG efforts.
50+
* Enforce and encourage good communication in the TAG efforts following the [CNCF CoC](https://www.cncf.io/conduct/).
51+
* Support the TAG Chairs.
52+
53+
## Working Group Lead
54+
55+
A working group lead is an experienced contributor to the TAG that applies to lead along one or two others a working group.
56+
Working groups as community governance structure are defined in the [CNCF TAG](https://github.com/cncf/toc/blob/master/tags) folder.
57+
TAG Chairs are responsible facilitating the working group applications and make sure that the process is done transparent, accessible and traceable for everyone.
58+
One of the TAG chairs serves as the working group sponsor and provides guidance to the working group leads.
59+
Working group leads are signed off by the TAG Chairs and the TOC Liaisons.
60+
The [leadership election process is described here](template-leadership-election-process.md#working-group-lead).
61+
62+
**A working group lead is expected to**:
63+
* Schedule, host, plan and facilitate meetings for the working group.
64+
* Provide technical direction unique to the working group.
65+
* Plan working group deliverables.
66+
* Report to the TAG on the working group status.
67+
* Evolve the working group.
68+
* Garner active participation.
69+
* Establish documents and correct permissions for contributions to occur.
70+
* Contribute content to the working group.
71+
* Onboard and setup the working group lead successor.
72+
73+
## Project Lead
74+
75+
A project lead manages a community group for a specified period of time and works to achieve a specific outcome that has been previously discussed and agreed upon.
76+
Unlike working groups, projects require a predetermined time frame and are limited in scope and focused on a central deliverable. The project proposal must be discussed at a meeting and actively communicated to the entire TAG community.
77+
A TAG Chair or TL acts as a sponsor of the project and dedicates a portion of their time to actively support the effort.
78+
TAG Chairs must sign off on the establishment of the project group.
79+
Due to the limited scope of the role, there are no specific requirements for structuring the selection process for the project lead.
80+
The TAG Chairs are responsible for selecting a suitable project lead and must ensure that the establishment of the project is transparent, accessible, and understood by all.
81+
82+
**A project lead is expected to**:
83+
* Schedule, host, plan and facilitate meetings for the project.
84+
* Provide technical direction unique to the project.
85+
* Plan the project deliverable.
86+
* Report to the TAG on the project status.
87+
* Garner active participation.
88+
* Establish documents and correct permissions for contributions to occur.
89+
* Contribute content to the project.
90+
91+
## TOC liaison
92+
93+
The [CNCF TAG](https://github.com/cncf/toc/blob/master/tags) process identifies a TOC Liaison.
94+
The TAG Chairs are responsible for establishing effective communication with the TOC liaison, including further communication to the wider TOC upon request.
95+
96+
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).
97+
98+
## Emeritus Chair
99+
100+
After a TAG Chair completes their term, they transition into the role of Emeritus Chair.
101+
This role does not impose any obligations on the TAG, but it acknowledges their committed time and effort.
102+
The role also lets them share information about their previous work and contributions to the TAG.
103+
An Emeritus Chair retains the same rights/access as in their previous role.

0 commit comments

Comments
 (0)