Accommodate spec development in a Project #205
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
|
I think it looks good as it is - maybe could strengthen the wording about using the community specification license... |
steiza
approved these changes
Oct 13, 2023
SecurityCRob
approved these changes
Oct 16, 2023
SecurityCRob
added
documentation
|
merging - 50% vote in favour so far |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses issue #204, changing the project lifecycle to accommodate for specification development as well as code development.
Note that this change should be endorsed by the GB with an update of the charter to extend the definition of a Project from "software focused" to "software or specification focused" for clarity.
If adopted, existing groups working on a specification should be "rebranded" accordingly.