potiuk commented on code in PR #60896:
URL: https://github.com/apache/airflow/pull/60896#discussion_r2724277054
##########
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
Review Comment:
> How is it going to work for existing providers? Are we going to nominate
stewards ad-hoc, or is it going to be applied only for new providers?
If it's only for new providers, it's better to mention that it applies only
for providers created after the approval of AIP-95 on Dec. 10, 2025.
Otherwise, we might need a further discussion of how existing providers will
adapt - because it's not that clear from the AIP.
I think the best approach for that - is that we are going to make a call for
stewards. I bet there will be some obvious (Google and AWS for example) and
less obvious people responding to stewardship call. The remaining ones will be
PMC stewarded - and I think once we slowly start rolling thing we will also
make some review and analysis of existing providers - and we will make
individual decisions for them.
--
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]
