Re: [alto] GitHub Use for IETF Working Groups
Qin Wu <bill.wu@huawei.com> Mon, 22 March 2021 11:09 UTC
Return-Path: <bill.wu@huawei.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B046B3A1148 for <alto@ietfa.amsl.com>; Mon, 22 Mar 2021 04:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level:
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jddtufq4HkrO for <alto@ietfa.amsl.com>; Mon, 22 Mar 2021 04:09:29 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B50E93A1145 for <alto@ietf.org>; Mon, 22 Mar 2021 04:09:28 -0700 (PDT)
Received: from fraeml741-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F3s8Q1JFvz6802P for <alto@ietf.org>; Mon, 22 Mar 2021 19:04:38 +0800 (CST)
Received: from fraeml797-chm.china.huawei.com (10.206.15.18) by fraeml741-chm.china.huawei.com (10.206.15.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 22 Mar 2021 12:09:20 +0100
Received: from fraeml797-chm.china.huawei.com (10.206.15.18) by fraeml797-chm.china.huawei.com (10.206.15.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 22 Mar 2021 12:09:19 +0100
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by fraeml797-chm.china.huawei.com (10.206.15.18) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Mon, 22 Mar 2021 12:09:19 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.116]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0513.000; Mon, 22 Mar 2021 19:09:17 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "kaigao@scu.edu.cn" <kaigao@scu.edu.cn>
CC: IETF ALTO <alto@ietf.org>
Thread-Topic: [alto] GitHub Use for IETF Working Groups
Thread-Index: AdcfC8uCCA3hNUQJRA+M7ftkLPhFFA==
Date: Mon, 22 Mar 2021 11:09:16 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAADE78F6B@dggeml511-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.123.117]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAADE78F6Bdggeml511mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/InDsW9-Qc--K3exzKAia8hFOHpw>
Subject: Re: [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: Mon, 22 Mar 2021 11:09:34 -0000
Excellent, Kai, can you move path vector document into https://github.com/ietf-wg-alto/<https://github.com/ietf-wg-alto/draft-ietf-alto-path-vector> which will be monitored by ietf secretariat and our Ads. You can see the entry point to ALTO github organization. https://datatracker.ietf.org/wg/alto/about/ -Qin 发件人: kaigao@scu.edu.cn [mailto:kaigao@scu.edu.cn] 发送时间: 2021年3月22日 18:31 收件人: Qin Wu <bill.wu@huawei.com> 抄送: IETF ALTO <alto@ietf.org> 主题: Re: [alto] GitHub Use for IETF Working Groups Hi Qin, Thanks for the email and I would like to second the suggestion. We are already using github for the Path Vector document: https://github.com/alto-wg/draft-alto-pv Best, Kai 2021-03-20 10:47:21"Qin Wu" <bill.wu@huawei.com><mailto:>wrote: ALTO: 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 https://github.com/martinthomson/i-d-template/blob/main/doc/REPO.md -Qin > 发件人: 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 > IETF. > > 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/