[Ietf-and-github] Simple WG policy for document management

Paul Hoffman <paul.hoffman@icann.org> Mon, 21 October 2019 17:50 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A6D12010F for <ietf-and-github@ietfa.amsl.com>; Mon, 21 Oct 2019 10:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYwPpPZmMoYe for <ietf-and-github@ietfa.amsl.com>; Mon, 21 Oct 2019 10:50:33 -0700 (PDT)
Received: from ppa4.dc.icann.org (ppa4.dc.icann.org [192.0.46.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B7C412016E for <ietf-and-github@ietf.org>; Mon, 21 Oct 2019 10:50:32 -0700 (PDT)
Received: from PFE112-CA-2.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.10]) by ppa4.dc.icann.org (8.16.0.27/8.16.0.27) with ESMTPS id x9LHoU1k003406 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <ietf-and-github@ietf.org>; Mon, 21 Oct 2019 17:50:31 GMT
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 21 Oct 2019 10:50:28 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1497.000; Mon, 21 Oct 2019 10:50:28 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
Thread-Topic: Simple WG policy for document management
Thread-Index: AQHViDgGJXqpIiC34EWv3+9BgJmVcg==
Date: Mon, 21 Oct 2019 17:50:28 +0000
Message-ID: <cb3ba8ae-3518-048f-e7dd-fbe7adfc899a@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.1.2
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: text/plain; charset="utf-8"
Content-ID: <22F7FEF45DF30848B99CF34644CAD000@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-10-21_04:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/UJRON79Ym0AfjngziWK35mnG48M>
Subject: [Ietf-and-github] Simple WG policy for document management
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Oct 2019 17:50:35 -0000

Greetings again. First, a big thank-you to Martin and Barbara for adding Section 5 to https://datatracker.ietf.org/doc/draft-ietf-git-using-github/ . I hope everyone in the WG looks at the revisions in document, particularly this new sections.

The new 5.1 seems limited to me, or maybe I would want an additional level between 5.1 and 5.2. In many WGs, I find that people want to do document management using GitHub but not issue tracking, but they want WG participants to be able to contribute text in the repo instead of just on the list. This is particularly useful for "please add a few sentences about $x" and "that paragraph was unclear, I think this would be better". Thus, I'd like to either see 5.1 be expanded to allow PRs from the WG, or a new section 5.2 inserted that is 5.1 plus WG PRs.

Does this match with what others have found in WGs that are just using GitHub for document management and pre-draft-revision change tracking?

--Paul Hoffman