Timeline for What should we do with questions about Vagrant?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 8, 2015 at 21:26 | comment | added | Jim B | @EEAA I do not disagree with your point about cpanel, yet admins are often forced to use it (much like the question on legacy software) While vagrant isn't cpanel, its not a tool primarily used by admins, which was the bar. If you are lowering the bar to anything that could used by an admin, that's fine wth me but it should not be a "I like that tool so its in" policy. We should have a clear policy. Since SO have clearly concluded that vagrant is not an admin tool, since most of the questions are not from admins at all, IMHO the consistent answer to the question is migrate. | |
| Oct 8, 2015 at 21:15 | comment | added | Jim B | @gWaldo, its not about whack a mole, there is a vibrant well established development community SE that supports its primary user base, and has over 4k answers on the topic. Why would we not want to migrate the questions over to that community- if only for consistency. | |
| Oct 8, 2015 at 21:11 | comment | added | EEAA Mod | @JimB You're missing the point. There is no sane way to do sysadmin with cPanel. We don't need to hash out that discussion yet again. Vagrant, while primarily a dev tool, does have legit use cases in systems administration. cPanel does not. It does not work to create classes of tools and define everything as "developer centric" to be off topic. Each product deserves its own nuanced approach, especially for those like vagrant that fall into a grey area. | |
| Oct 8, 2015 at 21:07 | comment | added | Jim B | @EEAA so the questions (numbered in the low thousands prior to the deletion) by admins forced to manage servers with cpanel installed is not a valid sysadmin question BUT the questions on a tool that's aimed at development system design and by our (SE) evidence is primarily a developer tool is somehow directly on point? I'm not trying to pick on you personally I'm simply advocating that we should be able to have a consistent, repeatable stance on what's allowed. The only stance on this I oppose is the "it depends" stance. | |
| Oct 8, 2015 at 16:56 | comment | added | EEAA Mod | @JimB As is evidenced in my answer above, vagrant has a valid use case in pro sysadmin. cPanel does not. Those two topics cannot be grouped into the same bucket. | |
| Oct 8, 2015 at 13:47 | comment | added | gWaldo | @JimB You are, of course, welcome to continue playing Whack-a-Mole with products that you don't want to support. It's probably fine. | |
| Oct 8, 2015 at 13:46 | comment | added | gWaldo |
Demonstrated being helpful by answering a question, the example being how to use the ignore tags and hide-ignored tags features. @Iain
|
|
| Oct 8, 2015 at 13:43 | history | edited | gWaldo | CC BY-SA 3.0 |
Showing how to hide filtered tags.
|
| Oct 7, 2015 at 8:09 | comment | added | Jim B | It's not about not wanting to see or answer them - it's about consistency- in the past the criteria for moving/closing questions was because we specifically said it's off topic (cpanel) OR the question was about something a user or developer would do. Vagrant is beyond a doubt (even if all you do is look at where questions go) a developer tool and by past standards off topic- if now the bar is anything an admin might do, I'm happy with that but then we should bring back cpanel, bluescreen, etc. | |
| Oct 6, 2015 at 22:03 | comment | added | user9517 | Can you explain how to add a filter so that you don't see stuff please ? | |
| Oct 6, 2015 at 16:24 | history | answered | gWaldo | CC BY-SA 3.0 |