Elaborate on motivation in template#3801
Merged
Merged
Conversation
The template had a very short explanation of the motivation, which probably led many people into believing that the motivation can be rather short, compared to the explanations. But really, the motivation is extremely important and should often contain a lot of information. This makes those expectations a lot more explicit. It also explicitly asks for use cases to be listed out, which can then be referenced in the rest of the RFC to make it clearer how it solves the problem.
Noratrieb
added
the
not-rfc
fmease
approved these changes
Apr 21, 2025
Member
|
This is a clear improvement, thanks Nora :) |
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
2 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 template had a very short explanation of the motivation, which probably led many people into believing that the motivation can be rather short, compared to the explanations.
But really, the motivation is extremely important and should often contain a lot of information. This makes those expectations a lot more explicit. It also explicitly asks for use cases to be listed out, which can then be referenced in the rest of the RFC to make it clearer how it solves the problem.