Diana Shannon wrote: > > Ok. I agree. I guess I was (naively?) hoping to build in more QA > (quality assurance), incentives, and ownership into that working > model -- whatever it turns out to be. I was seeking inspiration from > technical documentation practices that deal with similar challenges in > other rapidly changing fields. Open source projects are not alone with > this problem. > I really love to have more QA for the docs, so basically this a good idea.
> Believe me, I have doubts about my own approach too. I'm not trying to > "argue" with anyone, just increase my limited understanding. It's hard > to start contributing to Cocoon in this capacity. There's no existing > model to follow within Cocoon, so I wanted to get as much > feedback/advice as possible before starting. I think this is one of the things that work better the other way round, which means one should start by contributing single small pieces in areas he/she has understood. The community appreciates any feedback, regardless of it's size, and if the community sees that one is interested and trying to help, the community helps this person more than a totally foreign one. So this person gets to know more and more pieces up to the big picture. But first trying to understand the big picture before contributing anything is very difficult for both sides. I hope my english is good enough for this explanation :) So, in the end, just keep on with your good work and let's see what happens. Carsten Open Source Group sunShine - b:Integrated ================================================================ Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn www.s-und-n.de mailto: [EMAIL PROTECTED] The new weblog homepage: http://ziegeler.bei.t-online.de ================================================================ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
