I propose small-business-server be the official base tagI propose small-business-server be the official base tag for the product line. sbs and sbs-server should be merged into small-business-server. "Microsoft" and "Windows" don't need to be in the tag. It is better served if that is a separate tag in the question, e.g. windows small-business-server ("Microsoft" is too broad of a keyword and doesn't seem helpful).
Certainly, the words "small business server" can mean something other than the Microsoft Windows Small Business Server product, but I doubt too many people are going to be tagging a question about a small server for their business with small-business-server and if they do, it can be retagged. Thoughts?
The new proposal for the product line. sbs and sbs-server should be merged into small-business-server. "Microsoft" and "Windows" don't need to be in thegeneric SBS tag. It is better served if that is a separate tag in the question, e.g. windows small-business-serverwindows-sbs-yyyy-feature as per ("Microsoft" is too broad of a keyword and doesn't seem helpful)womble's answer below.
Version Specific Tags
Certainly, the words "small business server" can mean something other than the Microsoft Windows Small Business Server product, but I doubt too many people are going toEither we petition for the tag length limit to be increased or we use the acronym "SBS" in the version specific tags. I propose that the nomenclature be SBS-[year]-[additional features]. So sbs2003 should be merged with sbs-2003. sbs-2011-essentials, while not existing yet, could just as sbs-2011-premium may exist as well.
That means that a post about the Exchange instance running on a Small Business Server 2008 machine would most logically be tagged with exchange-2007 and sbs-2008 and possibly include small-business-server and windows. Thoughts?
There will be tagging a question about a small server for their business withno "base tag" of small-business-server and if they do, it can be retagged. Thoughts?
Version Specific Tags
Either we petition for the tag length limit to be increased or we use- all tags will have the acronym "SBS" inand the version specific tagsyear. I propose thatPerhaps having "Standard" and "Premium" in the nomenclature be SBS-[year]-[additional features]. So sbs2003 should be merged with sbs-2003tag isn't pertinent. sbs-2011-essentials, while not existing yetAlthough, could just asin SBS 2003 it was very pertinent sbs-2011-premium may exist as well.
That means that a post about(it was the Exchange instance running on a Small Businessdifference between is you had ISA Server 2008 machine would most logically be tagged with exchange-2007 and sbs-2008 and possibly include small-business-server and windowsor not which could significantly change things). Thoughts?
- Merge sbs and, sbs-server and small-business-server into windows-sbs. We'd have to be careful for the questions tagged small-business-server that don't have anything to do with the Microsoft product.
- Change sbs-2000 into windows-sbs-2000
- Merge sbs2003 intoand sbs-2003 into windows-sbs-2003.
- Merge sbs-2008 into windows-sbs-2008
- Change sbs-2011 into sbs-2008windows-sbs-2011
EDIT 1:
Okay, as Womble pointed out small-business-server isn't the best tag for the product. ChrisS points out that windows-server-yyyy is the traditional tag format, so the new SBS tag should likely be windows-sbs-yyyy-feature. I've updated the action list above to reflect this.
Can tags be "auto-forwarded" so that the small-business-server is blocked and substituted with windows-sbs?