Florian Hines

@pnadolny13 @tayloramurphy Based on my reading of the issues, I was sort of operating under the assumption that everything would be self-contained in the plugin/extension because at first glance that...

@tayloramurphy was mentioning to @aaronsteers that I'm just about ready to break out the extension sdk into its own repo and package. So we have to tackle the hardest challenge...

@tayloramurphy so for the sdk we currently have: - the repo: `http://github.com/meltano/sdk` - the package name: `singer-sdk` & `singer_sdk` So for this new addition, maybe something like: - the repo:...

fyi - Setup https://github.com/meltano/edk to house the extension ~~sdk~~ edk.

@aaronsteers @tayloramurphy given: > This is built with the the skeleton of a true Meltano SDK in mind - bonus if the skeleton is started. This should also be built...

@tayloramurphy fwiw, I think you nailed it for the product side and its mostly up to us (Engineering) to define the architecture and framework we need to enable this feature...

FYI - created https://github.com/meltano/ext-airflow so I can start moving things out of my dev repo

@tayloramurphy @aaronsteers how are y'all thinking we should transition to the new extension and what do we want the migration to be like for users? Just as a reminder, the...

> > My vote would be to do a preview/beta period for a couple of weeks (at least until the sdk is settled, and we get the dbt extension done)....

@tayloramurphy This will actually just be the name used in the meltano yaml and hub defs right? In that case, im cool with either (personally preferring the _beta suffix). The...