I don't think version numbers are helpful in any shape or form in our tag wiki.
If someone wants to know what the latest version of a software is, the Super User tag wiki is not the right place to learn it.
It is frowned upon and shouldn't be done.
You should make the tag wiki applicable to how it's used and relates to Super User. Lifting direct from external sources rarely is relevant.
But if the tag at this stage only needs a simple explanation or definition, it's no big effort to rephrase and distill external sources in your own words.
You only posted 10 tag wiki suggestions total:
You also edited tag wikis four times:
pxe, Jul 20
nas, Jul 20
shell-script, Jul 20
802.11, Aug 29
The rest are tag wiki excerpts, and they don't count, similar to how editing tags doesn't count towards the Copy Editor badge.
I'm not sure where the ...
The pdf tag wiki was deleted at some point and any attempts to reach the main edit page would redirect back to its /info page, even for moderators.
How was it deleted? There was a hole in our permission checks - moderators were allowed to pretty much delete anything, including tag wikis (although, this is not exposed in the UI currently).
The gates have ...
The user who rejected your suggestions said in chat:
I thought they were re-writes of previous edits. :( Sorry about that, can I do anything to fix it?
Sorry that there was a mistake, it looks like another user misunderstood the distinction between the suggested tag wiki edits and the tag wiki excerpts. This user has just hit 10k, and had probably not ...
As I understand it, many language-related issues are specific to the language. Tags for the individual languages are more likely to get the right people to see these questions. This seems useful and perfectly reasonable to me.
Instead of burning these tags, I suggest that we edit the tag wiki excerpts to specify proper usage. E.g.,
Use this tag for ...
Rules must be consistent and unduplicitous. If we handle one tag one way, we should handle all tags related with that tag in the same way (say, all 35 tags about Microsoft products). This might mean that we FIRST have to discuss tag wikis in a setting appropriate for debate and discussion, i.e. a chatroom. IMHO, a meta question is not the right place for ...
For normal edits, this doesn't come up because the reputation threshold for full edit rights (2000) is the same threshold as for approving edit suggestions (2000). There is a possibility to see your own edits in the queue, but only if you can suggest one and then make it to 2000 before it gets addressed.
However, the thresholds for tag wikis differ - full ...
Guidance for one facet, possibly a bullet in the wiki:
For questions dealing with the AWS services, themselves, or administrative tasks associated with the host, Server Fault may be a more appropriate site.
I propose the following change to the tag wiki excerpt, along with a similar change to the tag wiki, splitting it in a Windows and a Mac OS X section:
On Windows, services are processes running regardless of users logging in. They provide access and features to different programs or processes. On Mac OS X, services are menu bar and context menu items ...
Tag wiki content should be cited just as you would if you were posting it as an answer. You'd quote a few sentences with a link back to the source.
If you need to quote more than three sentences, that's already too much. (Three is just a rule of thumb and pinkie.)
Better no more than that and just fill out the rest of the tag wiki with more Super User ...
Charles, Thanks for raising this issue. I was unaware of the effort you had put into creating the tag wikis and it wasn't my intention to rain on your parade. It would help if you could post links to the specific questions. For now, I can only respond from memory.
I do remember seeing one or two of these. My recollection is that these were edits to ...
I think the problem is you can create any tag you like at 300 rep on Super User. Now, although it does take some knowledge and understanding to get to that point, obviously people will then just decide that "Oh, my post needs a Windows Azure tag, so I'll just go along and create it". It doesn't ask for a description, which is why so many are undefined and ...
We're doing the same for osx, so, why not?
Tag Wiki Excerpt
When talking only about the excerpt, then I wouldn't recommend doing this. The excerpt has enough space to explain what security is about. The space shouldn't be sacrificed for giving users directions on where else they might ask their question.
You brought up the point that a user ...
Excerpts need to be as long as they need to be.
Often, they're not needed at all as the tag is self-explanatory.
If it needs to break two lines, then it's too long. It should be short, sweet and to the point.
Yes, the original was too wordy and needing hedge trimming.
Excerpts are great for disambiguation, where it will go on to be ignored all the same....
That warning means to not just approve any tag wiki edits that appear.
If you grab one or two sentences from the proposed tag wiki suggestions they come up on Google pointing to other sites, verbatim.
Yes, the other tag wikis should probably be deleted since they add nothing to the site nor do they explain when best to use the tag. Ideally we'd also ban ...
I have to disagree with the accepted answer.
Why reject a perfectly good edit? What if the user put a lot of effort into the edit - why penalize them and risk them not participating in something they were interested in?
If it's not plagiarism (or un-cited) and it's not bad information - just approve it - it's acceptable. If the tag shouldn't exist, then ...
I took a moment to browse through a handful of the tagged questions here, and have some observations.
Of the few questions I looked at, most did not relate strongly enough to SharePoint to indicate that they would be strictly better off on SP.SE, although the most recent one, as of this writing, certainly does.
Some, like Sharepoint Sites on SP 2010, are ...
Sorry if this is a non-SU screenshot, but in the activity tab you can see all your suggested edits, being tag wikis, tag excerpt or when you were a non-2K user suggested edits:
and below you can select all the way back:
These are not separated of your suggested edits, actually every tag wiki edit counts as suggested edit (and you get 2 rep for that).
http://superuser.com/edit-tag-wiki/553 sends an HTTP 302 Found reply to redirect to the tag wiki page /tags/pdf/info. I don't think there's anything we can do to analyze this further.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/534.53.11 (KHTML, like Gecko) Version/5.1.3 Safari/534.53.10
Well seeing that you don't have the improve option, you have few options
Leave it as it is, someone else from the edit queue would pick it up
Accept the suggested edit & add an edit to fix the wrong part
Guidance for one facet, possibly a bullet in the wiki:
For questions about the operating system or any PC application hosted on AWS, post here on Super User (or any site on which the question's subject matter would be on topic for a PC).
Since posting analysis in the comments is difficult, I declare this community wiki to be used for sharing our findings!
Normal tag wiki:
<form class="form-submit" action="#" method="get">
<input type="button" onclick="window.location.href='/edit-tag-wiki/702'"
value="Edit Tag Wiki">
It's always handy to have a go-to Community FAQ / Community Wiki question in case another "Alternative to …" / "Recommend me …" question shows up. The problem is that:
We won't be able to create one for every possible application or tag
We're essentially creating the kind of Q&A posts we do not want
The FAQ is still very unclear about software ...
I wouldn't worry about how many undefined tags we have - instead focus on making sure that the top-used tags* (tags covering ~90% of questions) have tag wikis (and excerpts) that are meaningful and describe not only what the tag represents, but when the tag should be used as well.
Of course, if you're in the mood and feel like creating some lesser-used tag ...