Eron Lloyd wrote:
I too, would also like to assist in making sure that Zope3 is well-documented from the start. Particularly the API docs. If you look at projects that are very well documented, like QT, you can understand a large part of the reason why they are quite successful. This would guve me a chance to better understand the new code, too. A good living document that I always wished I had was an explanation of the code's structure, where config files and persistant storage folders are, etc. Looking at the CVS checkouts, it looks to be *much* different in Zope 3. Just list some things that need work, and I'll see what I can do.
OK, I'll get back to you. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (888) 344-4332 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org