David C. Rankin wrote:
One thing that I have found lacking is a useful *reliable* wiki for openSuSE. I know it has one -- don't get me wrong, this isn't bashing, but it is really hit or miss as to whether you will find anything useful there for any given package or issue. I used to think wikis were pretty much useless -- for that reason (not just suse's).
However, of all the distros I've used, Arch has done their wiki right. For virtually every package, there is a current *reliable* wiki with fairly complete information from package install, configuration and current issues. There, you are expected to consult the wiki first before posting to the list, because the devs can be reasonably sure the question has already been answered and that the answer is correct.
The package maintainers are responsible for the wiki information and the community fills in the blanks. It works really well.
openSuSE does many, many things right, but one area where it could be improved is having a *reliable* wiki that the community can refer to and be reasonably sure that any current issue has already been addressed there by the packager.
First thought - a wiki-page per package, not a bad idea at all. Second thought - duplication of information? I.e. what does the wiki-page cover that isn't already covered by other easily/publicly accessible information? Usually, a package will have a homepage with some docs, maybe one or two howtos and/or FAQs and plain man pages for the cli utilities and the configuration files.
No flames, this isn't a slam, it is just a recognition that issues like the Thunderbird/Firefox link problem are a perfect candidate for wiki use,
I agree, although I also think that issue really ought to be solved, not just documented. Maybe this thread is best continued on -project? -- Per Jessen, Zürich (0.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org