Re: Making the Tao a web page

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 31 May 2012 23:50 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 3D27911E8098 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 16:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.185
X-Spam-Level:
X-Spam-Status: No, score=-102.185 tagged_above=-999 required=5 tests=[AWL=0.414, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOc9C6fU+5oG for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 16:50:13 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC9611E8080 for <ietf@ietf.org>; Thu, 31 May 2012 16:50:13 -0700 (PDT)
Received: from [10.20.30.102] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q4VNoAD8059217 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 31 May 2012 16:50:12 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Making the Tao a web page
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="iso-8859-1"
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4FC7FF09.4020701@inex.ie>
Date: Thu, 31 May 2012 16:50:10 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie>
To: Nick Hilliard <nick@inex.ie>
X-Mailer: Apple Mail (2.1278)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 31 May 2012 23:50:14 -0000

On May 31, 2012, at 4:30 PM, Nick Hilliard wrote:

> On 01/06/2012 00:04, Paul Hoffman wrote:
>> Works for me, other than it should not be a "wiki". It should have one
>> editor who takes proposed changes from the community the same way we do
>> it now. Not all suggestions from this community, even from individuals
>> in the leadership, are ones that should appear in such a document.
> 
> In practice, if this is to be a living document then it should be open for
> inspection and poking rather than preserved in formaldehyde and put in a
> display case, only to be opened occasionally when the curator decides the
> glass needs some dusting.  That way leads to sclerosis.

Thank you for that most colorful analogy. :-) What I proposed is exactly what we are doing now, except that the changes would appear on the web page instead of an Internet-Draft and, five years later, an RFC. Are you saying that the current system (which you have not commented on until now) is sclerotic (a word that I have wanted to use since I learned it in high school)?

> Please put it on a wiki and put all changes through a lightweight review
> system.  If someone makes a change which doesn't work, then it can be
> reverted quickly and easily.  This approach is much more in line with the
> ietf approach of informality / asking for forgiveness rather than
> permission / rough consensus + running code / etc.


In the IETF approach, only the authors of an Internet-Draft can change the contents of that draft. I hope you are not proposing a change to that as well.

--Paul Hoffman