Re: [jakarta.ee-community] Fork Eclipse MicroProfile Configuration as Ja

[Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>]

On Wed, Apr 1, 2020 at 4:49 PM Heiko W. Rupp <hrupp@xxxxxxxxxx> wrote:

On 1 Apr 2020, at 16:34, Otavio Santana wrote:


> My question is: Does it make sense if we create a fork of Eclipse
> MicroProfile Configuration as Jakarta Configuration?

That is a nice Aprils fool of you :-)

I think the only thing you can make April fools jokes about these days are toilet paper :)

 

> The project seems stable and it will valuable to several projects such
> as JPA, JMS, and NoSQL.

Is(n't) the main obstacle of just including it that MicroProfile does
not have the IP
protection has, as it does not use the Eclipse Spec Process? If so, I
guess just
waiting on that Process to be used may be as good/quick as a fork and
would
prevent the two from drifting apart. Or that contributors have to
constantly
submit changes to two projects.

But I am sure I am missing some things

The decision within MicroProfile to go with the "Pull" approach to technical alignment actually advocates forking rather than referencing. Jakarta EE can then decide on what level of backward compatibility it wants without relying on the decisions made by MicroProfile. Just my 2 cents.

 

   Heiko

_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Eclipse Foundation: The Platform for Open Innovation and Collaboration