Skip to content

Commit 45cbeb3

Browse files
mcollinaljharbTrottctcpip
authored
Clarify why we are requiring at least 3 organizations in the Impact project leadership (#1402)
Signed-off-by: Matteo Collina <[email protected]> Co-authored-by: Jordan Harband <[email protected]> Co-authored-by: Rich Trott <[email protected]> Co-authored-by: Chris de Almeida <[email protected]>
1 parent 3f2b23f commit 45cbeb3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

PROJECT_PROGRESSION.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -199,7 +199,8 @@ To be considered for the At Large Stage, the project must meet the following req
199199

200200
#### Definition
201201

202-
The Impact Stage is for projects that have reached their growth goals and are now on a sustaining cycle of development, maintenance, and long-term support. Impact Stage projects are used commonly in enterprise production environments and have large, well-established project communities.
202+
The Impact Stage is for projects that have reached their growth goals and are now on a sustaining cycle of development, maintenance, and long-term support. Impact Stage projects are used commonly in enterprise production environments and have large, well-established project communities.
203+
Impact projects offer long-term stability guarantees, and therefore the governing bodies of Impact projects are expected to have representatives from at least three organizations.
203204

204205
#### Examples
205206

@@ -217,7 +218,7 @@ Impact Stage projects are expected to participate actively in CPC proceedings, a
217218
To graduate from At Large stage or for a new project to join as an Impact project, a project must meet the following criteria:
218219

219220
* Demonstrate that it is being used successfully in production by at least two independent end users which, in the CPC’s judgement, are of adequate quality and scope.
220-
* Have a defined governing body of at least 5 or more members (owners and core maintainers), of which no more than 1/3 is affiliated with the same employer. In the case there are 5 governing members, 2 may be from the same employer.
221+
* Have a defined governing body of at least 5 or more members (owners and core maintainers), of which no more than 1/3 is affiliated with the same employer. In the case there are 5 governing members, 2 may be from the same employer. This criterion is to ensure broad representation and to prevent a single organization from having excessive influence on project decision-making.
221222
* Have a documented and publicly accessible description of the project's governance, decision-making, contribution, and release processes. This is preferably laid out in a GOVERNANCE.md file and references a CONTRIBUTING.md and AUTHORS.md file showing the current and emeritus committers.
222223
* Demonstrate a substantial ongoing flow of commits and merged contributions.
223224
* Have a healthy number of committers from at least two organizations. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project.
@@ -226,7 +227,6 @@ To graduate from At Large stage or for a new project to join as an Impact projec
226227
* Other metrics as defined by the applying Project during the application process in cooperation with the CPC.
227228
* Receive a supermajority vote from the CPC to move to Impact stage. Projects can move directly from At Large to Impact, if they can demonstrate sufficient maturity and have met all requirements.
228229

229-
230230
### Incubating
231231

232232
#### Definition

0 commit comments

Comments
 (0)