Re: [ee4j-pmc] Renaming

[Ivar Grimstad <ivar.grimstad@xxxxxxxxx>]

Hi,

Just to be clear, it is not Wayne's proposal. The naming standard has been formed after discussions among all the members of the Jakarta EE Working Group Steering Committee and Specification Committee. You are free to come up with your own suggestions, but ultimately the names must be approved by (I would guess) the Specification Committee (maybe also the Steering Committee). 

So, to your proposal. EE4J is more than just Jakarta EE. It also contains implementations, such as Jersey. We have discussed splitting out the Jakarta EE projects to its own PMC and the implementations to its own but decided against it to avoid losing more time and introducing another layer of complexity. The topic may come up in the future though.

Ivar

On Fri, Apr 5, 2019 at 7:42 AM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

In case we follow Wayne's proposal to get rid of the "Eclipse Project for" prefix, I'd like to propose to replace the word "EE4J" by "Jakarta", too.

In particular it would be great if the URL of the Github API projects does not read like "…/eclipse-ee4j/…" but "…/jakarta/…" or "…/eclipse/jakarta/…" instead. :-)

According to Wayne it is up to the PMC to decide, so I hereby ask the PMC to decide about that.

-Markus

_______________________________________________
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