asked 2013-12-28 05:29:57 +0300
This post is a wiki. Anyone with karma >75 is welcome to improve it.
When to use question / answer / comment?
See also: Featured tags -> Guidelines (visible also in the front page)
Edit: bringing this guideline up for a while, as a lot of duplicates has been posted lately. Let's keep the corners clean around here :)
answered 2013-12-28 05:44:25 +0300
This post is a wiki. Anyone with karma >75 is welcome to improve it.
Before you write to together.jolla.com: read help After you have read the help, you know that searching is very important. Duplicates flood the portal.
If you have an idea, don't share that as a question. Instead write an appropriate question, and answer it yourself with your idea. This leaves other people a chance to give different answers, and there will be voting going on between several answers - including yours. The ones voted most are candidates for advancing to development. Remember to tag your question, it enables filtering. Please use max 4 tags - there's a possibility for 5, but 1 should be left free for a possible roadmap or any other dedicated tag.
Commenting is for clearing out the question/answer, so that the question/answer can be edited to be more specific. Extra commenting should be avoided (they flood the amount of posts) Your comment might include additional idea to a particular answer, but it won't necessarily become part of the answer. So, for your ideas, it's always better to write your own answer (you can copy ideas from other answers to build a new, and in your opinion, better answer)
An answer might be a direct answer to the question (if you know one), or your own idea of how the issue in the question should be developed. Do not include questions to an answer.
Answers should indeed stay on topic, and any other relevant information should be either in it's own thread or posted as a comment for improvement/clearance of the main question of the thread.
ps. no need to vote for quidelines, but feel free to edit them. You can find all the guidelines in the front page: Featured Tags ->
guidelines
answered 2014-01-13 17:23:26 +0300
The way bugs are reported is not aligned with this Howto..They are not questions/suggestions but (potential) bug descriptions where the conversation is mostly abt whether it can be confirmed or not, or whether it is important or not. This forum should have a bug-type of 'question' that isn't a question but a drscription of issue or erroneous behaviour of the system that the user needs to have fixed. The Q/A-type of forum is good for some things, but when a proper service-request type of categorization system is missing (the tags won't help cause their vocabulary is not controlled) then all kinds of requests/ideas/issues/wishes/bugs/etc. get mixed up, and for some of them the ptoper question form is hard to find. Or should each bug-request be forced to be wrapped to a question: How to fix 'issue-here' please?
answered 2014-01-27 22:50:04 +0300
This post is a wiki. Anyone with karma >75 is welcome to improve it.
Clarifying of a single question
Here's what you can do if you have the time and the energy:
Check the answers which seems more like comments, and ask the writer to think about converting it. Also, I've seen a few comments that could be edited as good answers - comment for those too (you also make the writer happy, as you value her/his comment high via suggesting that)
This was moved here from "Cleaning up Together" to narrow the subject there, and to expand this guideline. If you had important comments under the previous location concerning this matter, please paste them here (nothing is removed from there). Sorry for any trouble, it's just to make things work even better in a long run.
answered 2015-09-13 16:41:49 +0300
This post is a wiki. Anyone with karma >75 is welcome to improve it.
I'm considering picking the most voted answer to the new guideline topic "Question, Answer and Comment - General", but updating the layout and leaving out some things more related to posting new questions. Also, moving some of the lines from "general" to the related subtopics.
Also, picking some mentions from here under topic "Posting bug reports" under "Posting a new question". Bug reporting guideline doesn't exist yet, and that will probably gather ideas from several older guidelines, added by new ideas. From here, these mentions regarding bugs seems worth notifying on that new guide:
The guideline project discusses on these old guideline posts until September 20th, updating and gathering information from here to a new post The Guideline. You're welcome to join the project, for example by editing and commenting this answer.
Asked: 2013-12-28 05:29:57 +0300
Seen: 3,246 times
Last updated: Apr 10 '16
This is a good article and the first answer is the proper way to.use this forum. The problem is that most of the questions in Together are actually bug reports or feature-requests described in title.and.description as.such. The answers are usually accepted when the issue is acknowledged and/or roadmap'ed by Jolla. This Howto hopefully affects the new questions asked here so that propposals / ideas are not described in the question itself, but as an answer, but how do you report a bug as a question?
foss4ever ( 2014-01-13 15:05:08 +0300 )editThe way the bugs are reported so far looks just fine, and in those I haven't seen much workarounds or other answers included to the question part. Mixups (a question beeing an answer at the same time) seems to occur more especially with ideas / new feature requests.
simo ( 2014-01-13 15:55:16 +0300 )edit@simo, @jjaone: Please see the new instructions now available on: https://together.jolla.com/questions/ask/ thanks!
eric ( 2014-02-04 14:10:58 +0300 )edit@eric Nice :) Maybe add to the 3rd line: "...You can filter your searh result further by adding tags to the search box on the right panel"
simo ( 2014-02-04 14:18:10 +0300 )edit@simo: this textbox has a fixed size. No more text there, sorry. But your addition could nicely live in the related tag guideline post ;)
eric ( 2014-02-04 14:21:24 +0300 )edit