Would it be appropriate for me to reach out to one of the airflow-dbt maintainers and see if they’d be interested in managing a provider?
> On Mar 3, 2021, at 13:23, Ash Berlin-Taylor <a...@apache.org> wrote: > > I honestly think no: not because it's not useful, but because dbt have the > time and ability to maintain their own provider package, much like Great > Expectations do: > > https://greatexpectations.io/blog/airflow-operator/ > > I'd much rather we work with dbt to do what ever is needed to make it a full > provider than pull it in tree when it already exists as a third party package. > > -ash > >> On 3 March 2021 18:04:01 GMT, Ryan Hatter <ryannhat...@gmail.com> wrote: >> Hey all, >> >> dbt seems to continue to gain momentum. There's already an airflow-dbt >> project that is essentially a provider package. Would it make sense to fold >> the dbt_hook and dbt_operator into a provider package in the official >> airflow repo?
