Think it is a bit a too negative summary ;). On the identity part I guess we can decide it is important or consider we got a single mail and that whatever we do this issue can always popup with whatever name - in particular while we stay at "Apache". So not sure killing G solves anything at all at the end - don't forget subproject often highlight another term than Geronimo.
Also projects are not that random nor unrelated, all together they enable to build real applications. I understand they can look random if you just use one or two but there is some consistency in the dark there ;). That said I join you on the fact each subproject should get one or multiple leads who can handle user requests in a reasonable amount of time to not look too bad. Any idea on adressing that? Should we go on some automotion (on PR?)? Should we elect somebody per subproject? 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 mer. 23 nov. 2022 à 15:37, Raymond Augé <raymond.a...@liferay.com> a écrit : > Let's not forget that there is a branding issue that has been brought up > over the years (most recently here [1]). > > My proposal for retirement [2] of Geronimo was in large part in response > to that; but was also taking into account how low the activity is and how > disjointed the sub-projects are and how the project itself has a rather > confusing identity. Being a "bucket of random, unrelated subprojects" does > not seem very constructive or appealing. > > I understand that this is a hard choice and a tough pill for some people > to swallow, but taking the simple path of just ignoring the issue(s) does > not inspire much confidence in the health of this already struggling > project. > > Anyway, please don't just forget about that. Peace out! > > [1] https://www.mail-archive.com/dev@geronimo.apache.org/msg98301.html > [2] https://www.mail-archive.com/dev@geronimo.apache.org/msg98304.html > > On Wed, Nov 23, 2022 at 8:32 AM Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > >> @François Papon <fpa...@yupiik.com> cause we are far behind and it >> looked easier to use something already up to date (even if incomplete, >> smallrye has a ton of SPI but overall, once implemented it works) >> >> 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 mer. 23 nov. 2022 à 14:27, Francois Papon < >> francois.pa...@openobject.fr> a écrit : >> >>> Regarding our MP implementation, someone knows why the TomEE team >>> decided to move from our to Smallrye? >>> >>> As TomEE is an Apache project, it can make sense to use and promote the >>> Apache implementation of MP... >>> >>> regards, >>> >>> Francois >>> On 23/11/2022 11:11, Romain Manni-Bucau wrote: >>> >>> In terms of storage and committers you are right but in terms of users a >>> key difference is "will it be a new release". >>> If you look at MP it is quite unlikely since project seems way less >>> consummed than it was some years ago and since TomEE moves to smallrye at >>> the same time we don't update it anymore, not sure we would do any new >>> release. >>> So while it is ok to keep it there, we should also communicate clearly >>> we don't intend to do any new release if it is the case - same story than >>> geronimo server basically. >>> >>> >>> 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 mer. 23 nov. 2022 à 11:00, Jean-Louis MONTEIRO <jeano...@gmail.com> >>> a écrit : >>> >>>> Yeah I understand there isn't much activity, but from time to time, >>>> they are updated to follow specifications and they are used by other >>>> projects (transaction manager, batchEE, etc). So they need a home. Of >>>> course we can split them apart and give them to different projects, but it >>>> does not solve any problem. The people are the same. As soon as we allow >>>> all projects to contribute or even become committers here, I don't see any >>>> issue at the moment at least. >>>> >>>> Le mer. 23 nov. 2022 à 10:53, Mark Struberg via dev < >>>> dev@geronimo.apache.org> a écrit : >>>> >>>>> *Overall I don't understand the recent discussions to kill all >>>>> Geronimo projects and subprojects.* >>>>> >>>>> *+1* >>>>> >>>>> Actually I'd rather keep it here as it is used outside TomEE as well. >>>>> >>>>> LieGrue, >>>>> strub >>>>> >>>>> >>>>> Am 23.11.2022 um 10:15 schrieb Jean-Louis MONTEIRO <jeano...@gmail.com >>>>> >: >>>>> >>>>> I've opened a thread on the TomEE side to maybe transition BatchEE to >>>>> TomEE. >>>>> >>>>> *Overall I don't understand the recent discussions to kill all >>>>> Geronimo projects and subprojects.* >>>>> >>>>> Le mar. 22 nov. 2022 à 23:33, Romain Manni-Bucau < >>>>> rmannibu...@gmail.com> a écrit : >>>>> >>>>>> No requirement, just making it living (updating versions and spec >>>>>> impl). >>>>>> >>>>>> Le mar. 22 nov. 2022 à 23:31, Mark Struberg via dev < >>>>>> dev@geronimo.apache.org> a écrit : >>>>>> >>>>>>> I still use batchee very much. So I'd keep it well alive. Also >>>>>>> investing time on and on. >>>>>>> >>>>>>> Is there anything which is required to do? >>>>>>> >>>>>>> LieGrue, >>>>>>> strub >>>>>>> >>>>>>> >>>>>>> Am 18.11.2022 um 09:50 schrieb Francois Papon < >>>>>>> francois.pa...@openobject.fr>: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I don't have insights about how BatchEE is used today and how the >>>>>>> jbatch specification is support by others. >>>>>>> >>>>>>> +1 for freeze. >>>>>>> >>>>>>> regards, >>>>>>> >>>>>>> François >>>>>>> On 18/11/2022 08:21, Romain Manni-Bucau wrote: >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> We discussed some time ago to drop batchee as an active subproject, >>>>>>> wonder where we are now on this? >>>>>>> Do we freeze it and document we don't maintain it anymore? >>>>>>> >>>>>>> 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> >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> -- >>>>> Jean-Louis >>>>> >>>>> >>>>> >>>> >>>> -- >>>> Jean-Louis >>>> >>> > > -- > *Raymond Augé* (@rotty3000) > Senior Software Architect *Liferay, Inc.* (@Liferay) > OSGi Fellow, Java Champion >
