On Nov 19, 7:53 am, mdipierro <[email protected]> wrote: > True But I can keep track of that from the changelog and the date. > Eventually I will do that if nobody beats on time. > > Catching bugs in the book is more important because I never read it so > I do not see them.
I have very little time available, but what time I have been able to wrest away from my other responsibilities, I have put into improving the book. I really like this framework. Unfortunately, I don't manage to read every single message in the group as I would like, in order to catch opportunties for fixes to the docs. Other editors/posters/devs: if you see a thread in which a fix to the docs is suggested, or necessarily implied, please feel free to email that to me directly. I don't mind receiving such messages even if I have already seen original thread. As a general comment, it always puzzles me that in many open source projects, the documentation is poor. I have always found that documentation is something that a newbie can immediately begin to help out with, whereas it requires much more experience with the code to be in a position to make code fixes accurately and safely. Moreover, newbie involvement with documentation is especially useful precisely because their lack of experience is intended to be addressed by the documentation itself. In other words, it is the newbie that can recognize as quickly, or perhaps even quicker than the expert, when the documentation is poor in places (though not necessarily factual accuracy issues).
