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:09 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 615C53A0DBE for <tools-discuss@ietfa.amsl.com>; Thu, 11 Mar 2021 06:09: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, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 (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 UZm2pivUCOPV for <tools-discuss@ietfa.amsl.com>; Thu, 11 Mar 2021 06:08:59 -0800 (PST)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 456303A0DBC for <tools-discuss@ietf.org>; Thu, 11 Mar 2021 06:08:59 -0800 (PST)
Received: by mail-qt1-x830.google.com with SMTP id s2so1175607qtx.10 for <tools-discuss@ietf.org>; Thu, 11 Mar 2021 06:08:59 -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=+7c7Ee9MUvs1J2/ffAN2Ji86XoC98wCUDJzo+6bfBbg=; b=vUsxaPYogd8JEtWYmQTbsCfqDbOuagYb9gx+AHYzsYwoLJgZJIM6kN2S1ALwRqm+f4 rY6ldqkkM4B9XHD9ey7scQA+gZLR8NNr3Uo8rWA1kD9pyyV0OxJK1+Q5JAY1VWr+kVq+ jtexzdgb+sgjEK98jNtMXq4utdIH+g5ppFn1NJ0t4BojLglrRxxP14BRobzOT70g1f/M MTKjnmePJyphbiwABsJc6/z9N8iGv+1spaiwCe7OnF3JKrOLNYue5Exh9O8Bxd89a7q8 yff5ON1ZaFyaMuuxq0Okc+eu+OYVBrkVTKSVJDDX8sPdSMNNXdlByEqQdzOk0zt0X0jM rq7Q==
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=+7c7Ee9MUvs1J2/ffAN2Ji86XoC98wCUDJzo+6bfBbg=; b=Y5IlINGXirEnYTFrQNI4zBv5XEsygrod8ZLQuN6AnaQDdPdIgXdfhAoqly3dZ3FgTe WVUzFg+CnRGjOimjeoLH6N8mAXoqZrLA3/i7gZTW8YBjP5PZMm2McKpeEymZfGRFpKtZ 1rds0cTPkOD+bo0d9Vhof2HxR6N0H2Wu0CHRHmP+HGDGea9ja94PVVo1UpcZHeqlYBqe 50KwcM8DBkQrZRbzGUSmUexwE7tROocFH2Y+mHpwzTtfTso/2Q9fjKySYSg2uM0Iw3CR v6SuqyHidj8ccls5opR0Z7EUVV5dh8wrZiR5vHGcD/Ol5DYcPKUJ5kwm4O2HqZGa4zpt ZUWg==
X-Gm-Message-State: AOAM531+HfHYGpclo1JqN/XG+2Q0Rsts+hy3iswxyuIk/eS5CIcpRiFq xZ/tGP+DYVC9H24Nqqpa/cYKZ3veJouREJmnCsI=
X-Google-Smtp-Source: ABdhPJwSUrTi7wSlpXR+66KPvlt/RENR86fwIL6wcC5+Yl5YiIwc4s+0xAgbDJDgalRNzbuJgu9JBV3qQQpN8d0Vup4=
X-Received: by 2002:ac8:44cc:: with SMTP id b12mr7393467qto.382.1615471738113; Thu, 11 Mar 2021 06:08:58 -0800 (PST)
MIME-Version: 1.0
References: <e446a64e-0cfa-d97f-a604-50776242c8f0@nostrum.com>
In-Reply-To: <e446a64e-0cfa-d97f-a604-50776242c8f0@nostrum.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 11 Mar 2021 09:08:41 -0500
Message-ID: <CAA=duU2JBW3yEAUcAQ-2LuyDDyKG5X_---bpLf7pNwuz+EqnWQ@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="000000000000192aff05bd43530f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/De6Bw7XW2dQr0f75zE9BUuRrHrg>
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:09:01 -0000

Robert,

Are you also porting the tools at
https://xml2rfc.tools.ietf.org/experimental.html , especially the online
version of KramDown?

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
>
>