On Saturday 28 March 2009 02:44:21 pm Sven Burmeister wrote:
Given the resources, developers will focus on developing and leave the rest (support and docs) to the non-developers.
It doesn't actually matter, how thick or thin are resources. Coders are skilled to code, that is what they do the best. Taking how much time is needed to acquire that skills, it is waste of their time to do more than to proof read, giving comments on technical correctness of docs. That is how it works everywhere software is created. This is Ann Wilson signature: "New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase." Concise way to say how it should be in opensource. I would use opportunity to call people to read our wiki and contribute. Every little bit is help. Take article and correct grammar, it is help. One article in a year, it is fine. Write draft for some article, it is big help. Write whole article, it is awesome. Think of structure of index pages, give proposals how to make topic more accessible from new user, or expert, perspective. What words to use, how to organize information. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org