[ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
Richard Hartmann richih.mailinglist at gmail.com
Fri Mar 15 22:50:07 CET 2013
On Fri, Mar 15, 2013 at 10:35 PM, Sander Steffann <sander at steffann.nl> wrote: > 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 would not mind changing the proposal that way; I am confident git would win, anyway. Using anything else today would be weird at best. > I personally would like: > - a word-by-word diff (not line-by-line) See my initial email. word-by-word can be ambiguous. PDPs must be explicit and without doubt of the underlying data. Offering word-by-word as an optional extra to line-by-line diffs would be trivial, though. And you could even do so on your own client, have it color the diff the way you want, etc etc. > - being able to see the diff between a RIPE document and any RIPE document version that preceded it Trivial on CLI, may not be doable on web without minor updates to gitweb/gitolite. You will need both filenames. > - being able to see the history of a document with or without the policy proposal versions in between Trivial on CLI, may not be doable on web without minor updates to gitweb/gitolite. You will need specific commits or, better, tags. Every finished PDP can simply be tagged. > - for every RIPE document change I would like to see what caused it (policy proposal, cosmetic surgery, RIPE NCC, etc) That's what the commit message or the tag message is for. Plus, _every single copy_ of the document set (i.e. git repo) would carry all that info. > - being able to see the history even for policy proposals that haven't (yet) become RIPE documents Trivial. `git pull; gitk --all` > - a pony (optional) Sadly, you missed the time window in which every Ikea offered horse kotbullar. > 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. True. Maybe focus on policy documents for now? > 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. Should we do that in this early phase or later? I would prefer early. Richard