We have moved to a new Sailfish OS Forum. Please start new discussions there.

On what basis are new tags granted in t.j.c.? [answered]

asked 2015-05-08 19:35:24 +0300

Jolly-Jo gravatar image

updated 2015-05-09 01:29:26 +0300

ssahla gravatar image

Quite a long time ago, I noticed that my alarms vanished sometimes (rarely, luckily). Some time later I discovered that it was timed-qt5 which did not repond anything on dbus anymore and that that was the reason for the alarms 'vanishing'.

Having discovered that, I updated my question's / bug report's description accordingly and tried to add new tags 'timed' and 'timed-qt5' to it. When adding them, I was informed that the new tags would have to be approved first. Some time later, the new tags were gone, i.e. they apparently hadn't been approved. In order to make sure this disapproval hadn't happened by mistake, I repeated the process, and even updated the question headline to mention 'timed', but with the same outcome: The tags had been removed.

So here's my question: If a problem is really totally completely obviously caused by timed-qt5 breaking, why the heck don't t.j.c. moderators accept the tag 'timed' or 'timed-qt5' for that bug report? On what basis are new tags granted?

PS: Just for comparison, the 'timedclient-qt5' tag does exist!

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by Jolly-Jo
close date 2015-05-12 14:59:17.287179


I didn't know new tags have to be approved. Just to test, I tagged this ”timed”. No error message, but the tag didn't stick either... It just says updated by me...

ssahla ( 2015-05-09 01:42:40 +0300 )edit

I noticed the same and only once the new tag got proved and set. IMO it would be important getting more guidance and feedback by admins and moderators, at least in what alternative tag to use instead of the proposed. Suggesting a new tag is completely deliberate and not out of arbitrariness in propably all cases, and the intention to do so is because the requester wants to contribute to easier searchability.

lakutalo ( 2015-05-10 22:26:02 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2015-05-11 11:12:37 +0300

eric gravatar image

Tags are approved based on their relevancy and their potential to be re-used by others when creating posts. We currently have more than 3100 tags active, and a vast majority are one shots. I usually do not add any new entry, and regularly clean the single entries as some are either too specific or cryptic for most users...

edit flag offensive delete publish link more


I know this can be cumbersome. Do you keep tag proposals in evidence? Maybe it could be of help for the requester to get feedback on his/her proposals via yellow notification bar on top of the page. Would that be possible?

lakutalo ( 2015-05-11 12:14:23 +0300 )edit

@lakutalo: Tag proposals are only visible to admins/moderators and once rejected, dropped from the database. Askbot doesn't offer such functionality (though you might create a feature request upstream) and we do not have any time currently to add a dedicated notification for tag approval/rejection...

eric ( 2015-05-11 15:31:28 +0300 )edit

@eric: So what exactly would be the disadvantage of having, say, 10,000 tags as opposed to 3,100? What would work less well or whose life would be harder? And I don't take "the db server admin's" as an answer...

Jolly-Jo ( 2015-05-11 17:01:41 +0300 )edit

@Jolly-Jo having 15 tags for each topic where only one is needed removes any usability of tags, 2k tags being a oneshot has the same result as just mentioning it in the title or text as you wont search for it by tag. We already had tags like storejolla-storestore-app where people do not know which one to use so they use all of them, as there are only that much stores available, you could just remove any app specific tag and tag all of them store otoh people look for play and not for store so it doesn't get more useless to discuss the need of 10k tags. If every store has its own tag, there is no need for the store tag, otoh why does every store need its own tag anyway? Not every library needs its own tag as tagging with bug and the app in use is enough for Jolla to find your report and probably some will never get reused, in the question itself you can go in detail. Was that enough "the db server admin's"? It is just not a good idea to always use question titles as tags... tagging needs to be a grouping feature not another form of title. To be efficient they need to be clean and on the point $type$functionality$app$system-protocol$service

chemist ( 2015-05-11 17:40:13 +0300 )edit

@Jolly-Jo: As I stated before, many of the existing tags are one-shots, having a huge amount of them defeats the purpose of tagging. The moderation and clean-up are attempts at keeping the tag list short and relevant. Have a look at the tags page and scan through...

eric ( 2015-05-11 17:41:57 +0300 )edit

Question tools

1 follower


Asked: 2015-05-08 19:35:24 +0300

Seen: 220 times

Last updated: May 11 '15