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

[Brad Hards]

Richard Bos wrote:
> 
> Please put koffice@kde.org on the To or Cc in you want to discuss these
> things.  That's the only way to know whether these things will be possible at
> koffice level.
Done.

For those that came in late, the originating story line is that the kplato
(Kde PLAnning TOol) mailing list identified that document revision control was
a pretty key requirement for the "plan" document, to deal with change history
through a project. My point was that you want to track more than just the
"plan" at key change steps, in fact you really want to track an arbitary set
of documents which are functionally linked (and maybe electronically linked
too). So it needs to be at a higher level than a single package.

I don't see how it _can't_ be possible. We are only talking about a system
that can takes documents of various revisions, tags them, and regurgitates on
demand.
Nice front ends aside, it already exists as CVS, RCS, CVSup, etc. Those may
not support the formats that make sense for KOffice, since KOffice documents
are not source code, but parts could be used / reused. Also, there might be
significant efficiency savings for particular document formats - maybe
something like the algorithm used by gzip --rsyncable could be used in
general.

So I wonder if others have looked at providing configuration management
facilities for documents within KOffice, or had ideas for other suitable
tools, even without the nice front ends.

Brad

> On Tuesday 19 June 2001 10:20 pm, Brad Hards wrote:
> > I think that versioning support is critical, but that it is inappropriate
> > to do it natively. In the typical project example of versioning (contract
> > change), there is a lot more that needs to get "configuration managed" or
> > "versioned" than just the scheduling / planning tool. For example, the
> > change pages for the contract, the subcontracts, the cost breakdowns, the
> > engineering changes, etc, etc, etc.
> >
> > It should be supported at a KOffice level, rather than a kplato level or a
> > task/subproject level.
> _______________________________________________
> kplato mailing list
> kplato@master.kde.org
> http://master.kde.org/mailman/listinfo/kplato