Skip to content

Commit 49383c8

Browse files
Trottaddaleax
authored andcommitted
doc: improve triaging text in issues.md
Remove a double negative and many superfluous sentences. The sentiment in the removed material is good, but we already tell people that discussion should be focused, helpful, and professional. Having two extra paragraphs greatly reduces the likelihood that people will read the material. PR-URL: #34164 Reviewed-By: Anto Aravinth <[email protected]> Reviewed-By: James M Snell <[email protected]>
1 parent a9302b5 commit 49383c8

File tree

1 file changed

+1
-13
lines changed

1 file changed

+1
-13
lines changed

doc/guides/contributing/issues.md

Lines changed: 1 addition & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -84,23 +84,11 @@ See [How to create a Minimal, Complete, and Verifiable example](https://stackove
8484

8585
## Triaging a Bug Report
8686

87-
Once an issue has been opened, it is not uncommon for there to be discussion
87+
Once an issue has been opened, it is common for there to be discussion
8888
around it. Some contributors may have differing opinions about the issue,
8989
including whether the behavior being seen is a bug or a feature. This discussion
9090
is part of the process and should be kept focused, helpful, and professional.
9191

92-
Short, clipped responses that provide neither additional context nor supporting
93-
details are not helpful or professional to many. Such responses are simply
94-
annoying and unfriendly.
95-
96-
Contributors are encouraged to help one another to make forward progress as much
97-
as possible, empowering one another to solve issues collaboratively. If you
98-
choose to comment on an issue that you feel either is not a problem that needs
99-
to be fixed, or if you encounter information in an issue that you feel is
100-
incorrect, explain *why* you feel that way with additional supporting context,
101-
and be willing to be convinced that you may be wrong. By doing so, we can often
102-
reach the correct outcome much faster.
103-
10492
## Resolving a Bug Report
10593

10694
In the vast majority of cases, issues are resolved by opening a Pull Request.

0 commit comments

Comments
 (0)