[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
It strikes me that when we discussed this in January, we weren't anticipating the kind of renaming work we are now going to do.
Given the renaming is unavoidable and will require individual attention to the spec repos, is now our best opportunity to do a split?
Wayne, what would be involved in a split above and beyond the renaming work we have to do?
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852
> On Apr 6, 2019, at 8:38 AM, Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote:
>
> I fully agree with everything Markus and David wrote. And if I understood Ivar correctly, even the PMC agrees that splitting EE4J into a Jakarta EE and an implementation part is a good idea. The only disagreement seems to be about when to do it. Am I correct?
>
> Could anyone please clarify which steps would be required for such a split. And whether or not it is a huge effort that would delay further progress? According to David's mail the PMC members are actually overworked, so splitting sooner could potentially fix this problem.
>
> Am Sa., 6. Apr. 2019 um 10:12 Uhr schrieb Markus KARG <markus@xxxxxxxxxxxxxxx>:
> +1
>
> -----Original Message-----
> From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On
> Behalf Of David Blevins
> Sent: Samstag, 6. April 2019 00:33
> To: EE4J PMC Discussions
> Subject: Re: [ee4j-pmc] Renaming
>
> > On Apr 5, 2019, at 3:21 PM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
> >
> >> On Apr 5, 2019, at 10:52 AM, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
> >>
> >> I'm very much +1 for splitting up into Jakarta EE (= only APIs, TCKs,
> Specs) and EE4J (= only products like Jersey) to clearly tell third party
> vendors that Jakarta is open for them and there is no preference for Eclipse
> products. Whether there is time for that or not. It is simply inauthentic
> for market competitors that e. g. Jersey will not be preferred as long as it
> stays under the same PMC than JAX-RS, and the long artificial delay we had
> with JAX-RS due to particularly Jersey requests in the recent GlassFish
> release proofs that I am right. Standards MUST be independent or they are
> not really norms but just default choices!
> >
> > I was one of the minority PMC members who felt splitting sooner rather
> than later was better.
> >
> > I see the coming Jakarta EE and GlassFish releases not as a reason to
> delay, but as a reason we should do it now. A couple motivators in my eyes:
> >
> > - Major releases are opportunities to exercise PMC health. We'll lose the
> opportunity to exercise the two future PMCs if we wait and another
> opportunity won't come for quite a while.
> >
> > - The people in the EE4J PMC are overworked and have too many
> responsibilities. I think GlassFish is under served and deserves more
> dedicated people who have vested interest in it.
> >
> > - We could potentially double the hands who can help. I see it as time
> spent to go faster.
> >
> > The middle reason is the primary reason people do not want to do it now.
> I personally would rather see it done right and would be ok with potential
> delays. I think, however, eliminating the bottleneck could just as likely
> improve our speed and get us to releases faster.
>
> Using more universal language, I see splitting after the release a bit like
> writing the tests after you go to production.
>
> -David
>
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
>
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/ee4j-pmc
>
>
> --
> Christian Kaltepoth
> Blog: http://blog.kaltepoth.de/
> Twitter: http://twitter.com/chkal
> GitHub: https://github.com/chkal
>
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/ee4j-pmc