docs: clarify proposal-first contribution flow and update PR/issue templates#3395
Merged
docs: clarify proposal-first contribution flow and update PR/issue templates#3395
Conversation
quaquel
approved these changes
Feb 28, 2026
Member
quaquel
left a comment
quaquel
left a comment
There was a problem hiding this comment.
Looks good to me. I'll wait for some other maintainers to chime in as well before merging.
Member
|
LGTM |
jackiekazil
approved these changes
Feb 28, 2026
Member
|
I think there are some good ideas in here. If it will working in practice, let's find that out. |
EwoutH
pushed a commit
that referenced
this pull request
Mar 15, 2026
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
5 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.
As discussed among maintainers, feature PRs without prior alignment can create avoidable review burden. This PR is a first attempt to clarify our contribution flow so enhancements/new features follow a proposal-first process:
Bug-fix PRs remain flexible: direct PRs are still generally fine for clear, scoped bugs.
To reflect this, this PR updates
CONTRIBUTING.mdand the PR/issue templates, including checkboxes to confirm either:Further comments and suggestions are very welcome!