[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xmile] version control for Spec documents
Hi Bobby, My belief, and perhaps others do not agree, is that we can subdivide our final document into a relatively small number of pieces and assign authorship control of those pieces to one or two individuals at a time (essentially between meetings). Currently we have identified 5 pieces, and that might grow to 10 or 12, but I don't see it getting bigger than 20. With that approach there is never any issue of merging content, since the editors of each piece are clearly identified. If two people are working together on a piece then they can use whatever form they want to do so (track changes, google docs...). That editing is not being presented to the committee as a whole and need not be kept with the documentation records for the committee. When they finish editing to the point of wanting to share, that document then needs to be uploaded to oasis. I think this approach is both simple and practical. Allowing more people to change more things is necessary in code, but could be problematic in writing a spec. It seems more sensible to communicate how and why things need changing to the people holding the pen on the section needing change. If they disagree, or have a different idea, it could save a lot of rework and prevent unpleasant surprises. Bob Eberlein On 9/3/2013 10:13 AM, Bobby Powers
wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]