├── MEMBER_EXPECTATIONS.md ├── README.md ├── CHARTER.md ├── WORKING_GROUPS.md └── MODERATION_POLICY.md /MEMBER_EXPECTATIONS.md: -------------------------------------------------------------------------------- 1 | All participants in the webpack project must follow the 2 | [Code of Conduct][]. There are further expectations for members of the [TSC][]. 3 | 4 | When decisions are made within the established guidelines and policies of the 5 | project, those in leadership roles have a responsibility to uphold and respect 6 | the decision even if they disagree with it. This is especially important in 7 | external communications, for example in social media. Should the member be 8 | unwilling or unable to do so, then they should resign their leadership position. 9 | This does not mean that decisions cannot be revisited and discussed within the 10 | team at a later time. 11 | 12 | Everyone participating in the webpack project must conduct themselves in 13 | a professional and respectful manner in accordance with our 14 | [Code of Conduct][]. In addition, some general guidelines for 15 | leadership group members include: 16 | 17 | - Remediate quickly when you realize you made a mistake. Leaders are human, 18 | and they will make mistakes. However they should act swiftly to 19 | acknowledge mistakes and correct them. 20 | - Aim to remediate first and then discuss. If other members of the 21 | team express concerns about actions, acknowledge their concerns by 22 | stopping the actions in question and then discuss within the team 23 | to come to a common agreement. 24 | - Treat all community members with respect, consideration, and highest 25 | standards of ethical conduct. 26 | - Value a diversity of views and opinions. Avoid preferential 27 | treatment, and hold everyone (including ourselves) accountable to the same 28 | set of standards. Everyone gets to speak up. 29 | - Deal with issues directly with the person in question. Resist complaining 30 | about others in the project in a public sphere. 31 | - Build trust by keeping your promises. 32 | - Be the model of accountability and leadership. Provide the example of 33 | ownership and stewardship that everyone can follow to success. 34 | - Commit to ongoing development and learning best practices for governing. 35 | - Criticize ideas rather than people, discussing any concerns in person 36 | whenever possible, and taking responsibility for our statements. 37 | 38 | While the guidelines above focus primarily on the spaces where 39 | we participate in official foundation work (GitHub, IRC, meetings, 40 | conferences), it is important to recognize that the public behavior 41 | of members also reflects on the webpack project. 42 | 43 | If you're interested in an introduction to diversity, inclusion, and unconscious bias, 44 | [try this free training offered by our partners at the Linux Foundation](https://training.linuxfoundation.org/linux-courses/open-source-compliance-courses/inclusive-speaker-orientation). 45 | 46 | If it appears that any member of the project leadership is acting outside 47 | of the expectations set above please refer to our [moderation policy](./MODERATION_POLICY.md) 48 | which outlines the process of making an official complaint. 49 | 50 | --- 51 | 52 | _This document is an adaption of the Node.js project [Member Expectations](https://github.com/nodejs/admin/blob/main/MemberExpectations.md)_ 53 | 54 | [Code of Conduct]: https://github.com/webpack/webpack/blob/main/CODE_OF_CONDUCT.md 55 | [TSC]: ./CHARTER.md 56 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # webpack Project Governance 2 | 3 | webpack is an open source project that depends on contributions from the community. Anyone may contribute to the project at any time by submitting code, participating in discussions, making suggestions, or any other contribution they see fit. This document describes how various types of contributors work within the webpack project. 4 | 5 | * [Roles and Responsibilities](#roles-and-responsibilities) 6 | * [Contributors](#contributors) 7 | * [Committers](#committers) 8 | * [Reviewers](#reviewers) 9 | * [Technical steering committee](#technical-steering-committee) 10 | * [TSC meetings](#tsc-meetings) 11 | * [Consensus seeking process](#consensus-seeking-process) 12 | 13 | ## Roles and Responsibilities 14 | 15 | ### Contributors 16 | 17 | Contributors are community members who contribute in concrete ways to the project, most often in the form of code and/or documentation. Anyone can become a Contributor, and contributions can take many forms. There is no expectation of commitment to the project, no specific skill requirements, and no selection process. 18 | 19 | Contributors have read-only access to source code and so submit changes via pull requests. Contributor pull requests have their contribution reviewed and merged by a TSC member. TSC members and Committers work with Contributors to review their code and prepare it for merging. 20 | 21 | As Contributors gain experience and familiarity with the project, their profile within, and commitment to, the community will increase. At some stage, they may find themselves being nominated as either a Website Team Member or Committer by an existing Website Team Member or Committer. 22 | 23 | ### Committers 24 | 25 | Committers are community members who have shown that they are committed to the continued development of the project through ongoing engagement with the community. Committers are given push access to the project's GitHub repos and must abide by the project's [Contribution Guidelines](https://github.com/webpack/webpack/blob/main/CONTRIBUTING.md) 26 | 27 | To become a Committer: 28 | 29 | * One must have shown a willingness and ability to participate in the project as a team player. Typically, a potential Committer will need to show that they have an understanding of and alignment with the project, its objectives, and its strategy. 30 | * Committers are expected to be respectful of every community member and to work collaboratively in the spirit of inclusion. 31 | 32 | New Committers can be nominated by any existing Committer. Once they have been nominated, there will be a vote by the TSC members. 33 | 34 | It is important to recognize that committership is a privilege, not a right. That privilege must be earned and once earned it can be removed by the TSC members by a standard TSC motion. However, under normal circumstances committership exists for as long as the Committer wishes to continue engaging with the project. 35 | 36 | A Committer who shows an above-average level of contribution to the project, particularly with respect to its strategic direction and long-term health, may be nominated to become a reviewer, described below. 37 | 38 | ### Reviewers 39 | 40 | Reviewers are community members who have contributed a significant amount of time to the project through triaging of issues, fixing bugs, implementing enhancements/features, and are trusted community leaders. 41 | 42 | Reviewers may perform all of the duties of Committers, and also: 43 | 44 | * May merge external pull requests for accepted issues upon reviewing and approving the changes. 45 | * May merge their own pull requests once they have collected the feedback they deem necessary. (No pull request should be merged without at least one Committer/Reviewer/TSC member comment stating they've looked at the code.) 46 | 47 | To become a Reviewer: 48 | 49 | * Work in a helpful and collaborative way with the community. 50 | * Have given good feedback on others' submissions and displayed an overall understanding of the code quality standards for the project. 51 | * Commit to being a part of the community for the long-term. 52 | 53 | A Committer is invited to become a Reviewer by existing Reviewers and TSC members. A nomination will result in discussion and then a decision by the TSC. 54 | 55 | ## Technical Steering Committee 56 | 57 | A subset of the collaborators forms the Technical Steering Committee (TSC). 58 | The TSC has final authority over this project, including: 59 | 60 | * Technical direction 61 | * Project governance and process (including this policy) 62 | * Contribution policy 63 | * GitHub repository hosting 64 | * Conduct guidelines 65 | * Maintaining the list of collaborators 66 | 67 | The current list of TSC members is in 68 | [the project README](https://github.com/webpack/webpack/blob/main/README.md#current-project-members). 69 | 70 | The [TSC Charter][] governs the operations of the TSC. All changes to the 71 | Charter need approval by the OpenJS Foundation Cross-Project Council (CPC). 72 | 73 | ### TSC meetings 74 | 75 | The TSC meets in a Discord conference call or Discord thread. Each year, 76 | the TSC elects a chair to run the meetings. 77 | 78 | Any community member can create a GitHub issue asking that the TSC review 79 | something. 80 | 81 | The TSC may invite people to take part in a non-voting capacity. 82 | 83 | During the meeting, the TSC chair ensures that someone takes minutes. After the 84 | meeting, the TSC chair ensures that someone opens a pull request with the 85 | minutes. 86 | 87 | The TSC seeks to resolve as many issues as possible outside meetings using 88 | [the webpack's governance repository issue tracker](https://github.com/webpack/governance/issues). 89 | 90 | The process in the issue tracker is: 91 | 92 | * A TSC member opens an issue explaining the proposal/issue and @-mentions 93 | @webpack/tsc. 94 | * The proposal passes if, after 72 hours, there are two or more TSC voting 95 | member approvals and no TSC voting member opposition. 96 | * If there is an extended impasse, a TSC member may make a motion for a vote. 97 | 98 | ## Consensus Seeking Process 99 | 100 | The TSC follows a 101 | [Consensus Seeking](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making) 102 | decision making model. 103 | 104 | When an agenda item has appeared to reach a consensus, the moderator 105 | will ask "Does anyone object?" as a final call for dissent from the 106 | consensus. 107 | 108 | If an agenda item cannot reach a consensus, a TSC member can call for 109 | either a closing vote or a vote to table the issue to the next 110 | meeting. The call for a vote must be approved by a majority of the TSC 111 | or else the discussion will continue. Simple majority wins. 112 | 113 | ---- 114 | 115 | _This document is an adaption of the [Node.js project Governance Model](https://github.com/nodejs/node/blob/main/GOVERNANCE.md) and the [ESlint project Governance Model](https://github.com/eslint/eslint/blob/main/docs/src/contribute/governance.md)_ 116 | 117 | [TSC Charter]: https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md 118 | -------------------------------------------------------------------------------- /CHARTER.md: -------------------------------------------------------------------------------- 1 | # webpack TSC Charter 2 | 3 | ## Section 0. Guiding Principle 4 | 5 | The webpack project is part of the OpenJS Foundation. The project operates transparently, openly, collaboratively, 6 | and ethically. Project proposals, timelines, and status must not merely be open, but also easily visible to outsiders. 7 | 8 | ## Section 1. Scope 9 | 10 | The webpack project is a highly flexible and efficient module bundler for modern JavaScript applications. Its primary 11 | purpose is to transform and bundle various modules (JavaScript, CSS, images, etc.) into a format suitable for web 12 | applications. Webpack focuses on enhancing the developer experience, providing optimizations for production environments, 13 | and enabling configurations to support a wide range of use cases and edge cases for specific projects. 14 | 15 | With this, webpack not only simplifies the process of managing application dependencies, but it also offers tools to 16 | optimize performance, maintainability, and scalability. The webpack community contributes solutions to common challenges 17 | in modern web development, helping developers streamline their workflows and build robust applications. 18 | 19 | ### 1.1: In-scope 20 | 21 | - Bundling JavaScript files and their dependencies into a single output (or multiple outputs) for browser environments 22 | - Handling of asset files such as CSS, images, fonts, and other static resources 23 | - Optimization of assets for production, including minification, compression, and tree shaking (removal of unused code) 24 | - Enabling hot module replacement (HMR) for faster development feedback loops 25 | - Configuration and extensibility through plugins and loaders 26 | - Support for code splitting and lazy loading to enhance performance 27 | - Integrating with modern JavaScript frameworks (e.g., React, Vue, Angular) 28 | - Providing detailed build reports and debugging tools for development and production 29 | - Supporting multiple output formats (e.g., AMD, CommonJS, ES Modules) for compatibility with various environments 30 | - Community-driven tools and best practices provided through 31 | [plugins](https://webpack.js.org/plugins/) and [guides](https://webpack.js.org/guides/) 32 | - Technical help and discussions via community platforms such as 33 | [GitHub Discussions](https://github.com/webpack/webpack/discussions) 34 | 35 | In addition to the main repository, `webpack` (bundler), the organization maintains and manages several other core 36 | projects that are integral to the ecosystem such as `webpack-dev-server`, `webpack-cli`, and `webpack-contrib` projects. 37 | 38 | These repositories, along with others housed within the `github.com/webpack` and `github.com/webpack-contrib` are owned by the webpack project. 39 | 40 | ### 1.2: Out-of-Scope 41 | 42 | - Testing frameworks (e.g., unit, integration, or end-to-end testing tools). 43 | - APIs and tools that uses webpack in any way and are not in the webpack organization. 44 | - Server-side rendering directly (although it can integrate with SSR frameworks). 45 | - `webpack`-related frameworks and libraries that operate in their own capacity. 46 | 47 | ## Section 2. Relationship with OpenJS Foundation CPC. 48 | 49 | Most large, complex open source communities have both a business and a technical governance model. Technical leadership 50 | for the projects within the OpenJS Foundation is delegated to the projects through their project charters by the OpenJS 51 | Cross Project Council (CPC). In the case of the webpack project, it is delegated to the webpack Technical Steering 52 | Committee ("TSC"). OpenJS Foundation's business leadership is the Board of Directors (the "Board"). 53 | 54 | This charter can only be amended with the approval of the CPC. 55 | 56 | ## Section 3. Establishment of the TSC 57 | 58 | TSC members can be either _regular_ members or _voting_ members. Regular members can attend meetings and participate in 59 | TSC discussions, but do not vote. Voting members can do everything regular members can do, and also have the ability to 60 | cast votes when consensus is not reached on an issue. 61 | 62 | TSC memberships are not time-limited. There is no maximum size of the TSC. The TSC must have at least four voting 63 | members. 64 | 65 | The TSC may add additional voting members to the TSC through meeting consensus. The consensus requires at least five TSC members to be present to approve a new voting member. A TSC member can be removed from the TSC by voluntary 66 | resignation or by consensus with at least five voting members to be present. A vote in a TSC meeting can be used to change a regular TSC member to a voting 67 | TSC member, or to change a voting TSC member to a regular TSC member. 68 | 69 | No more than one-fourth of the TSC voting members may be affiliated with the same employer. If a change in TSC voting 70 | membership or a change of employment by a TSC voting member creates a situation where more than one-fourth of the TSC 71 | voting membership shares an employer, then the situation must be immediately remedied by the removal of voting member 72 | status from one or more TSC voting members affiliated with the over-represented employer(s). 73 | 74 | The TSC shall meet regularly using tools that enable participation by the community (e.g. weekly on a Google Hangout On 75 | Air, or through any other appropriate means selected by the TSC). The meeting shall be directed by the TSC Chairperson. 76 | Responsibility for directing individual meetings may be delegated by the TSC Chairperson to any other TSC voting member. 77 | Minutes or an appropriate recording shall be taken and made available to the community through accessible public 78 | postings. 79 | 80 | TSC voting members are expected to regularly participate in TSC meetings and issue triaging. 81 | 82 | A TSC voting member is automatically converted to a TSC regular member if they do not participate in three consecutive 83 | TSC votes. 84 | 85 | ## Section 4. Roles & Responsibilities of the TSC 86 | 87 | Subject to such policies as may be set by the CPC, the TSC voting members are responsible for all technical development 88 | within the webpack project, including: 89 | 90 | * Setting release dates. 91 | * Release quality standards. 92 | * Technical direction. 93 | * Project governance and process. 94 | * GitHub repository management. 95 | * Conduct and maintain guidelines defined by the OpenJS Foundation Cross Project Council. 96 | * Maintaining the list of additional collaborators. 97 | * Development process and any coding standards. 98 | * Mediating technical conflicts between collaborators or `webpack` projects. 99 | 100 | The TSC voting members will define webpack project's release vehicles. 101 | 102 | ### Section 4.1. webpack Project Operations 103 | 104 | The TSC voting members will establish and maintain a development process for the webpack project. The development 105 | process will establish guidelines for how the developers and community will operate. It will, for example, establish 106 | appropriate timelines for TSC review (e.g. agenda items must be published at least a certain number of hours in advance 107 | of a TSC meeting). 108 | 109 | Note that project operations remain subject to any relevant policy or process specified by the OpenJS Foundation board or Cross Project Council. 110 | 111 | ### Section 4.2. Decision-making, Voting, and/or Elections 112 | 113 | #### Section 4.2.1. Elections 114 | 115 | These processes are described in webpack's [GOVERNANCE](GOVERNANCE.md) document. 116 | 117 | #### Section 4.2.2. Decision Making 118 | 119 | For webpack projects' decisions, Collaborators and TSC voting members shall operate under Lazy Consensus ([consensus seeking][]). When an agenda item has appeared to reach a 120 | consensus, the moderator will ask "Does anyone object?" as a final call for dissent from the consensus. For all votes, a simple majority of all TSC voting members for, or against, the issue wins. A TSC voting member may 121 | choose to participate in any vote through abstention. Votes are needed to add new members, remove members from the TSC or deciding in project critical issues, such as roadmapping major versions of webpack core. 122 | 123 | 124 | ## Section 5. Definitions 125 | 126 | * **Project**: a technical collaboration effort, e.g. a subsystem, that is organized through the webpack organization creation. 127 | 128 | ---- 129 | 130 | This work is a derivative of the [Node.js Project TSC Charter](https://github.com/nodejs/node/blob/main/TSC_CHARTER.md). 131 | 132 | [consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making 133 | -------------------------------------------------------------------------------- /WORKING_GROUPS.md: -------------------------------------------------------------------------------- 1 | # webpack Working Groups 2 | 3 | webpack Working Groups are autonomous projects created by the 4 | [Technical Steering Committee (TSC)][]. 5 | 6 | Working Groups can be formed at any time but must be ratified by the TSC. 7 | Once formed the work defined in the Working Group charter is the 8 | responsibility of the WG rather than the TSC. 9 | 10 | It is important that Working Groups are not formed prematurely. Working 11 | Groups are not formed to begin a set of tasks but instead are formed 12 | once that work is already underway and the contributors 13 | think it would benefit from being done as an autonomous project. 14 | 15 | If the work defined in a Working Group's charter is complete, the charter 16 | should be revoked. 17 | 18 | A Working Group's charter can be revoked either by consent of the Working 19 | Group's members or by a TSC vote. Once revoked, any future work that arises 20 | becomes the responsibility of the TSC. 21 | 22 | ## Joining a WG 23 | 24 | To find out how to join a working group, consult the [GOVERNANCE.md][] in 25 | the working group's repository. 26 | 27 | ## Starting a Working Group 28 | 29 | A Working Group is established by first defining a charter that can be 30 | ratified by the TSC. A charter is a statement of purpose and a 31 | list of responsibilities. When requesting that a working group be chartered, it 32 | is also necessary to provide a list of initial membership. 33 | 34 | A working group needs 3 initial members. These should be individuals 35 | already undertaking the work described in the charter. 36 | 37 | The list of responsibilities should be specific. Once established, these 38 | responsibilities are no longer governed by the TSC and therefore should 39 | not be broad or subjective. The only recourse the TSC has over the working 40 | group is to revoke the entire charter. 41 | 42 | If the responsibilities described in the charter are currently undertaken by 43 | another working group then the charter will additionally have to be ratified by 44 | that working group. 45 | 46 | You can submit the working group charter for ratification by sending 47 | a pull request to this document to add the charter it to the 48 | list of current Working Groups. Once ratified, the list of 49 | members should be maintained in the Working Group's 50 | README. 51 | 52 | ## Bootstrap Governance 53 | 54 | Once the TSC ratifies a charter, the working group inherits the following 55 | documentation for governance, contribution, conduct and an MIT 56 | LICENSE. The working group is free to change these documents through their own 57 | governance process, hence the term "bootstrap." 58 | 59 | ```markdown 60 | ### *[insert WG name]* Working Group 61 | 62 | The webpack *[insert WG name]* is governed by a Working Group (WG) 63 | that is responsible for high-level guidance of the project. 64 | 65 | The WG has final authority over this project including: 66 | 67 | * Technical direction 68 | * Project governance and process (including this policy) 69 | * Contribution policy 70 | * GitHub repository hosting 71 | * Conduct guidelines 72 | * Maintaining the list of additional Collaborators 73 | 74 | For the current list of WG members, see the project 75 | [README.md](https://github.com/webpack/webpack/blob/main/README.md#current-project-members). 76 | 77 | ### Collaborators 78 | 79 | The *[insert WG name]* GitHub repository is 80 | maintained by the WG and additional Collaborators who are added by the 81 | WG on an ongoing basis. 82 | 83 | Individuals making significant and valuable contributions are made 84 | Collaborators and given commit-access to the project. These 85 | individuals are identified by the WG and their addition as 86 | Collaborators is discussed during the weekly WG meeting. 87 | 88 | Modifications of the contents of the *[insert WG repo]* repository are made on 89 | a collaborative basis. Anybody with a GitHub account may propose a 90 | modification via pull request and it will be considered by the project 91 | Collaborators. All pull requests must be reviewed and accepted by a 92 | Collaborator with sufficient expertise who is able to take full 93 | responsibility for the change. In the case of pull requests proposed 94 | by an existing Collaborator, an additional Collaborator is required 95 | for sign-off. Consensus should be sought if additional Collaborators 96 | participate and there is disagreement around a particular 97 | modification. See _Consensus Seeking Process_ below for further detail 98 | on the consensus model used for governance. 99 | 100 | For the current list of Collaborators, see the project 101 | [README.md](https://github.com/webpack/webpack/blob/main/README.md#current-project-members). 102 | 103 | ### WG Membership 104 | 105 | WG seats are not time-limited. There is no fixed size of the WG. 106 | However, the expected target is between 6 and 12, to ensure adequate 107 | coverage of important areas of expertise, balanced with the ability to 108 | make decisions efficiently. 109 | 110 | There is no specific set of requirements or qualifications for WG 111 | membership beyond these rules. 112 | 113 | The WG may add additional members to the WG by unanimous consensus. 114 | 115 | A WG member may be removed from the WG by voluntary resignation, or by 116 | unanimous consensus of all other WG members. 117 | 118 | Changes to WG membership should be posted in the agenda, and may be 119 | suggested as any other agenda item (see "WG Meetings" below). 120 | 121 | If an addition or removal is proposed during a meeting, and the full 122 | WG is not in attendance to participate, then the addition or removal 123 | is added to the agenda for the subsequent meeting. This is to ensure 124 | that all members are given the opportunity to participate in all 125 | membership decisions. If a WG member is unable to attend a meeting 126 | where a planned membership decision is being made, then their consent 127 | is assumed. 128 | 129 | No more than 1/3 of the WG members may be affiliated with the same 130 | employer. If removal or resignation of a WG member, or a change of 131 | employment by a WG member, creates a situation where more than 1/3 of 132 | the WG membership shares an employer, then the situation must be 133 | immediately remedied by the resignation or removal of one or more WG 134 | members affiliated with the over-represented employer(s). 135 | 136 | ### Consensus Seeking Process 137 | 138 | The WG follows a [Consensus Seeking][] decision-making model. 139 | 140 | If an agenda item cannot reach a consensus a WG member can call for 141 | either a closing vote or a vote to table the issue to the next 142 | meeting. The call for a vote must be seconded by a majority of the WG 143 | or else the discussion will continue. Simple majority wins. 144 | 145 | Note that changes to WG membership require unanimous consensus. See 146 | "WG Membership" above. 147 | 148 | 149 | ## Developer's Certificate of Origin 1.1 150 | 151 | Use of a CLA or DCO is mandatory for all all OpenJS Foundation projects. 152 | The webpack project has chosen to use the DCO 1.1 153 | 154 | By making a contribution to this project, I certify that: 155 | 156 | * (a) The contribution was created in whole or in part by me and I 157 | have the right to submit it under the open source license 158 | indicated in the file; or 159 | 160 | * (b) The contribution is based upon previous work that, to the best 161 | of my knowledge, is covered under an appropriate open source 162 | license and I have the right under that license to submit that 163 | work with modifications, whether created in whole or in part 164 | by me, under the same open source license (unless I am 165 | permitted to submit under a different license), as indicated 166 | in the file; or 167 | 168 | * (c) The contribution was provided directly to me by some other 169 | person who certified (a), (b) or (c) and I have not modified 170 | it. 171 | 172 | * (d) I understand and agree that this project and the contribution 173 | are public and that a record of the contribution (including all 174 | personal information I submit with it, including my sign-off) is 175 | maintained indefinitely and may be redistributed consistent with 176 | this project or the open source license(s) involved. 177 | 178 | ### Moderation Policy 179 | 180 | The [webpack Moderation Policy] applies to this WG. 181 | 182 | ### Code of Conduct 183 | 184 | The [webpack Code of Conduct][] applies to this WG. 185 | 186 | [webpack Code of Conduct]: https://github.com/webpack/webpack/blob/main/CODE_OF_CONDUCT.md 187 | [webpack Moderation Policy]: https://github.com/webpack/governance/blob/main/MODERATION_POLICY.md 188 | [Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making 189 | ``` 190 | 191 | ## Current Working Groups 192 | 193 | * [Core](#core) 194 | 195 | ### [Core](https://github.com/webpack/webpack) 196 | 197 | The Core Working Group is responsible for the development and 198 | maintenance of the webpack bundler and its technical direction. 199 | 200 | Responsibilities include: 201 | 202 | * Maintaining the core of the webpack bundler 203 | * Reviewing and merging pull requests 204 | * Managing releases and versioning 205 | * Ensuring code quality and consistency 206 | * Addressing issues and bugs reported by the community 207 | * Developing new features and enhancements 208 | * Writing and maintaining documentation 209 | * Coordinating with other working groups and the TSC 210 | * Ensuring compliance with the project's code of conduct and governance policies 211 | 212 | --- 213 | 214 | _This document is an adaption of the Node.js project [Working Groups Charter](https://github.com/nodejs/TSC/blob/main/WORKING_GROUPS.md)_ 215 | 216 | [Technical Steering Committee (TSC)]: ./CHARTER.md 217 | -------------------------------------------------------------------------------- /MODERATION_POLICY.md: -------------------------------------------------------------------------------- 1 | # Moderation policy 2 | 3 | If you are not a member of the webpack GitHub Organization and wish to submit a 4 | moderation request, please see [Requesting Moderation][] 5 | 6 | * [Applicability][] 7 | * [Terms][] 8 | * [Grounds for Moderation][] 9 | * [Requesting Moderation][] 10 | * [Consideration of Intent][] 11 | * [Guidelines and Requirements][] 12 | * [Collaborator Posts][] 13 | * [Non-Collaborator Posts][] 14 | * [Temporary Interaction Limits][] 15 | * [Temporary and Indefinite Blocks][] 16 | * [Privacy of the webpack/moderation Repository][] 17 | * [Escalation of Issues][] 18 | * [Modifications to This Policy][] 19 | 20 | ## Applicability 21 | 22 | This policy applies to all repositories under the `webpack` and `webpack-contrib` 23 | GitHub Organizations and all webpack Working Groups. This policy also 24 | applies to the [webpack Slack Community](https://webpack.slack.com), 25 | supported by the Admin team of the Slack organization. 26 | 27 | ## Terms 28 | 29 | * *Collaborator* refers to any individual with configured triage role or higher 30 | in any webpack GitHub organizations repositories. See 31 | [GitHub's Repository roles documentation][] for more information. 32 | * *TSC* refers to the [webpack Technical Steering Committee][]. 33 | * *Post* refers to the content and titles of any issue, pull request, comment, 34 | discussion, or wiki page. 35 | * *Moderate* means to modify, lock, or delete one or more Posts to correct or 36 | address Code of Conduct violations. 37 | * *Remove* refers to the act of removing the configured write (commit) 38 | permissions for an individual Collaborator's GitHub account from *all* 39 | webpack GitHub Organizations repositories as well as removing the account from 40 | the webpack GitHub Organizations membership. 41 | * *Block* refers to the act of prohibiting an individual GitHub account from any 42 | further participation in the webpack GitHub Organizations. A block may be 43 | *temporary* or *indefinite*. 44 | * This Moderation Policy applies only to blocking from the organization. 45 | Individuals may choose to 46 | [block other individuals from their personal GitHub accounts][]. This policy 47 | does not restrict blocking from personal GitHub accounts. 48 | * *Requester* refers to an individual requesting Moderation on a Post. 49 | 50 | ## Grounds for Moderation 51 | 52 | Any Post in violation of the webpack [Code of Conduct][] is subject 53 | to Moderation. 54 | 55 | The TSC is responsible for deciding what constitutes inappropriate 56 | behavior that may be subject to Moderation. 57 | 58 | ## Requesting Moderation 59 | 60 | Anyone may request Moderation of a Post. Requesting Moderation of a Post can be 61 | accomplished in one of four ways: 62 | 63 | * Via the [webpack-security@openjsf.org][] email address, 64 | * Via private email to individual TSC members, 65 | * Via a new Post in the same thread as the Post being requested for Moderation, 66 | * Via a new Post in the private webpack/moderation repository. 67 | 68 | Note that Collaborators may Moderate non-Collaborator Posts at any time without 69 | submitting an initial request (see: [Non-Collaborator Posts][]). 70 | 71 | Use of the [webpack-security@openjsf.org][] email address -- or private email to individual 72 | TSC members -- is appropriate when the individual requesting the 73 | Moderation does not feel comfortable directly or publicly making the request. 74 | All emails sent to the [webpack-security@openjsf.org][] address are currently forwarded 75 | to all members of the TSC. 76 | 77 | Requests should contain as much information and context as possible, including 78 | the URL and a screenshot of the Post in question. Screenshots may be modified 79 | to obscure obscene or offensive content. 80 | 81 | External public venues or social media services such as Twitter must never be 82 | used to request Moderation. 83 | 84 | Collaborators must never discuss the specific details of a Moderation request 85 | in any public forum or any social media service outside of the webpack GitHub 86 | Organization. 87 | 88 | Note that quoting the original content of a Post within a Moderation request or 89 | webpack/moderation repository issue is not a violation of the 90 | [Code of Conduct][]. However, discretion is advised when including such quotes 91 | in requests posted to public repositories. 92 | 93 | Requests for Moderation that do not appear to have been submitted in good faith 94 | with intent to address a legitimate [Code of Conduct][] violation will be 95 | ignored. 96 | 97 | ## Consideration of Intent 98 | 99 | Before Moderating a Post, Collaborators should carefully consider the possible 100 | intent of the author. It may be that the author has simply made an error or is 101 | not yet familiar with the [Code of Conduct][]; or it may be that cultural 102 | differences exist, or that the author is unaware that certain content is 103 | inappropriate. In such cases, the author should be given an 104 | opportunity to correct any error that may have been made. 105 | 106 | Note, however, that unfamiliarity with the [Code of Conduct][] does not excuse 107 | a Post from Moderation. 108 | 109 | ## Guidelines and Requirements 110 | 111 | * All Posts are expected to respect the webpack [Code of Conduct][]. 112 | * Any Collaborator with triage permission to a given repository (except 113 | webpack/moderation) may Moderate Posts within that repository's issue tracker. 114 | Only the TSC is allowed to moderate posts on webpack/moderation. 115 | * The TSC serves as the final arbiter for all Moderation issues. 116 | * TSC members may Remove or Block an individual from the webpack 117 | GitHub Organizations. 118 | * For any Removal or Blocking action, an issue describing the reasons for the 119 | action, and identifying the Github account being acted upon, must be posted 120 | to the Moderation Repository with an explanation provided by the Moderation 121 | Team member performing the action. 122 | * Any individual Blocked from the webpack GitHub Organizations will be recommended 123 | for exclusion from any webpack Foundation sponsored event or activity. 124 | * Minor edits to the formatting of a Post or to correct typographical errors 125 | are not "Moderation". Such edits and their intent must 126 | still be documented with a short note indicating who made the edit and why. 127 | 128 | ### Collaborator Posts 129 | 130 | * Prior to Moderating any Post authored by a Collaborator, the author must be 131 | given a reasonable opportunity to modify or remove the Post on their own. 132 | * If the author of the Post disagrees that Moderation is required, the matter 133 | can be escalated to the TSC for resolution. In such cases, no Moderation 134 | action may be taken until a decision by the TSC is made. 135 | * When Moderating any Post authored by another Collaborator, the moderating 136 | Collaborator must: 137 | * Explain the justification for Moderating the post, 138 | * Identify all changes made to the Post, and 139 | * Identify the steps previously taken to resolve the issue. 140 | * If the Moderation action included Blocking, an indication of whether the Block 141 | is temporary or indefinite is required, along with an issue posted to the 142 | moderation repository justifying the action. 143 | * Explanations of Moderation actions on Collaborator Posts must be provided in: 144 | * A new post within the original thread, or 145 | * A new issue within the private webpack/moderation repository. 146 | * Any Collaborator habitually violating the Code of Conduct or this Moderation 147 | policy may be Blocked temporarily or, in extreme cases, Removed and Blocked 148 | indefinitely. 149 | 150 | ### Non-Collaborator Posts 151 | 152 | * Posts authored by non-Collaborators are always subject to immediate Moderation 153 | by any Collaborator if the content is intentionally disruptive or in violation 154 | of the [Code of Conduct][]. 155 | * When moderating non-Collaborator posts, the moderating Collaborator must: 156 | * Explain the justification for Moderating the post, and 157 | * Identify all changes made to the Post. 158 | * If the Moderation action included Blocking, an indication of whether the Block 159 | is temporary or indefinite is required, along with a note justifying the 160 | action. 161 | * If an explanation of a Moderation action for a non-Collaborator Post is 162 | provided, it must be provided in: 163 | * The original Post being modified (as replacement or appended content), 164 | * A new post within the original thread, or 165 | * A new issue within the private webpack/moderation repository. 166 | * Moderation of Posts authored by non-Collaborators may result in those 167 | non-Collaborators being Blocked temporarily or indefinitely from further 168 | participation in the webpack GitHub organizations. 169 | * If it is clear that there is no intention to collaborate in good faith, 170 | it is possible to hide comments of non-Collaborators. In that case there is 171 | an exception to the reporting requirement described above. 172 | * Accounts that are reasonably believed to be bots (other than bots authorized 173 | by the TSC) are subject to immediate Blocking. 174 | * Issues, pull requests, discussions, and comments that are spam (job posting, 175 | service advertising, etc.) are subject to immediate moderation. 176 | * Issues, pull requests, discussions, and comments that are believed to be 177 | LLM-generated (e.g a PR coming from a new contributor changing a single file 178 | without clear motivation) should be closed with a comment such as "It seems 179 | you are using a LLM, please stop, this is not bringing any value and is 180 | wasting our time. If you are not using one, please read and follow our 181 | contributing guidelines." Report the user to the moderation repository so they 182 | get blocked if they do it again. 183 | * Collaborators may use the Hide feature in the GitHub interface for off-topic 184 | posts by non-Collaborators. 185 | * TSC members can delete any issues or comments posted by accounts that have 186 | been deleted by GitHub. These accounts show up in the GitHub interface as 187 | user `ghost`. There is no need to screenshot or document these deletions. 188 | 189 | There are a few examples of moderating non-Collaborator posts: 190 | 191 | Scenario 1: 192 | * A non-Collaborator posts a comment that indicates that they are a bot. 193 | * A collaborator sees the post and hides it. 194 | * No further action is necessary. 195 | 196 | Scenario 2: 197 | * A non-Collaborator posts a comment that is against the Code of Conduct. 198 | * A Collaborator sees the comment and asks the author to edit it. 199 | * The author refuses to edit their comment. 200 | * The Collaborator deletes the comment and posts an issue in the moderation 201 | repository explaining their actions. 202 | 203 | Scenario 3: 204 | * A non-Collaborator opens a pull request with comments indicating they are a 205 | bot. 206 | * A Collaborator sees that pull requests, closes it, deletes the comments 207 | and posts an issue in the moderation repository explaining their actions. 208 | * A TSC member sees the issue and decides to block the user from the 209 | organization. 210 | 211 | Scenario 4: 212 | * A non-Collaborator posts a comment on an old commit that is against the 213 | Code of Conduct. 214 | * A Collaborator sees the comment, takes a screenshot, and deletes it. 215 | * The Collaborator posts an issue in the moderation repository explaining 216 | their actions. 217 | 218 | ### Temporary Interaction Limits 219 | 220 | The TSC may, at their discretion, choose to enable [GitHub's 221 | Temporary Interaction Limits][] on any GitHub repository in the webpack GitHub 222 | Organization. 223 | 224 | Any Collaborator may request that the TSC enable the Temporary 225 | Interaction Limits by posting an issue to the moderation repository. If the 226 | TSC chooses not to do so, then a comment explaining why that decision was made 227 | must be added to the moderation repository thread. 228 | 229 | ### Temporary and Indefinite Blocks 230 | 231 | A Temporary Block is time limited, with the timeframe decided on by the Moderation 232 | Team at the time of issuing, depending on the severity of the issue. Recommended 233 | default options are 24-hour, 48-hour, and 7-day periods. 234 | 235 | An Indefinite Block is set for an unspecified period of time and may only be 236 | lifted for an individual through a simple majority vote of the Moderation 237 | Team. 238 | 239 | ## Privacy of the webpack/moderation Repository 240 | 241 | The webpack/moderation Repository is used to discuss the potentially sensitive 242 | details of any specific moderation issue. The repository is private but 243 | accessible to all Collaborators. The details of any issue discussed within the 244 | webpack/moderation repository are expected to remain confidential and are not to 245 | be discussed in any public forum or social media service. 246 | 247 | Any Collaborator found to be violating the privacy of the webpack/moderation 248 | repository by repeatedly sharing or discussing the details of webpack/moderation 249 | issues in any public forum or social media service risks being permanently 250 | removed from the webpack GitHub organizations. 251 | 252 | ## Escalation of Issues 253 | 254 | Moderation issue disputes not involving a TSC member may be escalated 255 | to the TSC for review by tagging the 256 | original issue, pull request, or associated webpack/moderation repository. 257 | Any such Moderation action may be overturned through a TSC vote. 258 | 259 | TSC members directly involved in a Moderation 260 | issue (as either the Requester or author of the Post in question) are 261 | required to recuse themselves from any decisions required to resolve the 262 | issue. 263 | 264 | Moderation disputes involving TSC members, including questions of whether a TSC 265 | member has violated the Code of Conduct, *shall* be referred to an 266 | Independent Mediator selected by the OpenJS Foundation. 267 | 268 | ## Modifications to This Policy 269 | 270 | Modifications to this policy are subject to approval by the TSC. 271 | When modifications are proposed, if there are no objections after 272 | 72 hours, the modifications are accepted. If there any objections to 273 | any proposed change, a TSC vote in favor of the change is required. 274 | 275 | --- 276 | 277 | _This document is an adaption of the Node.js project [Moderation Policy](https://github.com/nodejs/admin/blob/HEAD/Moderation-Policy.md)_ 278 | 279 | [Code of Conduct]: https://github.com/webpack/webpack/blob/main/CODE_OF_CONDUCT.md 280 | [webpack Technical Steering Committee]: ./CHARTER.md 281 | [GitHub's Repository roles documentation]: https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization#repository-roles-for-organizations 282 | [GitHub's Temporary Interaction Limits]: https://github.com/blog/2370-introducing-temporary-interaction-limits 283 | [Applicability]: #applicability 284 | [Terms]: #terms 285 | [Grounds for Moderation]: #grounds-for-moderation 286 | [Requesting Moderation]: #requesting-moderation 287 | [Consideration of Intent]: #consideration-of-intent 288 | [Guidelines and Requirements]: #guidelines-and-requirements 289 | [Collaborator Posts]: #collaborator-posts 290 | [Non-Collaborator Posts]: #non-collaborator-posts 291 | [Temporary Interaction Limits]: #temporary-interaction-limits 292 | [Temporary and Indefinite Blocks]: #temporary-and-indefinite-blocks 293 | [Privacy of the webpack/moderation Repository]: #privacy-of-the-webpackmoderation-repository 294 | [Escalation of Issues]: #escalation-of-issues 295 | [Modifications to This Policy]: #modifications-to-this-policy 296 | [webpack-security@openjsf.org]: mailto:webpack-security@openjsf.org 297 | [block other individuals from their personal GitHub accounts]: https://help.github.com/en/articles/blocking-a-user-from-your-personal-account 298 | --------------------------------------------------------------------------------