potiuk commented on code in PR #60896:
URL: https://github.com/apache/airflow/pull/60896#discussion_r2714839270


##########
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.

Review Comment:
   ```suggestion
   number of integrations while ensuring quality. Actual code acceptance and 
release governance remains with the Airflow PMC.
   ```
   
   I think ASF and our rules do not require governance of things like 
structure, code conventions, patterns within the provider. While PMC has 
exclusive governance on making a release. This is the legal act of Foundation 
that is important, and where we need to be strict. But I think it's quite ok to 
delegate decisions on the "provider-specific" choices on conventions/structures 
etc. as long as they follow some general architectural choices of Airflow. We 
have good precence in Google, Amazon. Teradata and other providers. where the 
PMC hardly makes decisions on approvals/conventions etc.,but it's cruscial we 
review and accept the code and release it.



-- 
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]

Reply via email to