Re: [jakarta.ee-spec.committee] Draft TCK License

["Kazumura, Kenji" <kzr@xxxxxxxxxxxxxx>]

Thank you for explanation.

I understand that we have to wait the trademark license.

 

-Kenji Kazumura

 

 

From: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx [mailto:jakarta.ee-spec.committee-bounces@xxxxxxxxxxx] On Behalf Of Steve Millidge (Payara)
Sent: Wednesday, October 03, 2018 7:06 PM
To: Jakarta specification committee
Subject: Re: [jakarta.ee-spec.committee] Draft TCK License

 

Again my understanding is if someone did that all they could claim was that their product passed the version of the TCK they built from a specific commit of the GitHub source. As Jakarta EE is a trademark of the Eclipse Foundation they would need to license usage of the Jakarta EE trademark from Eclipse Foundation to claim their product is compliant with “Jakarta EE”. I don’t think we’ve seen a draft of the trademark license but my assumption is that it would require you to pass the specific binary TCK version licensed under the TCK license.

 

Steve

 

From: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> On Behalf Of Kazumura, Kenji
Sent: 03 October 2018 11:00
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>; IP Advisory Committee <eclipse.org-ip-advisory@xxxxxxxxxxx>
Subject: Re: [jakarta.ee-spec.committee] Draft TCK License

 

Someone build the TCK binary from the github TCK source,

and they test their product with this TCK binary,

and the can claim their product is compliant with Jakarta EE.

 

We cannot prohibit them to do so by the current github license.

Is it correct ?

 

 

 

 

From: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx [mailto:jakarta.ee-spec.committee-bounces@xxxxxxxxxxx] On Behalf Of Steve Millidge (Payara)
Sent: Wednesday, October 03, 2018 6:43 PM
To: Jakarta specification committee; IP Advisory Committee
Subject: Re: [jakarta.ee-spec.committee] Draft TCK License

 

My understanding is this will apply to the specific binary build of the TCK that will correspond with a release of Jakarta EE and is used to “certify” an implementation as compatible.

 

GitHub license will be for the source code of the TCK.

 

Steve

 

From: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> On Behalf Of Kazumura, Kenji
Sent: 03 October 2018 10:39
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>; IP Advisory Committee <eclipse.org-ip-advisory@xxxxxxxxxxx>
Subject: Re: [jakarta.ee-spec.committee] Draft TCK License

 

It's not a comment for this draft,

but what is the relationship between this draft and the current github license below ?

 

<"https://github.com/eclipse-ee4j/jakartaee-tck/blob/febd0176d513a2b4d9b13354bf69b6d6c03d79a3/LICENSE.md">

 

 

 

From: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx [mailto:jakarta.ee-spec.committee-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich
Sent: Wednesday, October 03, 2018 6:35 AM
To: Jakarta specification committee; IP Advisory Committee
Subject: [jakarta.ee-spec.committee] Draft TCK License

 

All,

Please find attached an initial draft of the Eclipse Foundation TCK License.

This draft has not been reviewed or approved by either the IP Advisory Committee or the Board.

As always, comments are welcomed.

--

Mike Milinkovich

Executive Director | Eclipse Foundation, Inc.

mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx

@mmilinkov

+1.613.220.3223 (m)

Meet us at EclipseCon Europe 2018: Germany, October 23 - 25

 

---

This email has been checked for viruses by Avast antivirus software. www.avast.com