diff --git a/governance/chair-proposal-process.md b/governance/chair-proposal-process.md deleted file mode 100644 index a4122944..00000000 --- a/governance/chair-proposal-process.md +++ /dev/null @@ -1,23 +0,0 @@ -# TAG Environmental Sustainability Leadership Team - -The leadership team of the TAG are servant leads. -They are an enabler for the group and support the creation and success of the different activities. -They are the driver for the group for not losing the higher targets out of sight and taking decisions when no consensus can be found. - -## Team Structure - -The leadership team is conducted of: - -* Three Co-Chairs -* Tech Leads - -As a TAG in the CNCF, we strive to serve the Cloud Native community, and so it is especially important to allow everyone to contribute and to create as diverse a group as possible. - -## Proposal Process - -### Environmental Sustainability TAG Chair proposal process - -1. Environmental Sustainability TAG Co-chairs operate as a team. The Co-Chair team seeks to maintain full coverage of the leadership capabilities across the key qualities of industry experience, hands-on cloud-native and sustainability experience, as well as administrative experience needed to run a Environmental Sustainability TAG. -2. If a clear successor for the exiting Co-Chair exists based on the merit of their contributions ("plant trees, carry water") and relevant experience that will benefit the TAG, based on the TAG's collective experience over time, the exiting Co-chair may nominate a successor to the TOC. -3. The exiting Co-Chair should propose the desired successor to the other Co-Chairs. If there are any objections, the Co-Chair will have the opportunity to propose another worthy candidate. If Environmental Sustainability TAG Chairs, Tech Leads and TOC Liaisons are unable to put forward a candidate, then a selection process will need to be agreed upon and executed. -4. If no new Chair candidate is available, the role will remain vacant until the Co-chair's, TOC Liaisons or CNCF TOC propose a replacement. diff --git a/governance/communication-channels.md b/governance/communication-channels.md index a2c59e3a..579e88a5 100644 --- a/governance/communication-channels.md +++ b/governance/communication-channels.md @@ -2,6 +2,9 @@ This document describes the process for creating new communication channels for the CNCF TAG Environmental Sustainability (TAG ENV). Examples of such communication channels may be: Slack channels, accounts on social media platforms, etc. +- [Process for creating communication channels for TAG Environmental Sustainability](#process-for-creating-communication-channels-for-tag-environmental-sustainability) + - [Process for creating new Slack channels](#process-for-creating-new-slack-channels) + ## Process for creating new Slack channels All Slack channels must be created in the [CNCF](https://slack.cncf.io) workspace. TAG ENV has a main channel [#tag-environmental-sustainability](https://cloud-native.slack.com/archives/C03F270PDU6) with complementary sub-channels for some working groups or projects. The goal is to always provide the main channel with meaningful information, even if a sub-channel exists. This should be done by posting the message in the main channel and posting a link to the message in the sub-channel. diff --git a/governance/github.md b/governance/github.md index 89faeac2..98067abb 100644 --- a/governance/github.md +++ b/governance/github.md @@ -1,41 +1,30 @@ # Github access permissions and administration -Facilitation roles are identified in [github settings](/.github/settings.yml) which we use for Github admin permissions and managing issues. -Write permissions are enabled by the [GitHub Settings](/.github/settings.yml) file. +The main GitHub repository for the TAG is `tag-env-sustainability`. TAG Leads have admin access to the repository and elected leads of working groups and projects maintain access which is defined in the [`cncf/people/config.yaml`](https://github.com/cncf/people/blob/main/config.yaml). -There is typically more process for review and collaboration than is controlled by access permissions. -We expect members to review [governance](/governance) and ask questions by filing a Github issue and/or submit suggested changes via Pull Request if anything is not clear. +The TAG also has technical repositories. +The [`tag-env-tooling`](https://github.com/cncf-tags/tag-env-tooling) contains smaller project, larger projects get sourced in seperate repsitories. +All technical repositories are maintained in the [`cncf-tags`](https://github.com/cncf-tags) GitHub organization. +See [`cncf-tags`](https://github.com/cncf/toc/blob/main/tags/cncf-tags-github-org.md) to find out more about the intention behind the organization. -Chairs have admin privileges and have access to change settings in the Github UI. -Except where noted below, changes should be made in the repo files to control access privileges, not in the Github UI (so they are visible to everyone.) +- [Github access permissions and administration](#github-access-permissions-and-administration) + - [Adding a commit to a TAG ENV repository](#adding-a-commit-to-a-tag-env-repository) + - [GitHub project board](#github-project-board) -Note: Members of the CNCF TOC and some CNCF staff also have admin access; however, TAG Roles will be defined transparently using files described below, and will follow TAG processes in making any changes. +## Adding a commit to a TAG ENV repository -## Settings file - -Pull Requests to appoint members to new Roles in [github settings](/.github/settings.yml) must be approved by at least one Chair, along with whatever additional required process is defined in [roles](roles.md). -When a member has multiple roles, the role defined later in the file (that does not require additional access) is noted in a comment. -PRs to remove someone from a role must be approved by the person themselves or a majority of Chairs. - -## Writing to the main branch - -The following settings are controlled in the Github UI by those with admin access. -The "main" branch is "protected" (even for admins), with these requirements: - -- can't be deleted -- no direct commits (including no "force push"), also - - at least one reviewer must approve - - must be approved by someone listed as a `collaborator` with - `push` or `admin` access - - title must not indicate work in - progress ([WIP](https://github.com/apps/wip)) - -## Housekeeping - -To maintain the main branch in a feasible way the Pull Requests shall come from forked repositories from tag-environmental-sustainability. -After which an unique name should be assigned to identify what will be changed in the forked repository by utilizing branches. +Each contributor, including TAG leadership and CNCF personnel, does not commit directly to the `main` TAG ENV branch. +To commit to the repository, create a branch off to the `main` branch, if you have maintain or admin priviledges, or a [fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) to the repository. +After changes are made to the branch or fork, the change can be proposed via a [pull request (PR)](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). After being merged the branch will be deleted. Next contributions shall be in another fresh branch. This way we keep the repository clean and allows a faster acceptance as it's clear what exactly is addressed. This highly limits the amount of branches and stops having branches around for longer then needed. + +The [`CONTRIBUTING.md`](../CONTRIBUTING.md) gives more information about how to contribute to the TAG. + +## GitHub project board + +The TAG uses a [project board](https://github.com/orgs/cncf/projects/10) to visualize and track issues. +The project board has views for working groups or projects. diff --git a/governance/lead-proposal-process.md b/governance/lead-proposal-process.md new file mode 100644 index 00000000..db2ec6bc --- /dev/null +++ b/governance/lead-proposal-process.md @@ -0,0 +1,153 @@ +# TAG Leadership election process + +The leadership team of the TAG (Chairs and TLs) as well as the extended leadership team of working group chairs and project leads are servant leads in the community. +They are an enabler for the group and support the creation and success of the different activities. +They are the driver for the group for not losing the higher targets out of sight and taking decisions when no consensus can be found. + +Roles within the TAG outlining expectations and responsibilities are defined in the [roles](roles.md) governance document. + +The election process for TAG Leadership is described in the first part of this document. +The election process for Working Group and Project leadership is more lightweight and defined in the second part of this document. + +- [TAG Leadership election process](#tag-leadership-election-process) + - [TAG Chair and TL election process](#tag-chair-and-tl-election-process) + - [Process of nominations](#process-of-nominations) + - [Community timeline](#community-timeline) + - [Submitting a nomination](#submitting-a-nomination) + - [Additional note about the TAG Chair proposal process](#additional-note-about-the-tag-chair-proposal-process) + - [General nomination requirements](#general-nomination-requirements) + - [Justification for nominees](#justification-for-nominees) + - [Announcing nomination results](#announcing-nomination-results) + - [Next Steps](#next-steps) + - [Working Group and Project Leadership](#working-group-and-project-leadership) + - [Process of nominations](#process-of-nominations-1) + - [Community timeline](#community-timeline-1) + - [Submitting a nomination](#submitting-a-nomination-1) + +## TAG Chair and TL election process + +### Process of nominations + +TAG Lead roles are open to all interested participants within the community. +Depending on the needs of the community, as determined by the current TAG leadership team (Chairs and TLs), nominations may come from working group co-chairs, TAG co-chairs and/or tech leads and/or other community members. Each TAG is expected to define this for themselves. + +The TAG ENV leadership team is conducted of: + +* Three Co-Chairs +* Tech Leads + +Final nominations will adhere to the [CNCF's TOC described process](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md#elections) as well as to the leadership nomination requirements described below. + +Any individual who is a member of the TAG ENV, it's working group's, or otherwise considered an active participant of the group may nominate another individual. + +The process of endorsing and selecting individuals will consider the following factors to ensure both the need for proper community representation and the necessary technical expertise: + +* Gender diversity +* Company diversity +* Geo diversity +* Number of nominations from different companies, people, regions for a single individual +* Existing body of work +* Justification provided during nomination + +In case there are no individuals expressing interest in taking up leadership positions, an evaluation process for the TAG / working group or project archival may be initiated, as [outlined by the TOC](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md#retirement). + +#### Community timeline + +Community nominations will run for at least 1 month, with a maximum up to 2 months. + +* For TAG Chair nominations, the TOC will take a vote as [described by the TOC](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md#elections). +* For TAG TL, TAG Chairs will vote and propose the nomination to the TOC. The TOC takes the final vote. +* For Working Group and Project Chairs, the TAG Chairs and Leads will take a vote. + +Upon close of nominations, a decision should be made within the next month. + +#### Submitting a nomination + +Nominations are to be submitted to [TAG Co-Chair's email alias](mailto:cncf-tag-env-sus-chairs@lists.cncf.io) with the details: + +* Subject `"NOMINATION $(TAG Chair, TAG TL, WG XYZ Chair): $NAME-OF-NOMINEE"` +* CC the nominee +* Justification +* Nominee Biography + +#### Additional note about the TAG Chair proposal process + +1. Environmental Sustainability TAG Co-chairs operate as a team. The Co-Chair team seeks to maintain full coverage of the leadership capabilities across the key qualities of industry experience, hands-on cloud-native and sustainability experience, as well as administrative experience needed to run a Environmental Sustainability TAG. +2. If a clear successor for the exiting Co-Chair exists based on the merit of their contributions ("plant trees, carry water") and relevant experience that will benefit the TAG, based on the TAG's collective experience over time, the exiting Co-chair may nominate a successor to the TOC. +3. The exiting Co-Chair should propose the desired successor to the other Co-Chairs. If there are any objections, the Co-Chair will have the opportunity to propose another worthy candidate. If Environmental Sustainability TAG Chairs, Tech Leads and TOC Liaisons are unable to put forward a candidate, then a selection process will need to be agreed upon and executed. +4. If no new Chair candidate is available, the role will remain vacant until the Co-chair's, TOC Liaisons or CNCF TOC propose a replacement. + +### General nomination requirements + +The TAG ENV recognizes and values the achievements of individuals who have proven themselves in this community. +If a given nominee does not meet all the requirements, the TAG leadership will still review the nomination and justification to determine if enough intent and commitment is present to move forward with an endorsement. + +**Nominees must**: + +* Be the author of at least one pull request against the TAG ENV repository +* Be active in the community within the last 3 months before their nomination + * Active - Attending at least 1 TAG ENV Regular Meeting a month + * Engaging in community chat via Slack or lists + * Commenting on PRs and issues to drive suggestions to proposals, define scope, resolve clarity issues, etc. +* Agree to the nomination + +*additional requirements may be defined in the specific [roles](roles.md) governance document* + +**Nominations must**: + +* Come from someone other than the nominee +* Have justification from the nominator regarding the nominee's capabilities + +#### Justification for nominees + +To ensure nominations are thoughtful and supported, in addition to the above requirements, a justification must enumerate on the nominee's: + +* TAG Community involvement +* Leadership and collaboration skills +* Willingness to learn and expand existing technical knowledge + +### Announcing nomination results + +The TAG leadership will release aggregate information about the nominees at the end of the nomination process. Aggregate information will not include who nominated someone. + +### Next Steps + +If the role under nomination requires TOC approval or vote, the TAG Co-chairs are responsible for coordinating and executing that in accordance with the TOC's processes (defined previously). + +## Working Group and Project Leadership + +Working group and project leads are appointed by the TAG Chairs through the following process. + +### Process of nominations + +TAG Lead roles are open to all interested participants within the community. +There are currently no limits of leadership roles for working groups or projects if not specifed otherwise in the WG / project charter document. + +The process of endorsing and selecting individuals will consider the following factors to ensure both the need for proper community representation and the necessary technical expertise: + +* Gender diversity +* Company diversity +* Geo diversity +* Number of nominations from different companies, people, regions for a single individual +* Existing body of work +* Justification provided during nomination + +In case there are no individuals expressing interest in taking up leadership positions, an evaluation process for the working group or project archival may be initiated, as [working group archival process](project-formation.md). + +#### Community timeline + +Community nominations will run for at least 2 weeks, with a maximum up to 1 months. +The TAG Chairs will take a vote. +Upon close of nominations, a decision should be made within the next month. + +#### Submitting a nomination + +One of the TAG Leads will open an issue to initiate the nomination process. +Anyone interested can add a comment to the issue to clearly show interest. +The comment should adress the points specified below. + +* Justification + * TAG Community involvement + * Leadership and collaboration skills + * Willingness to learn and expand existing technical knowledge +* Nominee Biography diff --git a/governance/meeting-host-playbook.md b/governance/meeting-host-playbook.md index 66132b94..01b6ad40 100644 --- a/governance/meeting-host-playbook.md +++ b/governance/meeting-host-playbook.md @@ -2,6 +2,16 @@ Meetings are held to coordinate and discuss TAG ENV activities. The TAG ENV leads host these meetings. The following playbook can be used for reference to structure the meeting, you don't need to stick step by step (word by word), it should give guidance how a meeting usually is structured. +- [TAG Environmental Sustainability Meeting Host Playbook](#tag-environmental-sustainability-meeting-host-playbook) + - [Requirements to host the meeting](#requirements-to-host-the-meeting) + - [Pre-Meeting](#pre-meeting) + - [During the Meeting](#during-the-meeting) + - [Preparation](#preparation) + - [Intro](#intro) + - [Agenda](#agenda) + - [End of the Meeting](#end-of-the-meeting) + - [Post-Meeting](#post-meeting) + ## Requirements to host the meeting * Install Zoom and check your settings (especially audio and video). @@ -10,10 +20,10 @@ Meetings are held to coordinate and discuss TAG ENV activities. The TAG ENV lead ## Pre-Meeting -* Add a new blank agenda entry to the meeting notes by copying the template and editing the details accordingly. -* Announce a day in advance in Slack to add agenda items to meeting notes. +* Add a new blank agenda entry to the [meeting notes](https://bit.ly/cncf-tag-env-meeting-notes) by copying the template and editing the details accordingly. +* Announce a day in advance in Slack to add agenda items to [meeting notes](https://bit.ly/cncf-tag-env-meeting-notes). * Announce the meeting about an hour before in the `#tag-env-sustainability` Slack channel. -* Announce the meeting over [social media](https://github.com/cncf/tag-env-sustainability#contact) a day before. If there is a special presentation / occasion, you may want to announce it a total of two times a week in advance. +* Announce the meeting over [social media](https://github.com/cncf/tag-env-sustainability#contact) a day before. If there is a special presentation / occasion. You may want to announce it a total of two times a week in advance. ```markdown Hi folks! The CNCF TAG ENV bi-weekly meeting takes place 1 hour from now. diff --git a/governance/paper-process.md b/governance/paper-process.md index a496d6a7..50e89098 100644 --- a/governance/paper-process.md +++ b/governance/paper-process.md @@ -3,6 +3,27 @@ This document is intended to provide a consistent mechanism for cloud native environmental sustainability to produce community papers, ensure they are reviewed, and subsequently published. Content of this document does not supersede existing processes and is intended to be used in conjunction with [existing proposal to project instructions](process.md). +- [Process for creating papers](#process-for-creating-papers) + - [Proposal](#proposal) + - [Project](#project) + - [Tentative schedule milestones](#tentative-schedule-milestones) + - [Milestones](#milestones) + - [Audience, Goals, and refining scope](#audience-goals-and-refining-scope) + - [Tasking assignment](#tasking-assignment) + - [Content rough-in](#content-rough-in) + - [Opinions](#opinions) + - [References](#references) + - [Collaborative](#collaborative) + - [Executive summary and content wrap-up](#executive-summary-and-content-wrap-up) + - [Narrative voice](#narrative-voice) + - [Final group review](#final-group-review) + - [Community Review](#community-review) + - [Public comment adjudication](#public-comment-adjudication) + - [CNCF publishing engagement](#cncf-publishing-engagement) + - [Addition to the repo](#addition-to-the-repo) + - [Blog publishing and coordination](#blog-publishing-and-coordination) + - [Authorship, attribution and acknowledgements](#authorship-attribution-and-acknowledgements) + ## Proposal If a proposal is made that includes a paper as a deliverable, the proposal needs to ensure that there is a clearly identified lead and a well defined paper scope. diff --git a/governance/presentations.md b/governance/presentations.md index 4f533436..282b8b4f 100644 --- a/governance/presentations.md +++ b/governance/presentations.md @@ -5,6 +5,9 @@ We welcome any topic related to our mission and charter. Typical topics include projects, real-world use-cases, challenges or success stories. However, presentations must follow the following guidelines. +- [Environmetal Sustainability TAG presentations](#environmetal-sustainability-tag-presentations) + - [Guidelines](#guidelines) + ## Guidelines - Presentations are encouraged to expose the TAG to cloud native open source projects, cloud native sustainability concepts, and environmental conservation oriented groups. diff --git a/governance/process.md b/governance/process.md index eadf7c79..d0d0ef66 100644 --- a/governance/process.md +++ b/governance/process.md @@ -11,6 +11,13 @@ projects with a defined set of deliverables or a team to focus on a larger stream of work that may involve one or more projects and activities. +- [Proposals, projects, and team](#proposals-projects-and-team) + - [Creating, discussing and accepting proposals](#creating-discussing-and-accepting-proposals) + - [1. **Raise an Issue**](#1-raise-an-issue) + - [2. **Ask the group for collaboration**](#2-ask-the-group-for-collaboration) + - [3. **Accept or close the proposal.**](#3-accept-or-close-the-proposal) + - [Active projects](#active-projects) + ## Creating, discussing and accepting proposals Each proposal is unique and might deviate slightly from the process below. diff --git a/governance/project-formation.md b/governance/project-formation.md new file mode 100644 index 00000000..22020f9e --- /dev/null +++ b/governance/project-formation.md @@ -0,0 +1,58 @@ +# Working Group and Project formation Guide + +This document describes how to create a new project or working group in the TAG ENV. + +- [Working Group and Project formation Guide](#working-group-and-project-formation-guide) + - [Working Group or Project creation](#working-group-or-project-creation) + - [Discuss the Working Group or Project idea in the community](#discuss-the-working-group-or-project-idea-in-the-community) + - [How to write a charter document](#how-to-write-a-charter-document) + - [Finding Leads](#finding-leads) + - [Start the Working Group or Project](#start-the-working-group-or-project) + - [Working Group or Project archival](#working-group-or-project-archival) + +## Working Group or Project creation + +### Discuss the Working Group or Project idea in the community + +To discuss the project or working group follow the [process](process.md). +After the project has been discussed and should be followed up, the contributors need to work on a charter document. + +### How to write a charter document + +The following structure should be used to write the charter document. +The charter inherits the TAG ENV charter and should not be repeated. +You can browse existing charter documents for [working-groups here](../working-groups/). + +1. **Title and Introduction**: Start with a brief introduction that states the purpose of the document. Mention the project's affiliation, purpose and role under the TAG ENV. +2. **Motivation**: Explain the reasons behind forming the project. Describe the challenges, objectives, and goals it aims to address. Make it clear why the project is necessary and how it supports the broader mission of its parent organization. +3. **Scope**: Define the boundaries of the project's responsibilities. Clearly state what the project will and will not do. +4. **Goals**: List the specific objectives that the project aims to achieve. These should be measurable and related to the overall purpose of the group. Ensure that your goals are aligned with the motivation and scope of the group. +5. **Non-Goals**: Highlight what the project will not do. These are activities or responsibilities that are outside the group's scope. It's important to make these non-goals explicit to avoid misunderstandings and scope creep. +6. **Deliverables**: Detail what the project will produce or accomplish. Be specific about the expected outcomes and any documentation, tools, or processes that will be created. + +### Finding Leads + +To start the working group and project, contributor need to take ownership. +Roles are described in the [roles](roles.md) document. + +* A working group needs to have two or three Chairs. Working group tech leads can be added additionally. +* A project needs to have one or more project leads. + +How these leads get elected are defineed in the [lead election](lead-proposal-process.md) document + +### Start the Working Group or Project + +To start the working group or project open a PR to propose adding the charter document to the TAG repository. +The PR should also update the website and other parts of the repository to record the project accordingly. +This [PR](https://github.com/cncf/tag-env-sustainability/pull/151) serves as an example. + +## Working Group or Project archival + +Evaluation process for working group archival will follow the guidelines, as outlined below: + +* **Purpose and Relevance Review:** A review of the working group's initial purpose and its relevance in the current context will be conducted to determine whether the group's objectives have been achieved or remain essential for the community. If there are specific objectives that can be integrated into the scope of other working groups that exist within the Technical Advisory Group (TAG) or fall under the overall TAG's objectives, necessary efforts will be made to facilitate the transition of such objectives. +* **Community Engagement and Feedback:** Transparent communication and engagement with working group members as well as TAG members will be initiated to seek their feedback and opinions on the potential working group archival decision. This inclusive approach ensures that community interests and perspectives are considered. +* **Documentation:** Detailed documentation of discussions and the rationale for the working group archival decision will be recorded, preserving historical context and providing clarity on the decision-making process. +* **Public Announcement:** In the event that the working group is considered for archival, a public announcement will be made to communicate the decision and its underlying reasons to the wider community. This announcement aims to prevent any confusion and foster transparency. +* **Evaluation Period:** To ensure adaptability, a designated evaluation period may be specified, allowing for reevaluation of the working group archival decision if future changes in project needs or community dynamics arise. +* **Approval by TOC:** After reaching an agreement and alignment from the working group and TAG members, the working group archival decision will be submitted to the Technical Oversight Committee (TOC) for approval. Upon receiving approval from the TOC, the working group will be formally archived, and the archival process will be finalized. diff --git a/governance/publishing-deliverables.md b/governance/publishing-deliverables.md index 83d61aa4..417a7304 100644 --- a/governance/publishing-deliverables.md +++ b/governance/publishing-deliverables.md @@ -3,6 +3,16 @@ As part of regular business of TAG Environmental Sustainability, we publish several artifacts as deliverables coming out of different projects. The following guide is intended to help future project leads to deliver their artifacts by learning from past experiences of delivering such artifacts. +- [Guidance on Publishing and Delivering Artifacts](#guidance-on-publishing-and-delivering-artifacts) + - [Using GitHub Issues to Track Progress](#using-github-issues-to-track-progress) + - [Identifying External Dependencies](#identifying-external-dependencies) + - [Get Help from CNCF Service Desk](#get-help-from-cncf-service-desk) + - [Define Stages of Publication](#define-stages-of-publication) + - [Write a Blog](#write-a-blog) + - [Common Mistakes to Avoid](#common-mistakes-to-avoid) + - [Sharing Far and Wide](#sharing-far-and-wide) + - [Take Ownership and Give Credit](#take-ownership-and-give-credit) + ## Using GitHub Issues to Track Progress All deliverables need a single place where, anyone can go to: diff --git a/governance/roles.md b/governance/roles.md index b014952a..8c6eb888 100644 --- a/governance/roles.md +++ b/governance/roles.md @@ -1,29 +1,31 @@ # Roles within the TAG Environmental Sustainability -The TAG includes several key roles that are critical to the group's success. -The group will have many members, all serving in varying capacities. -Within this document, "member" may refer to a Chair, a Technical Lead, or other Member roles. - -Through the high variety of inputs we received during the TAG creation phase and the different perspectives displayed, a member structure similar to a TAG will be suitable. - -The following is the current listing of member roles: - -* [Chairs](#role-of-chairs) -* [Technical Leads](#role-of-technical-leads) -* [Project Leads](#role-of-project-leads) -* [TAG Representatives](#role-of-environmental-sustainability-tag-representatives) -* Team leads -* Group Members -* [TOC Liaison](#toc-liaison) -* [Facilitation Roles](#facilitation-roles) - -Members fulfilling any Roles in the TAG are responsible for understanding and abiding by the governance and policies defined in this group. -This commitment and execution of understanding includes not only commits to the repo, but also to any approvals or direction required by their Role. - -## Serving as a member in a specific role - -Each role has a different scope and responsibility to it, please refer to the role specific sections below for more information in terms of process, requirements and expectations. -If you serve in any of the roles described in this document please add yourself as a member with a Pull Request (PR) to this [file](https://github.com/cncf/people/blob/80529e2dac7b7e00cd385dbec2d3e6c7d04a1cfb/config.yaml#L1083). +The TAG includes several community roles which are defined in this document. +The [contributor path document](contributor-ladder.md) gives some idea how to progress as a contributor in the TAG throughout the roles. + +- [Roles within the TAG Environmental Sustainability](#roles-within-the-tag-environmental-sustainability) + - [General information serving in any role](#general-information-serving-in-any-role) + - [Maintaining active members](#maintaining-active-members) + - [Managing membership](#managing-membership) + - [TAG Chairs](#tag-chairs) + - [TAG Technical Leads (TLs)](#tag-technical-leads-tls) + - [Working Group Leads](#working-group-leads) + - [Duties of a Working Group Chair](#duties-of-a-working-group-chair) + - [Working Group Tech Leads](#working-group-tech-leads) + - [Duties of a Environmental Sustainability TAG representative](#duties-of-a-environmental-sustainability-tag-representative) + - [Project Lead](#project-lead) + - [Duties of a project lead](#duties-of-a-project-lead) + - [TOC Liaison](#toc-liaison) + - [Facilitation roles](#facilitation-roles) + - [Meeting facilitator](#meeting-facilitator) + - [Meeting Scribe(s)](#meeting-scribes) + - [Project teams](#project-teams) + +## General information serving in any role + +Members fulfilling any roles in the TAG are responsible for understanding and abiding by the governance defined in this group. +Each role has a scope and responsibility to it, please refer to the role specific sections below for more information in terms of process, requirements and expectations. +If you serve in any of the roles described in this document please add yourself as a member with a Pull Request (PR) to `tag-env-sustainability` in the [`cncf/people/config.yaml` file](https://github.com/cncf/people/blob/main/config.yaml). ### Maintaining active members @@ -38,7 +40,7 @@ If you serve in any of the roles described in this document please add yourself * Membership disagreements may be escalated to the Chairs. Disagreements among the Chairs may be escalated to a Environmental Sustainability TAG TOC Liaison. * Members *MAY* decide to step down at anytime and optionally propose a replacement. -## Role of chairs +## TAG Chairs The Chairs serve in administrative roles, guiding the TAG and support the decision taking. However, due to the pure complexity of the TAG topic, the role of the chairs include also the activities of technical leads. @@ -50,7 +52,7 @@ The Chairs serve in administrative roles, guiding the TAG and support the decisi * asking for new proposals to be made to address an identified need * partnering with Technical Leads to establish a roadmap and manage ongoing projects -## Role of technical leads +## TAG Technical Leads (TLs) Technical Leads (TLs) expand the bandwidth of the leadership team. Proposals must have a TL or Chair working as an active sponsor (as detailed in [TAG process](process.md)). @@ -63,47 +65,32 @@ The general list of activities for TL are: [Environmental Sustainability TAG TL nomination process](tech-lead-proposal-process.md) -## Role of project leads - -Project Leads lead specific projects where a deliverable has been defined within the issue. - -Project Leads are nominated and approved by the following process: +## Working Group Leads - 1. Project Lead actively participates in the group, initiates the proposal or volunteers to take on a project that has been prioritized by the group - 1. A Chair or TL nominates a candidate, or requests the community to nominate in a slack thread - 1. The issue is updated with the assignment of the project lead as "assignee" alongside the TAG Leadership member. - 1. Project Leads will be given the OWNER role of the directory or sub-directory for their team's activities in order to empower merge/approve. - -### On-going projects - -On the occasion where a project becomes long term, Project Leads are also given the OWNER role of the directory or sub-directory along with 1 other nominated individual to ensure continuity in review and ongoing support of the project. +On the occasion where a project becomes long term, a working group can be formed. +The process document gives information how to form a [working group](process.md). Depending on the expected length of the project, Project Leads may be assigned as OWNERS of the project directory in this repository to help facilitate and moderate new content to the project. -### Duties of a project lead +### Duties of a Working Group Chair -Project leads are responsible for the following: +Working group chairs are responsible for the following: - Adhering to the [project process](process.md) -- Proposing and refining the project scope, goal and schedule -- Ensure smooth day-to-day operations of the project. This includes: +- Proposing and refining the working group scope, goal and schedule as a charter document +- Ensure smooth day-to-day operations of the working group. This includes: - Ensuring meetings are scheduled, announced and recorded - Facilitation of meetings, ensuring minutes are recorded -- Ensure progress and status reports are communicated to the TAG representative of the project -- Resolving conflict within the project and escalating to leadership when required -- Outreach and recruitment for the project -- Provide retrospective of a project to the TAG +- Ensure progress and status reports are communicated to the TAG representative of the working group +- Resolving conflict within the working group and escalating to leadership when required +- Outreach and recruitment for the working group -## Role of Environmental Sustainability TAG representatives +### Working Group Tech Leads -Environmental Sustainability TAG representatives are leadership executive sponsors of a project. -The TAG representative acts as a point of liaison with the TAG leadership team and takes on a role of mentorship for the project lead(s). +Working group tech leads are executive contributors of the project. +Tech leads extend the working group chair leadership team. -TAG Environmental Sustainability representatives are required to be part of the TAG leadership team. -This includes co-chairs, technical leads and co-chair emeritus roles. -A TAG representative may be of capacity of an individual contributor but cannot be the project lead of the same project they are representing. - -Environmental Sustainability TAG representatives are appointed through the following process: +TAG ENV representatives are appointed through the following process: - A member of the leadership indicates that they would like to be a TAG representative on a project by: - editing the issue's "TAG Representative" field to their github ID. @@ -128,7 +115,26 @@ Examples are: - Uploading of meeting recordings to youtube - Approval of messages to TAG mailing list -## TOC liaison +## Project Lead + +A project can be formed if corss contributor collaboration is needed. +The process document gives information how to form a [project](process.md). + +Depending on the expected length of the project, Project Leads may be assigned as OWNERS of the project directory in this repository to help facilitate and moderate new content to the project. + +### Duties of a project lead + +Project leads are responsible for the following: + +- Adhering to the [project process](process.md) +- Proposing and refining the project scope, goal and schedule +- Ensure smooth operations of the project. This includes: + - Ensuring meetings are scheduled, announced and recorded. Recordings are facilitated by a TAG lead. +- Ensure progress and status reports are communicated to the TAG representative of the project +- Resolving conflict within the project and escalating to leadership when required +- Provide retrospective of a project to the TAG + +## TOC Liaison The TOC Liaison for the Environmental Sustainability TAG is nominated by the TOC. The TAG Chairs are responsible for establishing effective communication with the TOC liaison, including further communication to the wider TOC upon request. diff --git a/governance/tech-lead-proposal-process.md b/governance/tech-lead-proposal-process.md deleted file mode 100644 index 13bf7d01..00000000 --- a/governance/tech-lead-proposal-process.md +++ /dev/null @@ -1,97 +0,0 @@ - -# Environmental Sustainability TAG Technical Lead Proposal Process - -TAG Environmental Sustainability Technical Leads operate as a team alongside the TAG co-chairs. -The Technical Lead Team enhances the leadership capabilities of the existing co-chairs across the key qualities of industry experience, hands-on cloud-native, ESG experience (Environmental, Social, and Governance) as well as administrative experience needed to assist in the execution of the various projects and efforts. - -## Caveats of Technical Leads - -* The position of a technical lead does not guarantee future co-chair nomination -* The position of a technical lead is not a paid position (co-chairs are also not paid positions) -* Technical leads [have responsibilities](roles.md) to the Environmental Sustainability TAG, the leadership team, and the TOC -* Nominations by the community, with endorsements by 1 or more co-chairs, and [TOC approval](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md#elections) - -## Process of nominations - -Depending on the needs of the community, as determined by the Environmental Sustainability TAG leadership team, technical lead nominations may come in the form of "Nominees by community", "Nominees by co-chairs", or both. - -The Environmental Sustainability TAG does not have a current limit on the amount of technical leads. - -Final technical lead nominations will adhere to the [CNCF's TOC described process](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md#elections). - -### Nominees by community - -Community nominees should adhere to the technical lead nomination requirements described below. -Any individual who is a member of the Environmental Sustainability TAG list or the tag-environmental-sustainability slack channel may nominate another individual. - -The co-chairs reserve the right to endorse a nominee by the community based on: - -* Gender diversity -* Company diversity -* Geo diversity -* Amount of nominations from different companies, people, regions for a single individual -* Existing body of work -* Justification provided during nomination - -#### Community timeline - -Community nominations will run for at least 1 month with a maximum up to 2 months. -Upon close of nominations a decision will be made by the co-chairs within the next month in order to conform to the TOC process. - -#### Submitting a nomination - -Nominations are to be submitted to [Environmental Sustainability TAG Co-Chairs email alias](mailto:cncf-tag-env-sus-chairs@lists.cncf.io) with the details: - -* Subject "Technical Lead nomination: $NAME-OF-NOMINEE" -* CC the nominee -* TL requirements with examples (described below) -* Justification - -#### Endorsement of community nominees - -Co-chairs are responsible for providing endorsement of a community nominee to show concurrence and support. - -If no nominees are submitted by the community either as a result of lack of participation, lack of requirements, or from co-chair specific selection (non-community nomination process), the co-chairs must endeavor to nominate an individual(s) that meet as many of the requirements as exist. - -### Nominees by co-chairs - -Nominees by co-chairs adhere to the technical lead requirements described below. -Co-chairs are responsible for documenting statistic information of all nominee types for endorsement and presentation to the TOC. - -## Technical Lead nomination requirements - -In order to verify nominees by the community or by co-chairs have experience with the group and are actively contributing in a meaningful way, the following requirements must be met in order for an individual to be nominated. -At TAG Environmental Sustainability, we maintain a meritocracy in which we recognize and value the achievements of individuals who have proven themselves in this community. - -If a given nominee does not meet all the requirements, the co-chairs will still review the nomination and justification to determine if enough intent and commitment is present to move forward with an endorsement. - -Nominees must: - -* have been project or review lead on at least one project or assessment/review -* be the author of at least one pull request against the Environmental Sustainability TAG repository -* be active in the community within the last 6 months prior to their nomination. - * active - Attending at least 1 Environmental Sustainability TAG Regular Meeting a month - * engaging in community chat via slack or lists - * commenting on PRs and issues to drive suggestions to proposals, define scope, resolve clarity issues, etc. -* agree to the nomination - -Nominations must: - -* come from someone other than the nominee -* have justification from the nominator regarding the nominee's capabilities - -### Justification for nominees - -To ensure nominations are thoughtful and supported, in addition to the above requirements, a justification must enumerate on the nominee's: - -* TAG Community involvement -* leadership skills -* conflict resolution (technical and non-technical) -* mentorship -* willingness to learn and expand existing technical knowledge -* and any known affiliations or group memberships (if applicable) - -## Announcing nomination results - -The co-chairs will release aggregate information about the nominees at the end of the nomination process once the Technical Leads have been put forward for approval by the TOC. -Aggregate information will not include who nominated someone. diff --git a/governance/working-group-archival-process.md b/governance/working-group-archival-process.md deleted file mode 100644 index d9a35fb8..00000000 --- a/governance/working-group-archival-process.md +++ /dev/null @@ -1,18 +0,0 @@ -# Environmental Sustainability TAG Working Group Archival Process - -Working group co-chairs are responsible for providing endorsement of a community nominee to show concurrence and support. - -If no nominees are submitted by the community and/or working group/TAG co-chairs or tech leads, either as a result of lack of participation or lack of requirements, the working group co-chairs must endeavor to nominate an individual(s) that meet as many of the requirements as exist. - -However, should there be a situation where there are still no individuals expressing interest in taking up leadership positions within the working group, an evaluation process for working group archival will be initiated. - -## Working Group archival process guidelines - -Evaluation process for working group archival will follow the guidelines, as outlined below: - -* **Purpose and Relevance Review:** A review of the working group's initial purpose and its relevance in the current context will be conducted to determine whether the group's objectives have been achieved or remain essential for the community. If there are specific objectives that can be integrated into the scope of other working groups that exist within the Technical Advisory Group (TAG) or fall under the overall TAG's objectives, necessary efforts will be made to facilitate the transition of such objectives. -* **Community Engagement and Feedback:** Transparent communication and engagement with working group members as well as TAG members will be initiated to seek their feedback and opinions on the potential working group archival decision. This inclusive approach ensures that community interests and perspectives are considered. -* **Documentation:** Detailed documentation of discussions and the rationale for the working group archival decision will be recorded, preserving historical context and providing clarity on the decision-making process. -* **Public Announcement:** In the event that the working group is considered for archival, a public announcement will be made to communicate the decision and its underlying reasons to the wider community. This announcement aims to prevent any confusion and foster transparency. -* **Evaluation Period:** To ensure adaptability, a designated evaluation period may be specified, allowing for reevaluation of the working group archival decision if future changes in project needs or community dynamics arise. -* **Approval by TOC:** After reaching an agreement and alignment from the working group and TAG members, the working group archival decision will be submitted to the Technical Oversight Committee (TOC) for approval. Upon receiving approval from the TOC, the working group will be formally archived, and the archival process will be finalized. diff --git a/governance/working-group-chair-proposal-process.md b/governance/working-group-chair-proposal-process.md deleted file mode 100644 index ce3b6a37..00000000 --- a/governance/working-group-chair-proposal-process.md +++ /dev/null @@ -1,80 +0,0 @@ -# Environmental Sustainability TAG Working Group Chair Proposal Process - -TAG Environmental Sustainability Working Group Chairs operate as a team alongside the TAG's co-chairs and technical leads. -They provide guidance and directions to the working group members and ensure that the working group's efforts are in line with it's mission and values, as well as the overall goals of the TAG. They facilitate the working group's activities and coordinate its members' efforts. They schedule working group meetings, set meeting agenda, and maintain effective communication to ensure smooth collaboration among the working group's participants. -Finally, they provide regular updates to the TAG, keeping the TAG leadership team and members informed about the group's progress and deliverables. - -## Caveats of Working Group Chairs - -* The position of a working group chair is not a paid position (TAG co-chairs and tech leads are also not paid positions) -* Working group Chairs [have responsibilities](roles.md) to the Environmental Sustainability TAG, the leadership team, and the TOC -* Nominations made by the community, need endorsements by 1 or more working group/TAG co-chairs, or tech leads - -## Process of nominations - -The working group's leadership roles are open to all interested participants within the community. Depending on the needs of the community, as determined by the Environmental Sustainability TAG leadership team, working group chair nominations may come from working group co-chairs, TAG co-chairs and/or tech leads and/or other community members. - -The Environmental Sustainability TAG does not have a current limit on the amount of working group chairs. - -Final working group chair nominations will adhere to the [CNCF's TOC described process](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md#elections). - -Nominees should adhere to the working group chair nomination requirements described below. - -Any individual who is a member of the Environmental Sustainability TAG list or the tag-environmental-sustainability slack channel may nominate another individual. - -The process of endorsing and selecting individuals will take into account following factors to ensure both the need for proper community representation and the necessary technical expertise: - -* Gender diversity -* Company diversity -* Geo diversity -* Amount of nominations from different companies, people, regions for a single individual -* Existing body of work -* Justification provided during nomination - -In case there are no individuals expressing interest in taking up leadership positions within the working group, an evaluation process for the working group archival may be initiated, as outlined in [Environmental Sustainability TAG Working Group Archival Process](https://github.com/cncf/tag-env-sustainability/blob/main/governance/working-group-archival-process.md). - -### Community timeline - -Community nominations will run for at least 1 month with a maximum up to 2 months. -Upon close of nominations a decision will be made by the working group co-chairs within the next month. - -### Submitting a nomination - -Nominations are to be submitted to [Environmental Sustainability TAG Co-Chairs email alias](mailto:cncf-tag-env-sus-chairs@lists.cncf.io) with the details: - -* Subject "Working Group $NAME-OF-WORKING-GROUP chair nomination: $NAME-OF-NOMINEE" -* CC the nominee -* Justification - -## Working Group Chair nomination requirements - -In order to verify nominees by the community or by working group/TAG co-chairs have experience with the group and are actively contributing in a meaningful way, the following requirements must be met in order for an individual to be nominated. -At TAG Environmental Sustainability, we maintain a meritocracy in which we recognize and value the achievements of individuals who have proven themselves in this community. - -If a given nominee does not meet all the requirements, the working group co-chairs will still review the nomination and justification to determine if enough intent and commitment is present to move forward with an endorsement. - -Nominees must: - -* be the author of at least one pull request against the Environmental Sustainability TAG repository -* be active in the community within the last 3 months prior to their nomination - * active - Attending at least 1 Environmental Sustainability TAG Regular Meeting a month - * engaging in community chat via slack or lists - * commenting on PRs and issues to drive suggestions to proposals, define scope, resolve clarity issues, etc. -* agree to the nomination - -Nominations must: - -* come from someone other than the nominee -* have justification from the nominator regarding the nominee's capabilities - -### Justification for nominees - -To ensure nominations are thoughtful and supported, in addition to the above requirements, a justification must enumerate on the nominee's: - -* TAG Community involvement -* leadership and collaboration skills -* willingness to learn and expand existing technical knowledge - -## Announcing nomination results - -The working group co-chairs will release aggregate information about the nominees at the end of the nomination process. Aggregate information will not include who nominated someone.