I like the idea of segregate modules into repository, but not at that low level, some modules could ...

# arrow-contributors

[thanerian]

I like the idea of segregate modules into repository, but not at that low level, some modules could be stored into the same git repository as they are related, arrow-ank and arrow-ank-gradle could be in the same git repo for instance same for those with arrow-xxx-yyy structure that share the same xxx, WDYT? there is a technical issue about structure in that way?

[Rachel]

Good point @thanerian, thanks!! 👍

[simon.vergauwen]

Same for Arrow Fx which has 4 modules atm. mtl, reactor and rx besides the original one.

And we’ll probably split it up more later-on.

[simon.vergauwen]

And/or hopefully also gets more instances for KotlinX Flow, and other types.

[thanerian]

@Rachel I currently working on a multi repo environment with shared gradle properties and composite builds, if you are interested I could show you how we are now and problem we face

[Rachel]

Great, thanks @thanerian !!