Archived thread 379879 from Beginner Team. Markdown source: Beginner_Team/thread_379879_Standard_answers.md
I guess my previous was too comprehensive ( it got moved to feature requests :)
What I suggest is that the team have 'canned' standard answers - complete with links to explain why the fix will work. The noobie (like me) who wishes to learn more - can follow the links for details/explanations - the migrators who just want a fix will have a tested response quickly and an immediate problem solve.
BTW - once I know enough - will be happy to join the other side of the team!
speaking of standard answers... check out my forums faq in the sig - is that like what you are thinking of?
LOL freebird54 ...
I'm trying to keep it organized. When I'm looking for ideas for the team I figure I want to look in 1 looooong thread rather then 50 short ones ...
Your thoughts on a 3 tiered approach are good, although I feel almost obliged not to give answers without at least a little education (second tier) ...
In terms of canned answers, yea that's what I'm thinking. That is what is good about a team, we can peer review answers to FAQ ...
One random thought ...
I used to work with immigrants teaching them English and American customs ...
I noticed some of them were overwhelmed with freedom. When they went shopping, there was only 1 brand of soap (with a picture of the local dictator :) )
Here in America, why do we have to have so many brands of soap. How do you know which one to buy ???
Welcome to the freedom of Linux. We have several "brands" to choose from (distro's) and with any particular "problem" there are usually at least 2 potential solutions ...
Welcome to the freedom of Linux ...
nanotube said: speaking of standard answers... check out my forums faq in the sig - is that like what you are thinking of?
Nice links ....
Those links in the sig are great - but I meant a little more than that...
What I would like to see is an instantl, contextually significant explanation EMBEDDED in the canned answer. If the answer includes a sudo command, have it linked with sudo_root page/explanation automatically (for instance) - and for heavens sake let it be gksudo when appropriate! :biggrin:
I would have kissed the feet (well, maybe) of the person providing that IN CONTEXT when giving me the HowTo for installing fglrx. (how can same command be the answer to getting graphics drivers, adding a program, making a file run, or even editing a text file????)
Now, obviously the person who just pastes the text into his terminal and runs and is not seen again till the next problem won't dig further - but many of the people arriving these days KNOW computers - just not Linux, or especially the Ubuntu way. It's a long way from load "*",8,1 on C64 you know! (Even further from jsr FFD2 to print!)
Hope that makes it clearer - not that I am sure that link-loaded text would paste all that well, now I come to think of it.
Why not have single web-page instructions with details for the essential or mostly needed work with full information. Links can be given for those who want to browse around for more information. 10 headings shall cover most issues. Rest by the FORUMS.
If done with a clear understanding, UBUNTU can be installed and ready in less that 60 minutes, with most common applications installed and running.
dptxp said: Why not have single web-page instructions with details for the essential or mostly needed work with full information. Links can be given for those who want to browse around for more information. 10 headings shall cover most issues. Rest by the FORUMS.
If done with a clear understanding, UBUNTU can be installed and ready in less that 60 minutes, with most common applications installed and running.
You mean like this : http://ubuntuguide.org/wiki/Ubuntu_Edgy
went on irc last night, sound of silence:(
teaker1s said: went on irc last night, sound of silence:(
Which channel ?
We are at #ubuntuforums-beginners ...
freebird54 said: What I suggest is that the team have 'canned' standard answers - complete with links to explain why the fix will work.
Personally -- but maybe that is just me -- I have a problem with "canned" answers. It always gets me frustrated if someone is giving me a standard reply to a question that -- in my belief -- have not asked.
I think it is a good thought that we have a list of links to threads, howto's and/or wiki pages that clearly explain how to resolve frequently occurring problems.
My belief, and I always try to do this, is that an answer should have a personal "touch". I think this will prevent the one that is asking the question that he gets a standard answers and that his/her question is not taken seriously.
Just my 0.02
useResa said: Personally -- but maybe that is just me -- I have a problem with "canned" answers.
It always gets me frustrated if someone is giving me a standard reply to a question that -- in my belief -- have not asked.
I'd second this risk of canned answers. If a person offers a simple canned answer without properly seeing the problem which is being asked, or just the first response rather than engaging with the issue is to shoot out a response which may (or may not) be relevant both annoys the person who's asking the question as they feel like rather than having help from a person they're just getting information from a machine, and also it may well make them think - hey these guys don't know what theyre talking about, basically they just spout a simple answer which they think is relevant.
Giving links which are definitely linked to the problem is in my opinion preferable and also offers a slightly more personal touch than just a simple spit out an answer - (unless a canned answer is 100% sure the answer thats being looked for). If you don't know the answer, another issue which occasionally crops up its also not great to shoot out a load of swiftly googled links which may/maynot have any relevance. - a list of commonly used links listed under topics which are commonly asked could really be helpful and something I think the BT should really look in to :) Or, if like quite a lot of things one already exists, a pointer to the location of this would be cool. Il
I think you misunderstood the kind of 'canned answers' I am referring to - and their usage! An example of how things might run would be more like:
...this sounds like something that we ran into before, can you post for me the results of <command> - which is done like THIS....
(THIS being a link to How to open terminal and cat or whatever). ....
On a second message after more information is given - a canned HowTo with built-in links to more detail is provided. Then, hopefully a pointer can be given to some of the resources some others have mentioned....
Have you seen the Windows way/Ubuntu way comparison wiki?...
It is just that you might well have an answer, but no-one has time enough to write a custom 3 page tutorial for each instance of common troubles! If a structured 'canned' answer is available - it could be used IN CONTEXT to solve/clarify the problem... hopefully to the satisfaction of everyone concerned
freebird54 said: I think you misunderstood the kind of 'canned answers' I am referring to - and their usage!
You are right, I did misunderstood. I think we are basically then referring to the same sort of replies. Personalized but with reference to "pre made instructions" on what to do next. If now my understanding is correct, I fully support your suggestion.
No problem - no amount of smilies make up for the potential for misunderstanding the written post. We would do well to remember that when answering 'help' posts too - if we don't want the poster to 'go away mad' !!
I think we should try to identify the main 'classes' of potential adopters. I see so far:
I am sure there are more classes - but we need to identify experience/comfort level quickly to serve their needs!
LOL
What I am envisioning is more quality control rather then mind numbing spam ...
When we post to the forums as individuals we may make any number of mistakes.
When we work as a team we can provide quality answers reviewed by our peers.
As a team we can add to the wiki.
That is what I envision as "standard answers" ~ quality wiki with access and understandability to all (well OK I'll settle for most).
I seems obvious that these answers are tools and, as with all tools, work best when applied by skilled craftsman.
:lolflag:
Give good, quality canned food while you teach to cook. So that the person lives to learn to cook. :guitar: