RNHTTR commented on code in PR #60896:
URL: https://github.com/apache/airflow/pull/60896#discussion_r2714495770
##########
PROVIDERS.rst:
##########
@@ -88,49 +88,233 @@ Airflow main branch to being decommissioned and removed
from the main branch in
`Managing provider's lifecycle
<https://github.com/apache/airflow/blob/main/providers/MANAGING_PROVIDERS_LIFECYCLE.rst>`_
+Provider Governance Framework
+-----------------------------
+
+This section describes the governance framework for community providers,
including lifecycle stages,
+stewardship model, and quantitative health metrics.
+
+Airflow's success is built on its extensive ecosystem of community-supported
integrations—over 1,600
+hooks, operators, and sensors released as part of 90+ provider packages. These
integrations are critical
+for "ubiquitous orchestration." This governance framework establishes a
scalable method to grow the
+number of integrations while ensuring quality. All governance remains with the
Airflow PMC.
+
+Provider Stewardship Model
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Each provider or integration component must have designated **stewards**
responsible for ensuring
+the health criteria described below are met:
+
+* **Minimum stewards**: At least two unique individuals must serve as stewards
for each provider
+* **Role definition**: Stewards are subject matter experts for the integration
(service, language,
+ or skill). Stewardship is a responsibility, not an additional authority or
privilege
+* **Committer sponsorship**: Each steward must be sponsored by an existing
Airflow Committer who
+ ensures stewards fulfill their responsibilities. The sponsor is responsible
for guiding the stewards
+ through the process of maintaining the provider, following best practices
including regular dependency
+ updates, issue resolution, and ensuring the provider meets the health
metrics described below. The sponsor
+ is NOT responsible for the codebase itself, which remains the responsibility
of the stewards.
Review Comment:
```suggestion
* **Committer sponsorship**: Each steward must be sponsored by an existing
Airflow Committer. The
sponsor ensures that stewards fulfill their responsibilities and provides
guidance on maintaining the
provider according to best practices. This includes regular dependency
updates, issue resolution, and
ensuring the provider meets the health metrics required for its current
lifecycle stage (that is, incubation
or production). The sponsor is NOT responsible for the provider’s codebase,
which remains the
responsibility of the stewards.
```
##########
PROVIDERS.rst:
##########
@@ -88,49 +88,233 @@ Airflow main branch to being decommissioned and removed
from the main branch in
`Managing provider's lifecycle
<https://github.com/apache/airflow/blob/main/providers/MANAGING_PROVIDERS_LIFECYCLE.rst>`_
+Provider Governance Framework
+-----------------------------
+
+This section describes the governance framework for community providers,
including lifecycle stages,
+stewardship model, and quantitative health metrics.
+
+Airflow's success is built on its extensive ecosystem of community-supported
integrations—over 1,600
+hooks, operators, and sensors released as part of 90+ provider packages. These
integrations are critical
+for "ubiquitous orchestration." This governance framework establishes a
scalable method to grow the
+number of integrations while ensuring quality. All governance remains with the
Airflow PMC.
+
+Provider Stewardship Model
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Each provider or integration component must have designated **stewards**
responsible for ensuring
+the health criteria described below are met:
+
+* **Minimum stewards**: At least two unique individuals must serve as stewards
for each provider
+* **Role definition**: Stewards are subject matter experts for the integration
(service, language,
+ or skill). Stewardship is a responsibility, not an additional authority or
privilege
+* **Committer sponsorship**: Each steward must be sponsored by an existing
Airflow Committer who
+ ensures stewards fulfill their responsibilities. The sponsor is responsible
for guiding the stewards
+ through the process of maintaining the provider, following best practices
including regular dependency
+ updates, issue resolution, and ensuring the provider meets the health
metrics described below. The sponsor
+ is NOT responsible for the codebase itself, which remains the responsibility
of the stewards.
+* **Accountability**: Ultimate accountability remains with the Airflow PMC and
Committers
+* **Transitions**: Neither sponsorship nor stewardship are roles in
perpetuity—they can be
Review Comment:
```suggestion
* **Transitions**: Neither sponsorship nor stewardship are roles in
perpetuity; they can be
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
