On Wednesday 17 October 2007 19:44:07 Rajko M. wrote:
On Wednesday 17 October 2007 11:41:05 am Josef Assad wrote:
I looked at the separation from the perspective of someone who has something to write up on the wiki and is trying to figure out where it goes. Following your separation definition, I would suggest this as a more concise way to tell if it is SDB or HOWTO:
- If it is reactive (i.e. there was a problem de facto, this is how I solved it) then that's an SDB - If it is proactive (my box is fine, but I'd like to figure out how to do this or that) then this would be HOWTO
Hi Asad,
I vote for your definition.
Yes, very good.
That is what SDB was for me, a solution for existing problem: - summary of bug fix in bugzilla, and link where to pick up patch, or - workaround until bug is fixed - small fixes of default configuration which is not a bug, but needed to run some application
right
Though, IMHO SDB should not be edited at will. It has to be dependable source of information, it should be protected.
Everyone has enough space on wiki to write articles, and when they are good quality and fit in the SDB concept, than it is easy to include them in SDB.
i'm not agreeing with that, i don't want to protect stuff. But yes, this could be an option (actually i'm not sure if you can protect the whole namespace ... dunno). -- with kind regards, Martin Lasarsch, Core Services SUSE LINUX Products GmbH, Maxfeldstr. 5 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) martin.lasarsch@suse.de - http://www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org