From nobody Mon Apr 1 05:49:34 2019 Return-Path: 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 9F5E2120120 for ; Mon, 1 Apr 2019 05:49:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.749 X-Spam-Level: X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 4lc3B71H4UP8 for ; Mon, 1 Apr 2019 05:49:31 -0700 (PDT) Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0209312011D for ; Mon, 1 Apr 2019 05:49:31 -0700 (PDT) Received: by mail-yb1-xb33.google.com with SMTP id s7so341090ybo.3 for ; Mon, 01 Apr 2019 05:49:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=hOEKBIQN4OJ3QCTvB56j4AY6JpFX6wIOXhBncyC8aak=; b=p2Ikb5CDjdxwSCCPPYU4608Op6H0con7SRS0y9J8Q6MEiUHlhZtV9vDe46j3S0TFKj WLyKbbad/1o+RyDlfVcSyvSAGiPNtXvQgziedf8FgXX7FUb2xoqsfnTFSVXeJChD/aU6 kydLue1N0QUfxtm6ScEczXPVT+svy1mci+GkRA6G9A94/6D8J3rzfPFtPrHcDoh/YITB K6QJa5XAtJrq50x2qH/ryb9HS9UnXHzYTHR2UFriMvkXhl3zQQIH394N5AlrehBsmNDU Iy1diznUcU7E5tJd2cnaO9q5DdJqv2i2XNO6QpCYkzDJb05fSuHnZxfG98BFvUo7eU8Y pYsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=hOEKBIQN4OJ3QCTvB56j4AY6JpFX6wIOXhBncyC8aak=; b=dVG7pch4xQpfdBJCNZxfcZ4emG8gKf3gCsO0fbNIm80vBXtQDHHvbscMWCii6wNVHM LvjyMGaulPT2dJ/2uEFl5SDkiqMDDrdXUuep5RoLKbCeUMb4WWFZA0widWOGqGoNFXeO XEfA4HMgVg+hxkq4IM+HJwEQh2ewRcx688cjsmmqqlA7oROeq1sifhEHuLzglBrrFBMN kLkgN4l1OMHNvp6ZtSmYmKS5TVee/6msk7wv+QO2EQsi3qmn69pdbmDckkgDlY2rKmSK OaxY7cXtseAq5YXZIno33I3lTJOUkqfIfRMs+XaKvejwf9ddSH4QRWkA4zDfJKCNtpP1 QaLA== X-Gm-Message-State: APjAAAW+0+BNlZSelJ02yKsrMQdHDDUbMO3qRV5rTLa75eups/cgOBWc 9tkfux6ladsrsfU2HHtiaVpTsDvGDmp8pFbjZ7cp7Zy/ X-Google-Smtp-Source: APXvYqwlEUTMQpWv7JQVq9T+3hajjyzzVoVIAVyEZ0HHW2VwCqE4vycL01jyk/9qc6+u6HOvWejzCF+ONJljQTN2GVY= X-Received: by 2002:a25:bb8a:: with SMTP id y10mr13065537ybg.168.1554122969774; Mon, 01 Apr 2019 05:49:29 -0700 (PDT) MIME-Version: 1.0 From: Christopher Wood Date: Mon, 1 Apr 2019 05:49:09 -0700 Message-ID: To: ietf-and-github@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Ietf-and-github] Meeting minutes from IETF 104 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Apr 2019 12:49:33 -0000 Minutes from last week's GIT meeting in Prague are now online [1]. They're also copied at the end of this message. Please have a look and send any issues to the list. Thanks to Matt Miller for taking notes! Thanks, Chris [1] https://datatracker.ietf.org/doc/minutes-104-git/ ---- 2019-03-28 @ 11:50-12:20 CET Congress Hall 3 (LL) ## Administrivia ### Do we want to use GitHub? * "duh" * Keep (as best as possible) substantive discussion on the mailing list ### WG Tools and Projects * What other tools would help WGs? - Wiki for capturing ideas and info - We should document existing tools to improve understanding their use - We should document the entire process to improve understanding their integration - Many in room willing to help improve and maintain documentation ## GitHub Configuration for IETF Working Groups * Need resolve duplication between this document and draft-thomson-git-using-github. ## Using GitHub in the IETF * Worth documenting details with the time that it was valid * Some discussion in the document for how to evolve would be useful * How to deal with these drafts and changes in tooling / processes - This can document the guidelines that WGs maintain their details - Find a way to conceptually separate the static pieces from those that are dynamic - This document can remain an I-D - There are efforts in IESG to define living documents * Is there a good sense of normative vs. informative? - Having a higher level (normative?) document and keep more concrete information here * On advice on consensus (on how and when processes are put in place) - Note that having an issue does not mean it must be discussed in the working group - Issues do not reflect the consensus of the working group - (QUIC started using project boards to help evolve processes) - If splitting "light vs heavy" description, then move this advice to the "heavy" - Keeping this information can be useful to newcomers to a WG and is helpful for newly forming or new-to-GitHub WGs * **Adoption of this document?** -- consensus in room to adopt, and chairs will confirm on the list - Note that the document can change radically - Change "heavy" to note it is an option - Chairs will take this to for their contributions * **Volunteers to co-author?** - Chairs will solicit for volunteers to co-author - Mike Bishop offered to help * Suggested next step is to break out the concrete actions make sense - If valuable, progress both this document and an update to BCP 25 - Charter states that "not changing existing processes [BCP 9]", while the discussion is about adding to the processes - Actual changes to processes is not within scope for this working group From nobody Tue Apr 9 08:23:43 2019 Return-Path: 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 682F6120864 for ; Tue, 9 Apr 2019 08:23:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.337 X-Spam-Level: X-Spam-Status: No, score=-1.337 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, HTML_MESSAGE=0.001, KHOP_DYNAMIC=1.363, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 2MRTtlsUwhz7 for ; Tue, 9 Apr 2019 08:23:40 -0700 (PDT) Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::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 7AFDD1200B1 for ; Tue, 9 Apr 2019 08:23:40 -0700 (PDT) Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x39FLxib030981 for ; Tue, 9 Apr 2019 16:23:40 +0100 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 : mime-version; s=jan2016.eng; bh=7m6LUQPwa+JldDDmRO6k1kwXTo2PecTYCkAotSLeDuU=; b=S2pnxPU3mGAMS3FKRnrRcV9cKxiAGm1yxpnlQOgfMdntC4sZnKhdlQlQHt2iwrysZdhP Ys6UBCV1p0/Y70J1v3NdV6Qh112mc9P8siR2f1z/ySWP+glf660EEL90tGyrgMJamrmb Z15AzO/6lDj/guek0PsJ71q4DI8I1fDlOLlVO/um1PULdHQyCy9OH23wKMWwh0AQQ/1e BDZtlkaEq4108K2D3eek42sRi69NPC73m7/fGrQAJLoFToJ2nKyzhWnoAZsvz9wz5v2G KuH204mNlTbntXOts+QRx2uqbtUyt1IIhSj2n9wkGnTMleRIwCTKe8xYW6eQvs0z53tz ww== Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by mx0a-00190b01.pphosted.com with ESMTP id 2rrnm21y40-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 09 Apr 2019 16:23:39 +0100 Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x39FHQds011289 for ; Tue, 9 Apr 2019 11:23:38 -0400 Received: from email.msg.corp.akamai.com ([172.27.25.31]) by prod-mail-ppoint2.akamai.com with ESMTP id 2rpqevfbj0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for ; Tue, 09 Apr 2019 11:23:38 -0400 Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.27.101) by ustx2ex-dag1mb5.msg.corp.akamai.com (172.27.27.105) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 9 Apr 2019 10:23:37 -0500 Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.6.131]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.6.131]) with mapi id 15.00.1473.003; Tue, 9 Apr 2019 10:23:36 -0500 From: "Salz, Rich" To: "ietf-and-github@ietf.org" Thread-Topic: YANG Model Formatting Thread-Index: AQHU7lHhPg0LssW8iEmFQ3nngW2gmKY0BIYA Date: Tue, 9 Apr 2019 15:23:36 +0000 Message-ID: <5F854869-1E6A-4834-9F7F-92386BE5253C@akamai.com> References: <8F770E74-110D-4EC3-A94F-3A97E36B103B@cisco.com> In-Reply-To: <8F770E74-110D-4EC3-A94F-3A97E36B103B@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.18.0.190403 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.19.37.32] Content-Type: multipart/alternative; boundary="_000_5F8548691E6A48349F7F92386BE5253Cakamaicom_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-09_07:, , 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904090096 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-09_07:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904090097 Archived-At: Subject: [Ietf-and-github] FW: YANG Model Formatting 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 15:23:41 -0000 --_000_5F8548691E6A48349F7F92386BE5253Cakamaicom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 U29tZXRoaW5nIHRvIGF1dG9tYXRlIGF0IHNvbWUgcG9pbnQgSSBzdXBwb3NlLg0KDQpGcm9tOiAi QWNlZSBMaW5kZW0gKGFjZWUpIiA8YWNlZUBjaXNjby5jb20+DQpEYXRlOiBNb25kYXksIEFwcmls IDgsIDIwMTkgYXQgNToyOCBQTQ0KVG86ICdXRyBDaGFpcnMnIDx3Z2NoYWlyc0BpZXRmLm9yZz4N CkNjOiBNYXJ0aW4gQmpvcmtsdW5kIDxtYmpAdGFpbC1mLmNvbT4sICJvcHMtYWRzQGlldGYub3Jn IiA8b3BzLWFkc0BpZXRmLm9yZz4NClN1YmplY3Q6IFlBTkcgTW9kZWwgRm9ybWF0dGluZw0KDQpB bGwsDQoNCkkgaGFkIGEgWUFORyBtb2RlbCBSRkMgZGlzY3Vzc2lvbiB3aXRoIHRoZSBTYW5keSBH aW5vemEsIFJGQyBFZGl0b3IsIGF0IElFVEYgMTA0IGFuZCBzaGUgaW5kaWNhdGVkIHRoYXQgdGhl eSBhcmUgdXNpbmcgcHlhbmcgdG8gZm9ybWF0IFlBTkcgbW9kZWxzIHByaW9yIHRvIHB1YmxpY2F0 aW9uLiBJdCB3b3VsZCBoZWxwIGdyZWF0bHkgaWYgYXV0aG9ycyBkbyB0aGUgZm9ybWF0dGluZyBp biBhZHZhbmNlIHRvIGZhY2lsaXRhdGUgcmV2aWV3cyBhbmQgbGVzc2VuIHRoZSBSRkMgRWRpdG9y IHRhc2suIEhlcmUgYXJlIHRoZSBjb21tYW5kcyBpbiB1c2U6DQoNCnB5YW5nIC1mIHlhbmcgLS1r ZWVwLWNvbW1lbnRzDQpweWFuZyAtLWlldGYgLS1tYXgtbGluZS1sZW5ndGggNjkNCg0KDQpUaGFu a3MsDQpBY2VlDQoNCg0K --_000_5F8548691E6A48349F7F92386BE5253Cakamaicom_ Content-Type: text/html; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4 bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2 IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy aW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9 DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9y aXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpw Lm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1u YW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6 MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglm b250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNw YW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWNvbG9yOndpbmRv d3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVw bHk7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlw ZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0K CXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0K ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPg0KPC9o ZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4N CjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz dHlsZT0iZm9udC1zaXplOjExLjBwdCI+U29tZXRoaW5nIHRvIGF1dG9tYXRlIGF0IHNvbWUgcG9p bnQgSSBzdXBwb3NlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48 L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4w cHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48 c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPkZyb206IDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImNv bG9yOmJsYWNrIj4mcXVvdDtBY2VlIExpbmRlbSAoYWNlZSkmcXVvdDsgJmx0O2FjZWVAY2lzY28u Y29tJmd0Ozxicj4NCjxiPkRhdGU6IDwvYj5Nb25kYXksIEFwcmlsIDgsIDIwMTkgYXQgNToyOCBQ TTxicj4NCjxiPlRvOiA8L2I+J1dHIENoYWlycycgJmx0O3dnY2hhaXJzQGlldGYub3JnJmd0Ozxi cj4NCjxiPkNjOiA8L2I+TWFydGluIEJqb3JrbHVuZCAmbHQ7bWJqQHRhaWwtZi5jb20mZ3Q7LCAm cXVvdDtvcHMtYWRzQGlldGYub3JnJnF1b3Q7ICZsdDtvcHMtYWRzQGlldGYub3JnJmd0Ozxicj4N CjxiPlN1YmplY3Q6IDwvYj5ZQU5HIE1vZGVsIEZvcm1hdHRpbmcgPG86cD48L286cD48L3NwYW4+ PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv bnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAg Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHQiPkFsbCwgPC9z cGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv bnQtc2l6ZToxNC4wcHQiPjxicj4NCkkgaGFkIGEgWUFORyBtb2RlbCBSRkMgZGlzY3Vzc2lvbiB3 aXRoIHRoZSBTYW5keSBHaW5vemEsIFJGQyBFZGl0b3IsIGF0IElFVEYgMTA0IGFuZCBzaGUgaW5k aWNhdGVkIHRoYXQgdGhleSBhcmUgdXNpbmcgcHlhbmcgdG8gZm9ybWF0IFlBTkcgbW9kZWxzIHBy aW9yIHRvIHB1YmxpY2F0aW9uLiBJdCB3b3VsZCBoZWxwIGdyZWF0bHkgaWYgYXV0aG9ycyBkbyB0 aGUgZm9ybWF0dGluZyBpbiBhZHZhbmNlIHRvIGZhY2lsaXRhdGUgcmV2aWV3cyBhbmQNCiBsZXNz ZW4gdGhlIFJGQyBFZGl0b3IgdGFzay4gSGVyZSBhcmUgdGhlIGNvbW1hbmRzIGluIHVzZTo8L3Nw YW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u dC1zaXplOjE0LjBwdCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHQ7Y29sb3I6YmxhY2siPnB5YW5n IC1mIHlhbmcgLS1rZWVwLWNvbW1lbnRzPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9 Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHQ7Y29sb3I6YmxhY2siPnB5 YW5nIC0taWV0ZiAtLW1heC1saW5lLWxlbmd0aCA2OTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxw IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTQuMHB0O2NvbG9yOmJs YWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48 c3BhbiBzdHlsZT0iZm9udC1zaXplOjE0LjBwdDtjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxv OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6 ZToxNC4wcHQ7Y29sb3I6YmxhY2siPlRoYW5rcyw8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBj bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjE0LjBwdDtjb2xvcjpibGFj ayI+QWNlZTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu IHN0eWxlPSJmb250LXNpemU6MTQuMHB0Ij4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8 cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjE0LjBwdCI+Jm5ic3A7 PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo= --_000_5F8548691E6A48349F7F92386BE5253Cakamaicom_-- From nobody Tue Apr 9 08:49:29 2019 Return-Path: <0100016a02ca26fc-f9894f34-623d-4e55-9360-222006bfc974-000000@amazonses.watsen.net> 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 E873D12088C for ; Tue, 9 Apr 2019 08:49:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 kTbh2AtAzwaH for ; Tue, 9 Apr 2019 08:49:25 -0700 (PDT) Received: from a8-33.smtp-out.amazonses.com (a8-33.smtp-out.amazonses.com [54.240.8.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59AC812044E for ; Tue, 9 Apr 2019 08:49:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1554824964; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=OamcayGuUkCZtFMD9LQTeBDUEhC57stmlaej1QkKdQM=; b=fFZqjV7jdpjdY1rQbofBqrM09ThToaUIe6h/SCqBn8Pedn6frWAhjMbzHpRtDHGp 9DksD42DYuRjq+vY2g+0HfrsSzxtBgLmk3JJA+WS3IpGjRJMxeZHAQNFF6Xhj1UXaFG Tb9aDonmBgaydcp49RBuvTyCc5XjuGZfvGEcvVPg= From: Kent Watsen Message-ID: <0100016a02ca26fc-f9894f34-623d-4e55-9360-222006bfc974-000000@email.amazonses.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_29D4C748-F2F9-47E0-95C9-D4FC70865CF7" Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Date: Tue, 9 Apr 2019 15:49:23 +0000 In-Reply-To: <5F854869-1E6A-4834-9F7F-92386BE5253C@akamai.com> Cc: "ietf-and-github@ietf.org" To: "Salz, Rich" References: <8F770E74-110D-4EC3-A94F-3A97E36B103B@cisco.com> <5F854869-1E6A-4834-9F7F-92386BE5253C@akamai.com> X-Mailer: Apple Mail (2.3445.102.3) X-SES-Outgoing: 2019.04.09-54.240.8.33 Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES Archived-At: Subject: Re: [Ietf-and-github] YANG Model Formatting 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 15:49:28 -0000 --Apple-Mail=_29D4C748-F2F9-47E0-95C9-D4FC70865CF7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I plan to add it to `xiax`. > On Apr 9, 2019, at 11:23 AM, Salz, Rich wrote: >=20 > Something to automate at some point I suppose. > =20 > From: "Acee Lindem (acee)" > Date: Monday, April 8, 2019 at 5:28 PM > To: 'WG Chairs' > Cc: Martin Bjorklund , "ops-ads@ietf.org" = > Subject: YANG Model Formatting=20 > =20 > All,=20 >=20 > I had a YANG model RFC discussion with the Sandy Ginoza, RFC Editor, = at IETF 104 and she indicated that they are using pyang to format YANG = models prior to publication. It would help greatly if authors do the = formatting in advance to facilitate reviews and lessen the RFC Editor = task. Here are the commands in use: > =20 > pyang -f yang --keep-comments > pyang --ietf --max-line-length 69 > =20 > =20 > Thanks, > Acee > =20 > =20 > _______________________________________________ > Ietf-and-github mailing list > Ietf-and-github@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-and-github = --Apple-Mail=_29D4C748-F2F9-47E0-95C9-D4FC70865CF7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
I plan to add it to `xiax`.


On Apr = 9, 2019, at 11:23 AM, Salz, Rich <rsalz@akamai.com> wrote:

Something to automate at some = point I suppose.
 
From: "Acee Lindem (acee)" <acee@cisco.com>
Date: Monday, April 8, 2019 = at 5:28 PM
To: 'WG Chairs' <wgchairs@ietf.org>
Cc: Martin Bjorklund <mbj@tail-f.com>, "ops-ads@ietf.org" <ops-ads@ietf.org>
Subject: YANG Model = Formatting 
 
All, 

I had a YANG model = RFC discussion with the Sandy Ginoza, RFC Editor, at IETF 104 and she = indicated that they are using pyang to format YANG models prior to = publication. It would help greatly if authors do the formatting in = advance to facilitate reviews and lessen the RFC Editor task. Here are = the commands in use:
 
pyang -f yang = --keep-comments
pyang --ietf = --max-line-length 69
 
 
Thanks,
Acee
 
 
_______________________________________________
Ietf-and-github= mailing list
Ietf-and-github@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-and-github
=

= --Apple-Mail=_29D4C748-F2F9-47E0-95C9-D4FC70865CF7-- From nobody Tue Apr 9 08:56:43 2019 Return-Path: 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 18461120892 for ; Tue, 9 Apr 2019 08:56:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.75 X-Spam-Level: X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 iyRW8vMGavUO for ; Tue, 9 Apr 2019 08:56:40 -0700 (PDT) Received: from mail-yw1-xc2f.google.com (mail-yw1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C03BD12044E for ; Tue, 9 Apr 2019 08:56:40 -0700 (PDT) Received: by mail-yw1-xc2f.google.com with SMTP id j66so6407720ywc.10 for ; Tue, 09 Apr 2019 08:56:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=sb/hFkPKbs6GHoaLVcnybheK1CwUB1BjBkv42+ebSKE=; b=niwaC6w13wov/u9sgZgEV5bNxL5n40sWjNL7zTNpSMES3K/idfS2PboZ+YlkGY6i7d NgBWtk5cAKpZiP5vkiGKoeDAUJsRlkHtJ6eGjx0UQWcW7uz0h8K+nmACt6J9JXRCS2Ij f2JALNWWTf/ymGQTCIV6ARyRZmGRt7W/wIzs6w0WMLNG7VmHI0gAQaL5OFleRRnOkgX4 Zxb6DDgcncsVoB8V0ohQwyA8dH1LuWZRkqLv2/IjGLluRvQkUnnBC5Ky5SVMICZLU5hm AieOg46rK1UPQigyCwwhTy07BpsxofS9HbWEDGwoQbFV7VeQWzchhNrGNKqviDOgHknJ L+aQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=sb/hFkPKbs6GHoaLVcnybheK1CwUB1BjBkv42+ebSKE=; b=rjfA9DZcevb7DOIZQfUg6uwk3469brNLDGd2YGvnpi3r/5TTO1vbWbrC65wIj4Vk6R 0uTRO2owGgnokJcaDzbrQVd793eDvIy8JGem6J9UT9ww3ZlYKAtj7y3zzH3J2C9Tktc1 YVa5BH60a7DTs2e75G+70Td02bmhZ2Cya/MWLeiV+6VFJ2NAeLSCsbkv+BQbAIxuXK4K 1d+s9icieU/1mx+1gKNIIF2R8nM2zWUIiqF1kwaUvcPAXdv4RbpNYR8ym+xK2rSnHi7k tAmX8+X3yKrSDlPyLXb2Zjeg/HfXBLvZU2Q/BrEzWjOrZ7WdYvLLbfZt0uk/RJv4LPtn RIUQ== X-Gm-Message-State: APjAAAXG2EgtljDXkOYGielZes1ZGF35mCuKn6GXOFYHy6iYFqbDTenI d3OsC9IR1+0XOuZPsYGsLer+Uda+yFvV1PzE9Kg7ndhJ X-Google-Smtp-Source: APXvYqzJ5p1RU6d77F45vM/6iWne9EX0cewRyd+H+LpM9n9BbQ7HGoZvbRt2r9NV1G7i2mR4Anu5YFChGs6muSDQWUU= X-Received: by 2002:a81:984c:: with SMTP id p73mr29400765ywg.185.1554825399549; Tue, 09 Apr 2019 08:56:39 -0700 (PDT) MIME-Version: 1.0 From: Christopher Wood Date: Tue, 9 Apr 2019 08:56:28 -0700 Message-ID: To: ietf-and-github@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 15:56:42 -0000 In Prague, we decided to adopt the =E2=80=9Clight=E2=80=9D usage profile Gi= tHub for WG documents. This has the following implications: 1. All WG documents will be hosted under the GIT organization, located here: https://github.com/ietf-gitwg 2. WG contributors are encouraged to post issues on the documents either on the mailing list or as issues in the GitHub issue list. The authors will use the GitHub issues list to keep track of open and closed issues, but all substantive discussion of the issues should be on the mailing list. Thus, if an issue is opened on GitHub, the document authors should copy it to the list for discussion. Similarly, if an issue comes up first on the mailing list, the authors will open an issue on GitHub to help track it. We will configure some tooling to track GitHub activity in WG documents and send weekly summaries to the list. This will help those not following GitHub stay informed of issues or PRs filed. And finally, as before, consensus will always take place on the list. Thanks, Chris and Paul From nobody Tue Apr 9 10:13:17 2019 Return-Path: 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 E9142120417 for ; Tue, 9 Apr 2019 10:13:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org 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 k9RThaQtkpUH for ; Tue, 9 Apr 2019 10:13:13 -0700 (PDT) Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FC021203F1 for ; Tue, 9 Apr 2019 10:13:13 -0700 (PDT) Received: by mail-oi1-x236.google.com with SMTP id n187so14220765oih.6 for ; Tue, 09 Apr 2019 10:13:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lyzU2nrI++ZZCJC9cQseqk+rTO3iA9nWYHrpzA8H/vU=; b=dLb4RERSz83XuTgYUPzOEyTl4EB4YGUQmIms5q9JqSnAxC0NGJ+pbHFhp2kkmNCalA upy1SpJxryLx8W3Zq12AQ3DkiPwYoQNrzbYoTMXCRnR0zcA8+TIkVw0gwwp4CVIfC9u3 hdOt5wwpRmOnMfDK4Xs8gdOcg9CPZZpsnZHIY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lyzU2nrI++ZZCJC9cQseqk+rTO3iA9nWYHrpzA8H/vU=; b=EjwWbKV7UDJIXudouEcAT0i+xO7CuBfb9vCzkEdm8vSAk2XLFLVW2lIqHNQlKaD1pa lKFxuApk1xpTv3yAZ8S1jxgN++VYq3HxDq0x1yyo5edbvoLjMQNK4j8zhgbbfw3394Ow 61grCmp7815+sDmBDYgXIKIavYpT+uPpkLg5+yaRLNJ+dqwjzFCuNGWdzw1jjndvGprT g6ZRi1MqPe0wKxxt3ra7qHEromcEihJtMT6uDuZQM7hhTeZwBJlmeXktdDlm/XFPliCS 95EaPTf5CPS/wySJ3RRhQkgKi15slgnao8Wtm3Ou59Ug05ceT9IO1hqVU2oYkH86Deml usBg== X-Gm-Message-State: APjAAAXkRt40pjtAwGgKGGK41IjNqbiR5Dpq3KfLfxpOQ1jTSfjLpZfi av0jFbYIHOVi2c4gZ49snAQrXti1XtVDfeetqKg7VA== X-Google-Smtp-Source: APXvYqy92pUnDgCOGsABF51GobOQIa1Tt+wIBRWjHQnUZ4Wf8jKpvB21wbtCOq9JfSWlT81jZ4nAiI2Y6rAdshjWe3M= X-Received: by 2002:aca:da82:: with SMTP id r124mr20801936oig.49.1554829992122; Tue, 09 Apr 2019 10:13:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Joseph Lorenzo Hall Date: Tue, 9 Apr 2019 13:13:01 -0400 Message-ID: To: Christopher Wood Cc: ietf-and-github@ietf.org Content-Type: multipart/alternative; boundary="0000000000005df36405861c1178" Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 17:13:15 -0000 --0000000000005df36405861c1178 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Apr 9, 2019 at 11:56 AM Christopher Wood < christopherwood07@gmail.com> wrote: > In Prague, we decided to adopt the =E2=80=9Clight=E2=80=9D usage profile = GitHub for WG > documents. This has the following implications: > > 1. All WG documents will be hosted under the GIT organization, located > here: https://github.com/ietf-gitwg > 2. WG contributors are encouraged to post issues on the documents > either on the mailing list or as issues in the GitHub issue list. The > authors will use the GitHub issues list to keep track of open and > closed issues, but all substantive discussion of the issues should be > on the mailing list. Thus, if an issue is opened on GitHub, the > document authors should copy it to the list for discussion. Similarly, > if an issue comes up first on the mailing list, the authors will open > an issue on GitHub to help track it. > This is great; one question that may necessitate forking this thread: I've used MT's template to good effect, but I haven't contributed to a WG that uses continuous integration (which sounds so awesome now that I know a bit about what that does). Do we plan to do anything in this WG related to CI tools? I know some WGs have a soft (or hard?) requirement to use CI tools and submit PRs, etc. via the CI tooling. It would be great if there were good pointers on "How to get up to speed with CI tools as used in IETF WGs". I'm going to muddle around a bit and may be helpful contributing to an ID on this kind of stuff after my newbie-to-CI journey. --=20 Joseph Lorenzo Hall Chief Technologist, Center for Democracy & Technology [https://www.cdt.org] 1401 K ST NW STE 200, Washington DC 20005-3497 e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10 1607 5F86 6987 40A9 A871 --0000000000005df36405861c1178 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Apr 9, 2019 at 11:56 AM Chris= topher Wood <christopherw= ood07@gmail.com> wrote:
In Prague, we decided to adopt the =E2=80=9Clight=E2=80=9D u= sage profile GitHub for WG
documents. This has the following implications:

1. All WG documents will be hosted under the GIT organization, located
here: https://github.com/ietf-gitwg
2. WG contributors are encouraged to post issues on the documents
either on the mailing list or as issues in the GitHub issue list. The
authors will use the GitHub issues list to keep track of open and
closed issues, but all substantive discussion of the issues should be
on the mailing list. Thus, if an issue is opened on GitHub, the
document authors should copy it to the list for discussion. Similarly,
if an issue comes up first on the mailing list, the authors will open
an issue on GitHub to help track it.

Th= is is great; one question that may necessitate forking this thread: I'v= e used MT's template to good effect, but I haven't contributed to a= WG that uses continuous integration (which sounds so awesome now that I kn= ow a bit about what that does).

Do we plan to do a= nything in this WG related to CI tools? I know some WGs have a soft (or har= d?) requirement to use CI tools and submit PRs, etc. via the CI tooling. It= would be great if there were good pointers on "How to get up to speed= with CI tools as used in IETF WGs". I'm going to muddle around a = bit and may be helpful contributing to an ID on this kind of stuff after my= newbie-to-CI journey.

--
Joseph Lorenzo Hall
Chief Technologist, Center for Democracy &am= p; Technology [https://ww= w.cdt.org]
1401 K ST NW STE 200, Washington DC 20005-3497
e: joe@cdt.org, p: 202.407.88= 25, pgp: https= ://josephhall.org/gpg-key
Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10 =C2= =A01607 5F86 6987 40A9 A871

--0000000000005df36405861c1178-- From nobody Tue Apr 9 18:16:28 2019 Return-Path: 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 3FD5B1200C7 for ; Tue, 9 Apr 2019 18:16:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.749 X-Spam-Level: X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 neLcPRK34q6h for ; Tue, 9 Apr 2019 18:16:25 -0700 (PDT) Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99DC412000F for ; Tue, 9 Apr 2019 18:16:25 -0700 (PDT) Received: by mail-yb1-xb30.google.com with SMTP id b88so205914ybi.6 for ; Tue, 09 Apr 2019 18:16:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=PB2tN2eGfNUxqRzOZ5KBBcb+OyH6nS4HmFx3u1enXEw=; b=SW68eQB8hl7DJ73LF4dPCCbLjZ6Zajp4EMUzV5GR83WzimnTGuWW6lqKRoI+N6QLBL UOb2/MD80GPQnj4JBraaAxCr/jAwGjmPtQhRSkyMBSALXJveWmcv4YmlbOeed+Lh4QeL 5F3dShTdHf/sxSPDMp6NMoA20JKlyt5UULBusRlhI0SulE6XD8spZ9KfnEC8byOPo51P sFk53g1Or0L62qg+Az6ND7cNBgFwcJKJ4Y3Cpg8EptXMyIIyX5KFAhCAqFoahrWKeA5G nYXWeznu7wx5erN9iRwxk1N7s6+qddcztCto0MVLEOtsN39fJARI5nhNXdTZX4AqjcoA ujew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=PB2tN2eGfNUxqRzOZ5KBBcb+OyH6nS4HmFx3u1enXEw=; b=jMz+T6YgYL5FgvJtzzzomtEPWEC8JDAEVWuIdeM6e2FW9EhWUuhaH+nr1iO/EYVaCZ d6dOXavfU2uqzzEaU2qd5mhF4n+JpUOmJdxC3oxSaWiRplryNk1dIxbOkwWLcNpVwvbd ocKwwlIH5QTq3nwT0W2LYEwZZlQ8WuH0KJ8qfp29g+U5HCN1fnS7aOEcbJuagRxyLsdy qIy8ZUxSKIkf9BCzgoeiS4rxbafprBIJx+Q9SdV7v6V2AOymxAU0GAx1R5QjldBxixwa Zr81mBzCk4xJ90wAieMbp3HyucdIWER+hquRaj84WRLiT5+stYQb/OvvqMoYfzW0oTWN +l6w== X-Gm-Message-State: APjAAAWUD54EAlZ93V1D0Gn7yEVgXvyrWmEN60BzCD6ipgYO4Gb4/wbM qJOgYj5t9IunMr1Bk+1+EJYILDnOp28QIWhvnL0= X-Google-Smtp-Source: APXvYqzlcD4jEnrFB+M7S0V49g5oO1Yb6WbuueBDC8D1TVl2mVotgFQ+El80FyOdXLMzO7+BUy4QnMB8H07UMAus3Ek= X-Received: by 2002:a25:b004:: with SMTP id q4mr32652619ybf.34.1554858984665; Tue, 09 Apr 2019 18:16:24 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Christopher Wood Date: Tue, 9 Apr 2019 18:16:13 -0700 Message-ID: To: Joseph Lorenzo Hall Cc: ietf-and-github@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 01:16:27 -0000 On Tue, Apr 9, 2019 at 10:13 AM Joseph Lorenzo Hall wrote: > > On Tue, Apr 9, 2019 at 11:56 AM Christopher Wood wrote: >> >> In Prague, we decided to adopt the =E2=80=9Clight=E2=80=9D usage profile= GitHub for WG >> documents. This has the following implications: >> >> 1. All WG documents will be hosted under the GIT organization, located >> here: https://github.com/ietf-gitwg >> 2. WG contributors are encouraged to post issues on the documents >> either on the mailing list or as issues in the GitHub issue list. The >> authors will use the GitHub issues list to keep track of open and >> closed issues, but all substantive discussion of the issues should be >> on the mailing list. Thus, if an issue is opened on GitHub, the >> document authors should copy it to the list for discussion. Similarly, >> if an issue comes up first on the mailing list, the authors will open >> an issue on GitHub to help track it. > > > This is great; one question that may necessitate forking this thread: I'v= e used MT's template to good effect, but I haven't contributed to a WG that= uses continuous integration (which sounds so awesome now that I know a bit= about what that does). > > Do we plan to do anything in this WG related to CI tools? I know some WGs= have a soft (or hard?) requirement to use CI tools and submit PRs, etc. vi= a the CI tooling. It would be great if there were good pointers on "How to = get up to speed with CI tools as used in IETF WGs". I'm going to muddle aro= und a bit and may be helpful contributing to an ID on this kind of stuff af= ter my newbie-to-CI journey. Yes, definitely. In addition to the document(s*) we're currently working on, one desirable outcome is improved (and consolidated) documentation for using all of the tools located here: https://github.com/ietf-gitwg/wg-materials/wiki/Tooling In Prague, several WG attendees signaled an interest and willingness to help with this effort. I'll send out more information on this topic soon. Best, Chris *draft-thomson-git-using-github is not yet adopted, though the consensus call closes on Thursday. From nobody Tue Apr 9 18:24:46 2019 Return-Path: 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 8908F1200B2 for ; Tue, 9 Apr 2019 18:24:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=b+rR0DKT; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=6SpLVuGT 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 jDkqJ89o_tsm for ; Tue, 9 Apr 2019 18:24:42 -0700 (PDT) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B37012000F for ; Tue, 9 Apr 2019 18:24:42 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 60F3022F; Tue, 9 Apr 2019 21:24:41 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 09 Apr 2019 21:24:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=+ elLH/195lBCLh2colP8h5ZmEW4EC6XLD4sa1zW/HgE=; b=b+rR0DKTgw0b7SNz0 lTIRcnIxQlF2mHmQIdQ0M8rYjrUs6VQx99x8nBanKO0QEQ6RDkril14JXhfSBb8o blXlB7uE3U27obyRRkViR0uuS6k0lRCa/s61CN0hyIylZNmNRlxFKiyYNIAGyM8E 71V6igcnEul6KI2ih8JwfEAAs5UIrDF2STn/Ctz0OGsPiwLH0lF9N2hN88hR8PJ0 tOfkm9tarhxpkGevSiwwsHXFYgdQ1RXQlNN5nZDeQfmpPlAZG++SFFOMlQik+/mS RCN3OqIBpBamqEHx6E8spYNhS8sVW5LjAqHKVxn+GBk09X/lQNxV4931XS2DYKdM YQkVA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=+elLH/195lBCLh2colP8h5ZmEW4EC6XLD4sa1zW/H gE=; b=6SpLVuGTGW/Y82671jTSNC3bycTfbKOWtjofpyitcNMb2eWzhILo/Y0fq 6WpNZrXHSIMvD7JI/7wipxK9JuLw4jEcQmI8uKadmEmgdDBw5yyp2RhCftElR0+J 40PkAwd18KDLDwnODiJtfhYZqHIxQFNPIJmrNjvDw/tahAujazIUAfU+t5bZsnqJ 4n3WfeU6rVi5NLcqFLQ1HKAErNi14D57mNmU6hUww7J2DDASyFwiZ1plKssfftMc 1dzl6BhqgXyXy9jX+GWJqZCfCsHj9Bs27258AzTvoyWG+eDNyUNPkKHFIk1rrqJH BLHEd8r5bJ+ypDNA8jZR2kCKlzu8w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeigdegiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpe hmnhhothdrnhgvthenucfkphepudeggedrudefiedrudejhedrvdeknecurfgrrhgrmhep mhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivg eptd X-ME-Proxy: Received: from attitudadjuster.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id D9B92E407B; Tue, 9 Apr 2019 21:24:38 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) From: Mark Nottingham In-Reply-To: Date: Wed, 10 Apr 2019 11:24:36 +1000 Cc: ietf-and-github@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> References: To: Christopher Wood X-Mailer: Apple Mail (2.3445.102.3) Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 01:24:44 -0000 > On 10 Apr 2019, at 1:56 am, Christopher Wood = wrote: >=20 > WG contributors are encouraged to post issues on the documents > either on the mailing list or as issues in the GitHub issue list. The > authors will use the GitHub issues list to keep track of open and > closed issues, but all substantive discussion of the issues should be > on the mailing list. Thus, if an issue is opened on GitHub, the > document authors should copy it to the list for discussion. Similarly, > if an issue comes up first on the mailing list, the authors will open > an issue on GitHub to help track it. Creating issues in GitHub already has a very low bar, so I'm not sure = this is encouraging good behaviour; effectively, this is making the = authors do work for anyone who cares to create an issue, no matter how = trivial. If the volume is low this might suffice, but is this something = we want to promote to other WGs? (I was tempted to open an issue on GitHub to prove my point here, but I = won't abuse the authors...yet). Cheers, -- Mark Nottingham https://www.mnot.net/ From nobody Tue Apr 9 18:29:38 2019 Return-Path: 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 F422E12007A for ; Tue, 9 Apr 2019 18:29:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.749 X-Spam-Level: X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jTbiHC5McT1Q for ; Tue, 9 Apr 2019 18:29:36 -0700 (PDT) Received: from mail-yw1-xc41.google.com (mail-yw1-xc41.google.com [IPv6:2607:f8b0:4864:20::c41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EE23120003 for ; Tue, 9 Apr 2019 18:29:35 -0700 (PDT) Received: by mail-yw1-xc41.google.com with SMTP id v127so156013ywe.13 for ; Tue, 09 Apr 2019 18:29:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=xY7Ut6xBxGt1eikxTiPj4LB03JGuUBqlEWY6ACSWkZM=; b=U7TR6xS8LxoGQGWRb3RaCwy6ZLLkeCvjfq0UKK1VWU6OwP4ZwPs4dEc/f1Bzqm0R4c U/FiGB6c3DayEOHrJ0DNHIVwSKOxErPU3X7nuIQpx3vLBLoX66Bzy4ySpWBFwX3gW9o1 zefCkkr6AskPFxL7ehsVrsW4rwssztgKiG0MHCLlbFI73H4MZSIYHQ7N1l2r8+8rvVGr JSjtjiFAqXBW6m126ZLObNzxAycJOSw5RfDfl//Xb1i4giHscf3WIPD3rqNC3b6FTzI+ eYmTW97pYFl+O0ndSp+6uOiSYrYdT7Eu4Oja1pMH9SvOUfd5SJRiX0EmdW2qPohiToa3 f7Eg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=xY7Ut6xBxGt1eikxTiPj4LB03JGuUBqlEWY6ACSWkZM=; b=DwoVIxdCfqKilzcmsnHJ8hmcGzTuw47Eq6Wr7rRMrKMFxZroK4hUreUwLl78ZncyG7 7KDgHYF1NaJO+rgLRrUFvX8UzKAcddeIHp7hKI3LHWY8LL6Nzbg2Li6VeqU6uYhjkOGn 7eMScSts8JPfMe87xM97jSkMhYOq3eLo7IpcZWTr4PUChYiiaFcRwOOVKywl7tKt7dfw LyXbaSv3vld7I3SDtF/fs2VCXF6svfI5oBR3rn+FMLmC8OxLJALZoVVyJs/R/P6w5+wR Q7CSDMGQdJh0OBOPbAN5lx3wDGtDXUVxHErQ++JewnoZei/0DMUhmikSARVRAcK8+TuA 7IfQ== X-Gm-Message-State: APjAAAUdl8zU+30ivQG1QNl0zEp2Z4TE/OirluPUOpPrjbbhGM4ENqFO YGEbaBBxLjAyRNU0xO7y62Tks8/ALkSmFQthW48= X-Google-Smtp-Source: APXvYqwRpd1j1LlKV9qkSkg4LcCZRsqAacpyWHzmS88PnLiEMAPEwUFh1pDyLXjphVWCEm+lztISyO/7zQ5JiT29UP0= X-Received: by 2002:a81:984c:: with SMTP id p73mr31780019ywg.185.1554859774013; Tue, 09 Apr 2019 18:29:34 -0700 (PDT) MIME-Version: 1.0 References: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> In-Reply-To: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> From: Christopher Wood Date: Tue, 9 Apr 2019 18:29:22 -0700 Message-ID: To: Mark Nottingham Cc: ietf-and-github@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 01:29:37 -0000 On Tue, Apr 9, 2019 at 6:24 PM Mark Nottingham wrote: > > > On 10 Apr 2019, at 1:56 am, Christopher Wood wrote: > > > > WG contributors are encouraged to post issues on the documents > > either on the mailing list or as issues in the GitHub issue list. The > > authors will use the GitHub issues list to keep track of open and > > closed issues, but all substantive discussion of the issues should be > > on the mailing list. Thus, if an issue is opened on GitHub, the > > document authors should copy it to the list for discussion. Similarly, > > if an issue comes up first on the mailing list, the authors will open > > an issue on GitHub to help track it. > > Creating issues in GitHub already has a very low bar, so I'm not sure thi= s is encouraging good behaviour; effectively, this is making the authors do= work for anyone who cares to create an issue, no matter how trivial. If th= e volume is low this might suffice, but is this something we want to promot= e to other WGs? I suspect the volume will be quite low, which is why the text is framed as such. (Perhaps that list "will" could be a "may.") In general, authors should use their best judgement here. If an issue arises on the list that they don't want to lose sight of, file an issue on the corresponding draft's repo. > (I was tempted to open an issue on GitHub to prove my point here, but I w= on't abuse the authors...yet). :-) Best, Chris From nobody Tue Apr 9 19:51:21 2019 Return-Path: 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 C23F3120094 for ; Tue, 9 Apr 2019 19:51:19 -0700 (PDT) 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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=Ad4ceqi0; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=j1QXCpb1 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 CC8vfMVr9hXj for ; Tue, 9 Apr 2019 19:51:18 -0700 (PDT) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F98D12006A for ; Tue, 9 Apr 2019 19:51:18 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 96579264BF for ; Tue, 9 Apr 2019 22:51:17 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Tue, 09 Apr 2019 22:51:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=s4tYFZONY26blO+75NkCSOj7sjTmjqU ze4y5+N53STk=; b=Ad4ceqi0KCNs5R3sPmCwpKjbM+hdgZ7+uN9l35wFYeMwd6+ D6v72uGNor+cNc4HbHSK2i21UYzfifC0XxIwxtRzlbShOOZUHuS4Yq7pCjZnrd22 5an4sWz9aPwlpBZU9DND4dlM7etczp5pndKl3pLx2xOyT2Do0kNJDH17fmFbr4Xb 81wbZFZe+J38TM47/PufdtZmWvFe88npE+bRo+P1qC+JiHyilMH2zMS3URHEQJlH dbxTyxARm5FUdmzzdnhBQJjW3FimkyrANZmTeEzvM8NYx8OpLKUjmEquSS0sH/R7 G1zhahtUXZUYXj8/Nv8177UM9m69/xhcKMh8HjA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=s4tYFZ ONY26blO+75NkCSOj7sjTmjqUze4y5+N53STk=; b=j1QXCpb1Gu5MOAHvD1v1KI 18eAkTBqZW4Loi7Dqx4uVt7Mdjw6wBpQImfOmQxRxdKDD3p9FzVJ6Ri38gEiRGWF Z4bJZ5rSWbilMHlllyYtyhMHqSJjj5Rln5V0STG4Oha031Xk74IQuSq/OTUddSTb oA9J1hqLRkH2PKkeZBI0KnvfTKtaNkh/80xB3j8RopHEWjzbaQYpGwOUiPCDRbsk 4tDCjeVAZAbn5+q2yXGrdtpOpkrt+eT93XvNHRl5O3cuco3xIa97wXyMtPUQUZX1 WafAGQAE1JiXwN/DIVXaaTTd5Rn4QnPL3amDyX5iemXUj54vfzBDbPNbSY20SWdQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeigdeihecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofi gvnhhtrhhophihrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 054FC7C412; Tue, 9 Apr 2019 22:51:17 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-329-gf4aae99-fmstable-20190329v1 Mime-Version: 1.0 X-Me-Personality: 92534000 Message-Id: In-Reply-To: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> References: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> Date: Tue, 09 Apr 2019 22:51:19 -0400 From: "Martin Thomson" To: ietf-and-github@ietf.org Content-Type: text/plain Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 02:51:20 -0000 On Wed, Apr 10, 2019, at 11:24, Mark Nottingham wrote: > Creating issues in GitHub already has a very low bar, so I'm not sure > this is encouraging good behaviour; effectively, this is making the > authors do work for anyone who cares to create an issue, no matter how > trivial. If the volume is low this might suffice, but is this something > we want to promote to other WGs? I'm fairly sure that we can rely on authors to filter out spam. Yes, opening an issue creates work for authors, but in my experience, hitting the close button is pretty quick. I also know how to block people who really abuse the tracker. > (I was tempted to open an issue on GitHub to prove my point here, but I > won't abuse the authors...yet). Please do open an issue. We need to understand what recommendations we make to working group about issue creation. From nobody Tue Apr 9 20:35:41 2019 Return-Path: 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 F3AFF12023C for ; Tue, 9 Apr 2019 20:35:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=mxo7GI24; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=KRDZLg51 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 3mnOsXl-9K5c for ; Tue, 9 Apr 2019 20:35:37 -0700 (PDT) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBA221201D0 for ; Tue, 9 Apr 2019 20:35:37 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 0BD04358; Tue, 9 Apr 2019 23:35:36 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 09 Apr 2019 23:35:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=W +pGTPJcN+IhJHD5za42zhd23QM5l+a+5LSQGt4LKuM=; b=mxo7GI24vlURL5F9z 5Us4xbwe8L+X+8F49SI9S6/9Vp3gwJwI62r92w1Ywagn3KeEsRg97wpNWu23jtpF ihGhEsJ2j+iS9wm/VzFuT3kKwfX3peu4zDtURAlykdCUDlc/MKsrA4Dt15/HVWYA Uh7UsjQPY2uK08WmCUP9sNUTt9WMup8DG4cP30MRYAiZpE3Vf1lID9zM6ynmUAue 2W30/1JGzzOFMk94PJ5pXY7RqsevnNuhvX0eo54nuG/PcIZrV1xrgd+OCAkHqbrz nkBmGYmeYaCr3R4A4CsOnR8+hbGMrbPSyKv8pvzPk/M+Zp/zIPzQvXoSZ0NJQKzo 5ueWg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=W+pGTPJcN+IhJHD5za42zhd23QM5l+a+5LSQGt4LK uM=; b=KRDZLg51NJCrMOtny7dSQK3mB6sDQXQppIsphH+k0kGBcXCzKuXAmIKSQ 3HMidISWsyTcvIXCBuGPBHLZpIq4NnDce+MteROrm75L0khA+86Af2ieluynNp7u 4unpzsYl9C11NIK/M4+B8dw/bS7UlE8j841tQHCpP+pF8N6h4hzdDUztDMrM87eV JNpqyBamoyrwlx/KJ/uZhAdQz4spzHzGbkCJxySpic4dH1QnZBbdNIn0DmSp3lLO bNRNqufYlxX/qzbBc5FTqWxeVkUYyZR23Bq6Tx+frN3w/Tq8Jl6OR3Gs7GY+E1E5 TPB3Zmy47eD5uA700D/IQ/6Htm5Gg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeigdejgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpe hmnhhothdrnhgvthenucfkphepudeggedrudefiedrudejhedrvdeknecurfgrrhgrmhep mhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivg eptd X-ME-Proxy: Received: from attitudadjuster.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 8364AE4382; Tue, 9 Apr 2019 23:35:34 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) From: Mark Nottingham In-Reply-To: Date: Wed, 10 Apr 2019 13:35:32 +1000 Cc: ietf-and-github@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <9A9810B9-390D-40D2-A547-3B5B1178FEA1@mnot.net> References: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> To: Martin Thomson X-Mailer: Apple Mail (2.3445.102.3) Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 03:35:40 -0000 > On 10 Apr 2019, at 12:51 pm, Martin Thomson wrote: >=20 > On Wed, Apr 10, 2019, at 11:24, Mark Nottingham wrote: >> Creating issues in GitHub already has a very low bar, so I'm not sure=20= >> this is encouraging good behaviour; effectively, this is making the=20= >> authors do work for anyone who cares to create an issue, no matter = how=20 >> trivial. If the volume is low this might suffice, but is this = something=20 >> we want to promote to other WGs? >=20 > I'm fairly sure that we can rely on authors to filter out spam. Yes, = opening an issue creates work for authors, but in my experience, hitting = the close button is pretty quick. I also know how to block people who = really abuse the tracker. I read the text as saying that an author is expected to send email to = the WG for each new issues that's raised. -- Mark Nottingham https://www.mnot.net/ From nobody Tue Apr 9 21:19:22 2019 Return-Path: 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 C0D36120074 for ; Tue, 9 Apr 2019 21:19:20 -0700 (PDT) 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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=V2rqZgrx; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=EHruFumw 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 J6ZTXcJEJNFz for ; Tue, 9 Apr 2019 21:19:19 -0700 (PDT) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B6E0120043 for ; Tue, 9 Apr 2019 21:19:19 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4826A25936; Wed, 10 Apr 2019 00:19:18 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Wed, 10 Apr 2019 00:19:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm1; bh=S3wgpX8QjV7HFVwjpq5kOFA5XiCE LMbGjS/+78Jj0Qw=; b=V2rqZgrxNS6FRtVWBC9h1YQMuX2+eTQD5Gjm+wrqjKV/ d3i95UOf1C3VTuBHuBc8Kcno0XhOeDX9g4REHdFWj0b0XCIizr+e4ZigfBLbWz31 6B8SICXSo/TzFNUxayFx+afE9Gk+XG+5ScS+HQ04gVGiqw2s27JkU7vqY06fMuIP u9uWWiXOUnKp9wQj4mkexxXs7PJcAMXN6apISF4STsIIflYaVqWZpHK7PSWLKV/7 JpknRCeZJ8Fmg5gdONVOgfMnCcEX7HPZrHxeJnrR7brrfOexdFs4/fPyaMgVXLF4 IK0NieaquzO0SkOWiY8RqbT3HV4HT3911KnjLCSMJw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=S3wgpX 8QjV7HFVwjpq5kOFA5XiCELMbGjS/+78Jj0Qw=; b=EHruFumw+TIH1dJuPnr+OP FRR54YZ/S0BDAirV9ZJXBixaE0CpvtOcaUkDaycTKjmxslAJH5UCDE4UujwDaCIn e6y/jSFebHXQ4QfEFffdpWzGjCR+Co3eUTu0CRVEbXZCbP1y/WFN6prbzJhhgDjA twy4wxR68bz1oTVjFIUn+9EQKbpbzRmjTQ2Lk2khb+ebtARsBMFbXI4ItiyHDy2j agKMb3tRIBM1V/2AMNhjzjiR0NmWCSSUv7ysLDLOS7AUPjMY9mNm0rmaqXbQ0ewx fi2sDfksTvbbL3PXA9IiBmwNsS2sSxm5gxN/OViSKFzeBYLdbNr0YpN+MnOedVaA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeigdekgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfofgrrhht ihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenucfrrg hrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvthenucevlhhu shhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id AC1CF7C1B9; Wed, 10 Apr 2019 00:19:17 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-329-gf4aae99-fmstable-20190329v1 Mime-Version: 1.0 X-Me-Personality: 92534000 Message-Id: In-Reply-To: <9A9810B9-390D-40D2-A547-3B5B1178FEA1@mnot.net> References: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> <9A9810B9-390D-40D2-A547-3B5B1178FEA1@mnot.net> Date: Wed, 10 Apr 2019 00:19:20 -0400 From: "Martin Thomson" To: "Mark Nottingham" Cc: ietf-and-github@ietf.org Content-Type: text/plain Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 04:19:21 -0000 On Wed, Apr 10, 2019, at 13:35, Mark Nottingham wrote: > I read the text as saying that an author is expected to send email to > the WG for each new issues that's raised. Ahh, if you take a strict reading, that's a denial of service attack. Generally, I prefer to have the person who opens the issue bring it to the list. And I will not take a non-issue to the list, even if someone opens a GitHub issue. So a looser interpretation is fine. From nobody Tue Apr 9 21:27:14 2019 Return-Path: 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 80D39120110 for ; Tue, 9 Apr 2019 21:27:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 57hkyRoa2g4A for ; Tue, 9 Apr 2019 21:27:12 -0700 (PDT) Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1412120043 for ; Tue, 9 Apr 2019 21:27:11 -0700 (PDT) Received: by mail-qt1-x832.google.com with SMTP id d13so1370981qth.5 for ; Tue, 09 Apr 2019 21:27:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=p6P7kFrzRO/f/IXeT0crtFYH6GxqmlP6bFkAmPGKdXs=; b=I/a+3N9T5ud7YUAwhO8DiCUd2IR+qj6P1Vr8UjUT2WMXGkbHmLh96NsgK0XBYe3V3I YQV7Feeybh2iYCln6i/QWDhafQPrMhjl8Ptji8oPAIRV/2vQX6TFoHSyNANYpkmHSeRa 7lDMYzXQy4n4YC69Yj+fJigl1zEKOKc8nW7Tw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=p6P7kFrzRO/f/IXeT0crtFYH6GxqmlP6bFkAmPGKdXs=; b=HmjDNVGeeqFnw4x9XC2hHVxUoyv3xnsChpoO/L+j3rfnMvK0pMDPrehkZyeQK1F1CI zKYKzMedeyplaux8qWcKE0ozvngXL4bn2t3uB7Jlpe9LPxNz9A6S6bY75j3SocwL8DYP o607wpNS7qdJsjZjnd2qq57LyiVK47aExgeF/w0eSHdTzwLMY+I7N/v+cXG8SI4FDHaE mxs1QJesjTIoeiJGwZEqec44fU8yYwkzGhCf7jzLJOBKNK9FMnTx5ba1FQKDncS97FMO cTsNh+LYlOQ/iKT01GOH4MffpO6nHVJlY554Kf2RW+8tUkx1GWVQNEFsxse5TWnoz8e6 Nt6A== X-Gm-Message-State: APjAAAXESZrCGADPgZbhaSUa2+3GwL+6PEMSAZOzf+iQ94IIBD/z1GNw GXjxg44i4z6A2Y1iXz1Z5qbezzIPt6w= X-Google-Smtp-Source: APXvYqxcE+t17Zo7YC+iitKgEgNXR/q6arlYxBllzj21yJchCZ5YIpdhIayJVn2/7/n6h3EaDjZzVQ== X-Received: by 2002:ac8:1771:: with SMTP id u46mr26861549qtk.186.1554870430944; Tue, 09 Apr 2019 21:27:10 -0700 (PDT) Received: from sn3rd.lan ([75.102.131.36]) by smtp.gmail.com with ESMTPSA id c84sm18887581qke.0.2019.04.09.21.27.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Apr 2019 21:27:10 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) From: Sean Turner In-Reply-To: Date: Wed, 10 Apr 2019 00:27:09 -0400 Cc: Mark Nottingham , ietf-and-github@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <213F5162-3CBF-479A-BED5-5C42A2ADBBB8@sn3rd.com> References: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> <9A9810B9-390D-40D2-A547-3B5B1178FEA1@mnot.net> To: Martin Thomson X-Mailer: Apple Mail (2.3445.104.8) Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 04:27:14 -0000 > On Apr 10, 2019, at 00:19, Martin Thomson wrote: >=20 > On Wed, Apr 10, 2019, at 13:35, Mark Nottingham wrote: >> I read the text as saying that an author is expected to send email to=20= >> the WG for each new issues that's raised. >=20 > Ahh, if you take a strict reading, that's a denial of service attack. = Generally, I prefer to have the person who opens the issue bring it to = the list. And I will not take a non-issue to the list, even if someone = opens a GitHub issue. So a looser interpretation is fine. I am hoping that we lean towards Martin=E2=80=99s preference here. spt From nobody Tue Apr 9 21:49:45 2019 Return-Path: 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 B8E97120268 for ; Tue, 9 Apr 2019 21:49:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.748 X-Spam-Level: X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 LG5g1YOVqRdp for ; Tue, 9 Apr 2019 21:49:42 -0700 (PDT) Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA95C120269 for ; Tue, 9 Apr 2019 21:49:41 -0700 (PDT) Received: by mail-yb1-xb2a.google.com with SMTP id i10so355422ybk.0 for ; Tue, 09 Apr 2019 21:49:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/zs3rZ45PPgh/4FAaNGqViMaejrcAO+xFgrrkWcuEHg=; b=Dmh/QiUfWovjryNmKJ+vFQMH8FUiG17IflQ6tSYSdy0nfYGXHSlpGmMD6p9/ZKZ/RX bCxDwWZZ1AXov1Ozwgxf1B2K4TAkqqFYOqOBfdEpzLDFZxzzG/EJo2MXHM0dst04SIT4 UrDAdEuvqaiq716LUz5UwrbpEw9B+feqjHID7qzCARWU1pQw+9gg58eKVXxxwzgjWxBT 8NF0O+sM3FlUr1OZlF7IuRWMhCOj/tFThTeHkoEyvMb4hMHeAIsX6KNxO7NpI8PK2HKJ 8S4IYoAGThGZyzwCmNR4Koy3eGzgz7abIlk9zW5NP9z/H+5ScaEHDy0c48FG5v/nhvKi Pm+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/zs3rZ45PPgh/4FAaNGqViMaejrcAO+xFgrrkWcuEHg=; b=ZEfTsn/2hnEGZGxHIbwNFB7/WdasdF1HWE/r9GTCG/AqPT3Q+jp4so3ARj8l9fT1ps fn+XWSqqEUoLpQB3za3Xxk9QLtosZ3EjjopYN8BNmVptdvjtNLsvrmhEo5fpNpXWvjF6 D+t3WbMdhhsZG8awuINSbG/JlfxmYkZzDlJFN8ZAPrOapBlRqnmsyVAXY1aIaxnToPvC /jP1mRKhpD27Kl9aiJDQDnDRYI1xAd8jif2BJg47gshKKZB7pvZyd1SxJflOSGChC3Nn sENUSvqpES1K9knQkH272zLBiagOGShHz1kAZqVvwjBrtOVm9EtSH+Qu2qB3j5yHlPj2 HxMA== X-Gm-Message-State: APjAAAUY6XTIYYrzw04jWHIXsx2sNxubFTOCVFyUVmfFIZ4nNUQtlIyC ZeF88qhPYP0irKN89FD17yQL7lcoYrLFt/oOalk= X-Google-Smtp-Source: APXvYqyuZLGqmE5MVNCUJVHa7mBomg7PgQtXMtWceOeZUBwOld9BpYC71O5AgsDpRlXqWBTz1b2840DjbFGZn+vCtkk= X-Received: by 2002:a25:ae0b:: with SMTP id a11mr15249292ybj.156.1554871780952; Tue, 09 Apr 2019 21:49:40 -0700 (PDT) MIME-Version: 1.0 References: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> <9A9810B9-390D-40D2-A547-3B5B1178FEA1@mnot.net> <213F5162-3CBF-479A-BED5-5C42A2ADBBB8@sn3rd.com> In-Reply-To: <213F5162-3CBF-479A-BED5-5C42A2ADBBB8@sn3rd.com> From: Christopher Wood Date: Tue, 9 Apr 2019 21:49:29 -0700 Message-ID: To: Sean Turner Cc: Mark Nottingham , Martin Thomson , ietf-and-github@ietf.org Content-Type: multipart/alternative; boundary="0000000000002cd17d058625cc27" Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 04:49:44 -0000 --0000000000002cd17d058625cc27 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Apr 9, 2019 at 9:27 PM Sean Turner wrote: > > > > On Apr 10, 2019, at 00:19, Martin Thomson wrote: > > > > On Wed, Apr 10, 2019, at 13:35, Mark Nottingham wrote: > >> I read the text as saying that an author is expected to send email to > >> the WG for each new issues that's raised. > > > > Ahh, if you take a strict reading, that's a denial of service attack. > Generally, I prefer to have the person who opens the issue bring it to th= e > list. And I will not take a non-issue to the list, even if someone opens= a > GitHub issue. So a looser interpretation is fine. > > I am hoping that we lean towards Martin=E2=80=99s preference here. Correct =E2=80=94 looser interpretation was the intent! Best, Chris > > spt > > _______________________________________________ > Ietf-and-github mailing list > Ietf-and-github@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-and-github > --0000000000002cd17d058625cc27 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Apr 9, 2019 at 9:27 PM Sean Turner <sean@sn3rd.com> wrote:


> On Apr 10, 2019, at 00:19, Martin Thomson <mt@lowentropy.net> wrote:
>
> On Wed, Apr 10, 2019, at 13:35, Mark Nottingham wrote:
>> I read the text as saying that an author is expected to send email= to
>> the WG for each new issues that's raised.
>
> Ahh, if you take a strict reading, that's a denial of service atta= ck.=C2=A0 Generally, I prefer to have the person who opens the issue bring = it to the list.=C2=A0 And I will not take a non-issue to the list, even if = someone opens a GitHub issue.=C2=A0 So a looser interpretation is fine.

I am hoping that we lean towards Martin=E2=80=99s preference here.

Correct =E2=80=94 looser = interpretation was the intent!=C2=A0

Best,
Chris =C2=A0



spt

_______________________________________________
Ietf-and-github mailing list
Ietf-and-gith= ub@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-and-= github
--0000000000002cd17d058625cc27-- From nobody Wed Apr 10 09:21:14 2019 Return-Path: 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 251DE1203BA for ; Wed, 10 Apr 2019 09:21:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.339 X-Spam-Level: X-Spam-Status: No, score=-1.339 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, KHOP_DYNAMIC=1.363, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 eYRwGm5Pwb1d for ; Wed, 10 Apr 2019 09:21:07 -0700 (PDT) Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::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 9F1171203D3 for ; Wed, 10 Apr 2019 09:21:05 -0700 (PDT) Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.27/8.16.0.27) with SMTP id x3AGHid1023533; Wed, 10 Apr 2019 17:21:05 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=dOMFShTrRTDtGJ/f5S4s2bE/Fb3PMV/zRIkfljIjBb4=; b=n5vmBsdhlmbFDZ68vbRK9Y6xdCyX8Z/+ZLaOe+WHCQ2jaRbAJSFwm1qTbANlS6fIPb97 c1p29lHR9Xzq6/Ew19Pf//643teegiWvD/8rbR6+vakT8TEOr//UWEJ3v6ojR4Y0uQPn BUUV9Lpr4VVfjzMWLUngZDFzkNu7jvDkVST3xXpayt95zPk00G0VC0yqj1cQita1C1Nm kwatEQPK1RNbbuzP6OfTijC/abkwbCKQsYt4BGUDR/u1ldRvwzxyHqfMpB21sOYTHchv aSxklu/AqvO/8Ap1RU2Oah43g0fSS5vH1dpOION8IqBVkFsN9d+zg1Z1XGDGrBTmkoJf 8Q== Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by m0050095.ppops.net-00190b01. with ESMTP id 2rsf2jh4cy-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 10 Apr 2019 17:21:04 +0100 Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x3AGHfjW029736; Wed, 10 Apr 2019 12:21:03 -0400 Received: from email.msg.corp.akamai.com ([172.27.25.30]) by prod-mail-ppoint2.akamai.com with ESMTP id 2rpqevm9k9-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 10 Apr 2019 12:21:03 -0400 Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.27.101) by ustx2ex-dag1mb5.msg.corp.akamai.com (172.27.27.105) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 10 Apr 2019 11:20:47 -0500 Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.6.131]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.6.131]) with mapi id 15.00.1473.003; Wed, 10 Apr 2019 11:20:47 -0500 From: "Salz, Rich" To: Sean Turner , Martin Thomson CC: Mark Nottingham , "ietf-and-github@ietf.org" Thread-Topic: [Ietf-and-github] GitHub usage for GIT Thread-Index: AQHU7uzXQkTr0wrXQkC9SzQF1s6vlqY07kkAgAAYOoCAAAxbAIAADD0AgAACL4CAAIRVgA== Date: Wed, 10 Apr 2019 16:20:47 +0000 Message-ID: <1EC2C58C-35AD-4334-892E-6E981B9F0B98@akamai.com> References: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> <9A9810B9-390D-40D2-A547-3B5B1178FEA1@mnot.net> <213F5162-3CBF-479A-BED5-5C42A2ADBBB8@sn3rd.com> In-Reply-To: <213F5162-3CBF-479A-BED5-5C42A2ADBBB8@sn3rd.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.18.0.190403 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.19.42.89] Content-Type: text/plain; charset="utf-8" Content-ID: <228328835D5BFB45ADD3B488EB02F9E4@akamai.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-10_07:, , 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904100112 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-10_07:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904100112 Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 16:21:08 -0000 ICAgID4+IEdlbmVyYWxseSwgSSBwcmVmZXIgdG8gaGF2ZSB0aGUgcGVyc29uIHdobyBvcGVucyB0 aGUgaXNzdWUgYnJpbmcgaXQgdG8gdGhlIGxpc3QuICANCg0KPiAgICBJIGFtIGhvcGluZyB0aGF0 IHdlIGxlYW4gdG93YXJkcyBNYXJ0aW7igJlzIHByZWZlcmVuY2UgaGVyZS4NCg0KTWUgdG9vLiAg QW5kIHdlIGNhbiBlbmNvdXJhZ2UgdGhhdCBieSBwdXR0aW5nIHNvbWUgcmVtaW5kZXIgdGV4dCBp bnRvIC5naXRodWIvSVNTVUVfVEVNUExBVEU7IHNlZSBodHRwczovL2hlbHAuZ2l0aHViLmNvbS9l bi9hcnRpY2xlcy9tYW51YWxseS1jcmVhdGluZy1hLXNpbmdsZS1pc3N1ZS10ZW1wbGF0ZS1mb3It eW91ci1yZXBvc2l0b3J5DQoNCg0K From nobody Wed Apr 10 21:15:25 2019 Return-Path: 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 66CDF1200B3 for ; Wed, 10 Apr 2019 21:15:24 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 S8BYdrt8U0F3 for ; Wed, 10 Apr 2019 21:15:22 -0700 (PDT) Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-eopbgr800111.outbound.protection.outlook.com [40.107.80.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D19CA120077 for ; Wed, 10 Apr 2019 21:15:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=X074cSzoRScR2l3HwiMN5C/VH0wVfhpiXb65HTjyTr8=; b=GSJD/Wre60hd2iLztpBVoNceYaUNue7LEm0qtPW97WV7GrAgqPip/UX5nagqFJdn2CEvQqUDNUcwlBubWIAVK15PQ2vpVS7Zfrf8jKs+ZDjp08ws0VBQSchef4O1eiwcquw9I/OPinajkExgeKiISLBXHhvnnDcbKQ7DVD9SDGM= Received: from CY4PR22MB0983.namprd22.prod.outlook.com (10.171.164.151) by CY4PR22MB0392.namprd22.prod.outlook.com (10.173.191.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.21; Thu, 11 Apr 2019 04:15:17 +0000 Received: from CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::bc8f:9757:f4f4:7b86]) by CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::bc8f:9757:f4f4:7b86%9]) with mapi id 15.20.1771.016; Thu, 11 Apr 2019 04:15:17 +0000 From: Mike Bishop To: Martin Thomson , Mark Nottingham CC: "ietf-and-github@ietf.org" Thread-Topic: [Ietf-and-github] GitHub usage for GIT Thread-Index: AQHU7uzYwQUVSU9xBkWbllvFTYEes6Y0mncAgAAYO4CAAAxaAIAADD0AgAGQ/+A= Date: Thu, 11 Apr 2019 04:15:17 +0000 Message-ID: References: <930173E8-BC5B-4F4D-AC3E-052EC38CDC26@mnot.net> <9A9810B9-390D-40D2-A547-3B5B1178FEA1@mnot.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; x-originating-ip: [67.197.48.103] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: c757ab95-35a9-4281-c346-08d6be344e26 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:CY4PR22MB0392; x-ms-traffictypediagnostic: CY4PR22MB0392: x-ms-exchange-purlcount: 1 x-microsoft-antispam-prvs: x-forefront-prvs: 00046D390F x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(396003)(136003)(366004)(39830400003)(346002)(199004)(189003)(13464003)(53546011)(14454004)(6246003)(76176011)(3846002)(68736007)(508600001)(33656002)(11346002)(26005)(966005)(66066001)(7696005)(6116002)(186003)(81156014)(476003)(97736004)(53936002)(316002)(446003)(8936002)(6436002)(8676002)(55016002)(9686003)(4326008)(25786009)(6306002)(110136005)(81166006)(106356001)(5660300002)(99286004)(71190400001)(6506007)(229853002)(52536014)(256004)(71200400001)(105586002)(486006)(102836004)(305945005)(93886005)(74482002)(74316002)(86362001)(7736002)(4744005)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR22MB0392; H:CY4PR22MB0983.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: IZ/jQrwMshOuW0jjz0bzcB0TIjfWZG7LfaE/pHPM/4IxB5b6fk2fe89paxt2UNr2/x+yxfga6IZ5c9hzLgggP4/6JQVHHswygBl7YTn37CT39XFkaQbjakmosuX7P1276rGZEkoAChnsp5yP9pUvOdQxSKicawTTVn4s0LHSQNLtzPdEvlzMoHbE0KJlRqrr98HhObIzl/da0Y5PnWnEtIoQAjuqBV4ZffLvIuCGknn9BYMswzvP/RSYuCK0HdwhMF1v3A7GMKoC04OA3A/rNLGwR1U51ofMqBeeEFMkkKYqdl0bO4o0nW/g2Edhz93mMCAQqZFfZpWleVtrEusS4hvsiL1xOI1rySnvVj1OLtd7yuHaxLB3IWlIDKb86xubTcBARmmLbesrveA+Lm51ZGasDQx927v8XZQVjhBEQEs= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: evequefou.be X-MS-Exchange-CrossTenant-Network-Message-Id: c757ab95-35a9-4281-c346-08d6be344e26 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2019 04:15:17.7483 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR22MB0392 Archived-At: Subject: Re: [Ietf-and-github] GitHub usage for GIT 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2019 04:15:25 -0000 I would also loosen along the axis that purely editorial issues need not be= brought to the list, even if they are actual issues. -----Original Message----- From: Ietf-and-github On Behalf Of Marti= n Thomson Sent: Wednesday, April 10, 2019 12:19 AM To: Mark Nottingham Cc: ietf-and-github@ietf.org Subject: Re: [Ietf-and-github] GitHub usage for GIT On Wed, Apr 10, 2019, at 13:35, Mark Nottingham wrote: > I read the text as saying that an author is expected to send email to=20 > the WG for each new issues that's raised. Ahh, if you take a strict reading, that's a denial of service attack. Gene= rally, I prefer to have the person who opens the issue bring it to the list= . And I will not take a non-issue to the list, even if someone opens a Git= Hub issue. So a looser interpretation is fine. _______________________________________________ Ietf-and-github mailing list Ietf-and-github@ietf.org https://www.ietf.org/mailman/listinfo/ietf-and-github From nobody Fri Apr 12 07:35:23 2019 Return-Path: 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 147C7120306 for ; Fri, 12 Apr 2019 07:35:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.749 X-Spam-Level: X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 BafGa_ppq7Bb for ; Fri, 12 Apr 2019 07:35:18 -0700 (PDT) Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1349712030C for ; Fri, 12 Apr 2019 07:35:18 -0700 (PDT) Received: by mail-yb1-xb2b.google.com with SMTP id e76so3675862ybc.3 for ; Fri, 12 Apr 2019 07:35:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7l2OlFkVl5H6sk1JIbw7zRA6R1ptwh76GsLdEx9kzvI=; b=NLtfKPPFU/eMKaPKBaIW+sg1CSTtmBAjrGeuL+1ttYpALgtN0ulmrF2F7kV/1wS0VJ 8L8tNqjsv9kf2rBU9ydtPRaQpJuIstiSZvN91RSAvrkQJDkzJWVY4JnRMOf4x0Gt7TMA s05BypOAq/42QW8dJt9nTgdHfX4uhJMHqD+0r5ufKjqxx9wxSoRelSak1fM0KXYuLNMg 53I4gnd+DHljr9FO8Kg/u2u4w6wAWLKf7rle48AkZAnV2tc1ikejDlcBHuuw+yaLoxDK jDDOV/esjiPLrln6xXUK2GI1VV4sq/DYUp6vmzbuD3LFjOi2GK2KqqvRBhHlu1LiAlAm duuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7l2OlFkVl5H6sk1JIbw7zRA6R1ptwh76GsLdEx9kzvI=; b=bKbgQibmrkrj4Mr4OW4FNVcvYjGfPh/wyr/oHwxvSOjA8KQAMr3JLkNP+qnPReP2Cw cYvIVdnoyzHRTpWYUX8f7jF+B17bdqZm00N3/pNCmqieJRw90lbQrW/M/Fho5WaNlwCl YaxIF35mUAj+BEK9sEyRrtIiRbie+6kmjfRoWVyXZKz6VV68mk2RJXIo1Yo9nUEwHbvd 8W1midYcuOM4Fy8Sgb/Sw0xyfOWZ/7LKBhwzh7zsMH1KTYYUvHU0p8HQVwgKzggplxZN MjvIQlNaMjXR38sM7P2JJidl8mqDv6rP+mKSIXMtLmSFdW7A3T2SGV3zofgsAKIw+H58 YwGA== X-Gm-Message-State: APjAAAWHdsEtE4sI/iHN3dlpovlN4PTzgk+gPbMQNohGPKx+jnX0qR9k 3zdW2mhcMGZ1u/NXTcr8Q+H+ANBu64nyPuBvTmg= X-Google-Smtp-Source: APXvYqx7AIUnlfycO8MYkj3PDDnKEF0UeVRAm1aVA4k3ASd1YWXkCBR2ErstcedJBcInQKWuLbL1wMJRmhNxOPqRMIQ= X-Received: by 2002:a25:b004:: with SMTP id q4mr46406257ybf.34.1555079717029; Fri, 12 Apr 2019 07:35:17 -0700 (PDT) MIME-Version: 1.0 References: <33EC5505-4738-463B-8317-B453629934C0@eggert.org> In-Reply-To: <33EC5505-4738-463B-8317-B453629934C0@eggert.org> From: Christopher Wood Date: Fri, 12 Apr 2019 07:35:03 -0700 Message-ID: To: Lars Eggert Cc: Sean Turner , ietf-and-github@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Ietf-and-github] Adoption call for draft-thomson-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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Apr 2019 14:35:22 -0000 It looks like we have consensus to adopt this draft as a working group item. Martin, please submit the new version when ready. Best, Chris On Fri, Mar 29, 2019 at 12:12 AM Lars Eggert wrote: > > On 2019-3-28, at 17:56, Sean Turner wrote: > > I think the WG should adopt this draft and I am willing to review it. > > +1 > > Lars From nobody Fri Apr 12 07:37:01 2019 Return-Path: X-Original-To: ietf-and-github@ietf.org Delivered-To: ietf-and-github@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3C541207B6; Fri, 12 Apr 2019 07:36:58 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: ietf-and-github@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.95.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: ietf-and-github@ietf.org Message-ID: <155507981875.16910.9726462056993496927@ietfa.amsl.com> Date: Fri, 12 Apr 2019 07:36:58 -0700 Archived-At: Subject: [Ietf-and-github] I-D Action: draft-ietf-git-using-github-00.txt X-BeenThere: ietf-and-github@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Apr 2019 14:36:59 -0000 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 Author : Martin Thomson Filename : draft-ietf-git-using-github-00.txt Pages : 19 Date : 2019-03-30 Abstract: This document describes best practices for working groups that use GitHub for their work. Note to Readers Discussion of this document takes place on the GitHub@ietf mailing list (ietf-and-github@ietf.org), which is archived at https://mailarchive.ietf.org/arch/search?email_list=ietf-and-github [1]. 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-00 https://datatracker.ietf.org/doc/html/draft-ietf-git-using-github-00 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/