LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
Quote:
Originally Posted by cynwulf
You can blame the posters who post those threads - but while the focus in on them and on putting together guidelines no one will bother to read, the problem will remain as it always has. The people to address and to get on board with this are those responding to these threads and doing other people's research and web searching for them.
By creating solid, friendly, educational guidelines to point to we can surely educate some percentage of the new members creating this issue. Making it clear that not following the guidelines will result in most senior members not being willing to provide help, we can foster an friendly environment that is both welcoming to new members while also providing more senior members with an environment that does not drain them of their desire to help and participate here at LQ.
In our case, I suspect that there's a language barrier involved in at least a few of the "problem" posts. I think that those users just need to be coached on how to write their questions more productively.
In our case, I suspect that there's a language barrier involved in at least a few of the "problem" posts. I think that those users just need to be coached on how to write their questions more productively.
Great perspective, well and cleverly written! Should be required reading for both help-vampires and vampire-helpers.
Thanks for the link dugan!
I also think there is a language and culture (societal) barrier, or two, involved in our specific cases, more so than the author of that article may have noted. This is likely due in part to specific geographic shifts in technology sourcing (manufacturing, design, support) that dominate differently today and we see more directly than some other sectors.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
Thoughts on this as the canned response that could be linked to for offending posts? Note that this is just an initial rough draft so comments, suggestions, additions, etc. are desired.
Quote:
Hello and welcome to LQ. You were pointed here because a fellow LQ member feels the thread you started doesn't meet the minimum threshold that would enable us to help you. We understand that Linux can be intimidating for new members, and we really do want to help. That said, please understand that LQ is not a help desk, customer service line for a product you purchased or willing to do your homework (although we are happy to assist you with specifics, if you show some effort of your own!). We're a 100% volunteer organization that wants to help you help yourself.
Here are a couple tips that will enable us to help you moving forward:
When asking a question, be sure to provide as many relevant details as possible. You should include the distribution and version you're using, along with hardware details, application version and exact error messages where applicable.
If you're actively troubleshooting an issue you should also include any steps you've already taken.
You may want to include how what you are experiencing differs from what you expected to experience.
Before posting, have you used the search function to ensure your question hasn't been asked before?
You can edit your post by clicking the EDIT button in the bottom right corner of your message.
If you are unwilling or unable to ask questions in a manner that allows us to help you, it's unlikely our community will be able to provide you a solution. Unfortunately, serial offenders who show wanton disregard for this request may be asked to seek help elsewhere. We truly hope that isn't necessary, and assure you Linux and Open Source are extremely rewarding and well worth the learning curve in the long run.
I think it would be better without the "if you are unwilling..." paragraph. The stage where that answer should be linked is earlier than the stage where that level of escalation is appropriate.
I also think that "what have you tried?" (which is essentially the second bullet) should be emphasized more.
Thoughts on this as the canned response that could be linked to for offending posts? Note that this is just an initial rough draft so comments, suggestions, additions, etc. are desired.
Quote:
Hello and welcome to LQ. You were pointed here because a fellow LQ member feels the thread you started doesn't meet the minimum threshold that would enable us to help you. We understand that Linux can be intimidating for new members, and we really do want to help. That said, please understand that LQ is not a help desk, a customer service line for a product you purchased, nor are we willing to do your homework (although we are happy to assist you, if you show some effort of your own!). We're a 100% volunteer organization that wants to help you help yourself.
Here are a couple tips that will enable us to help you moving forward: Do some research on your own first. Asking that someone give you a step-by-step guide, or give you links to software or documentation is, essentially, asking people to look things up for you. Doing such research would help you learn, and may provide you the answer faster than waiting for someone to answer you.
When asking a question, be sure to provide as many relevant details as possible. You should include the distribution and version you're using, along with hardware details, application version and exact error messages where applicable.
You may want to include how what you are experiencing differs from what you expected to experience.
Before posting, have you used the search function to ensure your question hasn't been asked before?
You can edit your post by clicking the EDIT button in the bottom right corner of your message.
If you are unwilling or unable to ask questions in a manner that allows us to help you, it's unlikely our community will be able to (or WILLING to) provide you a solution. Unfortunately, serial offenders who show wanton disregard for this request may be asked to seek help elsewhere. We truly hope that isn't necessary, and assure you Linux and Open Source are extremely rewarding and well worth the learning curve in the long run.
Some additional reading that may help:
Edits in bold, but I think it's a great. Thanks, Jeremy.
I would just add PMing a member outside of a thread asking for personal help, (it happens to me sometimes),
is counter productive to another person reading said thread, for a solution to their problem, searching the net.
All inquiries should remain in the thread.
Any PM's I get. I explain the above and, no, I won't answer outside of the thread.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
Quote:
Originally Posted by rokytnji
I would just add PMing a member outside of a thread asking for personal help, (it happens to me sometimes),
is counter productive to another person reading said thread, for a solution to their problem, searching the net.
All inquiries should remain in the thread.
Any PM's I get. I explain the above and, no, I won't answer outside of the thread.
While probably outside the scope of this message, you're right; that shouldn't be happening. It is covered by the current rules though, which you can point them to:
Quote:
The best place for your question is in the forum. We get a large number of emails. If your email contains a technical question we will kindly point you to the forums. This also includes using the email forms to advertise or send out surveys. Do however email us when you need to discuss anything private regarding the site that should not be asked in the forums. Please do not post requests for help via email, IM or other personal communication channels.
Since PM's can only be sent by senior members, this is hopefully not too common of an occurrence.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
Quote:
Originally Posted by dugan
I think it would be better without the "if you are unwilling..." paragraph. The stage where that answer should be linked is earlier than the stage where that level of escalation is appropriate.
I think it needs to be clear that there is some consequence if the information is ignored. We do need to ensure, however, that the wording is clear and friendly enough that it does not put off well intentioned new members. Thoughts?
Quote:
Originally Posted by dugan
I also think that "what have you tried?" (which is essentially the second bullet) should be emphasized more.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
Quote:
Originally Posted by TB0ne
Edits in bold, but I think it's a great. Thanks, Jeremy.
I've made some adjustments, but am unsure about the "Do some research on your own first. Asking that someone give you a step-by-step guide, or give you links to software or documentation is, essentially, asking people to look things up for you. Doing such research would help you learn, and may provide you the answer faster than waiting for someone to answer you." clause. I'm open to what other members think though.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
Quote:
Originally Posted by bradvan
I think that looks fine. I say put it in a sticky post somewhere and just start using it. Time and experience may point to adjustments.
I'm going to give some additional time for feedback, but will post it to the FAQ with a permanent URL very soon. I'm sure it will be a work in progress as we roll it out and tweak it based on response and feedback.
I wouldn't include the "do some research on your own first" line. I think that is implied in the other bullets and by itself can come across as a bit negative.
* We should all still make a cognizant effort to be friendly and welcoming to new members. It's likely we should come up with a canned response that includes the above URL.
* This is very much a work in progress. Additional suggestions and feedback is very much desired.
Thank you to all members who have participated in this thread.
I've made some adjustments, but am unsure about the "Do some research on your own first. Asking that someone give you a step-by-step guide, or give you links to software or documentation is, essentially, asking people to look things up for you. Doing such research would help you learn, and may provide you the answer faster than waiting for someone to answer you." clause. I'm open to what other members think though.
--jeremy
How about a simple checklist on the "New thread" page, or a set of boxes for people to tick
This sort of thing:
_ _ _
1. Is this a Problem? |_| Query?|_| Comment? |_| (appropriate word is first on subject line)
_
2. Have you googled your exact error? Yes |_| (If no, go and do that now please)
and maybe some others. That's a little bit of html work, but it should be doable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.