HTCondor Project List Archives



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-devel] How/when to write a Design Document



On 10/23/2012 06:17 PM, Alan De Smet wrote:
Timothy St. Clair <tstclair@xxxxxxxxxx> wrote:
Why attach a separate MSFT.doc to a ticket, vs. making the
ticket be the design doc, and having all the sections you
mentioned?

Agreed.

A Word document adds unnecessary complexity.  You can run into
compatibility issues (be sure to save in Word 2003?).
In-document revision control may not work to varying degrees
depending on the software used and the configuration.  Resolving
conflicts if multiple people edit simultaneously is far clumsier
in a Word document than in a Wiki.  (Not that CVSTrac is great at
conflict resolution, but worst case you can extract the
unformatted text for the versions in question and do a merge in
your favorite 3-way merge tool.)  The mere existence of multiple
copies creates the possibility of accidental forks.  Keeping the
document self contained is a matter of discipline, moving the
documentation to its own file is only a marginal help.

Other proposals, in my order of preference:

1. The design document should be the "Description" section of the
ticket.  That the Remarks may grow without bound is irrelevant,
since you only need the Description at the top.  The document can
and should be updated to reflect reality.  This eliminates any
redundancy, the design and current plan are in one and only one
location.  Someone interested in older information can look in
the History, which is kinda sucky (it's diffs), but good enough
given how rare doing so is.

+1

And if you care about Remark clutter, they can be integrated into the Description and pruned.

Approaches storing the document in the repository do not allow for participation by non-committers.

There is value in maintaining information in one location.

Best,


matt