[Update] Approve "New Tag Requirements"

[AdultSun]

Needs official approval:
https://guidelines.stashdb.org/docs/tags/creating-tags/#new-tag-requirements

This section explains the rationale I've used for deciding if a new tag addition is appropriate, whether the tag would be helpful enough to be worth adding at all. It acknowledges that these determinations are subjective but that subjectivity is unavoidable when managing tags.

What this section does not cover is whether certain fields need to be filled out for a new tag request to be approved. Meaning, do we require a description and/or category for all new tags? And should that requirement be coded into Stash-Box/StashDB somehow? There was a discussion not too long ago about at least requiring a description for new tags. Personally, nearly any description would be enough for me. Just something to explain what the intended usage for the tag is, specific language and formatting can always be updated later. And if I'm the one doing the updating, it's always easier for me to "correct" an existing description than it is to come up with a completely new one by myself. I feel like this should probably be covered in a separate section of the guidelines though, so it may be appropriate to make a new issue covering these kinds of questions.

[PhuriousGeorge]

"Require" is a tough word to use in Guidelines (If it's truly a requirement it should be system-validated, not voter as you stated)

Back on point, my personal preference is to Require a description (ie: Brown Hair (Female) is blatantly obvious, but easy enough to fill-in a description). Category is preferred, but I personally don't push back if missing and honestly forget they exist at times since the majority of my work is in the app itself with spurts of reviews. Would be a dream to have the features in both tools aligned.