Repository navigation
Conversation
Member
|
Alternately, you could also implement this as a GitHub issue template. See examples in https://github.com/astropy/astropy-project/tree/main/.github/ISSUE_TEMPLATE |
Member
|
We have templates now, so I don't think we need this anymore. |
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
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 is the result of me readinf the cycle 3 project description. In some cases, I really did not know how to vote because it was unclear to me who benefits from this proposal. For example, for the AstropyLearn proposal a little more specific info (e.g. page views, use cases, audiences) would have helped me to understand if this will be money well spend.
The same is true for a few other proposals in cycle 3; so I tried to add a sentence so that people who write future funding requests can keep that in mind.
Since it's not appropriate to change the doc in the cycle3 directory at this stage, I've copied the file to the template directory where it will be found next year.