docs: clarify voting phase for feature requests (#42663)

PR Close #42663
This commit is contained in:
Mark Goho 2021-07-01 17:05:48 -04:00 committed by Andrew Kushnir
parent c1c1cda866
commit 88b15d572f
1 changed files with 13 additions and 7 deletions

View File

@ -28,16 +28,22 @@ initiates a voting process.
## Voting phase ## Voting phase
To include the community in the feature request process, we open voting for 60 days. Anyone can cast To include the community in the feature request process, we open voting for a fixed length of time.
a vote for the request with a thumbs-up (👍) reaction. When a feature request reaches 20 or more Anyone can cast a vote for the request with a thumbs-up (👍) reaction on the original issue description.
upvotes, we formally consider the feature request. Alternatively, the bot closes the request. When a feature request reaches 20 or more upvotes, we formally consider the feature request.
Alternatively, the bot closes the request.
**For issues that are 60+ days old**: The voting phase is 20 days
**For new issues**: The voting phase is 60 days
## Consideration phase ## Consideration phase
If the feature request receives 20 or more votes, we verify the Angular team can afford to maintain If the feature request receives 20 or more thumbs-up (👍) votes on the original issue description
the feature and whether it aligns with the long-term vision of Angular. If the answers to both of (during the voting phase described above), we verify the Angular team can afford to maintain the
these questions are yes, we prioritize the request, alternatively we close it with an explanation of feature and whether it aligns with the long-term vision of Angular. If the answers to both of these
our decision. questions are yes, we prioritize the request, alternatively we close it with an explanation of our
decision.
## Diagram ## Diagram