sunilkmallam commented on PR #35909: URL: https://github.com/apache/airflow/pull/35909#issuecomment-1831324366
> Before looking at that and spending any time on it by anyone, you should be aware @SatishChGit that you need to get approval on the devlist to contibute a new provider. > > Read this: https://github.com/apache/airflow/blob/main/PROVIDERS.rst#accepting-new-community-providers > > And follow it. Note that in case of external services that have enough of the resources and possibly teams that can manage their providers, we have strong preference that they release and manage the providers on their own - we have no experience nor will to manage 3rd-party providers in the community unless the 3rd-party will convince us that it's a good idea and convince us they will continue spending time on contributing and managing their implementation. > > One of the big and important prerequisites is have a 3rd-party provide and commits to maintaining of system tests that they will run and dashboards such as https://airflow.apache.org/ecosystem/#airflow-provider-system-test-dashboards > > Thre were a few discussions in the recent past wher we refused to accept such 3rd-party providers - for us such code increases maintenance burden and we generally prefer that the 3rd-parties do that on their own (especially when they are big and established providers like Teradata. > > Example discussion about it here where we refused to accept such a provider (it has link to previous discussions) https://lists.apache.org/thread/f5tk9c734wlyv616vyy8r34ymth3dqbc > > Here example discussion where decided to accept them (where Astronomer committed to maintenance, and made an effort to build and run their system dashboard for LLM-related providers: > > https://lists.apache.org/thread/0d669fmy4hn29h5c0wj0ottdskd77ktp > > Read all that, also try to search the devlist for similar discussions and see which path you want to follow. If you would like to still contribute it, you should start with discussion on the devlist proposing it and explaining why you think we should accep the new provider. Hey Jarek @potiuk, I'm Sunil Mallam, a Staff Product Manager at Teradata. I and Satish have had a few discussions with Kaxil about creating a proposal for becoming a Community Provider. I've actually reached out to him, but looks like he's away on a personal situation. Our main goal to be a community provider is for Teradata's customers (approx. 700 of Fortune1000) to be confident in the quality and stability of the operators. We have a team of engineers who are dedicated to build and support Third Party Connectors/Tools, which would make our contributions to Airflow consistent, i.e. end-to-end testing and adding/running relevant "system tests" with every upgrade (which we have considered for the initial implementation). Satish is working on the dashboard and we'd share the dashboard link shortly. I will also send an official email to Kaxil with the proposal and the dashboard link, for review. Would you want me to include you in the email as well? -- 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]
