Timeline for What should be featured in our list of off-topic close reasons?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2020 at 13:47 | history | edited | CommunityBot |
Commonmark migration
|
|
| Mar 17, 2017 at 10:12 | history | edited | CommunityBot |
replaced http://meta.superuser.com/ with https://meta.superuser.com/
|
|
| Mar 17, 2017 at 10:12 | history | edited | CommunityBot |
replaced http://meta.superuser.com/ with https://meta.superuser.com/
|
|
| Jun 27, 2013 at 21:32 | comment | added | nixda | "Questions asking for someone to design a solution to a problem" - I really love to see this option! | |
| Jun 14, 2013 at 17:35 | comment | added | nhinkle Mod | I think we all agree and are misunderstanding each other... | |
| Jun 14, 2013 at 16:44 | comment | added | Daniel Beck Mod | Even if it's open source, if it's not released, things can still change. Maybe the software is currently broken, and won't be when released. Questions specifically on unreleased software are usually about stuff that doesn't work right. We get enough "I'm running the nightly build (e.g. Chrome Canary build) and stuff is broken, please help!" on MSU. Recommending it in answers OTOH is completely different ("The feature solving your problem is in the nightly build and will be available soon" is perfectly OK). | |
| Jun 14, 2013 at 16:29 | comment | added | nhinkle Mod | @Luke I see no reason to ever close a question for being about software that's too old - if I understand correctly, that entry is referring to things that are too new. | |
| Jun 14, 2013 at 16:15 | comment | added | Canadian Luke | In regards to the third bullet point: I would definitely agree with that, but also want to add that I don't want to see it like Ask Ubuntu, where they immediately close old versions as Off Topic after a threshold, even if it's a public release | |
| Jun 14, 2013 at 14:18 | history | answered | allquixotic | CC BY-SA 3.0 |