Timeline for Proposed change to Server Fault guidelines
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 10:00 | history | edited | CommunityBot |
Commonmark migration
|
|
| Dec 5, 2014 at 23:01 | comment | added | Shane Madden StaffMod | Yeah, I want to find better wording for the sections you're talking about. Will give it some more thought! | |
| Dec 5, 2014 at 17:18 | history | edited | HBruijn | CC BY-SA 3.0 |
added 95 characters in body
|
| Dec 5, 2014 at 17:15 | comment | added | HBruijn | I struggled a bit to come with something suitable and failed, hence starting my answer with that question. I agree that questions and answers surrounding the operational aspects of managing the Dev support infrastructure in DevOps are and should remain on-topic, but the how to phrase that? | |
| Dec 5, 2014 at 16:58 | comment | added | voretaq7 Mod | Similarly "We're trying to create a good development environment using containers, we need X, Y, and Z, and we've tried A & B but can't quite get it doing what we want. Any ideas?" questions, again from sysadmin/DevOps folks, would in my view be on-topic since it's part of building and managing an infrastructure in a professional capacity. | |
| Dec 5, 2014 at 16:56 | comment | added | voretaq7 Mod |
The point of excluding development environments from our scope was to exclude "This WAMP stack on my workstation is broken. FIX IT FOR ME!" questions from developers, which are almost universally terrible questions. "We implemented X in our dev environment, it broke Y, any ideas on how to fix it so we can put it in production?" questions from sysadmin/DevOps types who know and understand the systems they're asking about have always been in-scope. If you can think of a way to better explain the goal here I have no objection to changing it.
|
|
| Dec 5, 2014 at 10:06 | history | edited | HBruijn | CC BY-SA 3.0 |
added 36 characters in body
|
| Dec 5, 2014 at 10:01 | history | answered | HBruijn | CC BY-SA 3.0 |