[L2sm] R: Opinions on issue tracker for L2SM please

Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it> Tue, 22 November 2016 13:53 UTC

Return-Path: <giuseppe.fioccola@telecomitalia.it>
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 1FFCE1293DB for <l2sm@ietfa.amsl.com>; Tue, 22 Nov 2016 05:53:26 -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 UFUjLPyOFtuh for <l2sm@ietfa.amsl.com>; Tue, 22 Nov 2016 05:53:24 -0800 (PST)
Received: from TELEDG001RM001.telecomitalia.it (teledg001rm001.telecomitalia.it [217.169.121.18]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF27812947A for <l2sm@ietf.org>; Tue, 22 Nov 2016 05:53:23 -0800 (PST)
Received: from TELMBXB02RM001.telecomitalia.local (10.14.252.27) by TELEDG001RM001.telecomitalia.it (10.19.3.111) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 22 Nov 2016 14:53:20 +0100
Received: from TELMBXB02RM001.telecomitalia.local (10.14.252.27) by TELMBXB02RM001.telecomitalia.local (10.14.252.27) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Tue, 22 Nov 2016 14:53:20 +0100
Received: from TELMBXB02RM001.telecomitalia.local ([fe80::2845:411e:c732:e844]) by TELMBXB02RM001.telecomitalia.local ([fe80::2845:411e:c732:e844%20]) with mapi id 15.00.1236.000; Tue, 22 Nov 2016 14:53:20 +0100
From: Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it>
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: AdJBOhBIlyfjMEmNRC2INN5CcvGuTQDYmdVQ
Date: Tue, 22 Nov 2016 13:53:20 +0000
Message-ID: <1d400463cd4a498eaf7e8cab3df331c7@TELMBXB02RM001.telecomitalia.local>
References: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk>
In-Reply-To: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.14.252.245]
x-ti-disclaimer: Disclaimer1
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/AWIQZ9fjJ9Wf6ggpgY5fI00BW5Q>
Subject: [L2sm] R: 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 13:53:26 -0000

We should move issue tracking into IETF tools, that could be better in order to have only one reference for the open issues.
Thanks,

Giuseppe

-----Messaggio originale-----
Da: L2sm [mailto:l2sm-bounces@ietf.org] Per conto di Adrian Farrel
Inviato: venerdì 18 novembre 2016 02:22
A: l2sm@ietf.org
Oggetto: [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

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.