- 🇳🇿New Zealand quietone
Reading #11 and #16 I decided to look at the evidence. There are 25 issues tagged bugsmash and accessibility that have been closed for reasons other than fixed.
won't fix: 2
works as designed: 7
cannot reproduce: 6 (includes several IE 11 issues)
outdated: 10 (includes several IE 11 issues)I opened all the issues and read how they were closed. I didn't find that any of them were closed improperly. I do agree with @pameeela in #14 that the Bugsmash triagers are "taking a cautious approach to this and treating every issue with care.".
I have added the proposed text to the initiative docs, https://www.drupal.org/community-initiatives/bug-smash-initiative/issue-... →
- Status changed to RTBC
over 1 year ago 8:07am 28 March 2023 - 🇧🇪Belgium borisson_ Mechelen, 🇧🇪
- 🇫🇮Finland lauriii Finland
+1 for the proposed policy, as a more manageable issue queue benefits everyone by increasing our efficiency. I believe that it's essential for us to emphasize that closing stale issues doesn't mean disregarding bugs or problems. Issues are being closed because they are lacking next steps due to insufficient information.
We should always respect reported problems and strive to understand them. However, if we cannot proceed on an issue due to inadequate information, it holds little value in the queue. While #11 brings up valid concerns, I don't believe that maintaining a queue filled with unactionable issues addresses those issues.
- Status changed to Needs work
over 1 year ago 3:40am 21 April 2023 - 🇹🇼Taiwan g-brodiei
Saw this issue from bug smash initiative channel from @quietone to check wordings on policy page.
+1 on the policy change. I’ve read through the threads and notice a slight wording diff on the policy page.
On the issue summary:
If the stale issue meets these criteria, it should be closed:On policy page → :
if an issue meets these three criteria, it should be closed:I believe the word `three` would make it clearer for future readers (not native English speaker) to understand the criteria, thanks!
- Status changed to Needs review
over 1 year ago 5:31am 21 April 2023 - Status changed to RTBC
over 1 year ago 5:34am 21 April 2023 - Status changed to Fixed
over 1 year ago 5:39am 21 April 2023 Automatically closed - issue fixed for 2 weeks with no activity.