Ask fedora guidelines: Difference between revisions

Revision as of 11:54, 12 March 2019

In other languages: Deutsch (de) English (en) español (es) Bahasa Indonesia (id) 中文 (zh) Ελληνικά (el) italiano (it) فارسی (fa) [edit]

This page lists the good practices while using Ask fedora:

Please feel free to add more points to the list. If you need to discuss something with the forum moderators, find us at #fedora-ask^[?].

Video

Watch a 5 minute video that'll help you get started with using Ask Fedora:

TBD

Old videos about use of Asknot need to be removed!

List

Go through the official Fedora Documentation
Go through the quick-docs. These cover common tasks and issues like installing Skype and Multimedia codecs.
Use the correct language specific categories: You should join the language group of choice and post using your preferred language in the correct categories.
Use the correct topic categories: You should use the correct topic categories to post your questions.
Use tags wisely: Make use of existing tags instead of adding new ones where possible. This increases the visibility of your question.
Search before you post: Search the interweb and then Ask Fedora itself before posting your question.
If you have more than one question, post them separately: Do not write a post that says “many Fedora questions” and ask them all together. You should ask each question separately so that they can receive individual answers.
It is perfectly OK to answer a question that you asked: There's nothing stopping you from answering your own questions. When you do, please post your answer separately, and not in the question description.
File bugs in bugzilla: If it is a package related issue or you are requesting an update for some package, do so directly via bugzilla. If you haven't done that before, refer to How to file a bug report.
Ask questions in a useful manner: Here are some more tips on getting answers.
Provide information about to help people help you better: People can't help you if you do not provide specific information on the issue you face. Some commands and logs that you should look for information to provide with your questions:
- journalctl -b: Journal logs from the most recent boot.
- lsusb: Information on USB devices
- lspci: Information on PCI devices
- dmesg: Kernel messages
- uname -a: Current running kernel
- Display server :
  - How to debug Wayland problems
  - How to debug Xorg problems
- How to debug Bluetooh problems
- Google: All of the above logs and commands can be learned from the internet.
Use formatting tools: When you want to post information along with your question, please use the tools, such as quoting, code snippet etc. If folks can’t read your questions quickly, they are not likely to answer them.
Is that an answer?: Only post answers when you're providing a solution to the asked question. For everything else, comment on the appropriate question/answer. Having a thread of conversation as answers just confuses people looking for information. Use comments. Only post an answer when you have one.
Please do not append "[Solved]" to your question summaries: Please do not add the tag [Solved] to your question summaries. If you received an answer that solved the issue, please mark the answer as correct and reward the helper with Badged. There is no need to modify the question summary.
Subscribe to questions you ask/answer/comment: A lot of answered questions are not marked so because the original person asking the question hasn’t responded to follow up queries!
If you see someone not using the forum correctly, point it out: Comment telling them what they're doing wrong politely.
Last but not least be polite and refrain from ranting: Ranting makes people not want to help you. There isn't anything else to it. If you're polite, folks will want to help you.

ScreenShot

TBD

Moderator responsibilities and guidelines

Ensure Ask Fedora is free of spam. With only FAS login enabled, there should not be much spam on the forum.
All questions, answers and comments must follow the Fedora code of conduct.
Encourage users to be helpful and participate actively.
Remind users of the guidelines listed above.
Ensure that questions are tagged appropriately.
Delete duplicate questions if they are exactly the same and have been posted by mistake.
If questions are very similar in content, you may close the duplicate question but MUST leave a comment pointing to the original question.
Do not close questions just because they are answered. Leave it open unless there are special circumstances that warrant closing.

@@ Line 38: / Line 38: @@
 * '''Use formatting tools:''' When you want to post information along with your question, please use the tools, such as quoting, code snippet etc. If folks can’t read your questions quickly, they are not likely to answer them.
 * '''Is that an answer?:''' Only post answers when you're providing a solution to the asked question. For everything else, comment on the appropriate question/answer. Having a thread of conversation as answers just confuses people looking for information. Use comments. Only post an answer when you have one.
-* '''Please do not append "[Solved]" to your question summaries''': Please do not add the tag [Solved] to your question summaries. If you received an answer that solved the issue, please mark the answer as correct and reward the helper with karma. There is no need to modify the question summary.
+* '''Please do not append "[Solved]" to your question summaries''': Please do not add the tag [Solved] to your question summaries. If you received an answer that solved the issue, please mark the answer as correct and reward the helper with Badged. There is no need to modify the question summary.
 * '''Subscribe to questions you ask/answer/comment:''' A lot of answered questions are not marked so because the original person asking the question hasn’t responded to follow up queries!
 * '''If you see someone not using the forum correctly, point it out:''' Comment telling them what they're doing wrong '''politely'''.

Search