|
All,
Thank you Steve...your interpretations were correct.
The draft TCK license is a binary license. The EPL specifically
allows binaries derived from EPL source code to be distributed
under a different license, subject to certain constraints. This
draft TCK binary license was written specifically with those
constraints in mind.
The draft TCK license specifically does not allow the use
of any trademarks. The trademark license is being drafted and I
hope to share that soon.
We need to keep clear in our minds the difference between claims
of compatibility, versus use of the Jakarta EE trademark. Someone
who obtains a copy of a TCK under the draft TCK license and
self-certifies could make factual statements that they are
compatible with whichever specification that TCK is for. However,
they could not use the Jakarta EE trademark unless: (a) the
specification in question is a Profile, (b) they are a party to
the still-to-be-drafted trademark license.
Note that if someone grabs the TCK source code or binaries under
the EPL-2.0 and use that as the basis for testing, they would not
be able to make any claims of compatibility whatsoever.
On 2018-10-03 6:25 AM, Kazumura, Kenji wrote:
Thank you for explanation.
I understand that we have to wait the trademark
license.
-Kenji Kazumura
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
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 ?
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
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">
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.
|
|
This email has been checked for
viruses by Avast antivirus software.
www.avast.com
|
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
