doc: clarify status of feature request issues #61505
Open
+10
−8
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
Collaborator
|
Review requested:
|
cjihrig
approved these changes
Jan 24, 2026
RafaelGSS
approved these changes
Jan 24, 2026
MikeMcC399
reviewed
Jan 24, 2026
| have the ability to direct resources toward specific work. The | ||
| features which are implemented are those for which volunteers | ||
| are individually motivated to work on. The best way to ensure | ||
| Feature requests are not a valuable source of input for the project. |
Contributor
There was a problem hiding this comment.
Suggested change
| Feature requests are not a valuable source of input for the project. | |
| Feature requests have a relatively limited value as a source of input for the project. |
Tones down the message a little, whilst still discouraging feature requests as primary sources of input.
MikeMcC399
reviewed
Jan 24, 2026
Comment on lines
+4
to
+5
| It is usually more productive to first send the Pull Request implementing the | ||
| feature, even imperfectly, and let the discussion happen during code review. |
Contributor
There was a problem hiding this comment.
Suggested change
| It is usually more productive to first send the Pull Request implementing the | |
| feature, even imperfectly, and let the discussion happen during code review. | |
| It is usually more productive to first send a Pull Request implementing a | |
| feature, even imperfectly, and let the discussion happen during code review. |
There was a problem hiding this comment.
What if the implemented feature is what you really don't want to, which will end up with great-pains-but-all-in-vain?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
The discussion in #61487 made me realize we lack a statement saying "you don't need to open an issue, actually we'd prefer if you open a PR directly if you already know what you want". In fact, we were kinda hinting the opposite, which does not reflect the reality of the issue tracker in my experience, resulting in frustrating experience for both reporters and triagers.