Re: [jakarta.ee-spec] Updated reference to EFSL and to indicate the spec

[<Hussain.NM@xxxxxxxxxxxxx>]

Kevin,

 

If the intention is to keep the EFSL text same as the original text, shouldn’t the copyright years in the notice text also be reverted to the original?

 

·       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]."

 

We have copyright years in the Copyright section of the document.

 

Thanks

Hussain

 

From: jakarta.ee-spec-bounces@xxxxxxxxxxx <jakarta.ee-spec-bounces@xxxxxxxxxxx> On Behalf Of Kevin Sutter
Sent: Saturday, August 15, 2020 2:01 AM
To: Jakarta specification discussions <jakarta.ee-spec@xxxxxxxxxxx>
Subject: Re: [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/kevinwsutter



From:        <Hussain.NM@xxxxxxxxxxxxx>
To:        <jakarta.ee-spec@xxxxxxxxxxx>
Date:        07/30/2020 19:51
Subject:        [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#copyright
1.     The original license text link is added to the Copyright itself
Copyright © 2018, 2020 Eclipse Foundation. https://www.eclipse.org/legal/efsl.php
2.     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 changed

The 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: &quot;Copyright &copy; [$date-of-document]

-      &ldquo;Eclipse Foundation, Inc. &lt;&lt;url to this license&gt;&gt;

+      &ldquo;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

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.