repository with revisions and verson control
Hi, I'm working on project where the implementation of some kind of repository for various types of documents is necessary. The main features to implement for this repository are: - version control: - history - reviewing - undoing changes - rolling back to any revision - immediate (read only) acces to every revision - files locking Each change made to a single document should be writen as a single revision for this object only (CVS like bechaviour) and where rollbacks and locking must be possible for each, single object where is possible. The repository will work through independent interface created in project and not through ZMI. I'm relatively new in Zope and Python. I understood the general concept of ZODB and it's long transactions (which seems to be a base for repository like projects). I've checked OFSP and it's Version support... nice idea but unfortunately I'll need to create a private sesion for each accesed document... it does't looks like solution rather like workaround. Also the project seems a bit abandoned (vide http://dev.zope.org/Wikis/DevSite/Projects/ZopeVersionControl/CurrentStatus). The concept of my project is closer to CVS like system than to one presented in OFSP. I'm strongly determined to implementy this in clean Zope/ZODB. I don't want to loose the benefits of object database (i'll loose it in CVS solutions) because in future the features like ZOE and e.g. DirectoryStorage will be very handy for me. Is there a way to implement such thing in easier way than writing the support for using ZODB transtactions in project from scratch? Best regards, -- Adam Szpakowski Silesian University of Technology - Institute of Physics Department of Optoelectronic e-mail: worf@optics.polsl.gliwice.pl
I'm working on project where the implementation of some kind of repository for various types of documents is necessary. The main features to implement for this repository are: - version control: - history - reviewing - undoing changes - rolling back to any revision - immediate (read only) acces to every revision - files locking
... I've checked OFSP and it's Version support... nice idea but unfortunately I'll need to create a private sesion for each accesed document... it does't looks like solution rather like workaround. Also the project seems a bit abandoned (vide http://dev.zope.org/Wikis/DevSite/Projects/ZopeVersionControl/CurrentStatus). The concept of my project is closer to CVS like system than to one presented in OFSP.
...
Is there a way to implement such thing in easier way than writing the support for using ZODB transtactions in project from scratch?
The OFS 'Version' is really a (possibly soon-to-be-reomved) site-admin tool. As you noticed, they won't help you much in your search for revision control. The Zope community seems to have decided that it's best to pursue revision control outside the ZODB, which makes sense to me. The ZopeVersionControl project does this, and while I don't know how useful it is on its own, it forms the backbone of a real revision-control system in the form of CMFStaging. Since you're in the realm of content management, you really need to head on over to the CMF world. Add CMFStaging to CMF and you've got most or all of the above requirements covered. For a more polished and complete distribution/implementation of the Content Management Framework, there's Plone, which will probably ship CMFStaging in the next release. And although you don't seem so keen on CVS, there's even an (unfinished) CVS-backed versioning for CMFStaging in the Collective. Links! http://cmf.zope.org http://cvs.zope.org/CMF/CMFStaging http://plone.org http://sourceforge.net/projects/collective --jcc
On Wednesday 18 of June 2003 22:41, J Cameron Cooper wrote: Thanks for Your informations. They were extremly helpfull but I have still few questions. Last time You wrote:
The ZopeVersionControl project does this, and while I don't know how useful it is on its own, it forms the backbone of a real revision-control system in the form of CMFStaging. Since you're in the realm of content management, you really need to head on over to the CMF world. Add CMFStaging to CMF and you've got most or all of the above requirements covered.
I read the ZVC Wiki page and its Vision Statement. Sounds great but unfortunately the project seems a bit dead. There are also CFMStaging and PloneStaging projects. From what i learned it seems that CMFStaging rise as a project for some commercial client and not as a general solution for Zope. It's very strictly corelated with CMF (support for skins, workflows and such) and is quite poorly documentated (only some discusions on CMFStaging from last year). The PloneStaging project is in my opinion aimed for close Plone support. The last two days which I spent reading documentation and browsing the sources gives me one question. What is the future for version control in Zope and CMF? Is CMFStaging projected to be a general solution for version control in CMF? And is there any documentation for it (beside sources and some discusion on the list last year)? Regards, -- Adam Szpakowski Silesian University of Technology - Institute of Physics Department of Optoelectronic e-mail: worf@optics.polsl.gliwice.pl
participants (2)
-
Adam Szpakowski -
J Cameron Cooper