jscheffl commented on code in PR #60896: URL: https://github.com/apache/airflow/pull/60896#discussion_r2714621580
########## providers/MANAGING_PROVIDERS_LIFECYCLE.rst: ########## @@ -18,6 +18,36 @@ **The outline for this document in GitHub is available at top-right corner button (with 3-dots and 3 lines).** +Provider Governance Overview +============================ + +Before diving into the technical details of creating and managing providers, please familiarize +yourself with the governance framework that applies to all community providers: + +* `Provider Governance Framework <https://github.com/apache/airflow/blob/main/PROVIDERS.rst#provider-governance-framework>`_ + +Key governance concepts: + +* **Lifecycle stages**: All providers move through Incubation → Production → Attic/Deprecation +* **Stewardship**: Each provider requires at least two stewards sponsored by Airflow Committers +* **Health metrics**: Quantitative criteria determine readiness for promotion or deprecation +* **Periodic reviews**: The PMC reviews provider health quarterly + +All new providers must start in the **Incubation** stage (unless specifically accelerated by the PMC) +and meet the graduation criteria before moving to Production status. + +Stewardship Requirements for New Providers +------------------------------------------ + +When proposing a new community provider, you must: + +1. Identify at least two individuals willing to serve as stewards +2. Secure sponsorship from at least one existing Airflow Committer for each steward Review Comment: Not, sure - is not clarified above... is it clear that a steward is a non-committer? Because if two committers take the lead then this does not apply, correct? ```suggestion 2. Secure sponsorship from at least one existing Airflow Committer for each steward (if steward is not itself a committer) ``` -- 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]
