Re: IETF Tools Architecture and Strategy Team

Michael Richardson <mcr@sandelman.ca> Wed, 05 February 2020 18:14 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A051120805 for <ietf@ietfa.amsl.com>; Wed, 5 Feb 2020 10:14:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 7uv77geRgMhE for <ietf@ietfa.amsl.com>; Wed, 5 Feb 2020 10:14:47 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27728120809 for <ietf@ietf.org>; Wed, 5 Feb 2020 10:14:46 -0800 (PST)
Received: from dooku.sandelman.ca (ip5f5bd76d.dynamic.kabel-deutschland.de [95.91.215.109]) by relay.sandelman.ca (Postfix) with ESMTPS id 7D7C01F45A for <ietf@ietf.org>; Wed, 5 Feb 2020 18:14:45 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 76CCC118A; Wed, 5 Feb 2020 13:14:42 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: IETF Tools Architecture and Strategy Team
In-reply-to: <FE0B5C44-B979-4781-883C-CF35A297BA85@ietf.org>
References: <FE0B5C44-B979-4781-883C-CF35A297BA85@ietf.org>
Comments: In-reply-to IETF Chair <chair@ietf.org> message dated "Wed, 05 Feb 2020 09:55:29 -0500."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 25.1.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 05 Feb 2020 19:14:42 +0100
Message-ID: <16926.1580926482@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yM2FsnDHVAM0IGU-AorkpnjL7aA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2020 18:14:49 -0000

IETF Chair <chair@ietf.org> wrote:
    > I'd like to introduce a new volunteer team that has been created in the
    > General area: the Tools Architecture and Strategy (TAS) team.

I think it is a really good idea to organize this.
I wonder if you considered just creating a WG in the general area?
What would seem to let the tools team leverage... the tools.
But, I guess you can create groups that aren't WGs based upon the links below.

    > It is not the role of the TAS team to implement, maintain, or manage
    > the operation of individual tools. Those responsibilities remain with
    > the IETF tools team. Once TAS team guidance documents become available,
    > the IETF Tools Project Manager (currently Robert Sparks) will establish
    > plans and workflows to align ongoing and future tools development with
    > the guidance.

I believe that the team will mostly produce plans, and those plans will not
be in the form of RFCs, and probably not even in the form of IDs.

    > The TAS team is expected to consult widely with the IETF community, to
    > draw on best practices from the software development industry and open
    > source communities, and to evolve its guidance over time as practices
    > change. The team's online presence resides at:

    > Datatracker page: https://datatracker.ietf.org/group/tools-arch/about/
    > Mailing list (only open to members, with a public archive): tools-arch@ietf.org
    > Github organization: https://github.com/ietf-team-tools-arch

May I suggest that one of these people be designated as the liason to the
WG-chairs list?  And another as the liason to the EDU-team?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [