On Wed, Dec 17, 2003 at 10:21:03PM +0200, Gil Freund wrote: > Yishay Mor wrote: > > > >>>wow. not that I have any ideas (other than CVS), but just out of > >>>curiosity, what is this for? > >> > >> > >>CVS would be nice if I could get people to use normal editors with > >>normal formats (read *ML) > >>Mainly for myself, and some startups I work with. > > > > > >Some guys get all the right startups! All the startups I was ever > >involved with thought I was the doc mgmt system (as in "dude, you got a > >copy of that presentation we gave the board last september?") > > I only wish.... > > The path usually taken is exactly as you described above. At some point > the technological savvy CxO (the one that reads Dudi Goldman and knows > all the latest technological advances), whats the above system, and I > have to listen to a leacture on the great advances the company would > have if we only had Exchange and SharePoint.... > > > > > > > >> > >>>If you don't find anything existing, I would consider developing it > >>>over Zope / Plone. > >> > >> > >>Thats content management. Different ballgame. > > > > > >Not exactly. Zope is an application server for Python, is provides > >persistence, authentication, workflow and other such services. Plone is > >an web-presentation layer above it. Somewhat like JSP and EJB in the > >Java world. They probably provide all the services you need for a doc > >mgmt system, but you still need the actual "product" that does it. Not a > >bad idea for an OS project. I would check if someone's already thought > >of it. > > > > > >As a Q&D alternative, I've used JSPWiki (.org). Its a wiki (surprise), > >very easy to customize, has several options of versioning, and handles > >attachments. So, I would set up a Wiki page for every tracked file, and > >add the actual file as an attachment. The system saves all attachments > >with the same name as versions, with a nice version table. Locking and > >workflow need to be handled by convention, e.g., edit the hosting wiki > >page & write the document status.
This duplicates information. A way to somewhat reduce the information duplication is to automatically convert the saved documet to HTML and allow presenting it. But still: Should one edit the real document or the wiki document? This also hilights one of the wikis' disatvantages: $WORD_PROCESSOR and $EDITOR are generally better editing tools than $BROWSER . It's nice to have the ability to work from everywhere on the document, but it is nicer to have good editing abilities, auto-save, speller, etc. -- Tzafrir Cohen +---------------------------+ http://www.technion.ac.il/~tzafrir/ |vim is a mutt's best friend| mailto:[EMAIL PROTECTED] +---------------------------+ ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
