Re: [irsg] Please comment on your use of trac

Dave Plonka <> Thu, 04 February 2021 14:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 996E33A14E8 for <>; Thu, 4 Feb 2021 06:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.098
X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_DOTEDU=1.997] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tHdepBQrXF6L for <>; Thu, 4 Feb 2021 06:11:31 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E56E63A14E9 for <>; Thu, 4 Feb 2021 06:11:30 -0800 (PST)
Received: by with SMTP id c4so3633596wru.9 for <>; Thu, 04 Feb 2021 06:11:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=464PKCeFsu1jmC0U2J21f2+mBkI8jBbkx2yfIzxr7ZU=; b=CZXVrrwwwLYByu30tmyW1b+lS2ypFUc3vvqv4XPfJR+F4kQT3NDmYxgzocbDLKVf7g 7XOMxttFQHVrYvapVT/6wJHzClHsZ2X6y9FWgRbn8x910Pl0beyLrV6eeO2+8hj/SRvI cr9rWsn+6GfD1mqYqpbySr9DWo3q/gJ+GJTf/2EeN5ft/maRFFuLTWro72Q+rqVNuSkW lTEn2yaTTwtlCwmuN5CBK7WP8UmLlUe4MH3VbRyikX+TPCmQaDEM9h+FfzvE+mRamyA3 Kj9uyMWDwisIjpXacwH1A5AK3Ipx45KG4qOT1R7bXpORMM+r/gNKw4BTARM8h0/zDekb iKdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=464PKCeFsu1jmC0U2J21f2+mBkI8jBbkx2yfIzxr7ZU=; b=Vo10dBImrENnnfXD0NuvOx6jnZcxiECJZ9Sqr2RXBdZahB1OlHSLGcIIV2kzHBu0mA S0OTu+LoGEb8iUcZpZokyuMv/fRErbPpLFynb1HBy7qD2qKc4N5Dz+ED5ccees1i+d7c nfCF/6aX7IWJf9Aapv4CMhgSIwIbkqZ7odhLwLbBq2skYo2m26V1Kgr9b9HukWSjLNeT CB82c2+BRfjF6W1gOQuVN5fXECAW0wDzyF27Ca8Gf3MPc6ryqd6B+BBUV7YXffcqwdVx wS3aFDO/vTQPKZLKr7Q/Uhv8C60WIb7+F0RHvVFzOnxFwRMLtcjsk7SqHLGurY4y1flj hSqA==
X-Gm-Message-State: AOAM533ytuMbO3DsdndPA8rAJSCkf+8+/Lx8BNn8Dcm0JT47oqXRowXp XDnfNUhM1LNwVwIxmF6Y6tYOmolpMm3IDe1EOeS/Tg==
X-Google-Smtp-Source: ABdhPJxmHzj7x1ztWNV5zfpbCVk/6+pA/ay3JXJd/UOPnv3jqdw3Fy7oHpO9yaTRLTBEu4FdQX8iibVzaCvcB8lUsiw=
X-Received: by 2002:a5d:62c4:: with SMTP id o4mr9774367wrv.292.1612447889245; Thu, 04 Feb 2021 06:11:29 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Dave Plonka <>
Date: Thu, 4 Feb 2021 08:11:18 -0600
Message-ID: <>
Subject: Re: [irsg] Please comment on your use of trac
To: Robert Sparks <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 04 Feb 2021 14:11:33 -0000

The Measurement and Analysis for Protocols RG, which primarily hosts
nascent measurement/performance results about IETF-defined protocols,
uses trac to keep an ordered index of all presentations/topics from
its meanings in the wiki:

Specifically, the wiki has worked well for being able to jump to the
right point in the IETF YouTube MAPRG meeting videos (minute and
second), given the meeting, presenter name, or title.

I would be open to a different wiki system if trac is changed or goes away.


On Wed, Feb 3, 2021 at 10:18 AM 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.
> RjS