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

Project artifacts do not have to be developed by the project team #64

Open
waynebeaton opened this issue Sep 17, 2021 · 0 comments
Open
Assignees

Comments

@waynebeaton
Copy link
Contributor

The current revision makes this statement:

The Specification Document and related technical artifacts must be developed by the Project Team.

This is incorrect.

It is completely reasonable that technical artifacts (e.g., APIs or TCKs) be developed by a different project (or otherwise obtained from sources outside of the specification project.

Further, it is completely reasonable that the source for a specification document be obtained from outside of the project team. Theoretically, a project team could grab appropriately-licensed specification content from an external source and release it without modification.

I've going to remove this statement.

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

1 participant