Cleaning up together - please join

Thanks for your contribution, merging done.

IMHO I prefer the "theotherhalf" since some people new to this forum might be a bit unfamiliar with "toh"

I also prefer to prevent abbreviations if possible. Because everyone which is new to the community does not understand them.

I'd prefer theotherhalf as well.

I agree with theotherhalf, too.

Thanks! toh entry deleted, please adjust to theotherhalf tag if you spot more...

Harbour should probably still be a separate tag (that's where the developers add their apps). Maybe keep/swap it to dev-harbour?

I vote for a removal/merging of appstore, and think jollastore (or, preferably, Jolla-Store, or jolla-store) would be the best, even though store is used more, as that would make it clear that it's none of the other app stores.

Agreed. Almost all harbour tagged questions refer to the dev-part of the store as far as I can see. Didn't check carefully enough before. Sorry for that. Will edit answer above.

+1 for jolla-store, to be expanded later (if needed) with yandex-store and possible other xxxxx-store's

I suggest, putting "store" at the front, i.e. store-jolla, store-yandex etc.

By the way, tags are lower case only -- automatically converted to.

@jgr when adding tags, starting to write "sto..." makes suggestion like jolla-store to become visible. Iget your point, but via that there's no great risk for people adding wrong tags later. Starting with the name of the store might just be adopted easier by our new members.

@eric said he regularly cleans up tags in the back-end. I guess we have to wait for those events to happen for the tags to disappear.

@jgr@Mohjive: Thanks for bringing this up :) The entries are removed now...

Just use android for both. I see no value to differentiate between hw and sw, besides is it really clear that alien-dalvik is sw, and android is sw.. seems quite arficial separation.. So, just Android for anything not SailfishOS / native Jolla stuff..

It could become useful, when Sailfish OS runs on former android devices. Then maybe there is an issue with camera support of nexus or anything else and be referred to as "Android" hardware. On the other hand, libhybris would be the correct tag there anyway, wouldn't it?

Just a small question. Am I supposed to do this clean-up? I didn't dare to do anything because I thought the cleaning is done by moderators. I don't even know, if I am able to retag other users question with my "low" karma. If I am supposed to do it, I will do it of course. Am I correct, that "everybody" agrees to change alien-dalvik to android tags?

I have a little concern here. android is generally referring to apps whereas alien-dalvik is quite specific to the layer itself. I honestly believe they both can used and I don't see how they overlap. I wouldn't personally merge, as I see a need for granularity when we talk about Android in general...

When I go through the questions, I see a lot using both tags, some referring to android apps using only alien-dalvik as tag and some referring to android compatibility/layer specific problems but using android as tag. So, allthough I agree that they don't have to overlap and may used both, currently the questions are totally mixed up within those alternative tags (IMHO).

Just interested: On how many of these a tag phone has been used together with callrelated tags?

Why reverse the natural ordet?.Much better and more easy to use if they are outgoing-call, incoming-call and emergency-call. No need to introduce technical jargon to tags on purpose, and IMI the tags search and conpletion work fine irrespective of where in the string the matching part is.

@jjaone: Was a suggestion, because in the list of tags (on page "ALL" to the right) it would sort better. But since it is not supported with the other tags (e.g. shop), it should not be done here.

I'd also stick with the natural order, and keep all three jgr mentioned. I also added all the call- tags (currently in the back-end) to the answer.

I'd favour lock-screen, but I'd like to hear from English native speakers...

https://together.jolla.com/question/5465/how-to-naming-jolla-ui-screens-gestures-and-components/#post-id-17401: "lock screen" (with space), i.e. for a tag with dash: "lock-screen".

Lock screen as 'lock-screen', Home screen as 'home-screen', Launcher screen as.'launcher-screen' etc. What's there to discuss abt still?

I am sure a native speaker would agree with lock-screen instead of lockscreen. Besides there only two questions tagged with lockscreen and 47 with lock-screen. In other words, I have retagged those two. Oh... seems somebody beat me to it. The lockscreen tag can be removed from the backend.

@avdwoude: Thanks, done.

Hmm, this one is trickier IMHO. Would someone be kinf enough to go through the existing reports and adjust if needed? We currently have 17 tagged with feature and I suspect some might not be requests...

I prefer "feature-request". "feature" alone would be valid 90% of the questions in this forum as most of the questions refer to a specific feature that is already implemented or needs improvement or needs to be added.

agree with @jukey that "feature" alone is a bit confusing.

@jukey@TimTTK@jjaone and others: So anyone willing to go through and update? I'll remove the feature tag then :) Thanks!

I have some spare time. Starting to change all feature tags to feature-request tags now. --> DONE.

I've no idea what semantic difference of those tags here might be, but I've understood that for some questions or topics 'feature-request' might be too strong and specific to apply and that's why a more abstract wish/need/proposal can be tagged. I'd vote those to be tagged as 'suggestion'' from now on to differentiate from feature-requests. (or leave even that out so the type of question is then implied from not having any specific tag to identify it as such, i.e. an abstract idea)

You edited the Q after I commented it, so addendum: enhancement is wish to make something existing better thus not a feature-request and not suggesting it but expressing a need to improve something..

A very good list of candidates, thanks for contributing :) I see these as:

• feature-request = totally new feature, not existing in SailfishOS / app at all. Should be left.
• enhancement = making an existing feature better. Should be left.
• idea = quite free about it's content, both bigger and smaller changes. Should be left, as it's well adopted.
• Other tags mentioned in your answer could be changed to one of these three.

Concerning comments: sometimes comments don't even appear directly but only after some time. Making it even more difficult to answer. I got some mails with comments and had to reload 3 times to see the "real" answer... Back to topic: I think the three tags suggested from @simo (idea, feature-request, enhancement) are good. I'd even drop enhancement, because an enhancement is either a feature-request (if it is concrete) or an idea (if it is vague).

@naytsyrhc Enhancement is to improve existing functionality, not a request for more or a new one. And 'idea' isn't very good as tag at all, cause anything can be an idea. Even in this comment there is an idea. So lets keep a feature-request, enhancement and suggestion (or proposal) for three different kind of user needs or reqs. And 'bug' for reported or identified or suspected failure or erroneous behaviour of system or apps (i.e. an issue or a problem for which no solution exists or the root-cause is unknown).

I would change them in following manner:

• Use only alarm and drop alarm-setting & alarm-off.
• Change alarm-clock to clock, Alarm clock is part of Clock-application, after all.

List continued (damn comment length limitations):

• Leave alert as it is, as it may mean e.g. calendar alert which is bit different thing. Perhaps questions with this tag have to be checked, i.e. are they really about alarms or not.

@JiiHoo Just continue writing when comment length is exceeded. The "...characters left" is just an indicator to help you, but it will not block the comment. I have posted some comments that have more characters than allowed and posted with "-xxx characters left". Maybe this will change in the future, but for now it is working. (This comment also has -73 characters left.)

+1 for JiiHoo's suggestions.