[ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
Jim Reid jim at rfc1035.com
Fri Mar 15 22:46:14 CET 2013
On 15 Mar 2013, at 21:23, Richard Hartmann <richih.mailinglist at gmail.com> wrote: > If RIPE NCC receives the proposal/update as simple text file, it > should import that data into git (retaining author information) and > commit the result NO! A million times no. First, git may well be the flavour-of-the-month as a version control repository/system today. It won't be in the future. What happens then? Next, this could force EVERYONE to use some git client. The NCC's supposed to be neutral. It should not get into the game of requiring the community to use specific tools or software. Just because some people have a git-shaped hammer doesn't mean every problem in the area of version control and document management has to be made to look like a git-shaped nail. You also appear to be defining outcomes before the requirements are agreed. Or even clear. Let's first understand what problem needs solved and then decide what's the best way to solve them.