Cleaning up together - please join

sailfish usually means SailfishOS, but porting is just a reference to making something to run on some other environment (hw/sw plarform)

You're right, for example I would tag android + porting.

yep just like that ;)

Because in tags, spaces should be replaced by dashes: "sailfish-os"

@jgr No, references to native platform should be tagged as 'sailfishos'.

it seems cover is also used to describe Jolla phone accessories...

@eric I found one, did you retag the others? I guess there should be another tag for cover as phone accessories.

Neo: no I didn't touch anything yet. We'd rather get an agreement first on merging appcover into activecover and create a relevant tag for the covers accessories. I hope we could find something better than cover-accesory for the purpose ;)

This is a tricky one...

Yes, IMO home-screen is the correct and preferred way to refer to Jolla UI Home screen. See: https://together.jolla.com/question/5465/how-to-naming-jolla-ui-screens-gestures-and-components/

Ping :) Who's picking this low hanging fruit? Let me know when done so I clean up the backend, thanks!

@eric done

ui = User Interface, gui= Graphical User Interface. These can be merged under ui, as the whole interface in the phone is graphical but ui is adopted better.

ux = User eXperience, and should be left as it is.

Ok, I understand that user-experience and user-interface are required. But I do not see the need to differentiate between "ui" and "gui" on a mainly graphical user interface.

Because I saw "ui" and "ux" synonymous (and will not be the only one), I suggest that not the abbreviations are used but the long terms (and an automatism in the background converts ui/ux to there long equivalent in case it should have been typed -- i.e. the "most-wanted-synonym" feature already mentioned).

No you cant make ui and gui the same: if i type with kbrd it's part of UI but it's not GUI. Come on, there is huge amount of tech/user-space terminology that has its use cases and if you just don't know the differences better leave them.as they are, cause the poster might have had good reasons to use e.g GUI and not.UI

UI is not only GUI, both of which are not UX. And @jgr definately not all abbrs should be turned to new invented tags - they are for.things.that have established names and titles and have been used for decades.

@jjaone: "not all abbrs should be turned to new ..." You are right. The people who select these, will know why. So it is not a problem that they may not be understood by the whole community.

No, some of those sync=tags refer to specific technologies, protocols or products/services; better not touch them light-heartedly ;)

The colored ones in your answer can definitely be under sync. Let's leave the rest for now.

@simo synch is synchronization for sure, but the others let them be for good (not only for now), I explained why already.. Overly merging tags that just look similar is a really bad idea unless you are sure there are no semantic differences in them..And in tech terms one letter can change everything to it's opposite..

@jjaone I wasn't clear enough... I always try to think these issues in a long run, so "for now" should have been like "as long as they seem to work well" or something like that... I suppose we have the same thought anyway. Not forever, not for now, but for as long as they serve us well ;)

@simo It doesn't work like that when you talk abt terms and vocabularies (tags as metadata). There is 'rsync' and there is 'syncml' and they will not start to mean the same thing, even if we waited for eternity for that to happens. In text/user-landscape terms are defined (that's why user guides usually have used terminology defined) and then used accordingly. It's not like lets use this term today like this, and let's see what we invent for this for tomorrow...

@simo I edited that @jgr's orginal Answer (with definitions and stuff), and no this is not a duplicate of that, this gives explanation why UI, UX, GUI should not be merged. I never got any PM from you,

@simo, @jaone: I suggest:

• jjaone puts this answer as comment underneath the original ui/ux/gui answer
• most of the trhead below the original answer is deleted, leaving only what is really necessary (maybe one post by simo, none of mine, the answer above by jjaone as comment)
• Delete above answer including the associated comments

@jgr Thanks for reply, you don't have the delete anything, I removed some of my OT comments, edited your Q with defs, posted my own Answer that those tags should not be merged, and I will keep it there cause it is important that there is a reason why it is not a good idea. Some PM currently on-going with "simo" but it's sleeping time here too, so Gnite to you, sweet dreams, I'l join soonish..

@jjaone Thanks for joining PM, we're getting issues solved. I'll remove more of my comments also, but tomorrow. Good night everyone :)

I see only three here :) Could you make a numbered list, sorted by question number, for easier commenting.

Sorry, you see three what? o.O

Three subjects above, meaning that some questions might (IMO) be merged (content moved to those).

Merging questions is not upported by askbot and even if topics are similar the idea here is that one question addresses unique problem or request, and if not then they should be marked as duplicates and closed (leaving the first/most descriptive/more voted one alive).