Split repo for extensions

[Hipska]

It might be better to split the extensions each into their own repository?

They will be easier to be found, downloaded, forked and made patches for it.

What do you think?

[jbostoen]

I've considered it before. But there are so many. It would feel like an overdose I think. That's why I keep them grouped. People can still pick what they want from it. On Jun 5, 2020 14:09, Thomas Casteleyn <[email protected]> wrote: It might be better to split the extensions each into their own repository? They will be easier to be found, downloaded, forked and made patches for it. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#31>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABQ7ZM3OE6ENJ2OOSJZ4PALRVDN6DANCNFSM4NTP36YQ>.

[Hipska]

To me it looks annoying that you need to pull/checkout this complete repository if you only want to use 1 extension.

[jbostoen]

Actually been leaving this open to consider. But keeping them together also makes it easier to find the other extensions.

[Hipska]

This repo could stay here to link them all (either via hyperlink in README or with git submodules)

[jbostoen]

I'll look into the submodules approach when I have some more time :)

[jbostoen]

I've started experimenting with the submodule approach.
I probably won't make all separate repos at once, but if there's any that you'd like to see split off sooner, let me know.

Otherwise it will probably happen when I have more time or work on it.

Already available:

• jb-mail-to-ticket-automation-v2