Skip to content

Commit cf2884a

Browse files
Incorporate better wording for rejection reasons
1 parent 3fc5954 commit cf2884a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

proposals/PROPOSALS.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ While the committee should take community discussion into account, they are expe
113113
Fundamentally, there are three potential recommendations: rejection, revision, and acceptance.
114114
*Rejection* means that the committee does not believe that the proposal would, in the balance, bring value to the community, and that it should not be acted upon.
115115
Furthermore, rejection implies that the committee sees no route to making the proposal acceptable that is short of rewriting it from scratch.
116-
Rejection may be because the problem statement itself is considered to be not one that should be solved, or that the harms of the proposed solution would be greater than the benefits.
116+
Among reasons for rejection may be that the problem itself is not considered significant, that the proposal has costs, harms, or overheads that outweigh the benefits, or that the proposal is simply unworkable or based on incorrect understanding and assumptions.
117117
*Acceptance* means that the committee believes that the proposal should be acted upon as-written.
118118
*Revision* means that the committee believes that the proposal as written should not be accepted, but that with some changes it could be accepted.
119119
This may be technical details, project governance issues, or clarity.

0 commit comments

Comments
 (0)