Hi,
I don't know how useful this is, as RIPE documents don't change once they are published. If a revision of a RIPE document is published it gets a new number. So I don't think a version control system will be useful here.
While that is true, this will still allow anyone to see how PDPs progressed and resulted in new documents.
Now, if *that* history is maintained then I see the value. 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. 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. 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. Thanks, Sander