> Unfortunately, it's much easier to get people to contribute code than > it is to get anybody to contribute docs of any sort. All of my > personal coding time since October has been spent writing these docs. > I've been busy with work this past month and busy with the holidays in > December.
Yes, this is always true. But, there could be a policy in place saying that if you don't provide at least a starting point for docs, your contribution doesn't go in to the release. Then after that others will at least clean them up, which is a *lot* easier for someone like myself to do than to start writing new docs. I can edit someone elses docs while learning a platform, but I am not going to write any new ones if I feel my understanding is incomplete. A policy like the above is used in Csound, and works very well. You don't write a manual entry and programmer docs: your new opcode or extension doesn't go in the canonical branch. IMHO a firm policy is the only thing that prevents undocumented feature creep. > Contributions are always welcome. It's a cliche response, but we're 2 > for 3 in converting rants to doc editors (myself and Christopher > Ardnt). Well, rants come from new users who are stumbling. They won't write docs until they are sure they won't mislead others. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
