I've started looking at the first few tags that people are using, and I think that we should keep a close eye on this. Here's a few tags that I propose to "erase" or modify:
- embedded-schema: delete, there is already a schema tag.
delete, too generic. To discuss whether we should have "<module>-configuration" tagsEDIT As mentioned in Glenn's answer, we'll keep this one but it should never be used by itself. Use cmeconfiguration and not configuration by itself.
- deployment: delete, too generic. Deployment may mean a lot of different things in Tridion, and none of the things that comes to my mind means the same that the poster had in mind
- polling: delete. Only used by Transport, right?
- long-running: delete.
- extension-model: too generic. Everything in Tridion can be extended, and the model will be different depending on what you are extending. If we must identify that something is an extension, then I propose to use "extensions" instead of "extension-model"
- communicator: I didn't even know of the communicator until about 2 months ago, as it is a (rather important) small part of the CME. I'm not sure if there's enough volume of communicator issues or questions to justify its own tag, I'd rather use cme instead.
rename to core-service? Or maybe question is specific to how WCF does something rather than the Tridion Core Service?Makes sense to keep wcf for questions that are WCF-related. CoreService != WCF.
- customurls: rename to custom-url?
- external-integrations: is the word "external" required? Doesn't integrations already implies it is with something else than Tridion?
- custom-events: rename to event-system?
Opinions? Leave them below as an answer.
In addition: would we be allowed to copy the definitions for a common tag (for instance xml) from StackOverflow?