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
|
|
Mar 17, 2017 at 10:13 | history | edited | CommunityBot |
replaced http://meta.serverfault.com/ with https://meta.serverfault.com/
|
|
Mar 17, 2017 at 10:13 | history | edited | CommunityBot |
replaced http://meta.serverfault.com/ with https://meta.serverfault.com/
|
|
Dec 5, 2014 at 23:08 | comment | added | Shane Madden StaffMod | On "professional" - I want to find good wording that asks for the right kind of questions, while taking away the focus on the user.. what's there might not do that well, though. On "_aaS", that section definitely needs better wording. I'll work "legal advice" back in, though I feel like circumvention is covered decently by "unauthorized use/misuse" - is that missing something important, do you think? | |
Dec 5, 2014 at 17:42 | history | edited | voretaq7Mod | CC BY-SA 3.0 |
Clarify Professional scope & Professional audience
|
Dec 5, 2014 at 17:42 | comment | added | voretaq7 Mod | @Iain Quite correct, and fixed(ish) - It's tough because "professional" is both a scope-limiter (we don't want the FixItFry questions that should be asked to the local sysadmin) and our audience (the sysadmin who just got asked a FixItFry question) | |
Dec 5, 2014 at 17:29 | comment | added | user9517 | I got part way through the second paragraph and would like to suggest you (like everyone else) stop conflating scope and audience. Scope is IT in a professional environment. Audience is the people 'managing' that scope. Other than that I'm with you. | |
Dec 5, 2014 at 17:26 | history | answered | voretaq7Mod | CC BY-SA 3.0 |