[Ietf-and-github] WGLC: draft-ietf-git-using-github-02

In section 3.2/3.3, it might be worth mentioning that GitHub has a feature<https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners> for the owners/administrators to give certain user(s) control of individual files, despite the global write access that contributors have.  This means it's possible to configure the SHOULD NOT on GitHub, rather than relying on everyone's good behavior.  I think this configuration should be RECOMMENDED for multi-document repos.

In section 4.0, we should probably include a reminder that, regardless of the from of contribution, all contributions are covered by the Note Well.  (I know that's implied by the term, but it's worth being explicit.)

In section 4.3, is it truly the WG that provides these facilities at the chair's request?  This seems like something that either a) chairs MAY configure independently at the WG's request, or b) something that the IETF would provide at the chair's request.  The latter seems the most sensible, but does represent a requirement for new functionality.

In Section 7, I'm not certain about the "greater time commitment" reasoning.  There is an identical level of traffic coming into your inbox regardless of whether the incoming deluge is e-mail or GitHub notifications.  And in fact, exactly the same discussions that take place on GitHub could take place on the mailing list.  The fact that GitHub facilitates a greater pace of interaction and therefore generates a greater volume of traffic is really what we're alluding to here.  GitHub helps working groups work more quickly, and quicker work risks leaving some people behind.

I second the comment that Section 10 is a bit over-the-top for a document we intend to publish as having IETF consensus.  GitHub doesn't speak IPv6.  This makes us sad.  It's still useful.  Hyperbole serves no useful purpose here.

Appendix A.2 states that the quicwg has only two repos, but it in fact has three.  Another example of the ops drafts being ignored.

-----Original Message-----

From: Ietf-and-github <ietf-and-github-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org

Sent: Tuesday, November 19, 2019 3:02 AM

To: i-d-announce@ietf.org

Cc: ietf-and-github@ietf.org

Subject: [Ietf-and-github] I-D Action: draft-ietf-git-using-github-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

This draft is a work item of the GitHub Integration and Tooling WG of the IETF.

        Title           : Using GitHub at the IETF

        Authors         : Martin Thomson

                          Barbara Stark

               Filename        : draft-ietf-git-using-github-02.txt

               Pages           : 27

               Date            : 2019-11-18

Abstract:

   This document describes best practices for Working Groups that use

   GitHub for their work.

The IETF datatracker status page for this draft is:

https://datatracker.ietf.org/doc/draft-ietf-git-using-github/

There are also htmlized versions available at:

https://tools.ietf.org/html/draft-ietf-git-using-github-02

https://datatracker.ietf.org/doc/html/draft-ietf-git-using-github-02

A diff from the previous version is available at:

https://www.ietf.org/rfcdiff?url2=draft-ietf-git-using-github-02

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:

ftp://ftp.ietf.org/internet-drafts/

_______________________________________________

Ietf-and-github mailing list

Ietf-and-github@ietf.org

https://www.ietf.org/mailman/listinfo/ietf-and-github