Christopher Arndt wrote:
Let's put our energy in implementing missing features and documentation instead
of arguing why it's a bad thing that this and that feature/documentation is
missing!
Unfortunately some of us are stuck in the void where you don't know
enough about the system to either use it or write about it. I'm sure it
is possible to get some use out of the code, if you have many hours
free to browse the source and experiment. I don't have that sort of
time. I like clear, well-organised documentation.
Documentation should be done as you go along, not left to the end for
whoever is willing to give it a go. I will politely keep drilling this
into the heads of developers until they listen. :) Until then, at least
I can hopefully make it very clear which documentation are missing,
because sometimes the experts who no longer need the docs have no idea
what the rest of us need.
--
Ben Sizer
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
