Re: [alto] GitHub Use for IETF Working Groups

kaigao@scu.edu.cn Mon, 22 March 2021 10:31 UTC

Return-Path: <kaigao@scu.edu.cn>
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 A95483A1024 for <alto@ietfa.amsl.com>; Mon, 22 Mar 2021 03:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[HTML_MESSAGE=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 uR3_OGP9fj7v for <alto@ietfa.amsl.com>; Mon, 22 Mar 2021 03:31:13 -0700 (PDT)
Received: from zg8tmty1ljiyny4xntqumjca.icoremail.net (zg8tmty1ljiyny4xntqumjca.icoremail.net [165.227.154.27]) by ietfa.amsl.com (Postfix) with SMTP id 8060D3A1016 for <alto@ietf.org>; Mon, 22 Mar 2021 03:31:11 -0700 (PDT)
Received: by ajax-webmail-app1 (Coremail) ; Mon, 22 Mar 2021 18:31:06 +0800 (GMT+08:00)
X-Originating-IP: [171.223.194.167]
Date: Mon, 22 Mar 2021 18:31:06 +0800 (GMT+08:00)
X-CM-HeaderCharset: UTF-8
From: kaigao@scu.edu.cn
To: "Qin Wu" <bill.wu@huawei.com>
Cc: "IETF ALTO" <alto@ietf.org>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT5.0.13 build 20210104(ab8c30b6) Copyright (c) 2002-2021 www.mailtech.cn mail
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAADE5EC62@dggeml511-mbs.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABAADE5EC62@dggeml511-mbs.china.huawei.com>
Content-Type: multipart/alternative; boundary="----=_Part_64041_498052418.1616409066160"
MIME-Version: 1.0
Message-ID: <199928b6.4737.178597cfab1.Coremail.kaigao@scu.edu.cn>
X-Coremail-Locale: en_US
X-CM-TRANSID: 4wAACgBH52DqcVhgSfsvAA--.5072W
X-CM-SenderInfo: 5ndlwt3r6vu3oohg3hdfq/1tbiAQQBB138kk1XYgA1s9
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/K99uCViso-FG72ickeLqRg3IDy8>
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 10:31:18 -0000

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>wrote;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>

> 主题: 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 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/