Re: Please comment on your use of trac

Todd Herr <> Thu, 04 February 2021 14:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0D7863A1534 for <>; Thu, 4 Feb 2021 06:37:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oWRaIkqhnuK7 for <>; Thu, 4 Feb 2021 06:37:44 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::82d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2064C3A152E for <>; Thu, 4 Feb 2021 06:37:44 -0800 (PST)
Received: by with SMTP id v3so2496221qtw.4 for <>; Thu, 04 Feb 2021 06:37:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ETrVQTXZnWUD3dArw4pRo4ym62sD3m1ZsqfMd+zkPLc=; b=LQXQZ54hUkLIHnmppmLquSeMK8sS1BH1yKz02bL21aK4T794yH70qKUuDsJfWET8cf 3S6rpgJfjxzFvcXAoByb2uIV2eRKRcgYHPGh2qUq3Es8sIg45a1aOAUX7MqjnnI6Limy /NXOMXcEd/Q7J1jwWljb+tdUTdhHekG2FJCwLAU8yIwD5HoW5Mhb73Gpo6Nyo9wIfGyX vNZPO2ld/ZuBQzezv8CmAp9oy5YQM6sTkNSXXJNZk00UU+bJ57PWEkbYOtoWA5fjphFE YfXDXSx1wO5bl6WZGWvc68PpYpU+EUcmdwZOufqUnq6iU391i17n/k8aWH4vARt8hivf vEWg==
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=ETrVQTXZnWUD3dArw4pRo4ym62sD3m1ZsqfMd+zkPLc=; b=OdZ3Li6uyZFwIVbBeZPdXdxVVJ1c+d9ID+5k4QxeXzSYwD2lNcTAys8ZhEGO8Pu7ex 9dsFcadUS8PsTrwAfF9PtoHhn1CpRlaCUI/sGM3pv1cK1UNgGByzrXpgLZt1Fgmm1ELJ LHYTMm+crDl2mjrC/dUVOmO3F4MOwRZl69+/jf7moE439oGJVDhgXlzBhdn5WUhmXUNU ewrQ+7UFk6RLc7AtseKaTq60jR9Y3Eio55y+JGwp1000Gw7u6xsVJxzUDs+JPau6T8Of NC80sqr+13a9slPjqxvGnOHmOmXLSPrJkLxWet54Y/REL9epPnNUX3JaKL42utEdecAR TpqA==
X-Gm-Message-State: AOAM532Ng9JMMXhzBe7zzVaKVT+XFOTA+kD/lN7yUXFF8iJza+SMArOc /GDW+/vOgufX8RoKItO4Keykf+PCJaruuiwIXzIwvhUqILc=
X-Google-Smtp-Source: ABdhPJyzxXPNpSi686EsnF6+JMhA8vX2wVyBmfDGqtI68/TEy38FWAn+kx/HcFr9Iirc2Aeh/i6l9F3ouHYH62jyr1U=
X-Received: by 2002:a05:622a:20c:: with SMTP id b12mr7421597qtx.208.1612449463061; Thu, 04 Feb 2021 06:37:43 -0800 (PST)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Todd Herr <>
Date: Thu, 4 Feb 2021 09:37:26 -0500
Message-ID: <>
Subject: Re: Please comment on your use of trac
To: Tim Wicinski <>
Cc: Robert Sparks <>, Working Group Chairs <>
Content-Type: multipart/alternative; boundary="00000000000076ee8705ba83a5aa"
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:37:46 -0000

+1 to what Tim said here. He and I recently went through an exercise to add
more status options/improve the workflow in the trac config for DMARC, but
for me that was only because I didn't know that there were other options.

Would happily migrate to GitHub or any other ticketing system.

On Wed, Feb 3, 2021 at 2:16 PM Tim Wicinski <> wrote:

> We use trac in DMARC but only because I feel it's the 'standard'
> I think I've said I would pay cash money(*) to make it go away.
> tim
> (*) - to be paid out of my wg chairs wealth fund of course.
> On Wed, Feb 3, 2021 at 11: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


*Todd Herr* | Sr. Technical Program Manager
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.