+1, makes sense since the adoption here leads to some issues which does not look like trivial to solve community wise.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le lun. 28 nov. 2022 à 11:27, Jean-Baptiste Onofré <j...@nanthrax.net> a écrit : > Hi guys, > > In regards of the discussion we have around Karaf log, the different > comments about Karaf vs Minho, clearly, we have two different visions > and communities: > - the Karaf community very likes Karaf as it is today (powered by > OSGi) and not willing to move to something else > - the Minho community would be "decoupled" from existing Karaf > community, coming from other projects like spring boot, microprofile, > etc > > So, it means that we would have two different communities in the Karaf > "umbrella", which is not ideal, and actually it can cause branding > issues. > We can have the issue where Minho at Karaf will "block" some users and > contributors because they will "couple" Minho to Karaf (which is not > the case). > > So, IMHO, it would be cleaner to keep Karaf to what it is today (an > OSGi runtime) and move Minho to its own project. > > I would call for a vote to remove Minho from Karaf and create a > project proposal based on it (and a couple of additional features). > > Thoughts ? > > Regards > JB >
