Update governance for TAG roles and WG/Project role nomination process

.github/ISSUE_TEMPLATE/presentation.md

@@ -45,4 +45,4 @@ enough time for discussion and other agenda items. (estimate) -->
 2. [ ] Then, add the topic to the Agenda of the upcoming regular meeting in the
    [meeting notes](https://docs.google.com/document/d/1TkmMyXJABC66NfYmivnh7z8Y_vpq9f9foaOuDVQS_Lo/edit).
    Format: `[NAME] Presentation: "<title of your presentation>" <link to this issue>`
-3. [ ] Post a message in the [CNCF Slack](https://communityinviter.com/apps/cloud-native/cncf) channel [#tag-environmental-sustainability](https://cloud-native.slack.com/archives/C03F270PDU6) to inform other TAG ENV members so that they can join!
+3. [ ] Post a message in the [CNCF Slack](https://communityinviter.com/apps/cloud-native/cncf) channel [#tag-environmental-sustainability](https://cloud-native.slack.com/archives/C03F270PDU6) to inform other TAG ENV contributors so that they can join!

CONTRIBUTING.md

@@ -26,7 +26,7 @@ By submitting a pull request (PR), you are agreeing to release the PR contents u
 
 Anyone interested in contributing should join the mailing list and other [communication channels](https://github.com/cncf/tag-env-sustainability#contact)
 
-We strongly encourage and support all our members to participate in anyway they can.
+We strongly encourage and support all our contributors to participate in any way they can.
 Not everyone can participate in the regularly scheduled live meetings, so we strive to make our processes friendly for people to be active contributors through asynchronous communication and contributions to our documentation in this repository.
 
 ## Github pull requests and issues
@@ -53,7 +53,7 @@ Open source is about collaboration and we are always there to support each other
 
 The purpose of this plan is to ensure that you become familiar with the team and know how you will contribute. The first step is to get yourself familiar with our mission at [Environmental Sustainability TAG charter](charter.md).
 
-New members are advised to:
+New contributors are advised to:
 
 * Join the [CNCF Slack team](https://slack.cncf.io/), particularly
   [#tag-environmental-sustainability](https://cloud-native.slack.com/archives/C03F270PDU6) channel and

governance/README.md

@@ -3,7 +3,7 @@
 Environmental Sustainability Working Group is a CNCF Working Group and reports to the Technical Oversight Committee (TOC).
 
 * [Charter](../charter.md) - mission and scope
-* [Roles](roles.md) - the work of the group is facilitated by Chairs, Technical Leads, and active group members
+* [Roles](roles.md) - the work of the group is facilitated by Chairs, Technical Leads, and active group contributors
 * [Process](process.md) - how projects are proposed and work is tracked
 * Writing [paper process](paper-process.md) - how to proceed if the proposed project include paper
 * [Presentations](presentations.md)

governance/blogpost-process.md

@@ -94,7 +94,7 @@ If a conflict cannot be resolved, ask your TAG ENV Blog Post Sponsor for assista
 
 ## Sponsorship
 
-Co-Chairs of the TAG are responsible for the content that the TAG produces, as such a Co-chair or Technical lead should be the primary "sponsor" of a blog post that allows a contributor or member of the TAG to lead the content creation, timelines, communication, and tracking approvals.
+Co-Chairs of the TAG are responsible for the content that the TAG produces, as such a Co-chair or Technical lead should be the primary "sponsor" of a blog post that allows a TAG ENV contributor to lead the content creation, timelines, communication, and tracking approvals.
 Once the "sponsor" is satisfied with the content, they notify the TOC liaison to review and provide final sign-off.
 
 As described in the previous chapter, one of the co-chairs or technical leads will assign your blogpost proposal themselves after an issue has been opened with an outline.

governance/contributor-ladder.md

@@ -45,7 +45,7 @@ By proactively driving topics that directly benefit the Environmental Sustainabi
 Once you have established connections within the TAG and actively participated in discussions and projects, you may encounter a topic that captures your interest and warrants further attention.
 This particular project might require more time and dedication from your side as well as the support of other individuals within the community.
 If you have a project idea that aligns with the objectives of the TAG, consider writing a proposal, in a GitHub issue, outlining its motivation, scope, goals, and deliverables.
-Present this proposal during a TAG meeting to initiate a discussion and gather feedback and support from fellow members.
+Present this proposal during a TAG meeting to initiate a discussion and gather feedback and support from fellow contributors.
 Taking on a [project leadership role](roles.md#role-of-project-leads) within the community project becomes your next significant step towards leadership recognition within the group.
 
 * Take ownership of a project within the TAG.
@@ -54,21 +54,21 @@ Taking on a [project leadership role](roles.md#role-of-project-leads) within the
 ## Helping out
 
 In open source, newcomers join the community need guidance and support as they embark on their journey, just as you once did.
-While it is essential to provide support to current members and leaders, it is equally important to focus on assisting and orienting newcomers.
+While it is essential to provide support to current contributors and leaders, it is equally important to focus on assisting and orienting newcomers.
 Modeling empathy and offering support to the community as a whole should be at the forefront of your actions.
 It is crucial to role model the values of the community as outlined in the [code of conduct](http://cncf.io/conduct/).
 
 There are various ways you can contribute to supporting and empowering new contributors.
 You can actively participate by offering mentorship and guidance when someone requests assistance. This could involve helping them navigate the community, providing technical guidance, or answering their questions.
-Additionally, if a member is unable to fulfill their responsibilities, you can offer to fill in their role temporarily or assist in any necessary tasks.
+Additionally, if a contributor is unable to fulfill their responsibilities, you can offer to fill in their role temporarily or assist in any necessary tasks.
 Co-hosting meetups and events is another way to provide support. By sharing the responsibility, you help create an inclusive environment where everyone feels supported and encouraged.
 
 Building a brand of being someone who consistently helps is highly valuable.
 Actions to help this include engaging in discussions, providing feedback on proposals, reviewing code contributions, and offering assistance in any way that aligns with your skills and expertise.
 By actively participating and contributing, you demonstrate your commitment to the community and showcase the values that the Environmental Sustainability TAG holds dear.
 
 * Helping out and mentor new contributors in their open source journey.
-* Helping out community members and leaders if they need support.
+* Helping out contributors and leaders if they need support.
 * Demonstrating empathy and embody the community values.
 
 ## Leading a Working Group
@@ -79,7 +79,7 @@ However, if the current working groups do not provide space for the topic you ar
 A working group must have community support and requires that you find sufficient backing before a working group is formed.
 To start this process, create a GitHub issue describing the initial charter in which you outline the motivation, scope, goals, and deliverables of the proposed working group.
 This working group charter document should form the basis for discussions with the TAG before initiating an official vote by the TAG co-chairs, which also requires approval by the CNCF TOC.
-It is important to present the working group proposal during TAG meetings and be vocal about the discussions, actively solicit feedback and input, and gain support from other members.
+It is important to present the working group proposal during TAG meetings and be vocal about the discussions, actively solicit feedback and input, and gain support from other contributors.
 
 * Taking on more responsibility and ownership within TAG.
 * Leading a community group within TAG.
@@ -112,4 +112,4 @@ Expectations of a Co-Chair:
 * Steering the TAG.
 * Coordinating between the TAG and the TOC.
 * Support and uplift other community leaders.
-* Welcome new members and help orient them.
+* Welcome new contributors and help orient them.

governance/lead-proposal-process.md

@@ -21,15 +21,13 @@ The election process for Working Group and Project leadership is more lightweigh
     - [Next Steps](#next-steps)
   - [Working Group and Project Leadership](#working-group-and-project-leadership)
     - [Process of nominations for Working Group and Project Leads](#process-of-nominations-for-working-group-and-project-leads)
-      - [Community timeline for electing Working Group and Project Leads](#community-timeline-for-electing-working-group-and-project-leads)
-      - [Submitting a nomination for Working Group and Project Leads](#submitting-a-nomination-for-working-group-and-project-leads)
 
 ## TAG Chair and TL election process
 
 ### Process of nominations for TAG Chair and TL
 
 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.
+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 contributors. Each TAG is expected to define this for themselves.
 
 The TAG ENV leadership team is conducted of:
 
@@ -38,7 +36,7 @@ The TAG ENV leadership team is conducted of:
 
 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.
+Any individual who is a TAG ENV contributor, 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:
 
@@ -117,9 +115,7 @@ If the role under nomination requires TOC approval or vote, the TAG Co-chairs ar
 
 ## Working Group and Project Leadership
 
-Working group and project leads are appointed by the TAG Chairs through the following process.
-
-### Process of nominations for Working Group and Project Leads
+Working group and project leads are appointed by the TAG Chairs according to the defined process that's outlined below.
 
 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 specified otherwise in the WG / project charter document.
@@ -135,20 +131,14 @@ The process of endorsing and selecting individuals will consider the following f
 
 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 for electing Working Group and Project Leads
+### Process of nominations for Working Group and Project Leads
 
-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.
+Following process should be followed when nominating an individual for Working Group and Project Lead role:
 
-#### Submitting a nomination for Working Group and Project Leads
+1. One of the TAG Chairs or active Working Group Chairs for the working group lead nomination must open an issue in the [tag-env-sustainability](https://github.com/cncf/tag-env-sustainability/issues) repository that will be used throughout the election process, including community voting. The issue must include information about the background for the nomination, the role that the individual is being nominated to and clarification on why the respective individual is being nominated into the role. Please refer an earlier [issue](https://github.com/cncf/tag-env-sustainability/issues/293) as an example.
 
-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 address the points specified below.
+2. GitHub issue created in step #1 must be linked in [#tag-environmental-sustainability](https://cloud-native.slack.com/archives/C03F270PDU6) channel, which is the main TAG channel, and all active sub-channels on Slack. Currently [#tag-env-wg-comms](https://cloud-native.slack.com/archives/C068XUD9AEA) and [#tag-env-wg-green-reviews](https://cloud-native.slack.com/archives/C060EDHN431) are active sub-channels.
 
-* Justification
-  * TAG Community involvement
-  * Leadership and collaboration skills
-  * Willingness to learn and expand existing technical knowledge
-* Nominee Biography
+3. Voting period starts. Everyone can vote on the GitHub issue by commenting ```+1``` for support, ```-1``` for block and ```0``` for neutral. Binding flag should be included as part of the comment: ```NB``` for non-binding which applies to all community members and TAG contributors; ```B``` for binding which applies to the TAG Chairs and Tech Leads.
+
+4. Community nominations will run for at least 2 weeks, with a maximum up to 1 month. As soon as all TAG leads vote and at least 2 weeks have passed the TAG Chairs and Tech Leads will take a vote. Upon close of nominations, a decision should be made within the next month.

governance/paper-process.md

@@ -151,9 +151,9 @@ The paper lead will need to create the paper's README.md that includes the follo
 
 * **Title**
 * **About**: covers what the paper was about, a brief summary
-* **Updates to the paper**: "intended to be a living document created and maintained for the community, by its members."
+* **Updates to the paper**: "intended to be a living document created and maintained for the community, by its contributors."
   * **Markdown**:  "maintained in markdown and all updates will be made in markdown."
-  * **Contributing updates**: "All members of the community are welcome to contribute updates. We ask potential contributors to refer to the original design decisions, listed below, as guidance when determining the content of their updates. It is highly recommended that you seek peer review for your updates beyond that of the Technical Leads and Co-Chairs of the TAG."
+  * **Contributing updates**: "All contributors of the community are welcome to add updates. We ask potential contributors to refer to the original design decisions, listed below, as guidance when determining the content of their updates. It is highly recommended that you seek peer review for your updates beyond that of the Technical Leads and Co-Chairs of the TAG."
   * **Versioning and publishing**: "It is expected that many minor updates will occur, corrections to grammar, spelling, clarification in language, translations, etc. When these occur they are considered minor changes to the overall content and will not warrant the regeneration of the PDF.  When significant changes to the intent, content, or numerous minor changes occur, the contributors will assess and determine if a new major version of the PDF needs published. When this decision is made, the markdown content will be converted to text document and sent to the CNCF technical writers to create the PDF. The PDF will then be published back into the repository annotating the new version, updating the links in the README.md accordingly.  Minor updates to the markdown shall receive a minor version bump indicated in the Metadata table of the document and recorded as WIP. When enough significant changes have been recorded, the markdown will be placed "In Review" (via PR) and solicited to the CNCF Environmental Sustainability TAG and TOC mailing list for review, at a minimum. Upon completion of review, the Environmental Sustainability TAG's TOC Liaison shall provide final approval on the PR. At which point the markdown state will be changed to "Approved" and merged."
 * **Original design decisions**: this is important as it is intended to enable the original contributors to not be gateways to content updates and allows both reviewers and future contributors to understand a create content around centralized guidance.
 * **Links**: include links to the files in the repo
@@ -167,8 +167,8 @@ To guide this process follow the steps outlines in the blog post [issue template
 
 #### Authorship, attribution and acknowledgements
 
-Papers and other resources created from the TAG Environmental Sustainability efforts are under the authorship of the TAG Environmental Sustainability, and all members who have made contributions to the document (through writing, editing, creating illustrations, etc.) are considered "Contributors".
-Members of the public or Environmental Sustainability TAG who have commented and given feedback during the Request for Comment (RFC) period of during the creation of the document are considered "Reviewers" of the project.
+Papers and other resources created from the TAG Environmental Sustainability efforts are under the authorship of the TAG Environmental Sustainability, and all contributors who have made changes to the document (through writing, editing, creating illustrations, etc.) are considered "Contributors".
+Members of the public or Environmental Sustainability TAG contributors who have commented and given feedback during the Request for Comment (RFC) period of during the creation of the document are considered "Reviewers" of the project.
 
 Individuals/groups who have made huge contributions/impact on the work can be acknowledged in an "Acknowledgements" section.
 This is to highlight stellar contributions and commitments by individuals that have went above and beyond to contribute to the project.

governance/presentations.md

@@ -1,6 +1,6 @@
 # Environmental Sustainability TAG presentations
 
-Part of the TAG activities include having guest presentations by members of the community.
+Part of the TAG activities include having guest presentations by TAG contributors or members of the broader community.
 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.