> You may also find our documentation process interesting:
> http://www.zope.org/DocProjects/intro

Yes, very interesting!

But I'm sorry to see that the Developer's Guide is only in the planning
stages.  Here is some info that should go into it (from our Zope notes

This section explains the directory structure you'll find when
you unpack the Zope 2.3.1b1 source tar file.

Root directory:

Extensions/  code for External Methods go in this directory
ZServer/     python code for ZServer and medusa (see the README.txt)
doc/         documentation (especially INSTALL.txt)
import/      used by the running Zope process to import objects into the
inst/        installation scripts
lib/         python library (most of Zope's code is under here)
pcgi/        C and python code for PCGI (see the README)
utilities/   random utilities (see the README.txt)
var/         contains the FileStorage for the ZODB (Data.fs)
             and various other files (logs, pids, etc.)

LICENSE.txt  Zope Public License (ZPL) Version 1.0
README.txt   general information about the Zope source release

w_pcgi.py    scripts for setting up Zope with PCGI
wo_pcgi.py                               without PCGI
z2.py        the start script for Zope
zpasswd.py   create or change the Zope emergency account and password


Components  python extension modules written in C
            - BTree, ExtensionClass, cPickle, zlib
python      everything else


Most of the Zope code is in here.

Fred Wilson Horch                       mailto:[EMAIL PROTECTED]
Executive Director, EcoAccess           http://ecoaccess.org/
P.O. Box 2823, Durham, NC 27715-2823    phone: 919.419-8354

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to