diff --git a/.github/ISSUE_TEMPLATE/presentation.md b/.github/ISSUE_TEMPLATE/presentation.md index 7f08d3bd..0a19a907 100644 --- a/.github/ISSUE_TEMPLATE/presentation.md +++ b/.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: "" <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! diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index adbeca03..1b705336 100644 --- a/CONTRIBUTING.md +++ b/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 diff --git a/governance/README.md b/governance/README.md index 9dd0c55a..b3371d83 100644 --- a/governance/README.md +++ b/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) diff --git a/governance/blogpost-process.md b/governance/blogpost-process.md index 3a1024d8..3407ec3a 100644 --- a/governance/blogpost-process.md +++ b/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. diff --git a/governance/contributor-ladder.md b/governance/contributor-ladder.md index 77984cf0..36155834 100644 --- a/governance/contributor-ladder.md +++ b/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,13 +54,13 @@ 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. @@ -68,7 +68,7 @@ Actions to help this include engaging in discussions, providing feedback on prop 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. diff --git a/governance/lead-proposal-process.md b/governance/lead-proposal-process.md index 857ecee6..3baca74b 100644 --- a/governance/lead-proposal-process.md +++ b/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 relevant sub-channels of the TAG on Slack. -* 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. diff --git a/governance/paper-process.md b/governance/paper-process.md index 3cd5ef10..45efcb59 100644 --- a/governance/paper-process.md +++ b/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. diff --git a/governance/presentations.md b/governance/presentations.md index da83c0c5..45bbe590 100644 --- a/governance/presentations.md +++ b/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. diff --git a/governance/process.md b/governance/process.md index d0d0ef66..998ab7ee 100644 --- a/governance/process.md +++ b/governance/process.md @@ -1,15 +1,10 @@ # Proposals, projects, and team -In addition to the activities driven by the -[CNCF Technical Oversight Committee][TOC], the work of the group often -originates from group members with ideas on how to reduce risk in cloud native -applications in alignment with the charter of the group and of interest and -importance to the community. +In addition to the activities driven by the [CNCF Technical Oversight Committee][TOC], the work of the group often +originates from group contributors with ideas on how to reduce risk in cloud native applications in alignment with the charter of the group and of interest and importance to the community. -This document explains how we transform ideas from our community into -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. +This document explains how we transform ideas from our community into 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) @@ -42,7 +37,7 @@ We also encourage outreach outside of the group, when there are experts who migh * A) On slack, share the issue link and ask whether others are interested in the problem and have feedback on your proposed solution or activity. -* B) Choose an upcoming meeting where you or another group member who is interested in working on the project is able to attend, then add the issue to the meeting agenda: include a link and the name of the person who will present the proposal in the "Planned Meeting" area of the [meeting notes](https://github.com/cncf/tag-env-sustainability#contact). +* B) Choose an upcoming meeting where you or another group contributor who is interested in working on the project is able to attend, then add the issue to the meeting agenda: include a link and the name of the person who will present the proposal in the "Planned Meeting" area of the [meeting notes](https://github.com/cncf/tag-env-sustainability#contact). Then at the meeting: * The presenter should screen share the github issue (or ask the meeting facilitator ahead of time to do so) and explain the motivation, expected outcome, ideas that they have for how it might happen, and ask if others have ideas or questions. * After a short discussion, people should be invited to chime in on the github issue and also mention of they are interested in collaborating. This ensures that solutions are created with multiple perspectives as well as verifies there is community interest and energy to work on the proposal. @@ -59,14 +54,14 @@ The outcome of this conversation will be: ### 3. **Accept or close the proposal.** -* A) **Accept**: assign to the Sponsor and the Project Lead(s) working on the effort, with members interested in contributing noted in the issue descriptions, along with information about expected duration, milestones, scope, and anticipated deliverables. An accepted proposal becomes an active project (see below) and the "proposal" label is removed, the "project" label is added and it is added to the backlog. +* A) **Accept**: assign to the Sponsor and the Project Lead(s) working on the effort, with interested contributors noted in the issue descriptions, along with information about expected duration, milestones, scope, and anticipated deliverables. An accepted proposal becomes an active project (see below) and the "proposal" label is removed, the "project" label is added and it is added to the backlog. * B) **Close**: a github comment on the issue should note the reason and link to discussion minutes (when decision is reached at a group meeting) or at least two members of the leadership team should be noted in agreement (which may include the person who closes the issue). * C) **Roadmap**: the issue will remain a proposal and be placed on a roadmap project board. The roadmap is reviewed quarterly. ### Active projects 1. **Track progress.** As long as work is ongoing, progress should be tracked both in the Issue and reported on periodically in meetings. - * Someone working on the project will attend weekly meetings to answer questions. In case of absence, ensure that github issues is updated and another member of the group who can attend the meeting is familiar with progress in case questions arise. + * Someone working on the project will attend weekly meetings to answer questions. In case of absence, ensure that github issues is updated and another group contributor who can attend the meeting is familiar with progress in case questions arise. * It's strongly encouraged to include a checklist in the Issue that shows what has been done and what work remains and should include a retrospective. 2. **Pull Requests.** Completed work should result in a Pull Request (PR). @@ -79,7 +74,7 @@ a comment of the PR or during a meeting, the person making the objection and the person making the proposal will be given time to present their view at the next meeting. If there are not objections, or if all concerns have been addressed, and the Pull Request has been stable for 24 hours, a Chair will add -it to the agenda for an upcoming meeting. Ideally, members who contributed to +it to the agenda for an upcoming meeting. Ideally, contributors who made changes to the project will attend that meeting to present their work or answer questions. 4. **Vote, if required.** In some cases, there's consensus to accept a diff --git a/governance/project-formation.md b/governance/project-formation.md index 6574e471..b043f2ad 100644 --- a/governance/project-formation.md +++ b/governance/project-formation.md @@ -51,8 +51,8 @@ This [PR](https://github.com/cncf/tag-env-sustainability/pull/151) serves as an 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. +* **Community Engagement and Feedback:** Transparent communication and engagement with working group contributors as well as TAG contributors 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. +* **Approval by TOC:** After reaching an agreement and alignment from the working group and TAG contributors, 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/roles.md b/governance/roles.md index eb499e5c..6b8de158 100644 --- a/governance/roles.md +++ b/governance/roles.md @@ -1,12 +1,15 @@ # Roles within the TAG Environmental Sustainability The TAG includes several community roles which are defined in this document. +The TAG doesn't have a member role. Everyone who joins the TAG starts out as a contributor, from where one can progress into one of the existing, more scoped roles within the TAG. The [contributor path document](contributor-ladder.md) gives some idea how to progress as a contributor in the TAG throughout the roles. +> Whenever "member" is mentioned in this document it means the member of the specific role group. + - [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) + - [Maintaining active role group members](#maintaining-active-role-group-members) + - [Managing role group membership](#managing-role-group-membership) - [TAG Chairs](#tag-chairs) - [TAG Technical Leads (TLs)](#tag-technical-leads-tls) - [Working Group Leads](#working-group-leads) @@ -23,11 +26,11 @@ The [contributor path document](contributor-ladder.md) gives some idea how to pr ## 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. +Contributors 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). +If you serve in any of the roles described in this document please add yourself as a role group 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 +### Maintaining active role group members * Members *SHOULD* remain active and responsive in their Roles. * Members taking an extended leave of 1 or more months *SHOULD* coordinate with other members to ensure the role is adequately staffed during the leave. @@ -35,7 +38,7 @@ If you serve in any of the roles described in this document please add yourself * Members of a role *SHOULD* remove any other members that have not communicated a leave of absence and either cannot be reached for more than 1 month or are not fulfilling their documented responsibilities for more than 1 month. This may be done through a super-majority vote of members, or if there are not enough *active* members to get a super-majority of votes cast, then removal may occur through a super-majority vote of the Chairs. * Members contribute to projects, according to the [process](process.md). -### Managing membership +### Managing role group membership * 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. @@ -45,9 +48,9 @@ If you serve in any of the roles described in this document please add yourself 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. * Primary role of Chairs is to run operations and the governance of the group. -* The Chairs are responsible for ensuring that group meetings are planned and facilitated effectively, while also engaging group members in leadership roles. Effective facilitation includes (but is not limited to) the following activities: +* The Chairs are responsible for ensuring that group meetings are planned and facilitated effectively, while also engaging group contributors in leadership roles. Effective facilitation includes (but is not limited to) the following activities: * setting the agenda for meetings - * extending discussion via asynchronous communication to be inclusive of members who cannot attend a specific meeting time. + * extending discussion via asynchronous communication to be inclusive of contributors who cannot attend a specific meeting time. * scheduling discussion of proposals that have been submitted * asking for new proposals to be made to address an identified need * partnering with Technical Leads to establish a roadmap and manage ongoing projects @@ -104,7 +107,7 @@ Environmental Sustainability TAG representatives are responsible for the followi - Reporting back to the leadership on the status of the project, indicating when the project requires external governance help. For example, these include: - Project is understaffed or suffers from rampant scope creep. - Project is inactive and needs to be discontinued. - - Inter-personal issues within leads and/or members causing disruption. + - Inter-personal issues within leads and/or contributors causing disruption. - Provide feedback to project lead to whether the current scope and operation of a project is in line with the vision and governance of the TAG. - Mentorship of project leads on matters of leadership and governance process. - Provide privilege facilities that a project lead does not have access to. @@ -143,11 +146,11 @@ The TOC Liaison will occasionally prioritize TAG activities, as needed by the TO ## Facilitation roles -Members often contribute by working in small groups that research and discuss options and then share their findings with the rest of the group in a presentation and typically contribute to the body of work in this repository (via Pull Request). +Contributors often contribute by working in small groups that research and discuss options and then share their findings with the rest of the group in a presentation and typically contribute to the body of work in this repository (via Pull Request). Some tasks can be effectively executed by simply chiming in on a github issue and independently contributing a PR without any particular role or authorization. -This section describes roles where more coordination is helpful and the work benefits from identifying one or more members who will take on specific responsibilities. -Our goal is to empower members to move forward independently, while defining an approval process designed to support communication and alignment across the wider group. +This section describes roles where more coordination is helpful and the work benefits from identifying one or more contributors who will take on specific responsibilities. +Our goal is to empower contributors to move forward independently, while defining an approval process designed to support communication and alignment across the wider group. New roles in this section are typically defined after someone has acted in that role for some time informally, then proposed as an on-going role by Pull Request which must be approved by a majority of Chairs. Process clarifications are welcome and PRs can be approved by any single Chair. @@ -165,7 +168,7 @@ In keeping with these goals, the meeting facilitator has the following responsib Prerequisites: -* active member +* active contributor * history of regular attendance One or more of the following: @@ -175,7 +178,7 @@ One or more of the following: * tech lead * co-chair -Any member who meets the above qualifications is encouraged to add themselves to the [list of people in this role](/.github/settings.yml). +Any contributor who meets the above qualifications is encouraged to add themselves to the [list of people in this role](/.github/settings.yml). ### Meeting Scribe(s) diff --git a/website/content/en/about/working-groups.md b/website/content/en/about/working-groups.md index 7d960b57..81809c7b 100644 --- a/website/content/en/about/working-groups.md +++ b/website/content/en/about/working-groups.md @@ -4,7 +4,7 @@ description: This section provides information about working groups that operate slug: working-groups --- -TAG Environmental Sustainability has working groups and teams to effectively collaborate and coordinate efforts towards achieving common goals and objectives, as well as to distribute tasks and responsibilities among its members for efficient execution. This approach allows for a more streamlined and organized approach to managing complex projects within the CNCF ecosystem. You can read more about the intention of working groups and the overall process behind submitting a working group proposal on the Technical Oversight Committee (TOC) GitHub: [CNCF Working Groups](https://github.com/cncf/toc/blob/main/workinggroups/README.md). +TAG Environmental Sustainability has working groups and teams to effectively collaborate and coordinate efforts towards achieving common goals and objectives, as well as to distribute tasks and responsibilities among its contributors for efficient execution. This approach allows for a more streamlined and organized approach to managing complex projects within the CNCF ecosystem. You can read more about the intention of working groups and the overall process behind submitting a working group proposal on the Technical Oversight Committee (TOC) GitHub: [CNCF Working Groups](https://github.com/cncf/toc/blob/main/workinggroups/README.md). Following working groups operate under the TAG Environmental Sustainability: diff --git a/writing-style.md b/writing-style.md index 524b78b3..ee826fc6 100644 --- a/writing-style.md +++ b/writing-style.md @@ -54,7 +54,7 @@ Every tool provides quite descriptive messages regarding the location of the err 3. **Markdown links.** ```markdown-link-check``` tool has a configuration file called [link-config.json](./link-config.json), that is located in the root of the repo, and it defines a set of rules that the tool following during its execution. It checks for link patterns that it should ignore and the links that should be modified to verify their validity. A good example here is where we place the images - the location for the images is different in the source code and the deployed website, therefore we need to perform validation towards a correct path which may not be the one referenced by the Markdown files in the source code (because those use the reference path that will be valid once the website is built and deployed). If the tool flags a specific link as invalid you need to verify what the error is and modify the link accordingly, on the line and in the file that the tool is referring to. For example, ```FILE: writing-style.md [✖] https://eco-qube.eu/ → Status: 410``` points to that the respective link in ```writing-style.md``` file is no longer valid and we can confirm it by navigating to the link in the browser. To fix that I would need to update ```https://eco-qube.eu``` with ```https://www.ecoqube.org```, which is its valid alternative. In some cases, for example in some of the Cloudflare-hosted websites, there is stricter protection against web scraping, which causes automated tools like ```markdown-link-check``` to return a ```403``` HTTP error upon accessing respective websites. The same error will also occur if respective websites are accessed via tools like ```cUrl``` or ```wget```. The alternative solution for tools like ```cUrl``` and ```wget``` is to use open source tools that fully simulate a browser, but this is not something that is currently supported by the ```markdown-link-check tool```. Therefore, **if the tool flags a URL as invalid, but you're able to access it via browser**, please add a ```<!-- markdown-link-check-disable-next-line -->``` flag right before the line with the link to disable checking of that link by the tool. -This guide is not extensive and if you're still experiencing issues that are not covered by this guide, don't hesitate to mention this as part of your pull request, reach out to the TAG ENV community on Slack or raise a GitHub issue and community members will be happy to help you out and progress with your work!😊 +This guide is not extensive and if you're still experiencing issues that are not covered by this guide, don't hesitate to mention this as part of your pull request, reach out to the TAG ENV community on Slack or raise a GitHub issue and the TAG ENV contributors will be happy to help you out and progress with your work!😊 ## Sources