abstractFlo/atlas

Monorepo - core and plugins seperate

abstractFlo opened this issue · 5 comments

I think about seperation for core and plugins.
Is it a good idea to provide a repository for each plugin? Manage by an github organization @atlas-framework? This organization is my own and we can publish plugins and so on with this.

You think this is a good idea? Let me know about it

We could make a repo for each one, one for core, and a repo for plugins, both to be monorepo.

I noticed that some projects after moving out from monorepo got outdated easily. Monorepo forces update packages as well

I think a monorepo for core and a single repo for every plugin would be a good solution. But i like Leonard's suggestion too.

i think the monorepo for core is good, but i am little confused about the plugins. It sounds good to have a repo for each plugin. But i like @FDiskas suggestion too, some plugins would not be updated/touched anymore.

Hard to find the right way

We have talk about this feature on stream, we stick with the current approach and let all the stuff inside the monorepo