Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
Automatically collect new tags for review As Codidact communities grow, I can see a need to transition smoothly from the norms of a "new" site to those with open, wide participation. Initially, pe...
Answer
#1: Initial revision
## Automatically collect new tags for review As Codidact communities grow, I can see a need to transition smoothly from the norms of a "new" site to those with open, wide participation. Initially, people should be trusted to create new tags, but eventually there will be a need to nip them in the bud. What I envision is a system whereby - rather than directly obstructing tag creation - whenever the first question is asked in a new tag (i.e., the person asking the question is creating a tag, by applying it to the question), the site *highlights* this fact: * By offering a filter on the Tags tab for tags *with exactly one question*. Then everyone can, at a minimum, propose an edit to remove the tag (or maybe fix its spelling or something); curators can just remove it. (The system should also automatically prune tags that have *zero* questions, unless usage information or a wiki exists; [currently, that doesn't appear to happen](https://meta.codidact.com/categories/3/tags/996)). * Possibly, by allowing users with the Curate ability to *opt in to notifications* about newly-created tags. * Possibly, by automatically generating a corresponding *post in the site's Meta* to discuss the proposed tag. IMO, if sites *still* get to the point where excessive tag creation is a problem, *then* we can talk about a separate "Create Tag" ability. ## Blacklisting and synonymization Regardless of the above, we are still going to want the abilities to * Explicitly list tags that may not be (re-)created (Moderators and perhaps Curators should be able to input these manually, and also have a convenient option to add them when removing a new tag) * Automatically transform tags into a canonical form (this information could be stored in the same place - i.e., have a mapping from the "bad" tag name to a "canonical" name, and simply omit the latter in order to prevent a tag from being used).