-
Notifications
You must be signed in to change notification settings - Fork 634
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: leonardpahlke <[email protected]>
- Loading branch information
1 parent
8551be6
commit 4490fd8
Showing
2 changed files
with
113 additions
and
1 deletion.
There are no files selected for viewing
12 changes: 12 additions & 0 deletions
12
tags/resources/tag-formation-templates/template-leadership-election-process.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,15 @@ | ||
# Leadership election process within the `<TAG NAME>` | ||
|
||
*tbd* - contributions are welcome! | ||
|
||
## Chair | ||
|
||
*tbd* - contributions are welcome! | ||
|
||
## Technical Lead | ||
|
||
*tbd* - contributions are welcome! | ||
|
||
## Working Group Lead | ||
|
||
*tbd* - contributions are welcome! |
102 changes: 101 additions & 1 deletion
102
tags/resources/tag-formation-templates/template-roles.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,103 @@ | ||
# Roles within the `<TAG NAME>` | ||
|
||
*tbd* - contributions are welcome! | ||
The TAG includes several key roles that are critical to the group's success. | ||
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) | ||
- [Chair](#chair) | ||
- [Technical lead](#technical-lead) | ||
- [Working Group Lead](#working-group-lead) | ||
- [Project Lead](#project-lead) | ||
- [TOC liaison](#toc-liaison) | ||
- [Emeritus Chair](#emeritus-chair) | ||
|
||
## Chair | ||
|
||
A Chair drives the CNCF community efforts of the TAGs domain. | ||
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. | ||
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). | ||
|
||
* 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 diversity in TAG work. | ||
* Enforce and promote good communication in TAG efforts in accordance with the [CNCF CoC](https://www.cncf.io/conduct/) | ||
|
||
## Technical lead | ||
|
||
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. | ||
Proposals must have a TL or Chair working as an active sponsor. | ||
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. | ||
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. | ||
The [leadership election process is described here](template-leadership-election-process.md#technical-lead). | ||
|
||
**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 encourage diversity in the TAG efforts. | ||
* Enforce and encourage good communication in the TAG efforts following the [CNCF CoC](https://www.cncf.io/conduct/). | ||
* Support the TAG Chairs. | ||
|
||
## Working Group Lead | ||
|
||
A working group lead is an experienced contributor to the TAG that applies to lead along one or two others a working group. | ||
Working groups as community governance structure are defined in the [CNCF TAG](https://github.com/cncf/toc/blob/master/tags) folder. | ||
TAG Chairs are responsible facilitating the working group applications and make sure that the process is done transparent, accessible and traceable for everyone. | ||
One of the TAG chairs serves as the working group sponsor and provides guidance to the working group leads. | ||
Working group leads are signed off by the TAG Chairs and the TOC Liaisons. | ||
The [leadership election process is described here](template-leadership-election-process.md#working-group-lead). | ||
|
||
**A working group lead is expected to**: | ||
* Schedule, host, plan and facilitate meetings for the working group. | ||
* Provide technical direction unique to the working group. | ||
* Plan working group deliverables. | ||
* Report to the TAG on the working group status. | ||
* Evolve the working group. | ||
* Garner active participation. | ||
* Establish documents and correct permissions for contributions to occur. | ||
* Contribute content to the working group. | ||
* Onboard and setup the working group lead successor. | ||
|
||
## Project Lead | ||
|
||
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. | ||
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. | ||
A TAG Chair or TL acts as a sponsor of the project and dedicates a portion of their time to actively support the effort. | ||
TAG Chairs must sign off on the establishment of the project group. | ||
Due to the limited scope of the role, there are no specific requirements for structuring the selection process for the project lead. | ||
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. | ||
|
||
**A project lead is expected to**: | ||
* Schedule, host, plan and facilitate meetings for the project. | ||
* Provide technical direction unique to the project. | ||
* Plan the project deliverable. | ||
* Report to the TAG on the project status. | ||
* Garner active participation. | ||
* Establish documents and correct permissions for contributions to occur. | ||
* Contribute content to the project. | ||
|
||
## 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). | ||
|
||
## 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 retains the same rights/access as in their previous role. |