What should Zope source code control look like?
Actually, after thinking about this further and discussing it with some colleagues, I've realized that what I need isn't the ability to store Zope objects in a CVS repository after all. It is the ability to use documents already stored in a CVS repository as Zope objects. Ideally, what I need is a Zope product that implements the client side of the CVS protocol, and can allow users to check out, modify, and then commit changes to documents stored in a repository. This seems like a much easier problem to solve than storing Zope objects in CVS. Does anyone know of an existing or planned Zope product that supports this kind of functionality? -jfarr ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Hi! I'm a signature virus. Copy me into your .sig to join the fun! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~