You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.
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)?
The text was updated successfully, but these errors were encountered:
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
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.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Eclipse Foundation TCK license requires that the testing party must:
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. agithub.io
or custom domain GitHub Pages site for an open source project)?The text was updated successfully, but these errors were encountered: