Ask / Submit
99

Cleaning up together - please join

asked 2014-01-20 10:43:49 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2016-02-01 19:36:43 +0300

JSEHV gravatar image

Have you seen questions or tags very close to each other, but not quite duplicates? In this wiki we sort these out together. Add an answer to start a new discussion.

1. Sorting of closely related questions (why is this important?)

2. To achieve a meaningful, clear, intuitive and shared notion of set of tags

3. Already cleaned (links to discussions):

4. Code-of-conduct! Before merging duplicates / changing existing tags:

  • Suggestions (formatted as "Answer") should be listed here for at least 2 working days to see what comments they get.
  • Thereafter, answers should be revised according to the result of the comments, for example, making it clear that a certain set of tags should not be merged and stating the reason.
  • Wait another working day before you start editing tags and check what the discussion is. If previously there has been a lot of different ideas and comments, you may even ask that a moderator gives the go-ahead.
  • Report all retagging with a comment, so that moderators can cleanup the back-end (otherwise unused tags are shown in the list of choises when tagging a question)
edit retag flag offensive close delete

Comments

@jgr I edited that part to be not so normative: "If you run into a question that can't actually be answered at all, or is a simple How-to or Poll / Survey consider commenting that to the writer and/or convert the question to a wiki (edit -> mark with "community wiki")"

Is it better now?

foss4ever ( 2014-01-20 12:38:03 +0300 )edit

I propose to introduce the concept of sticky topics centralizing news / main ideas and so on. A meta-topic could be created to gather sitcky topics title. Yesterday, I was suggested to use tags, but it's not efficient. I think sticky topics could be good to reduce the number of "duplicate topics".

TNZ ( 2014-01-21 10:44:09 +0300 )edit

@TNZ Who selects sticky topics, and by what criteria? And where are they shown?

foss4ever ( 2014-01-21 11:01:12 +0300 )edit

@jjaone : The main idea is to have a cleaner area. I think that guys who spend a lot of time here are the best (like admins & moderators) to manage sticky topics and the meta-topic.

Maybe, a specific site section giving news about activity here could help instead of maintening sticky-topics.

TNZ ( 2014-01-21 11:12:20 +0300 )edit

@TNZ A Dashboard giving a quick overview of what is happening in here, hot topis, latest questions, answer, comments, whos on line, top 10 roadmapped and / or closed questions, etc etc..with selectable sticky topics, news, howtos, guides + a link section to related Jolla & developnent spesific sites like Care, Store, blogs and community portals..

foss4ever ( 2014-01-21 11:28:01 +0300 )edit

51 Answers

Sort by » oldest newest most voted
0

answered 2014-03-26 01:47:41 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2014-03-26 01:47:41 +0300

jgr gravatar image

microSD cards

The tag list on this subject is long. After some cleaning, currently in use are:

  • sdcard (32)
  • microsd (27)
  • 64gb-sd (3)
  • microsdhc (1)
  • microsdxc (1)
  • mount-sd (1)

(It does not seem to make sense, to reduce this set further.)

Not used are:

  • sd
  • sd-card
  • card
  • µsd
  • missd (may have not been related to sd card)
  • micro

@eric: Could you please remove the unused tags from the system?

edit flag offensive delete publish link more

Comments

Just as a note: Cleaning included:

  • sd-card ==> sdcard (using the one, more often used)
  • sd ==> sdcard (using the one, more often used)
  • card ==> sdcard (using the one, more often used; no other use than in relation to SD card)
  • µsd ==> sdcard (using the one, more often used)

"missd" and "micro" were "empty tags" already.

jgr ( 2014-03-26 01:52:56 +0300 )edit

@jgr: done, thanks for helping :)

eric ( 2014-03-26 09:09:48 +0300 )edit
0

answered 2014-03-26 07:47:48 +0300

fblm gravatar image

Retagging has been done for:

mitakuuluu x3 mitäkuuluu x3

tagged to mitäkuuluu x6

edit flag offensive delete publish link more

Comments

Might be better the other way around, as not all users have these Scandinavic letters in their keyboards

simo ( 2014-07-18 12:00:03 +0300 )edit
0

answered 2014-10-23 11:33:36 +0300

saturn gravatar image

Sorry I don't have the rights to change them, but here is another case for cleaning:

  • notifications (208)
  • notification (5)
edit flag offensive delete publish link more

Comments

Has been cleaned

eric ( 2014-10-23 16:35:14 +0300 )edit
0

answered 2014-10-23 11:35:17 +0300

saturn gravatar image

Sorry I don't have the rights to change them, but here is another case for cleaning:

  • sensors (8)
  • sensor (4)
edit flag offensive delete publish link more

Comments

Has been cleaned

eric ( 2014-10-23 16:32:46 +0300 )edit
0

answered 2014-10-23 11:55:00 +0300

saturn gravatar image

Sorry I don't have the rights to change them, but here is another case for cleaning:

  • enhancement (135)
  • improvement (55)

note, some posts have both tags.

edit flag offensive delete publish link more

Comments

Has been cleaned, thanks.

eric ( 2014-10-23 16:58:42 +0300 )edit
0

answered 2015-01-12 23:03:41 +0300

saturn gravatar image

I have seen the discussion about ui, ux and gui.

What about these two:

  • ux (182)
  • user-experience (17)

should they be merged or there is a difference?

edit flag offensive delete publish link more

Comments

@saturn: Thanks, it's merged now.

eric ( 2015-01-13 09:53:41 +0300 )edit
0

answered 2015-01-20 02:30:31 +0300

null gravatar image

Cleanup suggestion:

  • xmpp (53)
  • jabber (9)
edit flag offensive delete publish link more

Comments

@null: Thanks, these are now merged...

eric ( 2015-01-20 10:23:51 +0300 )edit
0

answered 2015-02-07 08:00:42 +0300

simo gravatar image

updated 2015-02-07 08:17:42 +0300

Related questions about exFAT file format, sorted by date, oldes on top

(Amount of votes / Amount of answers) Link:

I think some cleaning of duplicates and combining few votes/answers/ideas from latter questions to older ones would be useful with these. Please comment!

edit flag offensive delete publish link more

Comments

For our goal here, I'd like to suggest that we try to reduce the amount of questions (25 listed above) to 5-7 with copying some relevant content, combining vote count (mods?), and then closing some newer questions which could be handled within the older. For this discussion, let's just use the question number visible in the url

simo ( 2015-02-07 08:45:41 +0300 )edit
0

answered 2015-02-19 20:44:11 +0300

There are currently three ways used to indicate version:

  • by name: Yliaavanlampi
  • by update number: update11
  • by version number: 1.1.2.15

I suggest everything is tagged by version number.

edit flag offensive delete publish link more

Comments

Given that the update number is being removed, and updates should be referred to by their major version number, i suggest we have a tag as follows:

X.X.X-LakeName eg. 1.1.2-Yliaavanlampi

r0kk3rz ( 2015-02-19 21:28:19 +0300 )edit

@eric: since tag moderation is enabled, we need you to enable these tags:

  • 1.0.0-kaajanlampi

  • 1.0.1-laadunjärvi

  • 1.0.2-maadajärvi
  • 1.0.3-naamankajärvi
  • 1.0.4-ohijärvi
  • 1.0.5-paarlampi
  • 1.0.7-saapunki
  • 1.0.8-tahkalampi
  • 1.0.9-uitukka
  • 1.1.1-vaarainjärvi
  • 1.1.2-yliaavanlampi

If you don't agree, tell us the preferred format and we'll do the changes. For each of these new tags, 2-3 tags will be removed so it'll be quite a cleanup.

(BTW: how to write tags in markdown syntax?)

jaacoppi ( 2015-02-24 14:19:17 +0300 )edit

there is one problem, 1.1.2.15 for example is an RC and you do not want bugs introduced in (just an example) 1.1.2.21 tagged as 1.1.2 but specifically as 1.1.2.21. I understand that one wants the lake name as tag but the bare version numbers are needed too - update## otoh is not really needed as there should be $shortened-month## for when it was fixed and the update## is just for announcements and probably upgrade specific issues

chemist ( 2015-02-26 10:53:18 +0300 )edit
1.1.2.15 for example is an RC and you do not want bugs introduced in (just an example) 1.1.2.21 tagged as 1.1.2

Why is that a big issue? Each bug report should get closed with a released in software update upon fix release, bugs identified in pre-releases and not fixed before full release are still relevant.

since we are now seeing more release numbers, having a tag for each and every minor version seems a bit too granular

r0kk3rz ( 2015-02-27 18:20:29 +0300 )edit

It tells when it was first found and most probably introduced. Additionally it is possible that someone finds a bug before upgrading to a newer version so it is known to the developer that this was already there eg 2 versions ago and not newly introduced in the current. There are various reasons why you would tag bugs that way - but actually only one good reason is needed to make it good habit to tag bugs with the version number they are found in.

chemist ( 2015-02-27 19:55:36 +0300 )edit
0

answered 2015-05-06 11:04:20 +0300

simo gravatar image

Related questions around Facebook API change (April 30, 2015), latest on top:

edit flag offensive delete publish link more

Comments

Excluding the #3 which is cleary about one separate application, I suggest that all the other four could be combined to the oldest #5, editing the topic as well, and then closing #1, #2 and #4

simo ( 2015-05-06 11:04:31 +0300 )edit
Login/Signup to Answer

Question tools

Follow
12 followers

Stats

Asked: 2014-01-20 10:43:49 +0300

Seen: 6,495 times

Last updated: Jul 15 '15