From faf2d6acc111dee603e0248faa2bcb067dd76a8e Mon Sep 17 00:00:00 2001 From: Ed Page Date: Wed, 12 Jun 2024 09:55:53 -0500 Subject: [PATCH] docs(contrib): Focus duplicates on root cause and not solutions --- src/doc/contrib/src/issues.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/src/doc/contrib/src/issues.md b/src/doc/contrib/src/issues.md index 67e4c45f175..8385fa7489a 100644 --- a/src/doc/contrib/src/issues.md +++ b/src/doc/contrib/src/issues.md @@ -197,10 +197,13 @@ issues have not yet been triaged. There are several things to consider when triaging an issue: * Is this a duplicate? Search the issue tracker (including closed issues) to - see if there is something similar or identical to what is reported. If it is - obviously a duplicate, write a comment that it is a duplicate of the other - issue, and close the issue. If it isn't obvious that it is a duplicate, - leave a comment asking the author if the other issue covers what they reported. + see if there is an issue with a similar or identical root cause to what is reported. + We generally focus issues around root causes so alternative solutions can be + discussed and evaluated together. + If it is obviously a duplicate, write a comment that it is a duplicate of the + other issue, and close the issue. + If it isn't obvious that it is a duplicate, leave a comment asking the author + if the other issue covers what they reported. * For a bug, check if the report contains enough information to reproduce it. If you can't reproduce it, solicit more information from the author to