Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

This morning, Ondra Žižka retagged 209 questions from to .

While the retag was thorough and may be justified*, it creates a problem. Every other versioned JBoss tag has been left alone, including:

There was already an inconsistency between the wording in the various version-specific tags, but adding another variation doesn't help. Consistency is good.

  • If one of the tags is going to be -as-'d, then the rest should as well.
  • The 5.x and 6.x tags should be hyphenated for consistency regardless.
  • We can probably merge 4.0.x, 4.2.x and 4.3.x. I'm not sure why there's no 4.1.x.

While this is being thought about, it may be wise to revisit the tag. The product name has always been "JBoss Application Server." Common colloquial use of "JBoss" alone has almost always been in reference to the application server. However, JBoss was a company (now a division of Red Hat) and offered many products. It is possibly inappropriate to continue the use of due to the potential confusion it can create between the multitude of JBoss-related projects. However, I expect that any of these tag renames are going to create needless confusion. Users don't tend to care about product names that include a company name and some entirely uncreative words. See also, Zend vs Zend Framework.

* The retagging seems to have been spawned by a content dispute last month, where he deemed the existing tag to be inaccurate, despite colloquial use and tag wikis disagreeing.

share|improve this question
This should be done through synonyms, if at all. Hopefully the user is suspended. – Matthew Read Feb 19 '12 at 22:31
I disagree about a suspension. The user may not be aware that it should be wise to gain consensus before making such large batches of edits. I do agree that synonyms may be a good solution here. – Charles Feb 19 '12 at 22:35
After the content dispute? The user's attitude seems to be that they'll foist it upon everyone, unwilling or not. Regardless of their knowledge of process, that should be obviously unacceptable. – Matthew Read Feb 19 '12 at 23:12
I believe moderators can undo massive retaggings like this? I think that's the appropriate course of action here. If anything is done, a synonym should be created like @Matthew suggests. – Cody Gray Feb 20 '12 at 2:05
Retagging took me about 15 minutes, no big deal. If you really intend to move it back, I can do it. – Ondra Žižka Feb 21 '12 at 7:01
up vote 3 down vote accepted

The synonym has been created, with being the master of .

share|improve this answer

We can probably merge 4.0.x, 4.2.x and 4.3.x

I disagree with that one. For reasons known only to RedHat, there are very substantial differences between those versions. Advice for one has a very good chance of being inapplicable for the other. Their version numbering at the time was an inconsistent shambles. They sorted it out by the time 5.x came along, though.

I'm not sure why there's no 4.1.x.

Because there was no JBoss AS 4.1. See above comment re: shambles.

share|improve this answer

The reason why "JBoss" was commonly used for the app server is that that was the only project.

Nowadays, JBoss is a brand, a community, or a project supporting group, like is Apache, Codehaus, SourceForge. With over 60 projects, see .

Would you argue for keeping tags:

  • Apache-5.5.x (for ActiveMQ) ?
  • Codehaus-2.x (for Sonar) ?
  • SourceForge-1.1.x (for JDom) ?

No, you would not. This is the same.

StackOverflow has an influence on user's perception of the naming conventions. Why not leveraging that to make the naming habits right? Let's promote the right naming through using jboss-as* tags.

share|improve this answer
Okay, sure. But the proper way to do this would be by creating a tag synonym and mapping all of the existing tags to a new master tag with the correct name. Manually retagging each question is not only a waste of everyone's time, but it comes with other side effects (like "bumping" all the old questions up to the top of the list), and it doesn't prevent the old (incorrectly-named) tags from continuing to be used. – Cody Gray Feb 21 '12 at 5:03
I fully agree with that. – Ondra Žižka Feb 21 '12 at 5:15

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .