Hi Alan!
> The commit activity you speak of is really just small number of minor patches
> and a merge of years of work by IBM.
No, this was all done in one big fat commit.
There really have been 60 other committs during that time!
So it's not just a one-time effect due to Yoko.
I have to ad
The commit activity you speak of is really just small number of minor patches
and a merge of years of work by IBM. I’m just adding a bit of clarity there.
On it’s own, it indicates to me that the “home for Java API specs” is not a
fruitful path. As it stands, there’s not a lot of activity and
I have not been active for a long time, so I will also be leaving.
On Mar 26, 2017 3:08 PM, "Jason Dillon" wrote:
I will be leaving as well.
—jason
On March 26, 2017 at 12:01:05 PM, Kevan Miller (kevan.mil...@gmail.com)
wrote:
I'll be leaving.
On Fri, Mar 24, 2017 at 4:21 PM, Romain Manni-B
I will be leaving as well.
—jason
On March 26, 2017 at 12:01:05 PM, Kevan Miller (kevan.mil...@gmail.com) wrote:
I'll be leaving.
On Fri, Mar 24, 2017 at 4:21 PM, Romain Manni-Bucau
wrote:
+1
Le 25 mars 2017 00:17, "David Jencks" a écrit :
I like this approach. Thank you for making a conc
I'll be leaving.
On Fri, Mar 24, 2017 at 4:21 PM, Romain Manni-Bucau
wrote:
> +1
>
> Le 25 mars 2017 00:17, "David Jencks" a écrit :
>
>> I like this approach. Thank you for making a concrete suggestion and
>> taking the lead. I intend to stay on the PMC and at least occasionally help
>> out.
+1
Le 25 mars 2017 00:17, "David Jencks" a écrit :
> I like this approach. Thank you for making a concrete suggestion and
> taking the lead. I intend to stay on the PMC and at least occasionally help
> out.
>
> david jencks
>
> > On Mar 24, 2017, at 8:55 AM, Mark Struberg wrote:
> >
> > Of cou
I like this approach. Thank you for making a concrete suggestion and taking
the lead. I intend to stay on the PMC and at least occasionally help out.
david jencks
> On Mar 24, 2017, at 8:55 AM, Mark Struberg wrote:
>
> Of course we do not have a huge community. But a very long lasting one. An
Of course we do not have a huge community. But a very long lasting one. And
there is not really standstill. There have been 64 committs in the last 3
monts. This is actually not too bad!
So how to move on?
Who wants to remain active in the PMC? Who wants to leave?
We already pinned down the pa
"need" and "in use" does not necessarily translate into community. The need
for the geronimo components that have been discussed is not new. As far as
I can tell, so far, that has not translated into a community.
If we want to continue the project, demonstrate the community that is
needed for the
I've been on vacation, so this was an interesting conversation to come home
to... :-) I'm not a member of the Geronimo PMC, but I've been monitoring
the activity with Geronimo for years. Thus, I have no "voting" capability,
but I do have an interest...
I like the analysis that Mark started with
Hi Alan!
There are quite a few things which fit into this scenario imo.
I think we really miss some 'toolbox project' for EE components at the ASF.
There was a tendency to make all those projects own TLPs for some time. But
that approach simply doesn't scale, and we end up with the same people i
After a good night’s sleep, I re-read this thread and I’ll respond without
trying to guide you in where and how you decide to go with your efforts; thanks
in advance for letting me reboot my reply. :)
Any pivot that this community decides upon, will have to be justified to the
ASF board. We w
I’m not opposed to aggregation, per se. I’m just trying to point out a
possibly different way of jumpstarting community activity, a different way of
searching for a new direction for Geronimo.
It’s different than doing an inventory of stuff we have and thinking, “how can
we make this stuff mor
I have quite a hard time to understand why it is an issue having a project
led by the aggregation of others and not by itself? Assume one sec we close
Geronimo or it doesnt exist, then we'll move the bit of code in one of the
project - let say tomee - and tomee will becomes the exact same kind of
p
It has been my personal experience that need is the catalyst for a vibrant OSS
project. The product and community spring forth from that. Adopting an “if we
build it they will come” tactic does not usually result in success. Rather
than rummaging through the trunk to see what bits people migh
> On Mar 8, 2017, at 10:44 AM, Mark Struberg wrote:
>
> Alan, I understand that you don't want to put much more energy into this
> project. That is totally understandable and fine.
> But while you are PMC chair you still cannot declare that the project is dead
> as long as there are enough PM
+1
> On Mar 9, 2017, at 5:46 AM, Alex Karasulu wrote:
>
> I think more important than whether or not JEE is popular (or whatever along
> those lines), are the questions about community health and is the PMC still
> capable of fulfilling its duties.
>
> My 2 cents,
> --Alex
>
> On Thu, Mar 9,
I totally agree.
But interest from the community is always a product of a good product and
feature roadmap.
Without any good product you will not be able to build a sustainable community
around it.
Of course there are many things which can trash a community despite a good
product. But without
ActiveMQ Artemis and ActiveMQ 5.x are using JMS and JMS 2.0
On Thu, Mar 9, 2017 at 4:08 AM, Mark Struberg wrote:
> Romain and I went through the Geronimo SVN and made a list of which
> components are used by other projects.
>
>
> Useful Geronimo components from https://svn.apache.org/repos/asf/g
I think more important than whether or not JEE is popular (or whatever
along those lines), are the questions about community health and is the PMC
still capable of fulfilling its duties.
My 2 cents,
--Alex
On Thu, Mar 9, 2017 at 12:08 PM, Mark Struberg wrote:
> Romain and I went through the Ger
Romain and I went through the Geronimo SVN and made a list of which components
are used by other projects.
Useful Geronimo components from https://svn.apache.org/repos/asf/geronimo/
https://svn.apache.org/repos/asf/geronimo/KEYS
https://svn.apache.org/repos/asf/geronimo/components/txmanager
I go back and forth on whether to shut G down completely. Perhaps it would be
useful to inventory which parts are used by which other projects? Off the top
of my head….
Specs …. who uses G’s and who has their own?
Components…. I think there are several users of the transaction manager, I
don’
A valid point is activity related to G happens elsewhere, However elsewhere
is not "tomee" which would make things simple to move but A, B, C so
shutting down G is likely the easiest solution for G itself but also the
worse for all its dependent projects - and ASF consistency since G is now
seen as
I’ve monitored G for several years since my departure. For me, JEE is not my
main area of focus and as such, I’ve invested little time in the project apart
from reading the e-mail threads. This is a community decision and posting the
discussion to dev@ is the right venue.
As an inactive membe
On March 8, 2017 at 10:44:45 AM, Mark Struberg (strub...@yahoo.de) wrote:
Alan, I understand that you don't want to put much more energy into this
project. That is totally understandable and fine.
But while you are PMC chair you still cannot declare that the project is dead
as long as there are
unsubscribe
On Wed, Mar 8, 2017 at 6:44 PM, Mark Struberg wrote:
> Alan, I understand that you don't want to put much more energy into this
> project. That is totally understandable and fine.
> But while you are PMC chair you still cannot declare that the project is
> dead as long as there are e
Alan, I understand that you don't want to put much more energy into this
project. That is totally understandable and fine.
But while you are PMC chair you still cannot declare that the project is dead
as long as there are enough PMC members still active to keep the project going.
Before we dum
I agree and I even acknowledged that below, but what I feel Mark and you are
not acknowledging is that the interest/activity is for a smaller subset of JEE.
Of that subset, even you list the OSS projects that are supporting the JEE
bits that are still relevant. They have active communities and
Thanks Alan! Many thanks for all you've done!
I think we all agree that it is time to retire the Geronimo Server portions
of the project.
My apologies to Romain, Mark, David, and others, but:
I think the entire project should be retired. I confess that I am not
closely following the dev list (I
I share that vision (the one of Mark).
The ee-commons part is really used and still active (even if in maintenance
mode for several parts) and we need to ensure other projects can still rely
on it (karaf, tomee, owb, meecrowave, openjpa, ... plus several open source
ones).
EE is also not dead, li
I see no lack of interest in Java EE to be honest. Of course Microservices are
currently spilled high on the hype cycle, but that will quickly blow up imo.
MS architecture is only very good for a certain kind of application. For most
business apps the granularity is way too fine grain and the mis
IMO, consultants and researchers are the earthworms of a vibrant OS community
that meets the standards sought after at the ASF. I don’t see how we’re going
to attract them. While the ideas posited on the mailing lists are pretty
interesting, I just don’t see any of the ideas attracting a large
32 matches
Mail list logo
