Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify why we are requiring at least 3 organizations in the Impact project leadership #1402

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions PROJECT_PROGRESSION.md
Original file line number Diff line number Diff line change
Expand Up @@ -199,7 +199,8 @@ To be considered for the At Large Stage, the project must meet the following req

#### Definition

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.
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.
Impact projects offer long-term stability guarantees, and therefore the governing body of Impact projects are expected to have representatives from at least three organizations.
mcollina marked this conversation as resolved.
Show resolved Hide resolved

#### Examples

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

* 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.
* 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.
* 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 is to ensure that no single organization can control the project.
Copy link
Contributor

@Trott Trott Dec 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Totally optional suggestion, but something like "excessive influence" might be less loaded than "control":

Suggested change
* 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 is to ensure that no single organization can control the project.
* 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 limitation is to ensure broad representation and to prevent a single organization from having excessive influence on project decision-making.

While that is less loaded, it might also be less clear, so...up to you. Just offering it up as a possibility.

* 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.
* Demonstrate a substantial ongoing flow of commits and merged contributions.
* 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.
Expand All @@ -226,7 +227,6 @@ To graduate from At Large stage or for a new project to join as an Impact projec
* Other metrics as defined by the applying Project during the application process in cooperation with the CPC.
* 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.


### Incubating

#### Definition
Expand Down
Loading