Re: [alto] GitHub Use for IETF Working Groups

Jensen Zhang <jingxuan.n.zhang@gmail.com> Mon, 22 March 2021 11:16 UTC

Return-Path: <jingxuan.n.zhang@gmail.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 7B92C3A1176 for <alto@ietfa.amsl.com>; Mon, 22 Mar 2021 04:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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=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 t-7qjh8yun3o for <alto@ietfa.amsl.com>; Mon, 22 Mar 2021 04:16:48 -0700 (PDT)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (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 781053A1175 for <alto@ietf.org>; Mon, 22 Mar 2021 04:16:48 -0700 (PDT)
Received: by mail-wr1-x430.google.com with SMTP id v11so16224031wro.7 for <alto@ietf.org>; Mon, 22 Mar 2021 04:16:48 -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=k/mawNWWMsJgnp3o5VVua8vSHJ4aih2Zwg4JHmiotVw=; b=ofUyXwps0x4fY0M96zx4KPLZ0g3HY+87aENqn/yTDujv/vQCwfTChv407fSs4527zN CkiviT4p5qIxfUHYhWlUR7P2V5++s8OSi/IMJiwGnMnW/yYb2BpeX3NvRa5j6uR4vRkp JrDJ0rxAe+6sA4QAqIvj1yUhyIUgoOc4LwiMQuJDuFozMv/6pQodrEmQan5Zja3xrO47 nyLbeWJGmMjSZj4P5FX4YQ+72eeyOdC8OVBP//R90FrBgBSahknkZW9fLakDCvZyn9aT zYO+UGdAFepwotlbn85dK95SUqR0Fdb7/tQK6Fr/F3vswGKN99v71Aza6yAKM9JEBDFd e9pg==
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=k/mawNWWMsJgnp3o5VVua8vSHJ4aih2Zwg4JHmiotVw=; b=V+vZyjI7lD3jTRBpVbe79717XDtRWWGBM44e/SmovUUzwQRdaPOG8Fa7YEGrB0r44/ dCtDNHR6JPCBUBGy+rVGBnyXdeDbXUSwruhxqYAWONC/aTSGUprv/viqHpznv6mrlZM3 aMIMqc7mTGjpX5+Rx9GbfBg/I85FyzD5RfgAEIbQyIB8ML7gC1ZsKElJj0VIS8cLQSmQ OFofutoDbJo1eG813MXQjaEHLjg1blIyc5rh1PXP4E1hB1WcN2LvOG/r52COQvrU79fQ ZzIuE2mY5yAZxlxjwr0ZVCN4TW5lI1hSCW/J9/l0Zaf50fFGmui3/I6Oh2jheNOCbkp4 220Q==
X-Gm-Message-State: AOAM5325FiEeShFvMJtQpIfPElnXMIakB6n/DUInHNW5D4x4GmJ38UWA 0wGDQZmo8lffpyqol/oPcIDqgxGCV6gZF9e9iUU=
X-Google-Smtp-Source: ABdhPJw6Ipa2rhv5q+K5JVyGpPA9UXZIEnmYjsd9aAFIPWcMYZQAGkxy3rE1NUBBGsrMXhvT+14CEwZBIIZxaJhdW2Q=
X-Received: by 2002:a05:6000:24b:: with SMTP id m11mr17664554wrz.393.1616411804999; Mon, 22 Mar 2021 04:16:44 -0700 (PDT)
MIME-Version: 1.0
References: <B8F9A780D330094D99AF023C5877DABAADE78F6B@dggeml511-mbx.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAADE78F6B@dggeml511-mbx.china.huawei.com>
From: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Date: Mon, 22 Mar 2021 19:16:33 +0800
Message-ID: <CAAbpuyqRc=POaWLq8ZJvBUva__s4ToDq1vM491LXyqJ0crT3fg@mail.gmail.com>
To: Qin Wu <bill.wu@huawei.com>
Cc: "kaigao@scu.edu.cn" <kaigao@scu.edu.cn>, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000072a3e305be1e3361"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/E3Jyo6ztgzGxaNJTc_UzJm-1Kb8>
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:16:54 -0000

Hi Qin,

It looks nice. Shall we send pull requests or you add us as collaborators
of each repo?

Cheers,
Jensen


On Mon, Mar 22, 2021 at 7:09 PM Qin Wu <bill.wu@huawei.com> wrote:

> 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>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
> <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/
>
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>