feat: proposal for funding use guidelines #299
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
UlisesGascon
approved these changes
Oct 31, 2024
ctcpip
requested changes
Oct 31, 2024
|
LGTM |
ctcpip
approved these changes
Oct 31, 2024
ljharb
approved these changes
Oct 31, 2024
bjohansebas
approved these changes
Oct 31, 2024
bjohansebas
reviewed
Oct 31, 2024
UlisesGascon
reviewed
Nov 6, 2024
|
I added the age restriction (same as CPC) in Given that we have a basic agreement, I will merge this PR in order to unblock the Express releases 👍 Note: We can always make more changes in the future to polish and extend the policy :) |
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.
We had a start of a discussion in the TC slack. I didn't want to do that in private since we seemed to dont have anyone fully opposed to our plans for financial support for the project. This is just a start, we would appreciate any input (even strong disagreement) here so that we are sure the maintainers, contributors, and community are comfortable with our plans.