potiuk commented on PR #41556: URL: https://github.com/apache/airflow/pull/41556#issuecomment-2296204906
@kodurusivakumar34 -> Those options are not really feasible. Apache Airflow is a project belonging to the Apache Software Foundation and whatever we keep and release - formally - as an "Apache Software Foundation software" has to be released formaly and legally using the ASF processess and governance - that includes responsibilty for managing the releases, security fixes, and more - PMC members have to approve and review every such release and we cannot endores or promote 3rd-party managed software to be released without the overhead incurred: review process, PMC and committers approval, licence compliance, security process and policies clear maintenance rules etc. etc. Anything that is released or hosted in "apache" repositories, has to have the ASF "stamp of approval" so to speak. You can start reading here if you are interested https://www.apache.org/legal/release-policy.html - but there are more links to follow when you read it. This is legal, compliance and governance issue, not a technical issue which prevents the ASF to be legally responsible for 3rd-party software that it does not have any control over, once the software gets contributed to the ASF it becomes "The ASF" software - with all the requirements and expectations that come with it. But there is nothing to prevent any other entities to build such a repository of 3rd-party providers or index them. For example there is https://registry.astronomer.io/ where you can browse various airflow providers. And you - or anyone else - can release magento provider on their own and submit it to such registries. -- 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
