is anyone active working on reorging the airbyte-integrations dir structure?

michel has a PR for it

yeah. honestly probably easier to start from scratch.

if not i’m going to go ahead and do it following jared’s structure https://github.com/airbytehq/airbyte/pull/626#pullrequestreview-512165494

does it have a ton of merge conflicts or something?

yes

issue is that maybe that structure is not very python friendly though

fair enough. what would make the structure python friendly?

i've been trying to make one but haven't succeeded yet

what is the concern with even the current structure from a python perspective? Is it within the individual package dirs? or the monorepo as a whole?

i think it’s important to get out of current state which is pretty non sensical.

yeah I think from a project organization perspective there are better options than what we have

I'm just trying to understand what makes a project structure good or bad for multiple python libraries and apps

python is not usually used in monorepo i think

but it should still be doable

outside of that are there constraints?