This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ncc-services-wg@ripe.net/
[ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All PDP emails, documents and websites should come with unified diff"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Hartmann
richih.mailinglist at gmail.com
Fri Mar 15 20:13:36 CET 2013
Dear all, this is the fourth suggestion: All RIPE documents are made available by means of a git repository, both via anonymous pull and via a web interface. The read-only access is open to everyone, RIPE member or not. Within RIPE, this git repository is the canonical place for all published documents. All published documents are copied from it. All PDPs will be maintained as a separate branch. Every new version of a PDP is an update within that branch. The branch will either be merged back into master or left unmerged but intact, depending on if they are accepted or not. Old documents and PDPs, if still on record, will be put into separate branches that reflect correct history. The master branch is then merged into old history, creating one single history. This will happen one year after this policy comes into effect at the latest. If the proposal "All PDP emails, documents and websites should come with unified diff" is accepted, all diffs will be generated from git. Rationale: git is here to stay, it's highly efficient, allows off-line work, and has generally won the fight for version control systems in the foreseeable future. Not relying on technical tools which were created with ever-chaning text files in mind is inefficient at best. I offer to help maintain said git repository pro bono for at least 12 months or until the history has been merged, whichever is later. Richard PS: Think of those five emails as a patchset ;)
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All PDP emails, documents and websites should come with unified diff"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]