RE: Please comment on your use of trac

"Rob Wilton (rwilton)" <rwilton@cisco.com> Wed, 03 March 2021 15:42 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA383A1516; Wed, 3 Mar 2021 07:42:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.62
X-Spam-Level:
X-Spam-Status: No, score=-9.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=OzmpoUe4; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=W45j1mRX
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 mX7cafrhn8WA; Wed, 3 Mar 2021 07:42:22 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E9713A1512; Wed, 3 Mar 2021 07:42:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7464; q=dns/txt; s=iport; t=1614786142; x=1615995742; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Q8mK8VKiqjrNZoCQxep0LeESa/3vuGJzu1Kqb8G+jS0=; b=OzmpoUe4A+3jXrncJ3pn/StjaEioIjEJvqnslbDURcAV9JrdY3xG9hXv Hw10nnrXqENgHoz9VcT2yvoyxXEp0JmpZZhjMy2DsxKY9K9wE9FDUVxOq Hz2pEqrLCeRZxGO12kLufJwdj/ypcQ9uHZ8eRqXJoWodeXLEG4DMvoZY+ w=;
IronPort-PHdr: 9a23:sCVeWh8kVy1qXP9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+7ZRSN7OlxylTOWNaT5/FFjr/QtKbtESwF7I2auX8POJpLS1ceiMoQkgBhZazNCUDyIPPwKSBvGsNEWQxs4239Ok9QS47yYlTIqSi06jgfUhz0KQtyILHzHYjfx8S63uy/4dvdeQJN0TG8erh1ah6xqFbc
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B6AQDZrT9g/49dJa1iHAEBAQEBAQcBARIBAQQEAQFAgT4EAQELAYFSUQeBUDYxCgGENoNIA4U5iFUDjxuKBoJTA1QLAQEBDQEBMgIEAQGETQIXgWMCJTcGDgIDAQELAQEFAQEBAgEGBHGFNAcmDYZEAQEBAwEjEQwBATcBBAcEAgEIEQQBAQECAiYCAgIwFQgIAgQBDQUIhT4DDiEBA6JyAooldoEygwQBAQaFJBiCEgmBDioBgnWECIJSgnl6JhyBSUKBEUOBWVAuPoQVK4MUNIIrgU8vTiY8ARAVBRQIMC8hAQodNAgWARcBBG2QCxqDMqVnCoJ8nEKDN4pPlVCUVZtRgU4pHIQ5AgICAgQFAg4BAQaBaiSBV3AVgyRQFwINgzeKaINvillzOAIGAQkBAQMJfIhTgTUBMV0BAQ
X-IronPort-AV: E=Sophos;i="5.81,220,1610409600"; d="scan'208";a="859050820"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Mar 2021 15:42:21 +0000
Received: from mail.cisco.com (xbe-aln-005.cisco.com [173.36.7.20]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id 123FgKGG020413 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Wed, 3 Mar 2021 15:42:20 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xbe-aln-005.cisco.com (173.36.7.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.792.3; Wed, 3 Mar 2021 09:42:20 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 3 Mar 2021 10:42:19 -0500
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 3 Mar 2021 10:42:19 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GXMZUB2oIQehQLg24ne1V04ff9m12WOHVT0z0ajCvq3XyfN/RZUJ30wiCt+A2ZxjSjfgEWpHkcmbXs8TkzqoWsnhQKDHx2e+JEl79PgquBUUGGYj4q0oRQG7oQlGjQ/nOwf3t25A32e2tcn/50b9gKEj9rMfy3of9EBOAtxOp6N8ieGN5QnQgYKky8TGMGi4Vc2zOPKmxIS9FJZiqk1gXxOeN2rKQM6l/XITAmI0z9Z84gQDLEgNgUGXldVPP/wHI+s1UGbBl4hLl3Hpngz8FV7SI9CBCJYGYSV3r1WcP150uU2MlE++2EloyVZEF+a+woWoXjt3/HtMH7RqDWpyow==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Q8mK8VKiqjrNZoCQxep0LeESa/3vuGJzu1Kqb8G+jS0=; b=A/F4EChWujGcNrrAiM6FB7VtPV872RQ7i9EA0qjJ0hLfWzJvdibMKTdzEujY9PJDl2r36SomJKPqyuPOiMzWEK2naNSSUqo8ngld8IVB7zuLDW/mZrzVWV6byviuJC/hBqZ3+IRaOZpX6Dhc4m4XcY5XIE1O5cNJ809RHXKYuLH74f+lxIM8KTvZaGebyC7guEl5cXFu2ktomXcmwYXgFizzZSQMbd4cDyQY5WDWlj3sFEuZogf0rKiDmA+XHoKJIgSgwZI7gnQOkm8co0D16Zqly2idUB0LtI//6scUoVHyedg2SwCnMwxLNHI8H7yOt+ERjNMDLhBZXZrWtlA/Qg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Q8mK8VKiqjrNZoCQxep0LeESa/3vuGJzu1Kqb8G+jS0=; b=W45j1mRX452txEfN0ON+DX7PqW4pGZgkIrEHcua9S2p3ggtrqgVoQ2ctudMK7He4kBxA+FhdRKZGj9aADKl3DA5rWiTc0TuD385OmlclRhGbuc8ke4/5KsnL9i9HuOzLo2jTmtmPc/4XlZ4IOjKv/JJuk/tSVCXibnJ5kNlsp1A=
Received: from BY5PR11MB4355.namprd11.prod.outlook.com (2603:10b6:a03:1c3::13) by BY5PR11MB4088.namprd11.prod.outlook.com (2603:10b6:a03:185::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3912.17; Wed, 3 Mar 2021 15:42:18 +0000
Received: from BY5PR11MB4355.namprd11.prod.outlook.com ([fe80::81c7:f68d:5e2f:a5d9]) by BY5PR11MB4355.namprd11.prod.outlook.com ([fe80::81c7:f68d:5e2f:a5d9%7]) with mapi id 15.20.3912.018; Wed, 3 Mar 2021 15:42:18 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: "STARK, BARBARA H" <bs7652@att.com>, 'Jay Daley' <jay@ietf.org>, "'wgchairs@ietf.org'" <wgchairs@ietf.org>
CC: 'Robert Sparks' <rjsparks@nostrum.com>
Subject: RE: Please comment on your use of trac
Thread-Topic: Please comment on your use of trac
Thread-Index: AQHW+kguJ/rvsgg1F0WKvwtTPh2gFappmb+AgAFBW4CAB2zpoIAAPByAgAAHAWA=
Date: Wed, 03 Mar 2021 15:42:18 +0000
Message-ID: <BY5PR11MB4355ADC986A858D059D48891B5989@BY5PR11MB4355.namprd11.prod.outlook.com>
References: <a77623bc-bebb-3aa2-4cf7-d645e00dcd45@nostrum.com> <99EEE704-6166-48FB-BAAF-953FDD066065@ietf.org> <DM6PR02MB6924D6A0B9367FC5622E056CC39D9@DM6PR02MB6924.namprd02.prod.outlook.com> <MN2PR11MB4366801F52B2537215855476B5989@MN2PR11MB4366.namprd11.prod.outlook.com> <DM6PR02MB6924501C6F1DF5548341A240C3989@DM6PR02MB6924.namprd02.prod.outlook.com>
In-Reply-To: <DM6PR02MB6924501C6F1DF5548341A240C3989@DM6PR02MB6924.namprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: att.com; dkim=none (message not signed) header.d=none;att.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [82.12.233.180]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f2865ea5-9df7-4d5d-909e-08d8de5aed37
x-ms-traffictypediagnostic: BY5PR11MB4088:
x-microsoft-antispam-prvs: <BY5PR11MB408868A0DD5465C69C639F9AB5989@BY5PR11MB4088.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: z/sqSHMmbw2+1W2YdxaMlV75HrbDgSzjjiRHmUXDecYvY0mr4YW71FYXB5OYYJJdDSsOG6BxGIvvvjM0hA4XnPqYVNj5MvzzkwJ6xUx0X6deLVBmAQvWogBOLUjzrVjoBkBVz9eZXMwKDuXIf1U5kgbJqNKO4r65pA4/drxjPDmkbAifDrkTLN68VFbYyOndt0ZZHC9S1GZaioIGoh7bwee0J/OPEQXECpEII8qDMU0i6x+blQk4YRHhoH6FDPQwGO6vVh48tK+GCq4Y1ExIHlcANrNq6rh83oDJ2CiQolaeBFxb0QIQh+ZuGXLeIcx7ucVk64hn+PCbj52g2tHkDaoWriFfobogAsTTETeNeGzTpT4R/VDKwakdBSY6rI34G2RvqOCnSNJ/OR9O4vZYnyTJRHt+kb4TTSLbSduNvB5t1J0gOZFqzDcNAEb825JbWBBJTUrB09ZaRz7Y6P3tfEf5GjbMbFfE1XU/tvVNpkQnR6RS5XbyOBDgX0bgabkMUenPueOhk6QnDkTN9PsLhFJKhd16DapnzaHMEOL3joliIztoN/VDe1UAdASzrZiw
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR11MB4355.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(136003)(346002)(376002)(39860400002)(366004)(396003)(64756008)(66946007)(5660300002)(66556008)(83380400001)(66476007)(66446008)(4326008)(478600001)(2906002)(33656002)(186003)(53546011)(55016002)(26005)(52536014)(8936002)(8676002)(9686003)(7696005)(71200400001)(86362001)(110136005)(76116006)(6506007)(316002)(491001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: Qr5nxrVUkaIMeO2nZHDUGLfqB4a7hZm2jAUx9t/Kkw3z4k7ujxoDzrPW8NIeVWil5C7uElWkQ1u0UvPx9LQW4weKB1jSa+ffG67v98hepvNVlA0+8zPN29BKfOSl5gotXS6QPbHP0QdEABOfZK4YzkNdqOQypOBd8hszg7NXFI8XRDA4CMdHczfPdjzn1mBAjdUu0AdO9HPccp+6lqKFRdjpHJ1/KEF2U0FAWoC9ir5DkubT1WAEaIkt1soskqY9rXliArf93XNtmOZFkeLvPCcxbhGhgALZtjMDop3DlXIthdMau3CGR1FSGfVpBJ8bO68onuWvJxu45LV64dKrADnpwgusa1DUQTT0lLXSXYVFtZh0rlrGKERkN/wPybPavsxmQb5L6RUM1Ye9Z6CCs6NFzfv9V9ujSu759uCQCURuncj7aTUcOR6VfAbEeIynuOa+jHmvsARQ3v5bG23FuRNOrJLyWKcqZ7WXIdeAo1YYCAZgrnJFB2OP6bUUqPBxv28E+dRm+lkv65uk6vKpXAk/LvgBF7rZjTxHsnsoFy3SrB8BovjKaYM4d4f7pLuYe7Wy2g7Jir02LgexBLeHHfGlElt/X+QTBTGjtNRdwmoNQS4i8jfzql+fOvHRPAJ02otuyqQH/Du9jbjvKaVpDevf9TQofWDkLLiVpeg3dK4WZPwubw24Y+DXi9uNIc2C38SNNWex4KzVlEgOwVCxO9/3Runxxe9eO5Tkp5CJcjtBeve3NF9CaEZJvS5cybEQkUf/WGj5W2z4lieb6Hvq+p83Gh6X1XjCPGym1jCtHyZMILOpEX9RwLb/btdYVBMUqKa8P2ppselQlVaqOHk5Cik0kywU9+M+ORyeKgTiOvmNA0QOqccX2DodWiwmOTfHv+cZtWFGxbVmbHS71uyA6Gcp4OOYevPOhqhb4B/m/7L4m0Ky0RXjfDrVZ/XKEulb9/toIqgqU/oaehkrg1nb5o7mUb1h6150JddJctpBB2J/qYkY563qMjowbtMrV9vvX5UhPWMZEam1C87+U6bAL3n3TZ2lsld7+qSMHZ3git+/Xn+zWuEMsZCVYRAZ/qK4xFpjuXtoVQQnhHxw/2u89h7FtUkMt1rpQKNlsehwE8SXIEAt89X3L6PymVsobNeKzaDEtqgeCZjgmYHaoZE36gQiCYLmxIiDDj97fQWmGXeq63S+WZtXEvZG8b0ljoj9qsP54T53yHvZ01Lii7pzPBG7cgd31jB1QZKiZKUi9bMSSIH/yfpI7T0aWRg1/InOCIn0AlK0ujES3wkrgNoK61yZVqzv/MMrld10ts0uxV9CXP1OVBUBnMpBIdieB1MC
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY5PR11MB4355.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f2865ea5-9df7-4d5d-909e-08d8de5aed37
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Mar 2021 15:42:18.0460 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: s5wNcYLHwXo5T/4zVzcAevn42XnaaU0Zo7wLm2Qd6hVST21t0LUTWgpVX+waLoR/UM3DTc3+Lux4phKj8MNygw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB4088
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.20, xbe-aln-005.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/08sLI-dGOj3IU-NLZYFu8A5KdjM>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2021 15:42:24 -0000


> -----Original Message-----
> From: STARK, BARBARA H <bs7652@att.com>
> Sent: 03 March 2021 14:49
> To: Rob Wilton (rwilton) <rwilton@cisco.com>; 'Jay Daley' <jay@ietf.org>;
> 'wgchairs@ietf.org' <wgchairs@ietf.org>
> Cc: 'Robert Sparks' <rjsparks@nostrum.com>
> Subject: RE: Please comment on your use of trac
> 
> Hi Rob,
> 
> > Hi Barbara, Jay,
> >
> > >
> > > > I’m in the process of drafting the RFP for this work and I want to
> check
> > > a few
> > > > things base on your replies:
> > > >
> > > > 1.  It sounds as it everyone is comfortable with a migration to a
> new
> > > wiki system
> > > >
> > > > 2.  A few WGs - EMAILCORE, DMARC and TSVWG are using trac for issue
> > > > tracking and need migrating to a new issue tracker.  Would you be
> happy
> > > if that
> > > > was GitHub? (DMARC has already indicated this is acceptable).
> > > >
> > > > 3.  Many more WGs used to use trac for issue tracking but no longer
> do.
> > > We
> > > > need to find a way to archive these for the historical record, but I
> > > want to check
> > > > you would be happy if that was just an export to a text file that
> could
> > > then be a
> > > > wiki page rather than moving them to a new issue tracking system?
> > >
> > > I'm fine with this, but want to note the private nomcom2020 wiki
> should be
> > > archived in a protected place and not be publicly accessible. It might
> not
> > > be great to have minutes of NomCom deliberations out there for all to
> see.
> > > So, just a request to take care with the archiving. Feel free to
> consult
> > > with me when this is done (I see RFC8713 says the impacted NomCom gets
> to
> > > vote on how to implement an archive). Also, NomCom archives are only
> > > required to last for the duration of the NomCom term. So it would be
> good
> > > to be able to delete this archive in the future. Victor may have
> thoughts
> > > on whether he'd like nomcom2019 archived at all, since its term is
> over. I
> > > also see there are nomcom2017 and nomcom2018 wikis. Someone should
> > think
> > > about these, too. - Barbara
> > [RW]
> >
> > Doesn't this text in RFC8713 require that the NomCom archive is deleted
> when it
> > is no longer required?
> >
> > 5.16.  Archives
> >
> >    The NomCom should archive the information it has collected or
> >    produced for a period of time but not to exceed its term.
> >
> > I don't know what information the NomCom archives contain, but my
> concern
> > here is potential reputational risk to IETF if confidential information
> ever leaked.
> > From a privacy perspective, if the information is longer required, then
> the safest
> > action seems to be to ensure that all copies of any confidential or
> private data is
> > destroyed.
> >
> > Regards,
> > Rob
> 
> I would certainly interpret it that way. But I'm not Chair (and nor was I
> a member) of a NomCom whose term is over. The 2020 NomCom's term ends in
> November (the Third IETF of 2021). I think it's for others to decide what
> to do with the artifacts of prior NomComs. I'm merely noting their
> existence while asking for the NomCom 2020 artifacts to be appropriately
> handled through November.
[RW] 
Okay, understood.

Regards,
Rob



> Barbara
> 
> > > > 4.  The following features for a new wiki system have been
> recommended:
> > > >
> > > > 	* document names resolve to links to the documents without having
> > > to
> > > > require explicit URLs.
> > > > 	* I would like a markdown based wiki system.
> > > >
> > > > 5.  We are currently considering moving to a *single* wiki instead
> of
> > > multiple
> > > > different instances of the same wiki.  The means the following
> features
> > > are
> > > > needed to support the various ways that WGs and other groups use
> their
> > > wikis:
> > > >
> > > > 	• support of OIDC for authentication with Datatracker
> > > > 	• permissions system (which will be limited to roles that
> > > Datatracker
> > > > know about)
> > > >
> > > > (so far the product that seems to meet these requirements the best
> is
> > > Wiki.js)
> > > >
> > > > Any comments, or any more to add?
> > > >
> > > > Jay
> > > >
> > > >
> > > > > On 4/02/2021, at 5:17 AM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
> > > > >
> > > > > We currently have instances of trac configured for each working
> group.
> > > Only
> > > > some are being used.
> > > > >
> > > > > If your group is using trac, are you using anything essentially
> trac-
> > > specific that
> > > > you find important?
> > > > >
> > > > > Would you be ok migrating (with help) to a different wiki system
> and a
> > > > different issue tracking system?
> > > > >
> > > > > The trac project itself is lagging with Python development -
> stable
> > > still only
> > > > runs on Python 2.7 and while there appears to be work towards Python
> 3,
> > > it is
> > > > not yet functional, and is not progressing quickly. We are working
> > > around it by
> > > > encapsulating it in docker instances running 2.7.
> > > > >
> > > > > I've had several people suggest we should stop supporting it, and
> I'd
> > > like to
> > > > know if that would be a particular hardship for any group.
> > > > >
> > > > > RjS
> > > > >
> > > > >
> > > >
> > > > --
> > > > Jay Daley
> > > > IETF Executive Director
> > > > jay@ietf.org