From e29eb8abfbfdfb793e08ac88e14b7ba6d2ff2136 Mon Sep 17 00:00:00 2001 From: Joey Perrott Date: Thu, 6 May 2021 17:24:03 -0700 Subject: [PATCH] docs: reword a few phrases in the GITHUB_PROCESS.md doc (#41977) Reword a few things in the explanation around our `Feature request process` to make the process a little clearer. PR Close #41977 --- docs/GITHUB_PROCESS.md | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/docs/GITHUB_PROCESS.md b/docs/GITHUB_PROCESS.md index e58966b18a..9e539311f3 100644 --- a/docs/GITHUB_PROCESS.md +++ b/docs/GITHUB_PROCESS.md @@ -1,6 +1,6 @@ # Automatic conversation locking -Closed issues and pull requests are locked automatically after 30 days of inactivity. +Closed issues and pull requests are locked automatically after 30 days of inactivity. ## I want to comment on a locked conversation, what should I do? When an issue has been closed and inactive for over 30 days, the original context is likely outdated. @@ -17,26 +17,27 @@ providing any of the additional information the team needs to investigate. # Feature request process To manage the requests we receive at scale, we introduced automation in our feature request -management process. After we triage a ticket and we identify it as a feature request, it goes +management process. After we triage an issue and we identify it as a feature request, it goes through several steps. ## Manual review -First, we manually review to verify if it aligns with any of the existing roadmap efforts. If it -does, we prioritize it. Alternatively, we keep it open and our feature request bot initiates a -voting process. +First, we manually review the issue to see if it aligns with any of the existing roadmap efforts. If +it does, we prioritize it accordingly. Alternatively, we keep it open and our feature request bot +initiates a voting process. ## Voting phase To include the community in the feature request process, we open voting for 60 days. Anyone can cast -a vote for the request with a thump-up (👍) reaction. If the feature request reaches 20 or more -upvotes, we review it again manually. Alternatively, the bot closes the request. +a vote for the request with a thumbs-up (👍) reaction. When a feature request reaches 20 or more +upvotes, we formally consider the feature request. Alternatively, the bot closes the request. ## Consideration phase -If the feature request receives 20 or more votes, we verify if we can afford to maintain it and -whether it aligns with the long-term vision of Angular. If the answers of both questions are yes, -we prioritize the request, alternatively we close it. +If the feature request receives 20 or more votes, we verify the Angular team can afford to maintain +the feature and whether it aligns with the long-term vision of Angular. If the answers to both of +these questions are yes, we prioritize the request, alternatively we close it with an explanation of +our decision. ## Diagram