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

[Scott Stark <sstark@xxxxxxxxxx>]

After further discussions on the terms of this license, we have the following additional concerns:

1. The restrictions placed on claims of compatibility does not seem suitable at this level. Rather, compatibility restrictions should be conditions in the trademark agreement associated with a given Jakarta EE profile.

2. Ultimately each specification project is going to have it's own TCK project. We don't know that it makes sense to have a TCK license such as proposed for anything but the ratified Jakarta EE profile TCKs. In our opinion, restrictions around subsetting, super-setting and compatibility claims are only a concern at the profile levels. We don't see a need to restrict how the JMS project TCK could be used as an example.

On Tue, Oct 2, 2018 at 2:35 PM Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> wrote:

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

_______________________________________________
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