potiuk commented on issue #53895: URL: https://github.com/apache/airflow/issues/53895#issuecomment-3136002627
The current process for contributing the provider to be "community provider" is described here https://github.com/apache/airflow/blob/main/PROVIDERS.rst#community-managed-providers - please read the documentation there including some past links to discussion and when we decided to accept or not a 3rd-party contributed provider. There are basically two ways you can follow: 1) You can release provider on your own - independently of the community 2) or - if you convince the community that this is fine for the community to accept the provider and maintenance of it (following the criteria describe in the document I linked) - it could become managed in the Airflow monorepo. Generally speaking - any new provider must be discussed on the devlist and there should be either LAZY CONSENSUS reached or vote passed to accept it. I am converting it to a discussion if needed, but you should generally follow the docs and past discussions on 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
