[kplato] Fwd: Re: [kproject] Planning and Analysis 101

[Anders Johansson]

We definitely need a versioning system, and CVS is as good as any. In fact, 
since it is so widely used in the open source community, it may be better. 
One problem I have with it, though, is locking. Resolving conflicts may be a 
fun way to spend a sunday for some, but I prefer a system with file locks.

Thoughts?

Regards
Anders

On Monday 18 June 2001 22:03, Richard Bos wrote:
> ----------  Forwarded Message  ----------
>
> Subject: Re: [kproject] Planning and Analysis 101
> Date: Mon, 18 Jun 2001 21:43:23 +0100
> From: shaheed <srhaque@iee.org>
> To: koffice@max.tat.physik.uni-tuebingen.de, "Michael Ansley (UK)"
> <Michael.Ansley@intec-telecom-systems.com>
>
> On Monday 18 June 2001 10:09 am, Michael Ansley \(UK\) wrote:
> > Well, I'd actually thought about having a CVS tool for KWord, rather,
> > because, at first glance, it seems a better way to handle the whole
> > thing.  Unless there is someone else looking at a CVS ioslave ;-)
> > I'm not sure that the storage paradigm works that well for CVS.  I
> > mean, even when you use CVS, you still have separate local storage
> > (working directory), you wouldn't work directly to/from the
> > repository.  Anybody with other thoughts/ideas?
>
> Not sure if noone read this, or if everyone thought it was a stupid idea
>
> :-)
>
> http://lists.kde.org/?l=koffice&m=99239761303912&w=2
>
> Basically, my idea is either to come up with a generic mapping for a DOM
> into a relational database that could be used for arbitrary koffice
> documents  - perhaps there is a standard for this already?
>
> And if this does not work, then at least a well defined mapping for
> kproject's DTD - there is at least a somewhat obvious mapping for a task
> list into a spreadsheet.
>
> Thanks, Shaheed
>
> -------------------------------------------------------