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.

Sign up for GitHub

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

Document TAG Roles - TAG governance template file #1116

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4490fd8
add tag roles governance template
leonardpahlke Jul 12, 2023
649b2e5
Update tags/resources/tag-formation-templates/template-roles.md
leonardpahlke Jul 13, 2023
b3364b9
merge wg and project sections
leonardpahlke Jul 13, 2023
b9462d2
update roles template
leonardpahlke Nov 21, 2024
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
12 changes: 12 additions & 0 deletions tags/resources/tag-formation-templates/template-leadership-election-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,15 @@
# Leadership election process within the `<TAG NAME>`
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved

*tbd* - contributions are welcome!

## Chair

*tbd* - contributions are welcome!

## Technical Lead

*tbd* - contributions are welcome!
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One thought I'd like to share here is that it would be beneficial to have a more data driven/evidential approach to identifying tech lead candidates. The thinking here is that whilst community activities (chop wood and carry water) are valuable, having deep seated expertise is a fantastic way to build trust with projects and act as the bridge between community and contributor.

I feel a fair way to assist in this might be to ask any nominee to contribute three examples of their work within the field that demonstrate aptitude and appropriateness for the role. As part of the election process this also gives the committee more substantive information to elect the appropriate representative.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍, interesting thought. We should keep it in mind for upcoming discussions. Since this PR doesn't make any other changes to this document, which templates the election process (just the headers to make the links), we'll pick this up in a follow-up PR. I will keep the discussion open nonetheless so others see it.


## Working Group Lead

*tbd* - contributions are welcome!
102 changes: 101 additions & 1 deletion tags/resources/tag-formation-templates/template-roles.md
View file
Open in desktop
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.
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)
- [Chair](#chair)
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved
- [Technical lead](#technical-lead)
- [Working Group Lead](#working-group-lead)
- [Project Lead](#project-lead)
- [TOC liaison](#toc-liaison)
- [Emeritus Chair](#emeritus-chair)

## Chair
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved

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/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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/)
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 diversity in TAG work.
* Enforce and promote good communication in TAG efforts in accordance with the [CNCF CoC](https://www.cncf.io/conduct/)
* 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)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@erinaboyd - Leo pulled together an initial list pertinent to the specific TAG operations, I'm sure there are elements here you've already captured in your draft for Chair responsibilities. I've added a placeholder here on line 38 for when we've got them drafted in a PR. I'd think keeping our defined responsibilities and expectations separate from the template here (for use by TAGs) is reasonable. What are your thoughts?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect. I will add the proposed suggestion already, but keep this discussion open, so we don't lose track, to update the placeholder, and add possible other suggestions.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@erinaboyd, if you find a bit of time, could you take at this section? Thanks! :)

@erinaboyd - Leo pulled together an initial list pertinent to the specific TAG operations, I'm sure there are elements here you've already captured in your draft for Chair responsibilities. I've added a placeholder here on line 38 for when we've got them drafted in a PR. I'd think keeping our defined responsibilities and expectations separate from the template here (for use by TAGs) is reasonable. What are your thoughts?


## 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.
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved
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.
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved
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
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved

A working group lead is an experienced contributor to the TAG that applies to lead along one or two others a working group.
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved
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).
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved

**A working group lead is expected to**:
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved
* 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's consolidate this with the Working Group Leads under a Group Lead function. One may be time-limited/deliverable oriented, the other may be focused groups for ongoing and continual activities. So long as these are defined by the TAG, and approved by the TOC liaisons, the general responsibilities are not much different except in the specifics of implementation.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, good idea. I will merge both sections. 👍

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

b3364b9


## 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

## 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.
leonardpahlke marked this conversation as resolved.
Show resolved Hide resolved