Specificity is useful. Over-specificity is probably irrelevant. If the version matters, maybe we should clarify the use of the umbrella tag, or burninate it.

For the people like me who hadn't heard about burninate... What does it mean to “burninate” a tag? :)

Summonning @Sarov , @tiagoperes, @GoncaloPeres, @MarkC.Wallace

Hello CG!

just pinged the people that was involved on these ms project tagging lately to hear from them

as I saw a few more tagging done today

I am trying to help the community the best I can. When I am on my mobile phone and I have some time, in order to make sure the posts are easier to find, I always try to categorize them better

By that, I update errors in tags, add relevant tags,...

I am not creating irrelevant tags. Just using tags already in the community.

In this particular case, there are always differences in software, that's why I have considered useful specifying the version

I also agree that it's useful (reading wise) to have them tagged... my concern is that by approving them all, all these questions goes up on the "newest" question queues

it may be silly, and if that's the case then we'll just continue mass tagging / approving them

The tag itself makes sense to be applied to the questions that it was proposed to.

I understand the claim though

In one side the community becomes more structured, it's easier to find questions and answers related to tags (which is something I fancy because then I can follow certain tags and they will show up on my feed and I'm able to act upon them - read, improve, answer, raise new questions)

On the other side, the recent posts become kind of hidden as those take place on the main feed

I wonder if there's a place these edits can go to instead of occupying the main feed right away

This might require improvements in the sorting mechanism the community provides as this will be an action I don't see being reduced throughout time unless people become forbidden of doing which then can make the community become a nonsense

Why nonsense? Because parent tags, such as ms-project, wouldn't have space together with sons, ms-project-2017. If I'm someone aiming to improve in ms-project in general, sad I would be missing on ms-project-2017 just because I would need to search specifically for that tag... what if I missed on other children? Eish I would have to check them all again one by one, etc etc

From that POV removing that tag would be wise. But this implies there's space for more tags to become burninated or people to be removed from this community

removed for wanting to lose less time going through posts of their interest

I kind of agree with @ToddA.Jacobs . Let's say the problem we are going through is specific to ms-project-2019. In this case makes sense to refer ms-project-2017. But I'm not seeing this type of events happening often. Ofc one has to think about the people tagging ms-project-2017 in their questions when they don't make sense. This will require oftentimes edit to remove that tag

Drupal answers does it well by specifying in the tag where can the tag can be applied to. Ex: 6 , 7 , 8 (numbers standing for drupal versions)

If one edits and adds a 7 just because one is using drupal version 7, the edit is rejected because in the description of the tag it tells specifically when to use, when the version is really important

Apologies on some mistakes the text has, I'm writing from a really tiny textarea as I write this from the phone