Re: [Tools-discuss] Deletion of unused and broken trac instances

Jim Fenton <fenton@bluepopcorn.net> Sun, 14 March 2021 22:50 UTC

Return-Path: <fenton@bluepopcorn.net>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F403A174C; Sun, 14 Mar 2021 15:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=bluepopcorn.net
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 A203AuMHfoYR; Sun, 14 Mar 2021 15:50:55 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 9C8243A174B; Sun, 14 Mar 2021 15:50:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=VpbTuZ7T1UAt+QtnjbXCDbbeJe9GBE8K+pNuMNBdxwk=; b=Y/lf2StZNuj4rhAGG0MsEu1wIf B16vhe0OZiLCTdNIHvxKsVA1X89idxjH3su0JTTZd2HvcWN6VbKKaQ8bfpSLcc5AoqGfP66cH811P SZtRyplmh4lAnPSsiy9ssTaViZpfLsC5A+Di8h+7OBbaI1GHrfVt8o2c+1jozAFHkNYY=;
Received: from [2601:647:4400:1261:e162:6c95:d14:8f0b] (helo=[10.10.20.144]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1lLZZW-0004N9-6f; Sun, 14 Mar 2021 15:50:54 -0700
From: "Jim Fenton" <fenton@bluepopcorn.net>
To: "Jay Daley" <jay@ietf.org>
Cc: "Tools Discussion" <tools-discuss@ietf.org>
Date: Sun, 14 Mar 2021 15:50:53 -0700
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <B601BBF6-FF47-4667-8D90-A8895C421DD8@bluepopcorn.net>
In-Reply-To: <92319CB2-D3E0-433F-81A1-4AFE2220B854@ietf.org>
References: <92319CB2-D3E0-433F-81A1-4AFE2220B854@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/daQef7LkvDkbzcJuspsZgH7_rAs>
Subject: Re: [Tools-discuss] Deletion of unused and broken trac instances
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Mar 2021 22:50:57 -0000

Jay,

On 14 Mar 2021, at 14:34, Jay Daley wrote:

> To support Robert as The Tools Team PM, I am working on an RFP to move 
> all the wiki pages in existing trac instances to a new wiki product 
> and all the issues to GitHb repositories.  In preparation for this 
> work, I propose to have all broken and unused Trac instances deleted 
> so that we do not waste resources having those migrated.

Does “all the issues” include the Datatracker issues? The current 
issue tracking system is hooked to subversion, where the datatracker 
code is managed, and I suspect we would lose that if the issues were 
migrated to GitHub. Unless there is also a plan to move the code to 
GitHub as well, of course.

-Jim