I’ve seen that there is fletcher, cetz, lilaq, touying, but some other used packages don’t have a tag (#subpar, #suiji, etc.). I can add a new tag, which might be only because of TL2. IMO, it’s better to have more tags, because they are more useful than plain text search. I’m not sure if any mention of a specific package will show the post in the search, but a tag will reduce the false positives for sure.
I think these new tags are reasonable. Feel free to create them when they come up, but we should probably limit ourselves to packages that are actually in broad use. Not every question concerning a specific package or template needs to be tagged, if the package is relatively obscure.
Re subpar: it’s currently unmaintained: Looking for a maintainer: subpar not sure if that should influence whether we create a tag.
I mean, I guess the experience is the guide. Otherwise, it’s pretty hard to know which one is used plenty or not.
I think that if it works and popular, then it doesn’t matter. If it breaks, then it just won’t be recommended in the future. But the key with tags is easy discovery, which doesn’t necessary relate to the state of a package.
I’m just saying, we don’t need to tag the very first question where a package comes up. And of course not all questions mentioning a package are really about that package. With templates I think it’s fairly pronounced. The issue is often customizability, and then templates is more useful than a specific tag.
Yeah agreed. Questions come in independently from maintenance status.
I think that since usually tags are added after the issue is resolved or when you can clearly see what it’s about, then it’s pretty clear what tag can be added. Though I think that a new one should be added after a solution is selected, in case it’s not clear from the start. If the question is about a package or if a package is used in a solution, then it should be added. A simple reference to a package that is not used in either place should be skipped.
1 Like