Sorry to keep you waiting that long. I am catching up with some old / unhandled threads.
> One major con is it won't be part of Airflow constraints file. What is the implication of this? If you have many dependencies that can conflict with other providers, we are publishing "constraints" that all but guarantee that there are no conflicting dependencies and that all the community providers can be installed together. But if you have little number of dependencies and you do not limit their versions excessively, that does not give you much. You can read more about constraints in https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pinned-constraint-files > - How would I make this provider discoverable to Airflow users? Is the Astronomer registry the main venue for this or are there others? * Anyone (like Astronomer) can run their own registry. But Astronomer is one of those stakeholders in Airflow that contributes a lot to it and certainly is recognizable among Airflow users. * Another option you have is to make PR to https://airflow.apache.org/ecosystem/ page for one. * Also there are trove classifiers in PyPI (that we applied for and got approved : https://pypi.org/search/?c=Framework+%3A%3A+Apache+Airflow+%3A%3A+Provider and you can add one when you submit your package. Generally there is no "endorsement" we can make as an Apache Software Foundation project for the code/projects that are not governed by Apache Airflow Governance rules (so basically any code that is in our repos) - this is mainly for legal/responsibility reasons, but you are absolutely free to "market" your own provider in any way you find fit - providing that you do not claim your provider is "Apache Software Foundation" software. There are some rules you can use and most notably there are clear rules about "Powered by Apache Airflow" - https://www.apache.org/foundation/marks/faq/#poweredby - Would I be able to contribute updates to this docs page, adding pandera as one of the supported tools? https://docs.astronomer.io/learn/data-quality This is a question to Astronomer, not to Airflow Community - you can ask them via their contact address. J. On Tue, Dec 6, 2022 at 9:06 PM Niels Bantilan <[email protected]> wrote: > @Kaxil > > > Would you be willing to maintain the provider in your own repos? > > And if accepted to Apache Airflow repo, would you or someone you know > would be open to maintaining it with newer APIs? > > I'm guessing these are mutually exclusive options, correct? I'd be open to > either one. Having a separate release cadence and isolated CI/CD seems like > a nice pro. > > > One major con is it won't be part of Airflow constraints file. > > What is the implication of this? > > Re: hosting my own repos, a few other questions I have are: > - How would I make this provider discoverable to Airflow users? Is the > Astronomer registry the main venue for this or are there others? > - Would I be able to contribute updates to this docs page, adding pandera > as one of the supported tools? > https://docs.astronomer.io/learn/data-quality > > -NB > > >
