Skip to main content
replaced http://meta.serverfault.com/ with https://meta.serverfault.com/
Source Link
replaced http://meta.serverfault.com/ with https://meta.serverfault.com/
Source Link

Pretty much any IT related question could be on topic for serverfault if people chose to consider it so. We though, through experience and precedent have narrowed the field considerably.

The scope of serverfault is something that we struggle with continuously and it cannot adequately be conveyed by a faq. The word server for example means all things to all people and it's pretty much the same with professional.

Let's consider one fairly narrow use case - developer tools in the form of *AMP and Visual Studio. They are in many respects the same thing. One click install, a database, a webserver, programming languages etc. They are though treated differently by people who use them. We have almost no Visual Studio questions - they all get asked on Stackoverflow because everyone knows that that's the place to ask developer tools questions, if they did get asked here they'd just as likely be closed off topic as *AMP questions are. Why then do people who use *AMP think that Serverfault is the correct place to ask their developer tool question ?

Everyone can interpret the faq to suit their purpose so I don't think the faq needs to be changed. It would end up as lists of things which has already been called outbeen called out.

We should though make more use ofmake more use of the and I'm sure this will be addressed in the near future.

Pretty much any IT related question could be on topic for serverfault if people chose to consider it so. We though, through experience and precedent have narrowed the field considerably.

The scope of serverfault is something that we struggle with continuously and it cannot adequately be conveyed by a faq. The word server for example means all things to all people and it's pretty much the same with professional.

Let's consider one fairly narrow use case - developer tools in the form of *AMP and Visual Studio. They are in many respects the same thing. One click install, a database, a webserver, programming languages etc. They are though treated differently by people who use them. We have almost no Visual Studio questions - they all get asked on Stackoverflow because everyone knows that that's the place to ask developer tools questions, if they did get asked here they'd just as likely be closed off topic as *AMP questions are. Why then do people who use *AMP think that Serverfault is the correct place to ask their developer tool question ?

Everyone can interpret the faq to suit their purpose so I don't think the faq needs to be changed. It would end up as lists of things which has already been called out.

We should though make more use of the and I'm sure this will be addressed in the near future.

Pretty much any IT related question could be on topic for serverfault if people chose to consider it so. We though, through experience and precedent have narrowed the field considerably.

The scope of serverfault is something that we struggle with continuously and it cannot adequately be conveyed by a faq. The word server for example means all things to all people and it's pretty much the same with professional.

Let's consider one fairly narrow use case - developer tools in the form of *AMP and Visual Studio. They are in many respects the same thing. One click install, a database, a webserver, programming languages etc. They are though treated differently by people who use them. We have almost no Visual Studio questions - they all get asked on Stackoverflow because everyone knows that that's the place to ask developer tools questions, if they did get asked here they'd just as likely be closed off topic as *AMP questions are. Why then do people who use *AMP think that Serverfault is the correct place to ask their developer tool question ?

Everyone can interpret the faq to suit their purpose so I don't think the faq needs to be changed. It would end up as lists of things which has already been called out.

We should though make more use of the and I'm sure this will be addressed in the near future.

edited body
Source Link
user9517 Mod
  • 116.8k
  • 4
  • 55
  • 131

Pretty much any IT related question could be on topic for serverfault if people chose to consider it so. We though, through experience and precedent have narrowed the field considerably.

The scope of serverfault is something that we struggle with continuously and it cannot adequately be conveyed by a faq. The word server for example means all things to all people and it's pretty much the same with professional.

Let's consider one fairly narrow use case - developer tools in the form of *AMP and Visual Studio. They are in many respects the same thing. One click install, a database, a webserver, programming languages etc. They are though treated differently by people who use them. We have almost no Visual Studio questions - they all get asked on Stackoverflow because everyone knows that that's the place to ask developer tools questions, if they did get asked here they'd just as likely be closed off topic as *AMP questions are. Why then do people who use *AMP think that Serverfault is the correct place to ask their developer tool question ?

Everyone can interpret the faq to suit their purpose so I don't think the faq needs to be changed as it. It would end up as lists of thingslists of things which has already been called out.

We should though make more use of the and I'm sure this will be addressed in the near future.

Pretty much any IT related question could be on topic for serverfault if people chose to consider it so. We though, through experience and precedent have narrowed the field considerably.

The scope of serverfault is something that we struggle with continuously and it cannot adequately be conveyed by a faq. The word server for example means all things to all people and it's pretty much the same with professional.

Let's consider one fairly narrow use case - developer tools in the form of *AMP and Visual Studio. They are in many respects the same thing. One click install, a database, a webserver, programming languages etc. They are though treated differently by people who use them. We have almost no Visual Studio questions - they all get asked on Stackoverflow because everyone knows that that's the place to ask developer tools questions, if they did get asked here they'd just as likely be closed off topic as *AMP questions are. Why then do people who use *AMP think that Serverfault is the correct place to ask their developer tool question ?

Everyone can interpret the faq to suit their purpose so I don't think the faq needs to be changed as it would end up as lists of things which has already been called out.

We should though make more use of the and I'm sure this will be addressed in the near future.

Pretty much any IT related question could be on topic for serverfault if people chose to consider it so. We though, through experience and precedent have narrowed the field considerably.

The scope of serverfault is something that we struggle with continuously and it cannot adequately be conveyed by a faq. The word server for example means all things to all people and it's pretty much the same with professional.

Let's consider one fairly narrow use case - developer tools in the form of *AMP and Visual Studio. They are in many respects the same thing. One click install, a database, a webserver, programming languages etc. They are though treated differently by people who use them. We have almost no Visual Studio questions - they all get asked on Stackoverflow because everyone knows that that's the place to ask developer tools questions, if they did get asked here they'd just as likely be closed off topic as *AMP questions are. Why then do people who use *AMP think that Serverfault is the correct place to ask their developer tool question ?

Everyone can interpret the faq to suit their purpose so I don't think the faq needs to be changed. It would end up as lists of things which has already been called out.

We should though make more use of the and I'm sure this will be addressed in the near future.

Source Link
user9517 Mod
  • 116.8k
  • 4
  • 55
  • 131
Loading