Skip to main content
Tweeted twitter.com/#!/ServerFault/status/102535697143046145
added 1311 characters in body
Source Link
Wesley
  • 33k
  • 23
  • 37

I propose be the official base tagI propose be the official base tag for the product line. and should be merged into . "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. ("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 and if they do, it can be retagged. Thoughts?

The new proposal for the product line. and should be merged into . "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. 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 should be merged with . , while not existing yet, could just as 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 and and possibly include and . Thoughts?

There will be tagging a question about a small server for their business withno "base tag" of 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 should be merged with tag isn't pertinent. , while not existing yetAlthough, could just asin SBS 2003 it was very pertinent 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 and and possibly include and or not which could significantly change things). Thoughts?

  1. Merge and, and into . We'd have to be careful for the questions tagged that don't have anything to do with the Microsoft product.
  2. Change into
  3. Merge intoand into .
  4. Merge into
  5. Change into

EDIT 1:

Okay, as Womble pointed out isn't the best tag for the product. ChrisS points out that is the traditional tag format, so the new SBS tag should likely be . I've updated the action list above to reflect this.

Can tags be "auto-forwarded" so that the is blocked and substituted with ?

I propose be the official base tag for the product line. and should be merged into . "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. ("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 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 the acronym "SBS" in the version specific tags. I propose that the nomenclature be SBS-[year]-[additional features]. So should be merged with . , while not existing yet, could just as 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 and and possibly include and . Thoughts?

  1. Merge and into .
  2. Merge into .
  3. Merge into

I propose be the official base tag for the product line. and should be merged into . "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. ("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 and if they do, it can be retagged. Thoughts?

The new proposal for the generic SBS tag is as per womble's answer below.

Version Specific Tags

Either 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 should be merged with . , while not existing yet, could just as 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 and and possibly include and . Thoughts?

There will be no "base tag" of - all tags will have the acronym "SBS" and the year. Perhaps having "Standard" and "Premium" in the tag isn't pertinent. Although, in SBS 2003 it was very pertinent (it was the difference between is you had ISA Server or not which could significantly change things).

  1. Merge , and into . We'd have to be careful for the questions tagged that don't have anything to do with the Microsoft product.
  2. Change into
  3. Merge and into .
  4. Merge into
  5. Change into

EDIT 1:

Okay, as Womble pointed out isn't the best tag for the product. ChrisS points out that is the traditional tag format, so the new SBS tag should likely be . I've updated the action list above to reflect this.

Can tags be "auto-forwarded" so that the is blocked and substituted with ?

deleted 17 characters in body
Source Link
Jeff Atwood
  • 13.3k
  • 18
  • 26

Here is a list for Microsoft Small Business Server tags that do not mention version number:

Here is a list of all SBS tags that I can find which are version specific:

Let's come to an official conclusion about how to name these tags.

Generic SBS tag:

Generic SBS tag

I propose be the official base tag for the product line. and should be merged into . "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. ("Microsoft" is too broad of a keyword and doesn't seem helpful).

I propose be the official base tag for the product line. and should be merged into . "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. ("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 and if they do, it can be retagged. Thoughts?

Version Specific Tags:

Version Specific Tags

Either 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 should be merged with . , while not existing yet, could just as 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 and and possibly include and . Thoughts?

Summary:

Summary

Assuming what I laid out above is accepted, here is the course of action:

  1. Merge and into .
  2. Merge into .
  3. Merge into

Here is a list for Microsoft Small Business Server tags that do not mention version number:

Here is a list of all SBS tags that I can find which are version specific:

Let's come to an official conclusion about how to name these tags.

Generic SBS tag:

I propose be the official base tag for the product line. and should be merged into . "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. ("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 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 the acronym "SBS" in the version specific tags. I propose that the nomenclature be SBS-[year]-[additional features]. So should be merged with . , while not existing yet, could just as 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 and and possibly include and . Thoughts?

Summary:

Assuming what I laid out above is accepted, here is the course of action:

  1. Merge and into .
  2. Merge into .
  3. Merge into

Here is a list for Microsoft Small Business Server tags that do not mention version number:

Here is a list of all SBS tags that I can find which are version specific:

Let's come to an official conclusion about how to name these tags.

Generic SBS tag

I propose be the official base tag for the product line. and should be merged into . "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. ("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 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 the acronym "SBS" in the version specific tags. I propose that the nomenclature be SBS-[year]-[additional features]. So should be merged with . , while not existing yet, could just as 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 and and possibly include and . Thoughts?

Summary

Assuming what I laid out above is accepted, here is the course of action:

  1. Merge and into .
  2. Merge into .
  3. Merge into
Changed title to make more sense
Link
Wesley
  • 33k
  • 23
  • 37

Tag merge request for root small-business-serverMicrosoft Windows Small Business Server tags

Source Link
Wesley
  • 33k
  • 23
  • 37
Loading