On Fri, Mar 15, 2013 at 9:12 PM, Sander Steffann <sander@steffann.nl> wrote:
Now, if *that* history is maintained then I see the value.
Of course it would be.
Seeing that a RIPE document is based on an older document, seeing which proposal changed it (from the commit message) and seeing the differences between them might be useful for some.
And visualizing those differences is laughably easy with git.
It might even be useful to maintain this for policy proposals to keep track of the proposed changes. The final version of the policy proposal could then be copied to the ripe-documents section.
That is the basic goal of this proposal. All changes during a PDP process are simply one patch for every update. Once the PDP changing document 123 gets approved and results in 124, the final commit in the branch is a simple `git mv 123 124` and is then merged into master.
Hmmm. It might be much more than we need, and rsync might be enough for what we need, but I can also see some benefits now.
I have noticed this particular proposal growing on people over time several times over the few months I bounced it around on IRC. Richard