From dfed96a280300780600229269f0476511b55e710 Mon Sep 17 00:00:00 2001 From: Matteo Collina Date: Wed, 11 Dec 2024 18:06:08 +0100 Subject: [PATCH 1/5] Clarify why we are requiring at least 3 organizations in the Impact project leadership Signed-off-by: Matteo Collina --- PROJECT_PROGRESSION.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/PROJECT_PROGRESSION.md b/PROJECT_PROGRESSION.md index 29ec2b35..2cf87f2d 100644 --- a/PROJECT_PROGRESSION.md +++ b/PROJECT_PROGRESSION.md @@ -200,6 +200,7 @@ 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. +Impact projects offer long-term stability guarantees, and therefore the governing body of Impact projects are expected to have representatives from at least threee organizations. #### Examples @@ -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. * 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. @@ -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 From 54b62f2647f29ad2197607f58308ba0928a8b5d0 Mon Sep 17 00:00:00 2001 From: Matteo Collina Date: Wed, 11 Dec 2024 09:12:22 -0800 Subject: [PATCH 2/5] Update PROJECT_PROGRESSION.md Co-authored-by: Jordan Harband Signed-off-by: Matteo Collina --- PROJECT_PROGRESSION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PROJECT_PROGRESSION.md b/PROJECT_PROGRESSION.md index 2cf87f2d..162bc831 100644 --- a/PROJECT_PROGRESSION.md +++ b/PROJECT_PROGRESSION.md @@ -200,7 +200,7 @@ 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. -Impact projects offer long-term stability guarantees, and therefore the governing body of Impact projects are expected to have representatives from at least threee organizations. +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. #### Examples From 9e1ee75cd9a9efd1bbf375c94278ea924a091b8b Mon Sep 17 00:00:00 2001 From: Matteo Collina Date: Wed, 11 Dec 2024 18:18:35 +0100 Subject: [PATCH 3/5] fixup Signed-off-by: Matteo Collina --- PROJECT_PROGRESSION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PROJECT_PROGRESSION.md b/PROJECT_PROGRESSION.md index 162bc831..da801804 100644 --- a/PROJECT_PROGRESSION.md +++ b/PROJECT_PROGRESSION.md @@ -199,7 +199,7 @@ 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. #### Examples From 5ae645ec9104738c30eeafdc93eff01a29619f47 Mon Sep 17 00:00:00 2001 From: Matteo Collina Date: Wed, 11 Dec 2024 09:52:39 -0800 Subject: [PATCH 4/5] Update PROJECT_PROGRESSION.md Co-authored-by: Rich Trott Signed-off-by: Matteo Collina --- PROJECT_PROGRESSION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PROJECT_PROGRESSION.md b/PROJECT_PROGRESSION.md index da801804..270dc274 100644 --- a/PROJECT_PROGRESSION.md +++ b/PROJECT_PROGRESSION.md @@ -218,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. 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. * 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. From e3062cb33b349118862f6dc9cd32f6ba80462f7c Mon Sep 17 00:00:00 2001 From: Matteo Collina Date: Fri, 20 Dec 2024 10:16:59 -0800 Subject: [PATCH 5/5] Apply suggestions from code review Co-authored-by: Chris de Almeida Signed-off-by: Matteo Collina --- PROJECT_PROGRESSION.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/PROJECT_PROGRESSION.md b/PROJECT_PROGRESSION.md index 270dc274..5c6f45fb 100644 --- a/PROJECT_PROGRESSION.md +++ b/PROJECT_PROGRESSION.md @@ -200,7 +200,7 @@ 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. -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. +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. #### Examples @@ -218,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. This limitation is to ensure broad representation and to prevent a single organization from having excessive influence on project decision-making. + * 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. * 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.