Update the process for hosted and core project proposals #117
Conversation
This file contains hidden or 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
This is for now just a simple list of projects I could identify, with links to websites and/or repositories as appropriate.
In the last TSC meeting, we discussed moving from an Issue- to a PR-based process for the proposals to align with the one for SIGs, streamline the review process, and generate easily discoverable documentation. This PR changes documentation and templates to apply that decision. Signed-off-by: Till Schneidereit <till@tillschneidereit.net>
Member
Author
|
Note that this PR builds on #116, so only the last commit needs to be reviewed here. |
fitzgen
approved these changes
Dec 30, 2024
ricochet
approved these changes
Jan 14, 2025
abrown
approved these changes
Jan 21, 2025
Signed-off-by: Till Schneidereit <till@tillschneidereit.net>
tschneidereit
added a commit
to tschneidereit/ba-governance
that referenced
this pull request
Apr 9, 2025
A proposal to promote Wasmtime to Core Project status has already been made bytecodealliance#114. The [TSC](https://github.com/bytecodealliance/meetings/blob/main/TSC/2025/tsc-01-28.md#topic-2) and the [Board](https://github.com/bytecodealliance/meetings/blob/main/TSC/2025/tsc-02-04.md#topic-1) of the Bytecode Alliance also already approved this proposal. After opening bytecodealliance#114, the TSC [changed the process](bytecodealliance#117) for how to handle these proposals to be based on Pull Requests instead of issues instead, however. This PR follows the new process, and contains exactly the same contents as bytecodealliance#114, but in a new file, together with the required changes to the `projects/README.md` file. Closes bytecodealliance#114. Signed-off-by: Till Schneidereit <till@tillschneidereit.net>
abrown
added a commit
that referenced
this pull request
Apr 15, 2025
* Core Project Proposal: The Wasmtime Project A proposal to promote Wasmtime to Core Project status has already been made #114. The [TSC](https://github.com/bytecodealliance/meetings/blob/main/TSC/2025/tsc-01-28.md#topic-2) and the [Board](https://github.com/bytecodealliance/meetings/blob/main/TSC/2025/tsc-02-04.md#topic-1) of the Bytecode Alliance also already approved this proposal. After opening #114, the TSC [changed the process](#117) for how to handle these proposals to be based on Pull Requests instead of issues instead, however. This PR follows the new process, and contains exactly the same contents as #114, but in a new file, together with the required changes to the `projects/README.md` file. Closes #114. Signed-off-by: Till Schneidereit <till@tillschneidereit.net> * Apply suggestions from code review Co-authored-by: Andrew Brown <andrew.brown@intel.com> --------- Signed-off-by: Till Schneidereit <till@tillschneidereit.net> Co-authored-by: Andrew Brown <andrew.brown@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
In the last TSC meeting, we discussed moving from an Issue- to a PR-based process for the proposals to align with the one for SIGs, streamline the review process, and generate easily discoverable documentation.
This PR changes documentation and templates to apply that decision.