Skip to content

Commit 4bc0e07

Browse files
Jatinyadav29Jatinyadav29
committed
added an script for content sync from webpack/governance
1 parent 1bbea7e commit 4bc0e07

File tree

7 files changed

+236
-138
lines changed

7 files changed

+236
-138
lines changed

‎src/content/contribute/governance/CHARTER.mdx‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,11 @@
11
---
2-
title: 'webpack TSC Charter'
3-
sort: 1
2+
title: Charter
3+
source: https://github.com/webpack/governance/blob/main/CHARTER.md
4+
edit: https://github.com/webpack/governance/edit/main/CHARTER.md
45
---
56

7+
## webpack TSC Charter
8+
69
## Section 0. Guiding Principle
710

811
The webpack project is part of the OpenJS Foundation. The project operates transparently, openly, collaboratively,
@@ -115,7 +118,7 @@ Note that project operations remain subject to any relevant policy or process sp
115118

116119
#### Section 4.2.1. Elections
117120

118-
These processes are described in webpack's [GOVERNANCE](GOVERNANCE.md) document.
121+
These processes are described in webpack's [Governance](https://github.com/webpack/governance.git) document.
119122

120123
#### Section 4.2.2. Decision Making
121124

‎src/content/contribute/governance/README.mdx‎

Lines changed: 0 additions & 120 deletions
This file was deleted.

‎src/content/contribute/governance/index.mdx‎

Lines changed: 118 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,123 @@
11
---
2-
title: 'Governance'
3-
sort: 9
2+
title: Governance Overview
3+
source: https://github.com/webpack/governance/blob/main/README.md
4+
edit: https://github.com/webpack/governance/edit/main/README.md
45
---
56

6-
This section describes how the Webpack project is managed and organized.
7+
## webpack Project Governance
78

8-
## Subsections
9+
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.
910

10-
- [Charter](./CHARTER)
11-
- [Member Expectations](./MEMBER_EXPECTATIONS)
12-
- [Moderation Policy](./MODERATION_POLICY)
13-
- [README](./README)
14-
- [Working Groups](./WORKING_GROUPS)
11+
- [Roles and Responsibilities](#roles-and-responsibilities)
12+
- [Contributors](#contributors)
13+
- [Committers](#committers)
14+
- [Reviewers](#reviewers)
15+
- [Technical steering committee](#technical-steering-committee)
16+
- [TSC meetings](#tsc-meetings)
17+
- [Consensus seeking process](#consensus-seeking-process)
18+
19+
## Roles and Responsibilities
20+
21+
### Contributors
22+
23+
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.
24+
25+
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.
26+
27+
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.
28+
29+
### Committers
30+
31+
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)
32+
33+
To become a Committer:
34+
35+
- 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.
36+
- Committers are expected to be respectful of every community member and to work collaboratively in the spirit of inclusion.
37+
38+
New Committers can be nominated by any existing Committer. Once they have been nominated, there will be a vote by the TSC members.
39+
40+
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.
41+
42+
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.
43+
44+
### Reviewers
45+
46+
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.
47+
48+
Reviewers may perform all of the duties of Committers, and also:
49+
50+
- May merge external pull requests for accepted issues upon reviewing and approving the changes.
51+
- 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.)
52+
53+
To become a Reviewer:
54+
55+
- Work in a helpful and collaborative way with the community.
56+
- Have given good feedback on others' submissions and displayed an overall understanding of the code quality standards for the project.
57+
- Commit to being a part of the community for the long-term.
58+
59+
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.
60+
61+
## Technical Steering Committee
62+
63+
A subset of the collaborators forms the Technical Steering Committee (TSC).
64+
The TSC has final authority over this project, including:
65+
66+
- Technical direction
67+
- Project governance and process (including this policy)
68+
- Contribution policy
69+
- GitHub repository hosting
70+
- Conduct guidelines
71+
- Maintaining the list of collaborators
72+
73+
The current list of TSC members is in
74+
[the project README](https://github.com/webpack/webpack/blob/main/README.md#current-project-members).
75+
76+
The [TSC Charter][] governs the operations of the TSC. All changes to the
77+
Charter need approval by the OpenJS Foundation Cross-Project Council (CPC).
78+
79+
### TSC meetings
80+
81+
The TSC meets in a Discord conference call or Discord thread. Each year,
82+
the TSC elects a chair to run the meetings.
83+
84+
Any community member can create a GitHub issue asking that the TSC review
85+
something.
86+
87+
The TSC may invite people to take part in a non-voting capacity.
88+
89+
During the meeting, the TSC chair ensures that someone takes minutes. After the
90+
meeting, the TSC chair ensures that someone opens a pull request with the
91+
minutes.
92+
93+
The TSC seeks to resolve as many issues as possible outside meetings using
94+
[the webpack's governance repository issue tracker](https://github.com/webpack/governance/issues).
95+
96+
The process in the issue tracker is:
97+
98+
- A TSC member opens an issue explaining the proposal/issue and @-mentions
99+
@webpack/tsc.
100+
- The proposal passes if, after 72 hours, there are two or more TSC voting
101+
member approvals and no TSC voting member opposition.
102+
- If there is an extended impasse, a TSC member may make a motion for a vote.
103+
104+
## Consensus Seeking Process
105+
106+
The TSC follows a
107+
[Consensus Seeking](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making)
108+
decision making model.
109+
110+
When an agenda item has appeared to reach a consensus, the moderator
111+
will ask "Does anyone object?" as a final call for dissent from the
112+
consensus.
113+
114+
If an agenda item cannot reach a consensus, a TSC member can call for
115+
either a closing vote or a vote to table the issue to the next
116+
meeting. The call for a vote must be approved by a majority of the TSC
117+
or else the discussion will continue. Simple majority wins.
118+
119+
---
120+
121+
_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)_
122+
123+
[TSC Charter]: https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md

‎src/content/contribute/governance/MEMBER_EXPECTATIONS.mdx‎ renamed to ‎src/content/contribute/governance/member-expectations.mdx‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
2-
title: 'Member Expectations'
3-
sort: 2
2+
title: Member Expectations
3+
source: https://github.com/webpack/governance/blob/main/MEMBER_EXPECTATIONS.md
4+
edit: https://github.com/webpack/governance/edit/main/MEMBER_EXPECTATIONS.md
45
---
56

67
All participants in the webpack project must follow the

‎src/content/contribute/governance/MODERATION_POLICY.mdx‎ renamed to ‎src/content/contribute/governance/moderation-policy.mdx‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,11 @@
11
---
2-
title: 'Moderation policy'
3-
sort: 3
2+
title: Moderation Policy
3+
source: https://github.com/webpack/governance/blob/main/MODERATION_POLICY.md
4+
edit: https://github.com/webpack/governance/edit/main/MODERATION_POLICY.md
45
---
56

7+
## Moderation policy
8+
69
If you are not a member of the webpack GitHub Organization and wish to submit a
710
moderation request, please see [Requesting Moderation][]
811

‎src/content/contribute/governance/WORKING_GROUPS.mdx‎ renamed to ‎src/content/contribute/governance/working-groups.mdx‎

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,10 @@
1-
# webpack Working Groups
1+
---
2+
title: Working Groups
3+
source: https://github.com/webpack/governance/blob/main/WORKING_GROUPS.md
4+
edit: https://github.com/webpack/governance/edit/main/WORKING_GROUPS.md
5+
---
6+
7+
## webpack Working Groups
28

39
webpack Working Groups are autonomous projects created by the
410
[Technical Steering Committee (TSC)][].
@@ -21,7 +27,7 @@ becomes the responsibility of the TSC.
2127

2228
## Joining a WG
2329

24-
To find out how to join a working group, consult the [GOVERNANCE.md]: https://github.com/webpack/governance/blob/main/GOVERNANCE.md in
30+
To find out how to join a working group, consult the [GOVERNANCE.md](https://github.com/webpack/governance/blob/main/README.md) in
2531
the working group's repository.
2632

2733
## Starting a Working Group

0 commit comments

Comments
 (0)