I hesitate to post this as an answer, but since this is a discussion, here goes. I can see some value in gathering historic information at U&L, if there are people who know (or know people who know) the answer to such a question. "Why" questions could have evidence behind the answers, or may have an unknown origin. The worst-case scenario is that it gets ...
There are two reasons why you shouldn't worry about “breaking rules”.
One reason is that the assertion that the user wants to “break local rule” is an assumption on your part. You have no way to know whether this is true. There is quite a leap of faith between “I want to install Screen” and “I want to bypass the job scheduler to run my jobs ahead of other ...
The most important thing for a new user asking a question is to get answers.
When someone's first contact with the site is to ask a question, that's usually because they have a problem to solve, not because they want to join a community. Joining a community comes later, if the community has proven to be useful or interesting.
So when evaluating questions ...
There's a specific close reason for this:
Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers.
That is available in the flag menu when you reach 50 reputation and, after 3000 reputation, it's in the close menu. If this is ...
My first instinct is that it wouldn't really be on topic, no. GRUB isn't a *nix thing, as such, it acts before the operating system so isn't really a part of any OS. Yes, it is a tool more commonly found in the *nix world, but using GRUB to install Windows systems doesn't seem to be something that would fall within the scope of this site.
It would, however,...
Leave the original in place and try and make it so that it's as clearly in line with the A's. Then start a new Q and post your learnings as a new A. Also reference the original so that others see the linkages.
Questions asking for lists of resources tend to degenerate into lists of items, as opposed to answers. They tend to become a poll rather than a question with its answers.
Stack Exchange does not work well for polls, where each answer is a separate items. Voting on the answers results in a score that does not at all reflect the quality of the item mentioned ...
We ask people not to cross-post, not that it helps much. If it's posted on both sites, flag it here with a link to the other site's version. If we think it's way better here we'll ask the other site to close their version, but usually we close ours and tell the asker they need to pick one site
As a general guideline across all Stack Exchange sites, cross-posting is generally frowned upon, especially if its a copy & paste job. There are exceptions, e.g., both Ask Ubuntu and us probably have a question about how to add a static route—but Ask Ubuntu probably focuses exclusively on using Network Manager's GUI, whereas we might talk about files in /...
Upvote button hover text:
This question shows research effort; it is helpful and clear
The fact that someone answers a question does not, de facto, make it a good question. Questions may have answers and show zero research effort, or be borderline incomprehensible and people will still answer them.
Upvotes are the only signifier of quality.
Did you leave an empty line before the code? For example:
line 1 indented by four spaces
line 2 indented by four spaces
Test line 2
line 3 indented by four spaces
line 4 indented by four spaces
Shows up as:
line 1 indented by four spaces
line 2 indented by four spaces
Test line 2
line 3 indented by four ...
I guess we may as well close them. Closed questions don't count as unanswered so there's no real reason to delete and, anyway, closed questions with no answers get deleted automatically after a while.
I'm not sure what reason we'd use to close them though. Non-reproducible is probably the best choice. We might want to consider adding a new close reason for ...
It's perfectly fine to ask distribution-specific questions here. In fact, look at all the distribution tags — we try to use them only on questions that are specific to a distribution (or class of distributions — for example, many questions tagged ubuntu are relevant to Mint), or at least that have solutions that are specific to a distribution.
It's also ...
If you've found an answer to your original question then I'd encourage you to provide an answer to it yourself. It's perfectly acceptable to answer ones own questions, even after you've continued to research it yourself. That's fairly typical, actually.
As to your new question. If it's completely different, then I'd ask it as it's own question and not ...
I sympathize with what you're saying, but if you look at those graphs that Braiam posted one thing you should be noticing is that they're all trending up. This IMO, is a good thing and will continue to grow if we keep doing what we've been doing here since the site's inception.
Keep the community friendly
Look for holes in the existing Q's, if you find ...
Does anyone know how to install xyz` under Labamba X.Y?
are about the capabilities of certain people and are off-topic on this site. So are questions, asking for names of people being able to help:
Who knows how to install xyz under Labamba X.Y?
Such questions are inappropriate for this site as they are not about Unix&Linux ...
There was a time years ago when Stack Exchange was on a big kick about phrasing titles as questions, but I think it mostly died out. Personally I couldn't care less, "Centos cannot ping default gateway" and "Why can't Centos ping default gateway?" are functionally identical.
Any statement in a question title comes with the implied question "how do I fix ...
Bad — titles should be a proper sentence or (usually better) sentence fragment:
GRUB - How do I apply parameters to specific kernels?
The system adds the most popular tag that isn't already in the tag as a prefix, which looks bad enough on its own — here, this leads to duplication:
grub2 - GRUB - How do I apply parameters to specific kernels?
There are already a bunch of questions on this topic on the main meta:
Should I retag a question with a tag that is based on the answer and not the question?
Retagging questions in terms of possible answer technologies
Retagging questions with the answer?
Should question include tags that are mentioned only in answers?
In summary, the thinking seems to be ...
My major problem with recommendations for outside material is they are by nature inevitably very weak questions. As terdon says, there is no real problem: it is not as if such material is hidden in some secret place requiring some special knowledge to find. If you can log in to an S.E. site, you can use a search engine, and that's exactly what a search ...
Popularity is not an end in itself, it should be a by-product of a high quality reference site maintained by a knowledgeable and approachable community.
Personally, I don't think that there is a "situation" that needs "improving." That isn't to say that the site can't be improved, it just means that there is nothing intrinsically wrong with a slow, ...
If harmonized file names are really useful to follow the question and answers, then please do harmonize them. Pick a sensible set, preferably the one in the question, failing that one used in an answer. Which answer doesn't really matter.
Harmonized file names don't always matter. If there's just one input file and one output file, it's easy enough to ...
You'd have to find a way to make it longer to get past the quality filter... For example, maybe list a few of the things you've checked. Or some system details. This isn't just a way to defeat the filter, it also makes your question better.
But in this case, there is already an answer here: What is a distro-agnostic way determine the OS install date?
I don't think a tag should be applied to a question when it applies to one possible answer (which I think is the case with the question you link). Just because fuse happens to be a solution (maybe even the only reasonable one) doesn't mean that the question is about fuse.
However, sometimes people ask questions where they're unfamiliar with the basic ...
There is no shadowban-like state in which you can post questions but they aren't displayed to other users. It is possible to be blocked from posting questions entirely, but you would get an error message when you tried. If you're able to post questions, other users can see them
To quote the relevant points of the ever-useful FAQ (useful to me, at least, as it contains explanations for many of Stack Exchange’s workings) regarding the community user:
Randomly poke old unanswered questions* every hour so they get some attention
* Questions with at least 30 days of no activity, at least one answer scoring zero, and no answers scoring ...
There's another syntax for code blocks which is mentioned in the advanced formatting help. Surround the code by three backticks on a line of their own. The backticks have to be on their own line but don't need a blank line.
echo Hello, world.
This is rendered as
echo Hello, world.
This syntax also makes it easy to request ...
I agree more with position 1.
It is extremely surprising for a user, to learn that some readers consider "thanks" harmful enough, that they will edit purely to remove it.
I saw a similar edit on a question marked as being from a new user. I cannot see enforcing this on new users as being "welcoming". If the poster works out what's going on, it feels like ...
The bounty lasts for a few days. If you look at the question, it'll tell you how much time is remaining. You can't take it back, but if an answer is good, you can assign the bounty. If not, just wait it out.
Release schedules have been known to change over time, I would consider this a localized problem, also known as "ask the developers". So no, please do not ask this.
Also CentOS/Scientific Linux are probably based on however long it takes them after Red Hat ships RHEL 7. It'll be done when it's done.