On 03/31/2011 12:47 PM, Per Jessen wrote:
First thought - a wiki-page per package, not a bad idea at all.
Exactly - not just rpm -qi info either... A monkey can get that information. The information that is needed is: - distro specific install and config - normal links to rpms, etc. - advanced configuration usage - that we all do, and have to find each time - current issues - packager contact (yes - that's rpm -qi :)
Second thought - duplication of information?
There will be to some degree no matter what format you use. The key here is make it distro relevant - otherwise you can google it. Second point - the package wiki page should pretty much be a "one stop shop" for information on that package as it relates to the distro.
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.
Couple of examples: Cups: https://wiki.archlinux.org/index.php/Cups Xorg: https://wiki.archlinux.org/index.php/Xorg There is just a loose basic look you are supposed to follow - nothing hard and fast - it is left to the packager or contributor to format the page in an intelligent manner. It works fantastically. Giving the user/community a bit more control of how they add and contribute information really imparts a bit more ownership of the resource on the user and IMHO results in a better product because the user takes that bit of extra effort in making sure their work product is something to community can rely on.
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?
5 hours and twenty minutes later - my contribution to the openSUSE Thunderbird wiki posting Wolfgang's help is still: "Changes will be published once an authorised user reviews them. The draft, shown below, contains 2 pending changes. Return to page section named "Links in Thunderbird do NOT open in Firefox". " It will be yesterday's news by the time the changes are actually reviewed and committed. Christian, all Novell folks -- this policy really has to change. It really leaves the user with the feeling of "what's the point of trying to get info up on the openSUSE wiki? -- it will be days before somebody looks over your shoulder to make sure you did it right...." Talk to the powers that be. Removing the "review before commit restriction" is probably the #1 thing Novell can do to spur community involvement. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org