[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[jakartaee-platform-dev] Do not update the EFSL text
|
Hi,A few months back,
I had created Issues against each of the Specification Projects to update
the EFSL text based on a discussion on these two mailing lists. It
turns out that some of that discussion was incorrect and we shouldn't have
updated the EFSL text. It has been explained to me that the EFSL
text must stay as it was originally written (even with the cryptic references
to other URLs or Specifications).For those errant
issues that I found open with no activity, I have since closed them. That
covered the majority of the Specification projects.Unfortunately,
the other set of Specification projects had already made these errant updates
to the EFSL text. Luckily, I got the okay from the Eclipse Foundation
to allow these errant changes to stay as-is for Jakarta EE 9. So,
if you have made the changes prescribed by my errant Issues, you can leave
them and correct them in a future release. (I'd open an Issue as
a reminder.) But, if you haven't finalized your Specification release
yet for Jakarta EE 9, you are welcome to clean this up now. It is
up to you to decide when to revert these changes to the EFSL.If you are unsure
of whether your project made the updates, or you are wondering what updates
I am referring to, here's an example...Here's an example
of the original errant Issue I created against the Platform Spec and API:https://github.com/eclipse-ee4j/jakartaee-api/issues/62The updates to
the EFSL as described in these Issues should not have been performed. I
have recently backed out or reverted these changes in the Platform Spec
and API via these PRs:https://github.com/eclipse-ee4j/jakartaee-platform/pull/237https://github.com/eclipse-ee4j/jakartaee-api/pull/72
Hope this helps explain the situation. And, my apologies for making
extra work for you!
---------------------------------------------------
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:
Kevin
Sutter/Rochester/IBMTo:
Jakarta
specification discussions <jakarta.ee-spec@xxxxxxxxxxx>Date:
08/14/2020
15:30Subject:
Re:
[EXTERNAL] [jakarta.ee-spec] Updated reference to EFSL and to indicate
the specification (#98)
Hi Hussain,I was looking
to send out a reminder to the wider development team (based on our recent
Platform call) and I came across this email from you. Sorry that
I missed it.In short, we shouldn't
do anything related to the EFSL. Any of the Specifications that did
to some changes to the EFSL due to the errant Issues I created don't have
to back them out. I closed out all of the errant Issues that were
still open. We can wait and clean this up in the next release. If
a component, such as EJB, has already done these changes, they are welcome
to back them out in Jakarta EE 9. That is what I did for the Platform
and Web Profile specs.
---------------------------------------------------
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:
<Hussain.NM@xxxxxxxxxxxxx>To:
<jakarta.ee-spec@xxxxxxxxxxx>Date:
07/30/2020
19:51Subject:
[EXTERNAL]
[jakarta.ee-spec] Updated reference to EFSL and to indicate the
specification (#98)Sent
by: jakarta.ee-spec-bounces@xxxxxxxxxxx
Kevin,
I
had reached out to Eclipse License team to check on the correctness of
changes we had made on updating the license text. I saw the minutes of
meeting from the last platform call and you had discussed this point.
I
would like to get a confirmation on what needs to be changed:
· Replace
license URL with placeholder
All
existing copyright notices, or if one does not exist, a notice (hypertext
is preferred, but a textual representation is permitted) of the form: "Copyright
© [$date-of-document] Eclipse Foundation, Inc. <<url to this license>>
"
· Replace
Notice text with original
"Copyright
© [$date-of-document] Eclipse Foundation. This software or document includes
material copied from or derived from [title and URI of the Eclipse Foundation
specification document]."
Thanks
Hussain
From:sharon.corbett@xxxxxxxxxxxxxxxxxxxxxx <sharon.corbett@xxxxxxxxxxxxxxxxxxxxxx>
On Behalf Of Eclipse License
Sent: Friday, July 31, 2020 12:43 AM
To: N M, Hussain (Cognizant) <Hussain.NM@xxxxxxxxxxxxx>
Cc: license <license@xxxxxxxxxxx>
Subject: Re: [eclipse-ee4j/jta-api] Updated reference to EFSL and to
indicate the specification (#98)
Hussain:
Kevin Sutter is on point for these changes. Can you please work with
him for consistency.
Thanks,
Sharon
On
Mon, Jul 27, 2020 at 11:47 AM <Hussain.NM@xxxxxxxxxxxxx>
wrote:
Please
advise on what will be the right way. These changes have been done across
all specification documents.
A
sample of what is expected in this page will be good.
Thanks
Hussain
From:sharon.corbett@xxxxxxxxxxxxxxxxxxxxxx<sharon.corbett@xxxxxxxxxxxxxxxxxxxxxx>
On Behalf Of Eclipse License
Sent: Monday, July 27, 2020 9:14 PM
To: N M, Hussain (Cognizant) <Hussain.NM@xxxxxxxxxxxxx>
Cc: license <license@xxxxxxxxxxx>
Subject: Re: [eclipse-ee4j/jta-api] Updated reference to EFSL and to
indicate the specification (#98)
Apologies
for the late response and we can see how this is confusing.
The
text of the license itself should not be modified in any way. The templates
are intended as instructions to those who use the license. The templates
should be copied out of the EFSL and pasted elsewhere in the document.
Hope
that helps.
Sharon
On
Tue, Jul 7, 2020 at 9:36 PM <Hussain.NM@xxxxxxxxxxxxx>
wrote:
Hi
Sharon,
With
Reference to your below note, I would like to get a confirmation on whether
we have made the right changes. Please review the copyright section in
the below document
https://jakarta.ee/specifications/enterprise-beans/4.0/enterprise-beans-spec-core-4.0-public-draft.html#copyright1. The
original license text link is added to the Copyright itselfCopyright © 2018, 2020 Eclipse Foundation.
https://www.eclipse.org/legal/efsl.php2. In
the original license text, the following line is changed from All
existing copyright notices, or if one does not exist, a notice (hypertext
is preferred, but a textual representation is permitted) of the form: "Copyright
© [$date-of-document] Eclipse Foundation, Inc. <<url to this license>>
"All existing
copyright notices, or if one does not exist, a notice (hypertext is preferred,
but a textual representation is permitted) of the form: "Copyright
© [$date-of-document] Eclipse Foundation, Inc. https://www.eclipse.org/legal/efsl.php"Rationale:
A person reading the license text from anywhere other than https://www.eclipse.org/legal/efsl.phpwill
not know what to fill in for <<url to this license>>3. As
you have said the Notice can be changedThe
notice is:
"Copyright
© 2018, 2020 Eclipse Foundation. This software or document includes material
copied from or derived from Jakarta® Enterprise Beans https://jakarta.ee/specifications/enterprise-beans/4.0/"
Please
let me know if anything needs to changed.
Discussion
thread on the jakarta.ee-spec mailing list: https://www.eclipse.org/lists/jakarta.ee-spec/msg00641.html
Thanks
Hussain
@SharonCorbettcommented on this pull request.
In
api/src/main/javadoc/doc-files/EFSL.html:
>
@@ -20,7 +20,7 @@ <h1>Eclipse Foundation Specification License -
v1.0</h1>
<li>All existing copyright notices, or if one does not exist,
a notice
(hypertext is preferred, but a textual representation
is permitted)
of the form: "Copyright © [$date-of-document]
-
“Eclipse Foundation, Inc. <<url
to this license>>
+
“Eclipse Foundation, Inc. https://www.eclipse.org/legal/efsl.php
@pombredanne:
Thanks for checking in on this. As indicated there is to be no modification
of the license text itself, it is to be used in its exact form as per https://www.eclipse.org/legal/efsl.php.
As you suggest, only the notice can have a variant as per the terms of
the EFSL itself.
For
those on this pull request, please ensure you are adhering.
If
there are any lingering questions, please contact license@xxxxxxxxxxx.
Regards,
Sharon
This e-mail and any files transmitted
with it are for the sole use of the intended recipient(s) and may contain
confidential and privileged information. If you are not the intended recipient(s),
please reply to the sender and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding, printing
or copying of this email, and/or any action taken in reliance on the contents
of this e-mail is strictly prohibited and may be unlawful. Where permitted
by applicable law, this e-mail and other e-mail communications sent to
and from Cognizant e-mail addresses may be monitored. This e-mail and any
files transmitted with it are for the sole use of the intended recipient(s)
and may contain confidential and privileged information. If you are not
the intended recipient(s), please reply to the sender and destroy all copies
of the original message. Any unauthorized review, use, disclosure, dissemination,
forwarding, printing or copying of this email, and/or any action taken
in reliance on the contents of this e-mail is strictly prohibited and may
be unlawful. Where permitted by applicable law, this e-mail and other e-mail
communications sent to and from Cognizant e-mail addresses may be monitored.
_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec