I am new here, but in my short time using Stack Overflow, I have noticed that for Nginx, where I look at most, over 99% of the questions should be on Pro Webmasters.
Having had a discussion with one of the moderators recently, I thought I'll propose that web server related tags (Nginx, Apache, etc.) should be barred on Stack Overflow.
Using Nginx which I am most familiar with as an example, the tagged questions basically all fall into one of the two following categories:
It is actually a "PHP" or "jQuery" or whatever question and the person just happens to use Nginx so they tag it "Nginx". Replacing "Nginx" with "Apache", "Ligthy", "Cherokee" or any other webserver would not change the issue and there is no point tagging it with "Nginx".
It is a server configuration question. Full stop.
If the "Nginx" tag was not available, Condition 1 would go away and those with Condition 2 would struggle with tagging their questions and would either.
A. Just pick any other tag in which case the inappropriate nature of the query would stand out and presumably get flagged for transfer
B. Rethink where they are posting.
On "B" however, most people only know of Stack Overflow. (I certainly didn't know of all the other associated sites until I started visiting regularly) and may not know where to put the question. Therefore they need help.
Option I: Automatically move all questions tagged with webserver names over to Pro Webmasters. It is after all supposed to deal with issues that affect whole websites ... such as Webservers. I gather there may be some issues with this
Option II: Generate a message suggesting that as they have selected a webserver related issue, they might want to move the query over to Pro Webmasters and give a button to click to do this. That is, get the OP to execute the migration themselves at the time of posting.
I may be totally off base due to my newness here, but this just crossed my mind. Any thoughts?
So following @Robert Harvey's challenge to prove the questions tagged with "Nginx" on Stack Overflow are all off topic and my nice down vote :), I have produced a summary of the 15 posts on the first page of the Stack Overflow Nginx tag as of 22 december 2011.
Why does Tire not connect to ElasticSearch in production mode (RoR)?: Something to do with configuring Ruby on Rails. (Condition 2. Server Configuration)
https://stackoverflow.com/questions/8604103/uwsgi-errorpython-application-not-found: Trying to get uWSGI working. (Condition 2. Server Configuration)
Is this the right entry for the sudoers file to give php access to reload nginx?: Wants to set up his sudoers file. (Condition 2. Server Configuration)
https://stackoverflow.com/questions/8600269/hostname-command-not-found-nginx: Having issues with server HOSTNAME. (Condition 2. Server Configuration)
https://stackoverflow.com/questions/8600178/nginx-gives-500-internal-error-when-accessing-zend-project: Issue with 500 Internal Server Error. (Condition 2. Server Configuration)
https://stackoverflow.com/questions/8593237/varnish-requirements: Wants to compare Varnish with Nginx - Closed. (Condition 3. Off The Wall)
ember.js node and nginx: Wants advice on server setup. - Probably should have been closed (Condition 3. Off The Wall)
nginx proxy_pass based on whether request method is POST, PUT or DELETE: Advice on using Lua to configure Nginx - Borderline but basically server configuration (Condition 2. Server Configuration)
django admin redirects to wrong port on save: Issue with Django redirecting to a wrong port. (Condition 2. Server Configuration)
Configuring Nginx and Socket.IO: Title says it all. (Condition 2. Server Configuration)
Nginx and Rails gzip configuration: Title says it all. (Condition 2. Server Configuration)
Persistence Workflow Design: Wants advice suitability of Nginx with some server setup. (Condition 2. Server Configuration)
Serving dynamic content from Mongo GridFS via Nginx without a 404 error: Nginx setup query. (Condition 2. Server Configuration)
https://stackoverflow.com/questions/8567697/nginx-having-trouble-processing-php: Nginx PHP setup query. (Condition 2. Server Configuration)
Only one of the fifteen is programming related and that is only incidentally related to Nginx.
I think this proves the point, doesn't it?
Not sure why this is being ignored / voted down without a comment given that I have responded to the challenge to demonstrate the case.
Anyone care to add to this?