|
» Stats |
Members: 153,054
Threads: 223,221
Posts: 1,288,426
Top Poster: bob (16,880)
|
| Newest Member bt088 |
|
| Posting Guidelines |
FedoraForum.org guidelines
Welcome to FedoraForum.
The following document will provide some rules and guidelines on how to ask questions the smart way, how to answer to best help your peers and how to behave to keep the Community Managers and everyone else happy.
Rules
The following rules must be obeyed, they are for the good of all the members of the forum. Breach of these rules will result in a user being banned from the forum.
- Respect the Forum Staff
We provide a service in our free time to keep the forum running efficiently; we are not here to make life harder for anyone. Any decision taken by the Administrators and Community Managers is final and will be respected. Do not argue with the Staff in a thread. If you want to discuss an issue, do it by email or by a PM (Private Message).
- Do Not be Abusive
Abuse doesn't get you anywhere. It generates bad feelings and is very likely to get you suspended from the forum. We're here to help each other not fight.
- Use Informative Titles
Instead of using a title like "Heellllppp!!!?!!!" or "ARGH Fedora Crashes AGAIN!!!!!", use a title that is specific. Such as "Mouse Glitch/HD Hit Once Per Second" or "No Sound With PulseAudio". A clear title will attract more views to your thread, as it gives a clear indication of the content of the post in a mature manner. Experienced users usually have little time for immature complaints. Ultimately this will allow you to get more help of a better quality. Failure to comply will normally result in your thread being ignored.
- Do Not Cross-Post (Double-Post)
Posting your thread in several parts of the forum is immature. Just because it's in more than one location doesn't mean that more people are going to answer it. In fact quite the opposite normally as experienced members have little time for this sort of behaviour, staff members will close all offending threads. Posts or threads advertising other posts are also seen as cross-posting.
- Do Not Advertise
We are not a space to advertise your product, and you are not permitted to do so without the express consent of the Staff. Links to commercial sites and products may also be considered as ads. Check before you post them.
- Do not post images containing nudity, violence or otherwise offending content.
This is a friendly support forum and we do not want to cause offense.
- Do not breach copyright
This is to prevent the forum from being sued. So please make sure you have permission before posting that super cool wallpaper you found to the gallery.
- Don't post Religious or Political threads
There are many forums for such posts. This isn't one of them. Most people have strong feelings on these topics and may be offended.
- Threads about "Cracking" will be closed
Yes, there are packages such as aircrack in the repositories but mostly they are used is for illegal purposes. The Staff will close such threads.
Guidelines
These guidelines if followed can help you get more from the forum and make it a more pleasurable experience for everyone.
General
- Be polite. This is a user forum and we all do this as a hobby, in our free time. Please and thank you can get you a long way.
- Try to make understanding as easy as possible. We're an international forum with users from all over the world and not all of us are fluent in English. Write in as proper English as you are capable of. Honest mistakes are fine, we all make them.
Remember:
- Write in English.
- Add whitespace to your posts. Use enter for paragraphs.
- Capitalize Correctly. All uppercase is considered screaming and very rude. All lower is hard to read.
- Use correct punctuation. Never use more than one question mark or exclamation mark and only at the end of a sentence.
- Never use "texting abbreviations", "leet-speak" or slang. The purpose of language is being understood, not sounding cool.
- Never invent acronyms, use as few acronyms as possible. It's called a problem, not a "pb" and a question, not a "Q".
- Never use colors in all of your posts. Colors are there to highlight something important.
- Read your post over before posting it. Try to catch typos. If you find an error after posting, use the Edit button to make your corrections.
- Don't "bump" your post by adding a second post with no worthwhile content. The Forum controls will automatically add any additional post as an 'edit' of your first post within the first 24 hours. If you haven't received a response in over 24 hours, consider following up with the efforts you've tried in the meantime and their result. Naturally, if you forgot to add important information, an edit of your first post is acceptable.
- Report bad posts. If you discover an abusive post or someone posting a thread in the wrong section, report it to the staff using the "Report Post" link, that is above every post.
- Go easy on the images, they may help to explain something more clearly or indicate a problem you are experiencing better but you have to remember that not everyone has the same amount of bandwidth to waste on downloading large image files. If you feel you have to post images, make sure that they're properly compressed and no more than 100KB at the absolute most.
Images are not welcome in signatures, as they can significantly increase the load time for users. Your avatar is a space for an image, your signature is not.
- Trolling, Flaming and Whining threads will be closed. We're not here to pit one distro or OS against another. In fact, most of us use multiple OS's and/or distros. Likewise, if you're displeased with Fedora and want to leave parting remarks, comment to the developers using the Communicate links at FedoraProject (handy "jump" is at top of the page). Remember that the Forum is users helping users and that we can't 'fix' the distro itself.
When Asking Questions
- Read The Unofficial Fedora F.A.Q. (Frequently asked questions) and Search FedoraForum.org before asking questions. Check the Read This First sub-forum for assistance. Search the Fedora mailing lists and give google a whirl as well. There's a good chance your question has been answered before.
- Details, details, details! Don't be brief. Include your Core release number, the architecture of your computer (i.e. AMD 64 or a Quad-Core, or in the case of video cards NVIDIA model or ATI model), the version of the component you're having trouble with and everything you think might help. If you're using 3rd party RPMs explain where you got them from. Attach screen shots or other files if you think it might be useful.
- Don't talk yourself down. Don't call yourself an idiot, we have all been newbies at some point. Don't add things like this to your posts:
Quote:
| I know I'm an idiot but I just can't figure this out.. |
No question is too stupid.
- Don't mark your question as important or critical. All questions asked are equally important.
- Come back to the forum even after your question has been answered and give your thanks to the people who helped you. Try to generate that good, warm, fuzzy feeling amongst your peers. And, as your skills increase, consider coaching others.
When Answering Questions
- Don't be cruel. We have all been newbies at one point and no one needs someone telling them how stupid they are.
- Don't use jargon in your instructions if it can be avoided, newbies may not understand. If you don't have any better answer than RTFM (Read the fine manual), just be quiet.
- Point the user to existing resources if they can provide useful information. Use community sites like fedorafaq.org and fedoraNEWS.org in your answers, searching the Red Hat bugzilla is a good idea as well.
- Always assume the the user has a default installation unless you're told otherwise. This means that you can't tell anyone to use APT without providing instructions on how to install APT or at least link to an APT tutorial, as APT isn't included in the default installation. If you tell people to use an application outside of Core, give instructions on how to install it.
- Always assume that the user is a newbie unless you're certain the user is not. Give detailed instructions.
- Use proper formatting, use[CODE] tags around terminal commands. You can attach files and pictures that you think might help.
- Do things the Fedora-way. There are always more than one solution to a problem, choose the one you think will be the easiest for the user. Automatic package installation (using YUM, PackageKit or Yumex) over manual installation. RPM over source. Where possible get people to use the official Fedora repositories and the related RPMFusion. They are of higher quality. Don't replace any Core packages and never instruct users to do anything that might break their system, this includes using --force and --nodeps when installing an RPM. Try to think as a newbie and choose the simplest solution.
- Explain each step of the solution. The ideal solution to a problem should be able to teach the user how to solve similar problems in the future. Teach people to fish, don't just throw them a salmon.
Thank you for using FedoraForum.
|
|
