You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2026/05/10 01:37:14 UTC

(airflow) branch main updated: simplify new provider acceptance policy to discussion-only (#66010)

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 03d3a8b41a0 simplify new provider acceptance policy to discussion-only (#66010)
03d3a8b41a0 is described below

commit 03d3a8b41a059196bbc31f39d906b9dd29d2e251
Author: Elad Kalif <45...@users.noreply.github.com>
AuthorDate: Sun May 10 04:37:07 2026 +0300

    simplify new provider acceptance policy to discussion-only (#66010)
    
    * simplify new provider acceptance policy to discussion-only
    
    * update
---
 PROVIDERS.rst                                   |  9 +--
 providers/ACCEPTING_PROVIDERS.rst               | 94 +++++++++++++++++++++----
 providers/SUSPENDING_AND_REMOVING_PROVIDERS.rst |  3 +-
 providers/THIRD_PARTY_PROVIDERS.rst             | 52 --------------
 4 files changed, 85 insertions(+), 73 deletions(-)

diff --git a/PROVIDERS.rst b/PROVIDERS.rst
index 717416e47ce..69c71872705 100644
--- a/PROVIDERS.rst
+++ b/PROVIDERS.rst
@@ -89,10 +89,8 @@ The following documents provide detailed information about specific aspects of p
    * - `Provider Governance <providers/PROVIDER_GOVERNANCE.rst>`_
      - Governance framework, stewardship model, lifecycle stages (incubation, production,
        attic/deprecation), health metrics, and periodic reviews
-   * - `3rd-Party Providers <providers/THIRD_PARTY_PROVIDERS.rst>`_
-     - Relation to community providers, system test dashboards, and mixed governance model
    * - `Accepting New Providers <providers/ACCEPTING_PROVIDERS.rst>`_
-     - Prerequisites, approval process, and historical examples for proposing new community providers
+     - Prerequisites, approval process, system tests guidance, and historical examples for proposing new community providers
    * - `Provider Releases and Versioning <providers/PROVIDER_RELEASES.rst>`_
      - Release process, SEMVER versioning, provider distribution states, and minimum Airflow
        version policy
@@ -164,4 +162,7 @@ See `Suspending and Removing Providers: Removing providers <providers/SUSPENDING
 3rd-party providers
 ===================
 
-See `3rd-Party Providers <providers/THIRD_PARTY_PROVIDERS.rst>`_.
+See the `Ecosystem page <https://airflow.apache.org/ecosystem/#third-party-airflow-plugins-and-providers>`_
+for a registry of available 3rd-party providers, and the
+`Accepting New Community Providers: Alternative — 3rd-party managed providers <providers/ACCEPTING_PROVIDERS.rst#alternative-3rd-party-managed-providers>`_
+section for guidance on when a 3rd-party provider is the right choice.
diff --git a/providers/ACCEPTING_PROVIDERS.rst b/providers/ACCEPTING_PROVIDERS.rst
index f79bc1420c7..5f02375a31b 100644
--- a/providers/ACCEPTING_PROVIDERS.rst
+++ b/providers/ACCEPTING_PROVIDERS.rst
@@ -29,6 +29,14 @@ guidelines and community principles.
 For details on the incubation stage and graduation criteria, see
 `Provider Governance <PROVIDER_GOVERNANCE.rst#incubation-stage>`_.
 
+.. note::
+
+   There are two options for providers:
+
+   1. A provider registered under Apache Airflow, subject to the process described below.
+   2. A 3rd-party managed provider published on the
+      `Ecosystem page <https://airflow.apache.org/ecosystem/#third-party-airflow-plugins-and-providers>`_.
+
 Prerequisites for proposing a new provider
 ------------------------------------------
 
@@ -36,26 +44,75 @@ Prerequisites for proposing a new provider
 2. **Stewardship commitment**: At least two individuals willing to serve as stewards
 3. **Committer sponsorship**: At least one existing Airflow Committer willing to sponsor the stewards
 4. **Quality standards**: Code, tests, and documentation meeting the Contributing Guide standards
+5. **System tests**: If the provider integrates with a live external service, the proposal should
+   describe how the integration will be continuously validated. The community encourages stewards
+   to run system tests and publish results on a publicly accessible dashboard. See the
+   `System Test Dashboards <https://airflow.apache.org/ecosystem/#airflow-provider-system-test-dashboards>`_
+   for examples of how existing providers handle this.
 
 Approval process
 -----------------
 
-Accepting new community providers requires a ``[DISCUSSION]`` followed by ``[VOTE]`` thread at the
-Airflow `devlist <https://airflow.apache.org/community/#mailing-list>`_.
+Accepting new community providers requires a ``[DISCUSS]`` thread on the Airflow
+`devlist <https://airflow.apache.org/community/#mailing-list>`_. No formal vote is required.
 
-For integrations with well-established open-source software (Apache Software Foundation, Linux
-Foundation, or similar organizations with established governance), a ``[LAZY CONSENSUS]`` process
-may be sufficient, provided the PR includes comprehensive test coverage and documentation.
-
-The ``[DISCUSSION]`` thread should include:
+The discussion thread should include:
 
 * Description of the integration and its value to the Airflow ecosystem
 * Identification of the proposed stewards and their sponsoring committer(s)
 * Commitment to meet incubation health metrics within 6 months
 * Plan for participating in quarterly governance updates
+* Sponsoring committer(s) if you already have alignment with one or asking for a volunteer
+
+If no objections are raised within 7 days, the proposal is considered accepted and the
+contributor may proceed with opening a PR.
+
+Discussion thread template
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Use the following template when opening your ``[DISCUSS]`` thread on the devlist:
+
+.. code-block:: text
+
+   Subject: [DISCUSS] New Community Provider: <name/service>
+
+   Hi Airflow community,
 
-The ``[VOTE]`` follows the usual Apache Software Foundation voting rules concerning
-`Votes on Code Modification <https://www.apache.org/foundation/voting.html#votes-on-code-modification>`_
+   I'd like to propose adding a new community provider for <Service/Tool Name>.
+
+   Integration overview
+   --------------------
+   <Brief description of what the service/tool does and why it is valuable to Airflow users.>
+
+   System tests
+   ------------
+   <If the provider integrates with a live external service, describe how system tests will be
+   run and validated, and whether results will be published to a public dashboard. If no live
+   service is involved, state that system tests are not required. See the existing dashboards
+   for examples: https://airflow.apache.org/ecosystem/#airflow-provider-system-test-dashboards>
+
+   Proposed stewards
+   -----------------
+   - <Name, GitHub handle, email>
+   - <Name, GitHub handle, email>
+
+   Sponsoring committer(s)
+   -----------------------
+   - <Name, GitHub handle>
+
+   Working implementation
+   ----------------------
+   <Link to the draft PR or repository demonstrating a working implementation.>
+
+   Incubation commitment
+   ---------------------
+   We commit to:
+   - Maintaining the provider and responding to issues within a reasonable time
+   - Meeting the incubation health metrics within 6 months
+   - Participating in quarterly governance updates
+
+   Best regards,
+   <Your name>
 
 Alternative: 3rd-party managed providers
 -----------------------------------------
@@ -70,17 +127,24 @@ provides visibility for 3rd-party providers, and this approach allows service pr
 * Support older Airflow versions if needed
 
 There is no difference in technical capabilities between community and 3rd-party providers.
-See `3rd-party providers <THIRD_PARTY_PROVIDERS.rst>`_ for more details.
+See the `Ecosystem page <https://airflow.apache.org/ecosystem/#third-party-airflow-plugins-and-providers>`_
+for a registry of available 3rd-party providers.
 
 Examples
 --------
 
-* Vespa.ai - `[PROPOSAL] New Provider: Vespa.ai - AIP-95 <https://lists.apache.org/thread/6myz043vx7v57zk95qo3wd0qcwt9r9th>`_, `Missing Vote <missing>`_
-* Informatica - `[PROPOSAL] New Provider: Informatica - AIP-95 <https://lists.apache.org/thread/wsfgh23jm6hkrly4lx1m21ftllqshpgo>`_, `Missing Vote <missing>`_
-* Stripe - `[DISCUSS] Interest in adding a Stripe provider to Airflow <https://lists.apache.org/thread/r9fr6571w3ssx07bnd5lgc9m88r1xy3c>`_, `Missing Vote <missing>`_
+WIP: To be added later
+
+Examples (pre policy simplification)
+-------------------------------------
+
+* Akeyless - `[PROPOSAL] New community provider: apache-airflow-providers-akeyless <https://lists.apache.org/thread/ztf1mqbkoc39qz6o419lynttk4fhoz0t>`_, `[VOTE] New Community Provider: apache-airflow-providers-akeyless <https://lists.apache.org/thread/jqvbo8x82g87okn0fqh5o2bxxx84g9qj>`_, `[RESULT][VOTE] New Community Provider: apache-airflow-providers-akeyless <https://lists.apache.org/thread/87zn154n2vppg2vsxlbhscnfl68vb4ls>`_
+* Vespa.ai - `[DISCUSS] New Provider: Vespa.ai - AIP-95 <https://lists.apache.org/thread/6myz043vx7v57zk95qo3wd0qcwt9r9th>`_
+* Informatica - `[DISCUSS] New Provider: Informatica - AIP-95 <https://lists.apache.org/thread/wsfgh23jm6hkrly4lx1m21ftllqshpgo>`_
+* Stripe - `[DISCUSS] Interest in adding a Stripe provider to Airflow <https://lists.apache.org/thread/r9fr6571w3ssx07bnd5lgc9m88r1xy3c>`_
 
-Historical examples (Before AIP-95)
------------------------------------
+Historical examples (pre-AIP-95)
+--------------------------------
 
 * Huawei Cloud provider - `Discussion <https://lists.apache.org/thread/f5tk9c734wlyv616vyy8r34ymth3dqbc>`_
 * Cloudera provider - `Discussion <https://lists.apache.org/thread/2z0lvgj466ksxxrbvofx41qvn03jrwwb>`_, `Vote <https://lists.apache.org/thread/8b1jvld3npgzz2z0o3gv14lvtornbdrm>`_
diff --git a/providers/SUSPENDING_AND_REMOVING_PROVIDERS.rst b/providers/SUSPENDING_AND_REMOVING_PROVIDERS.rst
index 9a54b9eec79..c53b07f292f 100644
--- a/providers/SUSPENDING_AND_REMOVING_PROVIDERS.rst
+++ b/providers/SUSPENDING_AND_REMOVING_PROVIDERS.rst
@@ -43,8 +43,7 @@ This means:
 * Tests of the provider will not be run on our CI (in main branch)
 * Dependencies of the provider will not be installed in our main branch CI image nor included in constraints
 * We can still decide to apply security fixes to released providers - by adding fixes to the main branch
-  but cherry-picking, testing and releasing them in the patch-level branch of the provider similar to the
-  mixed governance model described in `3rd-party providers <THIRD_PARTY_PROVIDERS.rst#mixed-governance-model>`_.
+  but cherry-picking, testing and releasing them in a dedicated patch-level branch of the provider.
 
 The suspension may be triggered by any committer after the following criteria are met:
 
diff --git a/providers/THIRD_PARTY_PROVIDERS.rst b/providers/THIRD_PARTY_PROVIDERS.rst
deleted file mode 100644
index dc3953a6474..00000000000
--- a/providers/THIRD_PARTY_PROVIDERS.rst
+++ /dev/null
@@ -1,52 +0,0 @@
- .. Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
- ..   http://www.apache.org/licenses/LICENSE-2.0
-
- .. Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-3rd-Party Providers
-====================
-
-.. contents:: Table of Contents
-   :depth: 3
-   :local:
-
-Relation to community providers
----------------------------------
-
-Providers, can also be maintained and released by 3rd parties (service providers or systems integrators).
-There is no difference between the community and 3rd party providers - they have all the same capabilities
-and limitations.
-
-This is especially in case the provider concerns 3rd-party service that has a team that can manage provider
-on their own, has a rapidly evolving live service, and believe they need a faster release cycle than the community
-can provide.
-
-Information about such 3rd-party providers are usually published at the
-`Ecosystem: plugins and providers <https://airflow.apache.org/ecosystem/#third-party-airflow-plugins-and-providers>`_
-page of the Airflow website and we encourage the service providers to publish their providers there. You can also
-find a 3rd-party registries of such providers, that you can use if you search for existing providers (they
-are also listed at the "Ecosystem" page in the same chapter)
-
-While we already have - historically - a number of 3rd-party service providers managed by the community,
-most of those services have dedicated teams that keep an eye on the community providers and not only take
-active part in managing them (see mixed-governance model below), but also provide a way that we can
-verify whether the provider works with the latest version of the service via dashboards that show
-status of System Tests for the provider. This allows us to have a high level of confidence that when we
-release the provider it works with the latest version of the service. System Tests are part of the Airflow
-code, but they are executed and verified by those 3rd party service teams. We are working with the 3rd
-party service teams (who are often important stakeholders of the Apache Airflow project) to add dashboards
-for the historical providers that are managed by the community, and current set of Dashboards can be also
-found at the
-`Ecosystem: system test dashboards <https://airflow.apache.org/ecosystem/#airflow-provider-system-test-dashboards>`_