Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Yes, but with some notes I think this a good idea, but we will need to provide more details and agree on some details. A tag must be named appropriately, considering Tag naming guidelines. ...
Answer
#1: Initial revision
by
Alexei
·
2023-08-18T06:42:54Z (about 1 year ago)
## Yes, but with some notes I think this a good idea, but we will need to provide more details and agree on some details. > 1. A tag must be named appropriately, considering Tag naming guidelines. I have mixed feelings about using uppercase in the tag names. I am inclined to switch to using the original naming (e.g. all uppercase for acronyms), but this goes against the reflex created by communities such as SE ones. This is also supported by Codidact tagging search functionality (when editing the post) which is case-insensitive. > 2. A tag must be on-topic, meaning it has to be related to Software Development. > 3. A tag must be unambiguous in the context of Software Development. It should not mean two very different things at once. This is clear to me. > 4. A tag must add at least some meaningful information regarding what the question is about. This requires more details and I guess it is tightly related to [Deciding if a concept can be materialized to a tag](https://software.codidact.com/posts/287635) meta question which needs more feedback from the community. > 5. A tag should not be too localized/specialized, but about some well-known term in Software Development. If it is unlikely that other posts will ever use the tag, it is too localized. This is also clear and I think we should adopt it.