1 - I would say 'Don't provide instructions that involve the command line if the same thing can be done through the server manager'.
I went back and forth on this. My first impulse is to throw a bunch of command line stuff into the forum - but then I thought "why not open a bug report, put the command line stuff there, and refer to it from the forums?" - that way the developers get to weigh in on the validity of my impulses without needing to scan the forums for my misguided advice.
I see a work-flow like this:
- The first time a question is asked in the forum, an advice-giver like myself finds a reference to the answer and gives the link, or creates a bug for the question and proposes a solution there
- the bug then proceeds wherever it goes - ending in 'fixed in....' an updated RPM or a wiki update or a documentation update
- the next time this question is asked, the solution is referred to in the wiki or docs
The "pro" side of this is that all advice goes through bugzilla so the developers get to see it. The "con" side is that I don't like opening frivolous bugs and potentially wasting the developers' time.
Also, I don't know how to remove anything from bugzilla - if I upload a proposed script that ends up causing problems, or make a post with code in it that doesn't work, how can I make sure no one uses it? In the forums I try to go back and edit any post I give where my advice is "just wrong" to keep folks from using it.
Having said that, I will follow the recommended procedures to the best of my ability, whatever they are!
4 - sounds good, but not really related to good/bad advice in the forums.
Yes, but once we publish "question answering" guidelines I think they should include the requirement that the answer flow all the way through to either an updated RPM, an updated wiki or manual page, or a concise statement (understandable by end users) why not...