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

[Scott Stark <sstark@xxxxxxxxxx>]

We had touched on the requirements for publishing results previously and there were concerns that the full TCK results could be an onerous amount of content. So, for 3b, perhaps there should only be a requirement for a full results summary page. That would also simplify the requirement for item 4 as you could simply attach the summary to the product download. However, that introduces requirements on TCKs in terms of the format of output we have not gotten into.

For item 5 regarding claims of partial compatibility, I would want to make sure we are not precluding the publishing of TCK status publicly for products that are under development. There should be a distinction between TCK results and claims of compatibility. I would argue that simply making results public in a CI site for example, does not in itself constitute any claim about compatibility. This could certainly be placed in a FAQ vs the license itself.

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