Creating tags is a privilege that comes with 150 rep.
We have found, through experience, that an explosion of tags is a bad thing on Code Review. Just because you can create a tag, does not mean you should.
Creating tags should be done with significant fore-thought, and probably discussion too:
- Code Review has a number of existing tags
- a number of tags have a history of mergers, burninations, and other murky activities
- tags on Code Review are not necessarily used the same way as they are on other sites (specifically Stack Overflow).
Are you fully aware of what they are, why the tags are like they are?
The answer Simon gave you included a link to the Privileges help page. Part of that page contains:
Most common tags already exist on a mature site. You should always favor existing tags; only create new tags when you feel you can make a strong case that your question does cover a new topic that nobody else has asked about before on this site.
Are we at the point where we have to ask you to make your (strong) case for your tag creation?
You have been in the process of creating multiple tags, close to a dozen, in the past few days. Many of the tags you have created are not appropriate, or have previous discussions on Meta. Some of them are good, though, so, this is not all bad.
map was a bad tag to create, there is already hash-map, and map could mean other things to other people. At a minimum, you should have consulted with Meta (asked a question here) before creating that tag. There are many requests like this... in fact, there is a tag on Meta, for discussion around tags: tags.
upload is also a bad tag. What language is upload? What purpose does it serve?
Ask yourself, who would follow this tag, if I create it? How does it add value to the whole community? Does the new tag add more value than the cost of diluting existing tags?
There is a fine balance between creating tags that help organize the site, and allow people to find what they are looking for, and follow the things important to them.
Please slow down and be more communicative before adding tags.
Now, time for me to head off, and follow in your footsteps, cleaning up some mess.
- playframework is just mvc in a specific language
- anorm is a subset of data access abstraction. Not sure that it should be tagged at all. It is implied any time you have SQL in code.
- connection is .... nothing special. There's already socket, and others.
- upload is discussed already.
- nio is a subset of io
In general, language tags are good, but specific features of languages are bad, unless those features relate to broad concepts, like MVC, OOP, etc. so there are 'concept tags' that, when combined with the language, are useful...
If you think you can provide a good case for and of the above tags, I will be happy to discuss here in Meta. I may have been over-zealous in the clean out.... these things happen.
Also, remember, we are always avaialble in the 2nd Monitor chat room if you want to discuss things.
To create a tag, you edit an existing question that you think could use the tag and add the tag to the taglist at the bottom, or add the tag when creating a new question.
It is not possible to create a tag without attaching it to a question.
For more information see Privileges - Create Tags.
Note that only users with at least 150 reputation can do this.