[L2sm] Opinions on issue tracker for L2SM please
"Adrian Farrel" <adrian@olddog.co.uk> Fri, 18 November 2016 01:22 UTC
Return-Path: <adrian@olddog.co.uk>
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 CF0C4128E18 for <l2sm@ietfa.amsl.com>; Thu, 17 Nov 2016 17:22:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 4afVFUGxbpsA for <l2sm@ietfa.amsl.com>; Thu, 17 Nov 2016 17:22:15 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93A6B126579 for <l2sm@ietf.org>; Thu, 17 Nov 2016 17:22:15 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id uAI1MCa2008525 for <l2sm@ietf.org>; Fri, 18 Nov 2016 01:22:13 GMT
Received: from 950129200 (dhcp-885c.meeting.ietf.org [31.133.136.92]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id uAI1M97P008513 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <l2sm@ietf.org>; Fri, 18 Nov 2016 01:22:12 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: l2sm@ietf.org
Date: Fri, 18 Nov 2016 01:22:07 -0000
Message-ID: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdJBOhBIlyfjMEmNRC2INN5CcvGuTQ==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22706.004
X-TM-AS-Result: No--2.539-10.0-31-10
X-imss-scan-details: No--2.539-10.0-31-10
X-TMASE-MatchedRID: hLCpkDKaeHYR9y8WJPyXEBJEh4A6+HuFYu7s3QSSN+T2nE4Y4IcpXG8A 97SYsaq8iCMyfrGuZhdpykTUaVN5S5DQGJm7p8JD/c0+LJTMrN1oFNaNcVdd3wpcq1+LTpsUo8W MkQWv6iV95l0nVeyiuBQF+BLVItD4C24oEZ6SpSmcfuxsiY4QFBcNsK3MAovEJOsMB+uQ9VP7AG hGO8MhdODCRKrdUZ3hh6E8FGha9eoRxZ5k5S3drrgrpCiF0ClCAr3gsUencER7BAT9a9xCDfR5g LDNdb9LuOZoyiCGGN8YgmnfWgSln5vaf0QvfUyeS4W/MRhJ1X4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/mL9Z7-rvRFWHKRRRGyjG4bfx7Xw>
Subject: [L2sm] Opinions on issue tracker for L2SM please
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Fri, 18 Nov 2016 01:22:17 -0000
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