Update funding process with 2025 schedule #435
Merged
+63
−46
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
- Streamline workflow / review process - Add examples of successful funding requests Signed-off-by: Zach Steindler <steiza@github.com>
Signed-off-by: Zach Steindler <steiza@github.com>
bobcallaway
approved these changes
Jan 13, 2025
Signed-off-by: Zach Steindler <steiza@github.com>
marcelamelara
approved these changes
Jan 13, 2025
There was a problem hiding this comment.
Thanks for these updates @steiza ! I only have one minor comment that isn't a blocker. I'm also in favor of following this up with a transition from issues to PRs for funding requests :)
lehors
approved these changes
Jan 14, 2025
Signed-off-by: Zach Steindler <steiza@github.com>
|
I think this falls under "Content" on the TAC decision process in which case it has the necessary approvals - thanks everyone! |
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.
For #419
There wasn't consensus on rolling evaluation vs batching, so I decided on batching every 2 months instead of every 3 months. This gives us 5 review periods (without trying to squeeze one in at the end of the year). Review periods by the TAC are two weeks long, in case some TAC members are on vacation or otherwise temporarily unavailable to vote.
This change also streamline workflow / review process and addd examples of successful funding requests.
It does not change the funding process from using issues to using pull requests, although I'm still considering that for a follow-up change. For the upcoming review cycle we already have at least 1 issue to include in our review anyways, namely #424.