IETF Logo Mail Archive

Re: [Ietf-and-github] Anecdotal appendices in draft-ietf-git-using-github

"Salz, Rich" <rsalz@akamai.com> Wed, 04 December 2019 15:57 UTC

Return-Path: <rsalz@akamai.com>
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 344FB120025 for <ietf-and-github@ietfa.amsl.com>; Wed, 4 Dec 2019 07:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 kUN-Gze5PxG8 for <ietf-and-github@ietfa.amsl.com>; Wed, 4 Dec 2019 07:57:27 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 24D97120019 for <ietf-and-github@ietf.org>; Wed, 4 Dec 2019 07:57:27 -0800 (PST)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id xB4FsRCL016636; Wed, 4 Dec 2019 15:57:26 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=bCASEtvVki8C9ZCbWtWUzjhTZNXJyFIMrqtA+MBFzvc=; b=E/mFL8IxgI/l3okcwgTQc3vjQROqhrtuaJWRygvbgoZGF7k5LS3OvY5Ih5FVpxSOT9KS J3yGjU9vRir1t8JkvKItLVXSUJ8obN1T/mnqpU3/1jDS00UF7E9k4rZn4AwXl/bcFqrT KsPuHiUoAICNYUxaGWsNXE5xc8YX8w2NLCfRnv/PK8xRqTX0e8mO+kJTFjNvJWieb/Cf QKixWk4iBj/z3057/G8DzMAALp47mlKhANYrO1VswlAlPUPMwL/XSXpLuXHtr9Wg0rp8 f61hjWBi8ffzehDipz9N11FMt5bfign/zn5/rfHmIJ57KLSJvwK39pGiW0eDRRiP10xs Vw==
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 2wnk65xbg6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 04 Dec 2019 15:57:26 +0000
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xB4Fl5AC030329; Wed, 4 Dec 2019 07:57:25 -0800
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint5.akamai.com with ESMTP id 2wkq9b8epj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 04 Dec 2019 07:57:25 -0800
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 4 Dec 2019 10:57:24 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([172.27.123.103]) by usma1ex-dag1mb3.msg.corp.akamai.com ([172.27.123.103]) with mapi id 15.00.1473.005; Wed, 4 Dec 2019 10:57:24 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Martin Thomson <mt@lowentropy.net>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
Thread-Topic: [Ietf-and-github] Anecdotal appendices in draft-ietf-git-using-github
Thread-Index: AQHVqmFzmQcvcuVnYE2QPPIK1gF4DqeqIkWA
Date: Wed, 04 Dec 2019 15:57:23 +0000
Message-ID: <FCC37441-51E1-4E00-929A-918ED1D01FE0@akamai.com>
References: <f09ab496-1ee8-4dcc-ba0f-c483ddefe5a6@www.fastmail.com>
In-Reply-To: <f09ab496-1ee8-4dcc-ba0f-c483ddefe5a6@www.fastmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.20.0.191202
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.117.81]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8FA16E15A373284D9A49327B859D066F@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-12-04_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=957 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1912040131
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-04_03:2019-12-04,2019-12-04 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 priorityscore=1501 phishscore=0 mlxlogscore=925 clxscore=1015 lowpriorityscore=0 adultscore=0 impostorscore=0 mlxscore=0 suspectscore=0 spamscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912040132
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/TCmDH3k22_L8Ij0-IjlKKTGGFm0>
Subject: Re: [Ietf-and-github] Anecdotal appendices in draft-ietf-git-using-github
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, 04 Dec 2019 15:57:29 -0000

>    I've never really known what to do with these sections.  As input to the process of this working group, they are useful, but I'm not sure how much value we get out of creating a publication with this content.

Other groups have done 'use cases' drafts that are never intended for publication; that seems to make sense here.

v2.23.0 | Report a Bug | By Email