Did you mean;
that the only financial requirement in that **trademark** license will be that the entity is at least a Participant Member of the Jakarta EE working group.
From: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx>
On Behalf Of Mike Milinkovich
Sent: 04 October 2018 16:58
To: jakarta.ee-spec.committee@xxxxxxxxxxx
Subject: Re: [jakarta.ee-spec.committee] Draft TCK License
On 2018-10-03 7:00 PM, Bill Shannon wrote:
I understand the need to protect the Jakarta EE trademark and branding. But, we have to be aware that there will be projects that will want to show
"compliance" with the spec and tck, but without paying any additional licensing fees. No matter how we word this restriction, someone will figure out a way around it...
The TCK is free. There's no need to use the source code and build it yourself to save money. The only reason to use the source code is to do something that the TCK license won't allow you to do, e.g., make a claim of partial compatibility,
or modify the tests before claiming compatibility.
To add to what Bill says: there is *nothing* in this TCK license that says anything about "...paying any additional licensing fees." It is explicitly a free license to use the TCK. If you use the free binary TCK provided under this license you will be able
to make factual statements of compatibility. The still-being-drafted *trademark* license will allow an entity to also use the Jakarta EE logo. I think we at the EF (and still to be vetted by the Steering Committee) have decided that the only financial requirement
in that TCK license will be that the entity is at least a Participant Member of the Jakarta EE working group.
![Avast logo]()
|
This email has been checked for viruses by Avast antivirus software.
www.avast.com
|