Re: [Tools-discuss] Clarifying the state of and the transition plan for tools.ietf.org

"Andrew G. Malis" <agmalis@gmail.com> Thu, 11 March 2021 14:21 UTC

Return-Path: <agmalis@gmail.com>
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 B95573A0E26 for <tools-discuss@ietfa.amsl.com>; Thu, 11 Mar 2021 06:21:21 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 (2048-bit key) header.d=gmail.com
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 7Efp-p2KStbR for <tools-discuss@ietfa.amsl.com>; Thu, 11 Mar 2021 06:21:19 -0800 (PST)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9D8B3A0E25 for <tools-discuss@ietf.org>; Thu, 11 Mar 2021 06:21:19 -0800 (PST)
Received: by mail-qt1-x82a.google.com with SMTP id j7so1213334qtx.5 for <tools-discuss@ietf.org>; Thu, 11 Mar 2021 06:21:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=soClGJJH2rASYmyeVu6KXv/xIZIwcximD1vlhlnvU3M=; b=Tqjuql56F1MA83cboZDfpZt8FP/cyo58Npryz8JPLYWESlDg6131aWZVRqd5Mr4GYM TyPKfetv1Tf7RRUjRMWXnmjMLr09qDLBgjdT/AzRsBNfQ0byenGzJdXxjygKTUiCPDtB 4D7cwstT9GDVG3kvR9O08TlExxJOkJUjZJqkPBDMZpZ2BBB+rLCYprTF5NyLflLDM3UZ vyeZPeQo8xlL0BOI/yL84jvjV5/1OnJpSXOHtwZpoMNqEemVXMm3HatWGRUE9sgRqOjL HCaIVs1kxerNXV4njYlDKy6ADD5a6vdQ04ZQzI4Q1PzIsk6bF7+JQWYJkxHQ4q+rpAFR fmPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=soClGJJH2rASYmyeVu6KXv/xIZIwcximD1vlhlnvU3M=; b=svUOeeWXd/p3hn3+lidNz6meGs0ofYasEZdAWuo2v3/lnW3523auXR7cLysdo7huLR CpcCnNzesoVeR2isNdo22gq1s6fJt6+pCF9sme3nkyUzz0qXKpXp99QwmeMK8u9iTMzA 7uZ7reWPD+eVKHaehG8JXEi/G2Hwr0qPksF92TY+Bk/9YedhVSpvf0Jlw3cgZVAU5YwV mbZhIruIk4IkjJ1UnvMkMvapvGBLd/YIEjhYzwJKbDNx7x+lMeWThdTRTGUJhr4juF7V FDXwuu3o8fHjrWFRImfTT9eGINWraMOyl62/fU6Y243HljOOEUkgKATfTGD46JxvUcZj OIdw==
X-Gm-Message-State: AOAM533sbUVISzdv4guogNdlJ8MmNA/70QunySJFpu8SrwIkmMMovOTe m+55nVzhMALu2l1kX0z+xOxWlGZ1h5yaxXAhk/EGmpWFWrA=
X-Google-Smtp-Source: ABdhPJzHRUXNi7mc+/og/7hrMzLlUsGseKkZP8z9FSjDnOBKK+xk4VK7TRj5q37yI0Clzpd5BAkIrql3GE9l+e5b0W0=
X-Received: by 2002:aed:3ae1:: with SMTP id o88mr7354197qte.154.1615472478832; Thu, 11 Mar 2021 06:21:18 -0800 (PST)
MIME-Version: 1.0
References: <e446a64e-0cfa-d97f-a604-50776242c8f0@nostrum.com> <CAA=duU2JBW3yEAUcAQ-2LuyDDyKG5X_---bpLf7pNwuz+EqnWQ@mail.gmail.com> <cfc826b4-896f-41cf-8061-4ceb81d47e42@nostrum.com>
In-Reply-To: <cfc826b4-896f-41cf-8061-4ceb81d47e42@nostrum.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 11 Mar 2021 09:21:02 -0500
Message-ID: <CAA=duU2tKP-6UswZXP3G58DsK2y_5jq6o7F07F0vXFckG8hVmQ@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Cc: tools-discuss <tools-discuss@ietf.org>, Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="0000000000003ecb7d05bd437fa2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Pg95jQ3kLbfJRG_vZl_z_GmcHYY>
Subject: Re: [Tools-discuss] Clarifying the state of and the transition plan for tools.ietf.org
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: Thu, 11 Mar 2021 14:21:22 -0000

Robert,

Thanks. much appreciated!

Cheers,
Andy


On Thu, Mar 11, 2021 at 9:10 AM Robert Sparks <rjsparks@nostrum.com> wrote:

>
> On 3/11/21 8:08 AM, Andrew G. Malis wrote:
>
> Robert,
>
> Are you also porting the tools at
> https://xml2rfc.tools.ietf.org/experimental.html , especially the online
> version of KramDown?
>
> Yes, the planned replacement online xml2rfc service will have all of those
> conversions available.
>
>
> Thanks,
> Andy
>
>
> On Tue, Mar 9, 2021 at 1:16 PM Robert Sparks <rjsparks@nostrum.com> wrote:
>
>> The services at tools.ietf.org are undergoing a transition.
>>
>> As most of you know Henrik Levkowetz has retired. He is continuing to
>> support
>> the services that he has provided for decades at tools.ietf.org on a best
>> effort basis as we transition the essential features to LLC supported
>> platforms. The plan is to finish the transition before IETF 111 and wind
>> tools.ietf.org down.
>>
>> The process of moving these features has been ongoing for several years.
>> Most have already been moved, but a few important ones remain.
>>
>> We have recently moved the tools.ietf.org style of presenting htmlized
>> text
>> documents into the Datatracker. The plan is to redirect those pages from
>> tools.ietf.org into the Datatracker soon.
>>
>> We will be replacing the online xml2rfc and bibxml services with modern
>> rewrites of the existing services.
>>
>> We are transitioning the svn/trac source repositories for the Datatracker
>> and xml2rfc to the IETF Secretariat, with a longer term goal of moving
>> them
>> to GitHub.
>>
>> At the beginning of this meeting, we identified that the ability to add to
>> individual sessions (as opposed to all sessions of a group) to a
>> subscribable
>> calendar needs to be added to the Datatracker.
>>
>> We will look again to identify any other features that need to be moved.
>> But as
>> you notice features at tools.ietf.org that are important but can't find
>> at the
>> Datatracker, please send a note either to me or to tools-discuss@ietf.org
>> .
>>
>> Henrik and I communicate frequently, and he is supporting us with this
>> transition on a best effort basis, but tools.ietf.org is not getting as
>> much of
>> his time as we have become accustomed to in the past. Please be patient
>> with us
>> during the next few months.
>>
>> As you identify issues with tools.ietf.org, please email Henrik or let
>> me know,
>> and I will bring them to Henrik's attention.  In general, neither the IETF
>> Secretariat nor the tools team can address issues at tools.ietf.org
>> directly.
>> Our focus will be on moving functionality to platforms like the
>> Datatracker.
>>
>> I would like to express my gratitude for all of the support Henrik has
>> provided
>> to the community over the last couple of decades. Early on, long before we
>> started projects like the Datatracker, he set up several tools on his
>> own that
>> became very popular with the community. During this time, the domain
>> tools.ietf.org
>> was delegated to him, and he used it to gather the volunteer created
>> tooling from
>> many contributors.
>>
>> As the community grew, we began hosting more services at the IETF
>> Secretariat.
>> During Russ Housley's tenure as IETF Chair, the tools team, under the
>> IOAC's
>> direction, began moving essential services to IETF Secretariat-supported
>> platforms. Through donated and contracted time, Henrik has been helping
>> make
>> these transitions as an ongoing process. But tools.ietf.org continued to
>> be a
>> set of services that he maintained and improved primarily by himself or
>> through
>> coordinating other volunteer effort.
>>
>> Of course, Henrik was also a principal architect and contributor for the
>> Datatracker and xml2rfc, and we are richer for all of his hard work over
>> decades on so many tools.
>>
>> --
>>
>> Robert Sparks
>>
>> Tools Team chair
>>
>>