Re: [Ietf-and-github] [Ext] Proposed new titles for the documents

Paul Hoffman <paul.hoffman@icann.org> Wed, 11 December 2019 01:10 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 03E38120219 for <ietf-and-github@ietfa.amsl.com>; Tue, 10 Dec 2019 17:10:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 HhniO2eDBEso for <ietf-and-github@ietfa.amsl.com>; Tue, 10 Dec 2019 17:10:07 -0800 (PST)
Received: from ppa5.dc.icann.org (ppa5.dc.icann.org [192.0.46.78]) (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 9B1A012008C for <ietf-and-github@ietf.org>; Tue, 10 Dec 2019 17:10:07 -0800 (PST)
Received: from PFE112-CA-2.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.10]) by ppa5.dc.icann.org (8.16.0.27/8.16.0.27) with ESMTPS id xBB1A5cZ025665 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <ietf-and-github@ietf.org>; Wed, 11 Dec 2019 01:10:06 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; Tue, 10 Dec 2019 17:10:03 -0800
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; Tue, 10 Dec 2019 17:10:03 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
Thread-Topic: [Ext] [Ietf-and-github] Proposed new titles for the documents
Thread-Index: AQHVr7+3yZrECLVXGkW/jNu9S6+jdA==
Date: Wed, 11 Dec 2019 01:10:02 +0000
Message-ID: <F5BAEDE7-8320-493B-BE09-8963BC96F19D@icann.org>
References: <CEAC58BE-B06F-4CD4-AE7C-0386A27DAAFD@icann.org> <6A776595-DF05-4406-83DB-1EAEF77FDC09@mnot.net>
In-Reply-To: <6A776595-DF05-4406-83DB-1EAEF77FDC09@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
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: multipart/signed; boundary="Apple-Mail=_F141F0FD-8065-4D86-95C1-6E145B14D3A4"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-12-10_08:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/GBgZGBORbLHo0LeXCerl_uWqS00>
Subject: Re: [Ietf-and-github] [Ext] Proposed new titles for the documents
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: Wed, 11 Dec 2019 01:10:09 -0000

On Dec 10, 2019, at 5:01 PM, Mark Nottingham <mnot@mnot.net> wrote:
> 
> I think these are marginally better; the delineation between the documents still isn't great.
> 
> That said, the suggested titles are pretty dense. Did you consider something a bit more explanatory / active, like:
> 
> Using GitHub in IETF Work: Advice to Administrators
> Using GitHub in IETF Work: Suggested Working Group Polices and Practices
> 
> ?

No, but these look fine to me. Wordy RFC titles are generally fine.

--Paul Hoffman