Hi Amelia, Thanks for pointing
out these items. These are just accidental usage of the "Eclipse"
name as we were kicking off the Working Group. One single git issue
will probably not suffice since there is not one person or team that has
access across all of the Jakarta EE related pages and repositories.
The other item
you highlighted in the git issue you raised is actually with the Tutorial
project, which is mentioned in your Issue description: https://eclipse-ee4j.github.io/jakartaee-tutorial I will try to
just re-route this Issue, but if I can't, then I would suggest you recreate
it. I'll put comments in the issue as to my success (or not).
--------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect @ IBM e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
Eiras <aeiras@xxxxxxxxxxxxx> To:
EE Community <jakarta.ee-community@xxxxxxxxxxx> Date:
[jakarta.ee-community] [Required Fixes on the naming of Jakarta EE across
its mediums] It is NOT Eclipse Jakarta EE =/ It is Jakarta EE Sent
Back in early June
I sent a message to this forum about the need to adjust the naming of what
it was thrown as Eclipse Jakarta EE TCK to be Jakarta EE TCK. Though this was fixed
& voted as an error/oversight during on the June 24th Specification
call with the Jakarta EE Working Group, the minutes for June are not yet
available in the Jakarta EE Website under Resources.
It is of much importance
for Jakarta EE to protect is branding and make sure that the name accross
its website, git, articles, etc reflect its correct name.
As such, I have sent
the page connected to the EE4J space that mentions Jakarta EE as Eclipse
Jakarta EE (which is not correct-- twice listed) I hope that 1 git
issue suffices to fix every where the Eclipse has been insertedwith respect to the Jakarta EE name.