Hi,
That said, while I agree that Git is a very good tool, I'm reluctant to micro-manage the NCC by saying «you MUST use Git» (or any other particular tool for that matter).
I agree. If we want something then we should specify *what* we want and give the NCC the freedom to choose an implementation that fits both the needs of the community and of the NCC itself. I personally would like: - a word-by-word diff (not line-by-line) - being able to see the diff between a RIPE document and any RIPE document version that preceded it - being able to see the history of a document with or without the policy proposal versions in between - for every RIPE document change I would like to see what caused it (policy proposal, cosmetic surgery, RIPE NCC, etc) - being able to see the history even for policy proposals that haven't (yet) become RIPE documents - a pony (optional) And we have to remember that not all RIPE documents are policy documents. Working Groups and the RIPE NCC also publish other types of RIPE documents. I suggest we see what we want, and then ask the NCC to give feedback on how they see it, if it is doable etc. Sander