Skip to main content
Commonmark migration
Source Link

##Objections

Objections

##Conclusion

Conclusion

##Objections

##Conclusion

Objections

Conclusion

replaced http://superuser.com/ with https://superuser.com/
Source Link

Just because your profession calls you to someone's home, doesn't mean that the work falls within the scope of ServerFault. People who manage or maintain computers in a professional capacity would then include many of the questions that you see on SuperUser, like for instance this one that I asked in the capacity of someone who maintains computers in a professional capacitythis one that I asked in the capacity of someone who maintains computers in a professional capacity. Then again, Scott also says:

Just because your profession calls you to someone's home, doesn't mean that the work falls within the scope of ServerFault. People who manage or maintain computers in a professional capacity would then include many of the questions that you see on SuperUser, like for instance this one that I asked in the capacity of someone who maintains computers in a professional capacity. Then again, Scott also says:

Just because your profession calls you to someone's home, doesn't mean that the work falls within the scope of ServerFault. People who manage or maintain computers in a professional capacity would then include many of the questions that you see on SuperUser, like for instance this one that I asked in the capacity of someone who maintains computers in a professional capacity. Then again, Scott also says:

replaced http://meta.serverfault.com/ with https://meta.serverfault.com/
Source Link

Before I blow through a day's worth of flags on this, perhaps there's a better way. I believe that virtually no question with the tag belongs here. Here's a discussion on the topic from two years ago: "How to deal with Windows Home Server questions on Serverfault?How to deal with Windows Home Server questions on Serverfault?"

Most people seem to want it dead yesterday. However, there is some dissent worth considering. The dissent highlites possible weaknesses in our FAQ and stated purpose. Let's use this as a time to refine our FAQ revisionFAQ revision.

Oorang saysOorang says:

Scott saysScott says:

If that's how we define "SysAdmin-related" then we've got some serious FAQ rewriting to do (and, of course, we are doing thatwe are doing that. Yay!)

Kev saysKev says:

Before I blow through a day's worth of flags on this, perhaps there's a better way. I believe that virtually no question with the tag belongs here. Here's a discussion on the topic from two years ago: "How to deal with Windows Home Server questions on Serverfault?"

Most people seem to want it dead yesterday. However, there is some dissent worth considering. The dissent highlites possible weaknesses in our FAQ and stated purpose. Let's use this as a time to refine our FAQ revision.

Oorang says:

Scott says:

If that's how we define "SysAdmin-related" then we've got some serious FAQ rewriting to do (and, of course, we are doing that. Yay!)

Kev says:

Before I blow through a day's worth of flags on this, perhaps there's a better way. I believe that virtually no question with the tag belongs here. Here's a discussion on the topic from two years ago: "How to deal with Windows Home Server questions on Serverfault?"

Most people seem to want it dead yesterday. However, there is some dissent worth considering. The dissent highlites possible weaknesses in our FAQ and stated purpose. Let's use this as a time to refine our FAQ revision.

Oorang says:

Scott says:

If that's how we define "SysAdmin-related" then we've got some serious FAQ rewriting to do (and, of course, we are doing that. Yay!)

Kev says:

Tweeted twitter.com/#!/ServerFault/status/160231626591313920
Source Link
Wesley
  • 33k
  • 23
  • 37
Loading