Re: [L2sm] Opinions on issue tracker for L2SM please
Qin Wu <bill.wu@huawei.com> Tue, 22 November 2016 01:58 UTC
Return-Path: <bill.wu@huawei.com>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 470A1129416 for <l2sm@ietfa.amsl.com>; Mon, 21 Nov 2016 17:58:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.718
X-Spam-Level:
X-Spam-Status: No, score=-5.718 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-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 bTyRdO29YuWz for <l2sm@ietfa.amsl.com>; Mon, 21 Nov 2016 17:58:23 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7918126D73 for <l2sm@ietf.org>; Mon, 21 Nov 2016 17:58:22 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DBC48852; Tue, 22 Nov 2016 01:58:20 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 22 Nov 2016 01:58:19 +0000
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.151]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Tue, 22 Nov 2016 09:58:14 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "l2sm@ietf.org" <l2sm@ietf.org>
Thread-Topic: [L2sm] Opinions on issue tracker for L2SM please
Thread-Index: AdJBOhBIlyfjMEmNRC2INN5CcvGuTQDKW1vA
Date: Tue, 22 Nov 2016 01:58:14 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA85490E0D@nkgeml513-mbx.china.huawei.com>
References: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk>
In-Reply-To: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.78.218]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.5833A63D.0053, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.151, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: a1a5206490bfbd0921c87abbada6c7b2
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/4L23rMkoFnLdF8OSB10OqcNrFO4>
Subject: Re: [L2sm] Opinions on issue tracker for L2SM please
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2016 01:58:26 -0000
Maintaining L2SMissue in both github and IETF issue tracker requires syncup between them. I prefer to use IETF tool to keep track of these open issues. -Qin -----邮件原件----- 发件人: L2sm [mailto:l2sm-bounces@ietf.org] 代表 Adrian Farrel 发送时间: 2016年11月18日 9:22 收件人: l2sm@ietf.org 主题: [L2sm] Opinions on issue tracker for L2SM please Hi, During the development of the current draft, the authors used issues tracked in github using an old (and possibly inappropriate user ID) at https://github.com/alreadytiredofnomcom/L2SMissues/issues This worked "somewhat" depending on which authors had access to github. We have a three-way choice, IMHO: 1. just continue that issue tracker in github 2. stay in github but move to a better account 3. move issue tracking into the IETF using IETF tools Does anyone have an opinion? Thanks, Adrian _______________________________________________ L2sm mailing list L2sm@ietf.org https://www.ietf.org/mailman/listinfo/l2sm