IETF Logo Mail Archive

Re: [tao-discuss] Review Request for Possible Revision of the Tao of the IETF

Mirja Kuehlewind <ietf@kuehlewind.net> Thu, 14 April 2022 15:03 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: tao-discuss@ietfa.amsl.com
Delivered-To: tao-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE77E3A1BBE; Thu, 14 Apr 2022 08:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 hiOoOP3Ris_w; Thu, 14 Apr 2022 08:03:50 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 52E663A1BD7; Thu, 14 Apr 2022 08:03:49 -0700 (PDT)
Received: from dslb-002-205-104-077.002.205.pools.vodafone-ip.de ([2.205.104.77] helo=emb-w4epjhc9.fritz.box); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1nf10a-00019l-59; Thu, 14 Apr 2022 17:03:44 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <78BF279C-DEED-42BD-897D-1BC3DC972DE2@akamai.com>
Date: Thu, 14 Apr 2022 17:03:42 +0200
Cc: Jay Daley <exec-director@ietf.org>, "tao-discuss@ietf.org" <tao-discuss@ietf.org>, IESG <iesg@ietf.org>, Lars Eggert <lars@eggert.org>, Greg Wood <ghwood@staff.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Niels ten Oever <mail@nielstenoever.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD1AA00F-A0B6-4FB1-8BC8-7AC0732E7038@kuehlewind.net>
References: <905c834c-30d7-ede7-6ea1-a5b200a249d7@nielstenoever.net> <45a73c1d-0564-10a6-4243-bf1a209da307@gmail.com> <0C41A5AD-CEFB-4A37-9229-64C03723193F@akamai.com> <c9679cee-afa4-f7d4-80a1-83e635d8ad26@gmail.com> <FE38E0F3-C368-42B6-9FD8-2804C38EC7E1@eggert.org> <62445876-1CCA-4D1A-9E30-00E7EDDEE130@ietf.org> <78BF279C-DEED-42BD-897D-1BC3DC972DE2@akamai.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1649948629;3a175fbe;
X-HE-SMSGID: 1nf10a-00019l-59
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/wqN9SQMrPoNkcsBDPkMEM1pZilU>
Subject: Re: [tao-discuss] Review Request for Possible Revision of the Tao of the IETF
X-BeenThere: tao-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of the Tao of the IETF <tao-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tao-discuss/>
List-Post: <mailto:tao-discuss@ietf.org>
List-Help: <mailto:tao-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2022 15:03:52 -0000

I would like to note that there is some kind of tradition or cultural identity of this community connected to the Tao. However having said this, Jay, I think your analysis is right: it doesn’t serve the intended audience well and there is not one intended audience. I’m all in to reorganise all content related to participation on the webpage in a more useful way but then let’s do that and just not call it Tao anymore.

> On 14. Apr 2022, at 16:53, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
> 
> Very nice analysis!
> 
>>   While I admire the effort that has gone into the Tao, I think we need to move on from this style of documentation.  Replacing it with several smaller documents/sites/pages would be much more useful: "Guide to the role and structure of the IETF", "Guide to participating in IETF working groups", "Guide to making the most of IETF meetings", and so on.
> 
> Works for me.  I am happy to completely stop working on it.  Although what's on the website is seriously cringe-worthy. How that should be addressed I leave to you. I note that the RFC requiring IESG review is informational, not even BCP. Hint, hint.
> 
>

v2.23.0 | Report a Bug | By Email