Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

Clarify what is a "testing party’s website" in the TCK License #52

Open
bjhargrave opened this issue Jun 9, 2021 · 4 comments
Open

Comments

@bjhargrave
Copy link

bjhargrave commented Jun 9, 2021

The Eclipse Foundation TCK license requires that the testing party must:

make TCK test results showing full and complete satisfaction of all requirements of the TCK publicly available on the testing party’s website

It is not entirely clear what is acceptable for the testing party’s website.

Must this be a website under the testing party's commonly used domain name (e.g. ibm.com for IBM). Or it is acceptable that the website and/or its content merely be under the control of the testing party (e.g. a github.io or custom domain GitHub Pages site for an open source project)?

@bjhargrave bjhargrave changed the title Clarify what is a "testing party’s website" Clarify what is a "testing party’s website" in the TCK License Jun 9, 2021
@mmilinkov
Copy link

I will, of course, defer to Wayne if he disagrees. But I think we would be happy with any website under the control of the party claiming compatibility.

In this world of hosting services I don't see any value in being prescriptive about a domain name.

@bosschaert
Copy link

Would it be possible to clarify this in the TCK license? Maybe say something like:

make TCK test results showing full and complete satisfaction of all requirements of the TCK publicly available on a website

instead?

@mmilinkov
Copy link

No, we are not going to change the text of the TCK License. That would require an exhaustive legal review and Board approval. Sorry, not gonna happen.

@bjhargrave
Copy link
Author

Perhaps, in a future update, the EFSP can define the term "testing party’s website" to bring more clarity. This would not require modifying the TCK license text.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants