First off I should say I'm ignoring the following meta tags: beginner, homework, reinventing-the-wheel, and most with less than 100 views.

A short overview of the discussions around these tags is outlined below:

1. Tag synonyms (optimize -> optimization)

   We synonymized optimize -> optimization.

2. status-completed - Tags for [optimization], [performance], [speed]

   This came about as there was a synonym request between performance and optimization. We merged speed and performance. However it was raised that optimization should instead be three tags; speed-optimization, memory-optimization and code-size-optimization. Only the last tag seemed to have disagreement.

3. status-planned - Should we just put an end to [optimization]?

   This suggested removing the optimization altogether, in favor of other tags. Such as algorithm and performance.

   Again splitting this tag into three x-optimization tags was suggested, heavily upvoted and seems to be the plan.

4. [tag:optimization] was made a synonym of [tag:performance]

5. Optimizing [performance]

   This requested that optimization be merged with performance. But we don't think we should yet. It also seems like we know there are issues with this tag, but don't know how to deal with them.

6. Time limit exceeded and performance: what's the difference?

   We agree that these are not the same tag, and so shouldn't be synonymized or merged.

7. Would burninating [performance] bring good performance?

   Where we came to the conclusion that it's a useful tag. And points to three ways to optimize the code; performance, memory usage and readability.

And so we now have the tags: performance, optimization, time-limit-exceeded, complexity, memory-optimization and cyclomatic-complexity. I'm not sure if algorithm fits in this too.

And so I'd like to request we do the following:

1. Normalize the naming of the tags. This sets a clear naming scheme to follow when adding similar tags. And also helps users find the correct tag when searching for 'optimization'.

   • performance -> speed-optimization
     Additional synonyms performance-optimization
   • complexity -> complexity-optimization
   • cyclomatic-complexity -> cyclomatic-complexity-optimization
   • Should we rename time-limit-exceeded?
   • Should we rename algorithm?

2. Should we add more of these tags?

   • code-size-optimization
   • readability-optimization

3. How should we deal with optimization?

First off I should say I'm ignoring the following meta tags: beginner, homework, reinventing-the-wheel, and most with less than 100 views.

A short overview of the discussions around these tags is outlined below:

1. Tag synonyms (optimize -> optimization)

   We synonymized optimize -> optimization.

2. status-completed - Tags for [optimization], [performance], [speed]

   This came about as there was a synonym request between performance and optimization. We merged speed and performance. However it was raised that optimization should instead be three tags; speed-optimization, memory-optimization and code-size-optimization. Only the last tag seemed to have disagreement.

3. status-planned - Should we just put an end to [optimization]?

   This suggested removing the optimization altogether, in favor of other tags. Such as algorithm and performance.

   Again splitting this tag into three x-optimization tags was suggested, heavily upvoted and seems to be the plan.

4. [tag:optimization] was made a synonym of [tag:performance]

5. Optimizing [performance]

   This requested that optimization be merged with performance. But we don't think we should yet. It also seems like we know there are issues with this tag, but don't know how to deal with them.

6. Time limit exceeded and performance: what's the difference?

   We agree that these are not the same tag, and so shouldn't be synonymized or merged.

7. Would burninating [performance] bring good performance?

   Where we came to the conclusion that it's a useful tag. And points to three ways to optimize the code; performance, memory usage and readability.

And so we now have the tags: performance, optimization, time-limit-exceeded, complexity, memory-optimization and cyclomatic-complexity. I'm not sure if algorithm fits in this too.

And so I'd like to request we do the following:

1. Normalize the naming of the tags. This sets a clear naming scheme to follow when adding similar tags. And also helps users find the correct tag when searching for 'optimization'.

   • performance -> speed-optimization
     Additional synonyms performance-optimization
   • complexity -> complexity-optimization
   • cyclomatic-complexity -> cyclomatic-complexity-optimization
   • memory-optimization: no change
   • Should we rename time-limit-exceeded?
   • Should we rename algorithm?

2. Should we add more of these tags?

   • code-size-optimization
   • readability-optimization

3. How should we deal with optimization?

First off I should say I'm ignoring the following meta tags: beginner, homework, reinventing-the-wheel, and most with less than 100 views.

A short overview of the discussions around these tags is outlined below:

1. Tag synonyms (optimize -> optimization)

   We synonymized optimize -> optimization.

2. status-compleate - Tags for [optimization], [performance], [speed]

   This came about as there was a synonym request between performance and optimization. We merged speed and performance. However it was raised that optimization should instead be three tags; speed-optimization, memory-optimization and code-size-optimization. Only the last tag seemed to have disagreement.

3. status-planned - Should we just put an end to [optimization]?

   This suggested removing the optimization altogether, in favor of other tags. Such as algorithm and performance.

   Again splitting this tag into three x-optimization tags was suggested, heavily upvoted and seems to be the plan.

4. [tag:optimization] was made a synonym of [tag:performance]

5. Optimizing [performance]

   This requested that optimization be merged with performance. But we don't think we should yet. It also seems like we know there are issues with this tag, but don't know how to deal with them.

6. Time limit exceeded and performance: what's the difference?

   We agree that these are not the same tag, and so shouldn't be synonymized or merged.

7. Would burninating [performance] bring good performance?

   Where we came to the conclusion that it's a useful tag. And points to three ways to optimize the code; performance, memory usage and readability.

And so we now have the tags: performance, optimization, time-limit-exceeded, complexity, memory-optimization and cyclomatic-complexity. I'm not sure if algorithm fits in this too.

And so I'd like to request we do the following:

1. Normalize the naming of the tags. This sets a clear naming scheme to follow when adding similar tags. And also helps users find the correct tag when searching for 'optimization'.

   • performance -> speed-optimization
     Additional synonyms performance-optimization
   • complexity -> complexity-optimization
   • cyclomatic-complexity -> cyclomatic-complexity-optimization
   • Should we rename time-limit-exceeded?
   • Should we rename algorithm?

2. Should we add more of these tags?

   • code-size-optimization
   • readability-optimization

3. How should we deal with optimization?

First off I should say I'm ignoring the following meta tags: beginner, homework, reinventing-the-wheel, and most with less than 100 views.

A short overview of the discussions around these tags is outlined below:

1. Tag synonyms (optimize -> optimization)

   We synonymized optimize -> optimization.

2. status-completed - Tags for [optimization], [performance], [speed]

   This came about as there was a synonym request between performance and optimization. We merged speed and performance. However it was raised that optimization should instead be three tags; speed-optimization, memory-optimization and code-size-optimization. Only the last tag seemed to have disagreement.

3. status-planned - Should we just put an end to [optimization]?

   This suggested removing the optimization altogether, in favor of other tags. Such as algorithm and performance.

   Again splitting this tag into three x-optimization tags was suggested, heavily upvoted and seems to be the plan.

4. [tag:optimization] was made a synonym of [tag:performance]

5. Optimizing [performance]

   This requested that optimization be merged with performance. But we don't think we should yet. It also seems like we know there are issues with this tag, but don't know how to deal with them.

6. Time limit exceeded and performance: what's the difference?

   We agree that these are not the same tag, and so shouldn't be synonymized or merged.

7. Would burninating [performance] bring good performance?

   Where we came to the conclusion that it's a useful tag. And points to three ways to optimize the code; performance, memory usage and readability.

And so we now have the tags: performance, optimization, time-limit-exceeded, complexity, memory-optimization and cyclomatic-complexity. I'm not sure if algorithm fits in this too.

And so I'd like to request we do the following:

1. Normalize the naming of the tags. This sets a clear naming scheme to follow when adding similar tags. And also helps users find the correct tag when searching for 'optimization'.

   • performance -> speed-optimization
     Additional synonyms performance-optimization
   • complexity -> complexity-optimization
   • cyclomatic-complexity -> cyclomatic-complexity-optimization
   • Should we rename time-limit-exceeded?
   • Should we rename algorithm?

2. Should we add more of these tags?

   • code-size-optimization
   • readability-optimization

3. How should we deal with optimization?