[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakarta.ee-community] [Required Fixes on the naming of Jakarta EE across its mediums] It is NOT Eclipse Jakarta EE =/ It is Jakarta EE
|
Amelia,As my original
reply mentioned, many of these agreements, documents, and web pages were
created back when the Jakarta EE Working Group was still in its infancy.
All of us were using "Eclipse Jakarta EE" and "Jakarta
EE" interchangeably. So, it doesn't surprise me that there are
areas that still need to be looked at.But, concerning
the Participation Agreements... If you take a look at all of the
other WG Participation Agreements (https://www.eclipse.org/org/workinggroups/explore.php),
they all say "Eclipse xyz" -- even the new ones like AsciiDoc
and Sparkplug. So, this is not something that Eclipse has done just
to the Jakarta EE Working Group. It looks like they have had a template
for a long time... It probably costs $$$ to modify these agreements,
so why update them on a whim?But... With the
move of the Eclipse Foundation from New Jersey to Belgium, these Agreements
may need to go through an update in the near future. ("may"
is the key word, I have no idea if this is required or not) If these
Agreements need to be updated due to this change of incorporation, then
maybe the "Eclipse" can be removed from the new agreement titles?
I really don't know. I'm just offering up an observation. There
may be reasons why the "Eclipse" wording is included on these
Agreements.Anyway, I agree
that we should take a look at these Agreements and determine whether the
"Eclipse" should be dropped or not. At the same time, I
really don't see why this is such an important topic that needs to be addressed
with urgency. Most of the occurrences of "Eclipse Jakarta EE"
have been shortened to just "Jakarta EE". We should open
Issues where the other occurrences still exist and get them addressed in
due time. It shouldn't be a panic (imho).BTW, I'm not going
to copy all of the Eclipse Committers since I consider that spamming the
committer community...
---------------------------------------------------
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/kevinwsutterFrom:
Amelia
Eiras <aeiras@xxxxxxxxxxxxx>To:
Jakarta
EE community discussions <jakarta.ee-community@xxxxxxxxxxx>, Committers
Eclipse Foundation <eclipse.org-committers@xxxxxxxxxxx>Date:
08/11/2020
18:30Subject:
[EXTERNAL]
Re: [jakarta.ee-community] [Required Fixes on the naming of Jakarta EE
across its mediums] It is NOT Eclipse Jakarta EE =/ It is Jakarta EESent
by: jakarta.ee-community-bounces@xxxxxxxxxxx
To everyone who contributes
to project (s) under the Eclipse Foundation, I am going to be
honest, I am deeply disappointed that the Eclipse Foundation Management
has chosen to insert the Eclipse word in the Jakarta EE project. Many
tries but the latest one I cannot let slide. Jakarta
EE Working Group Agreement
NOT approved by the WG. Reminder that the
name of the project was chosen by the Java EE Community via a public vote
by close to 7,000 votes as listed on this article by
InfoWorld. Important: The
Foundation has no say/no power on the Jakarta EE Management & leadership
(NO VOTE). But continued actions continue to push for the contrary.
Your actions cannot longer go unnoticed & cannot longer be handled
via private mediums. The latest insult
to this project Community is the legal adjustment of the Jakarta EE Working
Group Agreement, changing the name is a serious threat. Tomitribe as many
other Members signed the Jakarta EE agreement, which we helped write
back in 2018/19. Please see below a copy of what it was signed & what
needs to be. It is NOT right nor correct what is shown today in the
public Jakarta EE WG Agreement. I can no longer let
things continue sliding in the dark. Moving backgrounds instead of forwards.
This forum will get updates of what's what until finally the 3 Committee
calls become public and recorded so that the light is the protected of
the project itself. Already
a thread was sent about the emergency of that action. On the MicroProfile
side, I already pulled in the Eclipse Board of Directors via the public
forum, I asked for their attention, for help to zoom- in and pay closer
attention to the actions of those behind the management of the foundation. It has become a deeply
exhausting, bothersome & sadly unnecessary task to flight on fixing
( that was never meant to exist in the first place) WHY THE HELL ARE
WE HERE? Projects & diverse
communities are not being created or moved to the Eclipse Foundation to
serve the EF's internal goals. The point is that:The Eclipse Foundation
is meant to be the soil that allows for the opportunity/conditions of growth
& development where individuals and corporations, alike can be nutrients
& equal participants. To the EF: I don't
know where that message was lost. But I ask you to shake what current is
and to be true to what the Foundation is meant to do. To Jakarta EE contributors
& committers & to every committer of the Eclipse Foundation---
is what I have shared in this message doesn't concern you, shake
you- ask yourself why that is.
Amelia
Eiras twitter.com/ameliaeirasTribe: http://tomitribe.com
https://tribestream.io
OSS: http://microprofile.io
https://jakarta.eeOn Tue, Aug 11, 2020 at 3:45 PM Amelia
Eiras <aeiras@xxxxxxxxxxxxx>
wrote:To the Eclipse Foundation
team, Please correct the
Jakarta
EE Working Group Agreementby deleting the Eclipse from preceding Jakarta EE. Other Jakarta EE
legal documents applicable to the Working Group, specially binding Members,
need to follow suit. Thank YOU, Amelia
Eiras twitter.com/ameliaeirasTribe: http://tomitribe.com
https://tribestream.io
OSS: http://microprofile.io
https://jakarta.eeOn Wed, Jul 29, 2020 at 9:44 AM Amelia
Eiras <aeiras@xxxxxxxxxxxxx>
wrote:+1 Scott, thank YOUfor owning that front! :) Amelia
Eiras twitter.com/ameliaeirasTribe: http://tomitribe.com
https://tribestream.io
OSS: http://microprofile.io
https://jakarta.eeOn Wed, Jul 29, 2020 at 9:13 AM Scott
Marlow <smarlow@xxxxxxxxxx>
wrote:Thanks, this is very timely as I was
just searching for the previous conversation about this and found this
new thread! From discussion in https://github.com/eclipse-ee4j/jakartaee-tck/pull/389,
I think that the TCKs should change "Eclipse EE4J Jakarta EE"
to "Jakarta EE". We should also change "Eclipse Jakarta
EE" to "Jakarta EE" as well in the TCKs.ScottOn Wed, Jul 29, 2020 at 11:39 AM Amelia
Eiras <aeiras@xxxxxxxxxxxxx>
wrote:Kevin, Thank you for fixing
the 1 page, upon your consuming of this message. I appreciate you, plus
you so ROCK as a Jakarta EE #ossDOER :) Via the git issue,
with your help and that of @chrisguindon & @jgallimore the
PR fixing the name has been also submitted to the Tutorial page. I want to thank you
Kevin for reminding everyonein this ecosystem that the access to the Jakarta EE project is deeply distributed.
Any required adjustments ought not be sent only to the hired
team BUT actually are the responsibility & ownership of the Jakarta
EE ecosystem, which is made of Contributors & Committers, alike. With that in mind,
I ask one of you, #ossDOERs, to please help audit the naming of the entire
Jakarta EE platform using this thread in addition to:- to
the Jakarta
EE Trademark Brand Usage Handbook.
The 9 page slides was published in 2018, it was reviewed & approved
by the WG. I was one of the individuals working on that write-up &
its review, hence my message early in June & now.
- The Handbook
is supplemented by the March
2020 Jakarta EE Trademarks.
As
Kevin nicely pointed out, it is our responsibility to trace back what currently
is & match it or adjust it. Cheers with tea from
foggy Santa Monica, Amelia
Eiras twitter.com/ameliaeirasTribe: http://tomitribe.com
https://tribestream.io
OSS: http://microprofile.io
https://jakarta.eeOn Wed, Jul 29, 2020 at 6:07 AM Kevin
Sutter <sutter@xxxxxxxxxx>
wrote: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.
I have cleaned up the Jakarta EE Platform PMI page: https://projects.eclipse.org/projects/ee4j.jakartaee-platform (A
git issue the Platform project (https://github.com/eclipse-ee4j/jakartaee-platform)
would have highlighted this need.)
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
From: Amelia
Eiras <aeiras@xxxxxxxxxxxxx>
To: Jakarta
EE Community <jakarta.ee-community@xxxxxxxxxxx>
Date: 07/28/2020
20:15
Subject: [EXTERNAL]
[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 by: jakarta.ee-community-bounces@xxxxxxxxxxx
Hola Jakartees,
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 a git
issue on
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. 
Thank you in advance to the assigned EF Jakarta EE marketing team for prioritizing
the naming of Jakarta EE as Jakarta EE.
Jakarta EE 9 release work continues to welcome new Contributors that are
using the current tutorial and the documentation accross the tools used
that is available. The fix cannot be delayed.
Thank you in advance to the assigned EF Jakarta EE marketing team for prioritizing
the naming of Jakarta EE as Jakarta EE.
PS: I had to send a new thread instead of the original b/c the EF email
forums do not allow for a smart search of its content yet.
Amelia Eiras
twitter.com/ameliaeiras
Tribe: http://tomitribe.com
https://tribestream.io
OSS: http://microprofile.io
https://jakarta.ee_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community