Timeline for Improving question closed banners for most users - short wording needed for site specific reasons
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2022 at 20:34 | history | edited | CatijaStaff | CC BY-SA 4.0 |
added 548 characters in body
|
| Dec 10, 2021 at 15:46 | comment | added | Catija Staff | @Zanna Yeah, the rewording in the close modal could be really valuable - something like "Use this close reason on questions that are attempting to report a bug. Do not use it on questions that are caused by bugs. Those questions should be answered with guidance on how to work around the bug unless they're duplicates of an existing question." Or something like that. :) | |
| Dec 10, 2021 at 15:43 | comment | added | Zanna Mod | oops sorry for the duplication! The last 2 comments didn't appear until I posted mine. Anyway I was going to continue... jokerdino tells me that this close reason is meant to only be for questions that are actually attempts to make bug reports (or feature requests), which does happen, and perhaps we do need a close reason for that, but this close reason is (mis)used much more broadly in practice. Qs about bugs are often popular and their answers of longstanding use. Perhaps it's time for a bigger discussion about it and possibly rewording or retiring. I guess that can come later though. | |
| Dec 10, 2021 at 15:37 | comment | added | Zanna Mod | Bugs reports and especially feature requests for flavors can be made on the flavors' own support forums, but if I understand correctly, all packages in Ubuntu repositories (which includes all official flavors' packages) have project pages on Launchpad and can have bugs reported against them there too. Nonetheless, the situation is complex and I'm not sure what text would be best there. Your objections to my suggested wording are good. | |
| Dec 10, 2021 at 15:19 | history | edited | CatijaStaff | CC BY-SA 4.0 |
added 65 characters in body
|
| Dec 10, 2021 at 15:17 | comment | added | Catija Staff | Thanks for doing that check, @Dan - it's really helpful. And thanks. :) | |
| Dec 10, 2021 at 15:16 | comment | added | Dan | @Catija I just double-checked each official flavour of Ubuntu, and I can confirm that all of them direct users to report bugs on Launchpad. I agree with Zanna that saying "... should be reported onLaunchpad" is more correct as it informs users about the platform in case they don't know about it. Otherwise, I quite like your recommended wordings, especially the "This question was closed because [...]" instead of "This question is off topic. [...]" parts as they sound more friendly. | |
| Dec 10, 2021 at 14:20 | comment | added | Catija Staff | As to the validity of the close reason - I did read through your discussion and I think you make really good points - I think that helping people work around a bug is more useful than telling them "go report the bug". Answers could be anything from "this seems to be a bug but here's a workaround that should get you what you need" or "unfortunately, this is a bug that's existed for a while and has been reported already. Here's a duplicate that shows some options to avoid this problem."... etc. | |
| Dec 10, 2021 at 14:17 | comment | added | Catija Staff | @Zanna This is probably a place where I'm not sure about the fine points - which is understandable and why I'm getting feedback. :) I was under the impression that Launchpad was for only official Ubuntu releases - if that's not correct and all of the flavors have places to receive bug reports there, then that makes sense. The other thing is if I just say "should be reported" people might look for a place here on AU to do that reporting - which would be confusing to people - so either something like "to Ubuntu" or something like that seems important if we're not linking anywhere. | |
| Dec 10, 2021 at 14:14 | comment | added | Catija Staff | Regarding the links, @BeastOfCaerbannog the other option is that I can update the other fields to remove them or link to a different place so that they aren't linked twice. I actually looked around for discussions here on meta about some of these topics but I couldn't find anything. The meta discussion/decision is often a good target for more information - if y'all do have that, I can use those in one place or the other. | |
| Dec 10, 2021 at 13:58 | comment | added | BeastOfCaerbannog | I agree with your proposals and I also agree with Zanna's comment. Additionally, I think that links should be added in two close reasons: 1. -> link to official Ubuntu flavors, as on the full text reason; 3. -> link to unsupported releases, as on the full text reason; | |
| Dec 10, 2021 at 12:56 | comment | added | Zanna Mod | Re. the bug part, I think that "reported to Ubuntu" might not be right - Bugs in Ubuntu software should be reported on Launchpad which is the development platform for Ubuntu - most people don't know this (like, ubuntu.com is definitely not the right place, and many people think we are Ubuntu). Bugs in third party software should be reported to whoever is maintaining that software (there's a discussion about this in the comments on this question... I think it's just a bad close reason, myself!) | |
| Dec 10, 2021 at 5:54 | history | answered | CatijaStaff | CC BY-SA 4.0 |