Re: Please comment on your use of trac

Paul Wouters <paul@nohats.ca> Wed, 03 February 2021 16:34 UTC

Return-Path: <paul@nohats.ca>
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 BDA543A0990 for <wgchairs@ietfa.amsl.com>; Wed, 3 Feb 2021 08:34:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 1M35xuzXeJxl for <wgchairs@ietfa.amsl.com>; Wed, 3 Feb 2021 08:33:58 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF2183A0A0B for <wgchairs@ietf.org>; Wed, 3 Feb 2021 08:33:38 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4DW6gh3blFz311; Wed, 3 Feb 2021 17:33:36 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1612370016; bh=BoKPsqza0u1qN4QUv+mr+SpHscYvW+oc4YIfTVmYPIo=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=VRFEE8s/CY3tj0kd6sdfs0s8WN/2GDJ+W0eohcRlHRIWvbItVeuOc6V1flPpYYWbM 7TEzWmSiRPt5hBvi03rxmZ1WzCzYHShWIT1Zp4TWAwXJ6ZmNqpJEWpZIT2pA+ncwfh Ecy2uJp2S4eh+kCCkzhgnrhL5HxiGtu5krkDouUA=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 0QTEzqkXxAx5; Wed, 3 Feb 2021 17:33:35 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 3 Feb 2021 17:33:35 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 268286029B62; Wed, 3 Feb 2021 11:33:34 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 254A266B1E; Wed, 3 Feb 2021 11:33:34 -0500 (EST)
Date: Wed, 03 Feb 2021 11:33:34 -0500
From: Paul Wouters <paul@nohats.ca>
To: Robert Sparks <rjsparks@nostrum.com>
cc: wgchairs@ietf.org
Subject: Re: Please comment on your use of trac
In-Reply-To: <a77623bc-bebb-3aa2-4cf7-d645e00dcd45@nostrum.com>
Message-ID: <cd4395f5-dda7-372-3a4-74ca891b4ee@nohats.ca>
References: <a77623bc-bebb-3aa2-4cf7-d645e00dcd45@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/kqK-5_K8LJ2O0tIwoSYGees5yUE>
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 Feb 2021 16:34:02 -0000

On Wed, 3 Feb 2021, Robert Sparks 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.

trans is using it, but we would be fine with a migration to something
else (and hope to be done and close before this work would happen).

Paul