Update the process for hosted and core project proposals #117
+90
−28
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
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 <[email protected]>
|
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
| * Do not make unsubstantiated claims; provide evidence. For example, if you claim that your project has a CI job running tests under [AddressSanitizer](https://clang.llvm.org/docs/AddressSanitizer.html), provide links to its CI configuration, test infrastructure, and bugs caught. | ||
| * moving any existing files from `/projects/hosted/$PROJECT_NAME` to `/projects/core/$PROJECT_NAME` | ||
| * If a `proposal.md` exists for the project, move it to `/projects/core/$PROJECT_NAME/proposal-hosted.md` | ||
| * An update to `/projects/README.md` to move the project to the list of core projects. |
There was a problem hiding this comment.
nit: I personally would have chosen to use paths relative to the project root, e.g., projects/README.md... but not a significant issue.
There was a problem hiding this comment.
I guess now that #116 has landed I can just turn this into a link?
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.
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.