Use of github for draft-ietf-6man-spring-srv6-oam WGLC

otroan@employees.org Wed, 18 December 2019 13:57 UTC

From: otroan@employees.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Use of github for draft-ietf-6man-spring-srv6-oam WGLC
Message-Id: <2F716D74-DE14-43CF-B507-A58E84A3CCCF@employees.org>
Date: Wed, 18 Dec 2019 14:57:06 +0100
To: 6man WG <ipv6@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/l9WxpuON74JrVJ-8QJ5IugXoynw>
Precedence: list

All,

During a working group last call, there are many comments and issues brought up on the mailing list.
It is not easy to keep track of the issues raised, and how they map into actual changes in the document.

For the SRH document we used the IETF issue tracker, but found that didn’t work very well for a variety of reasons.

Using source control management has benefits, e.g. tracking of changes, focus discussion on the actual document text, give change control to the working group, improved tooling, and so on.

We want to encourage people to complement a last call comment on the list with actual text changes represented as a pull request against the document.
This is an experiment and voluntary.

All discussion about the document change must happen on the working group mailing list (not as comments on the pull request).

The SRv6 repository is here: https://github.com/ietf-6man/srv6-oam

See also:
https://tools.ietf.org/html/draft-ietf-git-using-github-02#section-4.2
https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests

If you are unfamiliar with use of git/github, it's a little bit of a learning curve.
In essence you need to fork the repository, clone your own copy, make edits, push changes, and create a pull request.

Best regards,
Ole & Bob, 6man co-chairs

Use of github for draft-ietf-6man-spring-srv6-oam… otroan