[alto] GitHub Use for IETF Working Groups

Qin Wu <bill.wu@huawei.com> Sat, 20 March 2021 02:47 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id EC7063A1812 for <alto@ietfa.amsl.com>; Fri, 19 Mar 2021 19:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id pIFqK2lCZTw5 for <alto@ietfa.amsl.com>; Fri, 19 Mar 2021 19:47:32 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E8663A1811 for <alto@ietf.org>; Fri, 19 Mar 2021 19:47:32 -0700 (PDT)
Received: from fraeml706-chm.china.huawei.com (unknown []) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F2Q6J3wmkz680CT for <alto@ietf.org>; Sat, 20 Mar 2021 10:42:48 +0800 (CST)
Received: from fraeml706-chm.china.huawei.com ( by fraeml706-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Sat, 20 Mar 2021 03:47:26 +0100
Received: from DGGEML424-HUB.china.huawei.com ( by fraeml706-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.2106.2 via Frontend Transport; Sat, 20 Mar 2021 03:47:26 +0100
Received: from DGGEML511-MBS.china.huawei.com ([]) by dggeml424-hub.china.huawei.com ([]) with mapi id 14.03.0513.000; Sat, 20 Mar 2021 10:47:21 +0800
From: Qin Wu <bill.wu@huawei.com>
To: IETF ALTO <alto@ietf.org>
Thread-Topic: GitHub Use for IETF Working Groups
Thread-Index: AdcdMg8N/OEc7DpLQHCfajgRUGK2Qw==
Date: Sat, 20 Mar 2021 02:47:21 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAADE5EC62@dggeml511-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAADE5EC62dggeml511mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/IAHhintf0M072lASanr18Sx5nhc>
Subject: [alto] GitHub Use for IETF Working Groups
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Mar 2021 02:47:35 -0000


I think it is a good practice to use Github to keep track of any open issues on chartered items.

For all the document authors, I recommend to move your WG drafts to the github,

The following is the guideline to tell you how to upload your drafts



> 发件人: WGChairs [mailto:wgchairs-bounces@ietf.org] 代表 IETF Secretariat

> 发送时间: 2021年3月10日 4:11

> 收件人: Working Group Chairs <wgchairs@ietf.org<mailto:wgchairs@ietf.org>>

> 主题: GitHub Use for IETF Working Groups


> To the WG Chairs,


> Many IETF working groups are now using GitHub. RFC 8875 [1] and 8874

> [2] detail IETF Working Group GitHub administration. Per the RFCs, the

> WG Chairs must add the IETF Secretariat (@ietf-secretariat) and the

> WG's Area Directors as owners of the WG GitHub organization.

> Instructions for how to create your WG GitHub, as well as how to add

> the appropriate owners, can be found on the WG Chairs page [3].


> If you already have a GitHub organization for your working group,

> please verify that the IETF Secretariat (GitHub user ID: @ietf-

> secretariat) is an owner. In addition, please make sure that the WG

> GitHub is included within the “Additional Resources” section of the

> the WG’s Datatracker page (e.g.,

> https://datatracker.ietf.org/wg/drip/about/). In addition to making it

> easier for people to find, linking your GitHub from within the

> Datatracker also ensures that the GitHub data will be backed up by the



> If your working group does not yet have a GitHub Organization and you

> would like us to set one up for you, please send email to

> support@ietf.org<mailto:support@ietf.org> with the subject line "GitHub Organization Request

> for WGACRONYM." Please include the GitHub ID for each WG Chair and WG

> Secretary.


> If you have any questions, please let us know!


> Best regards,


> The IETF Secretariat



> [1] https://www.rfc-editor.org/info/rfc8875

> [2] https://www.rfc-editor.org/info/rfc8874

> [3] https://www.ietf.org/chairs/github/