Re: Making the Tao a web page

Lucy Lynch <> Tue, 05 June 2012 16:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F283521F85A0 for <>; Tue, 5 Jun 2012 09:39:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uNs1sQjiiwEq for <>; Tue, 5 Jun 2012 09:39:47 -0700 (PDT)
Received: from ( [IPv6:2001:418:1::80]) by (Postfix) with ESMTP id 4D57721F8726 for <>; Tue, 5 Jun 2012 09:39:47 -0700 (PDT)
Received: from (localhost []) by (8.14.3/8.14.3) with ESMTP id q55Gdf9C048025 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Jun 2012 09:39:42 -0700 (PDT) (envelope-from
Received: from localhost (llynch@localhost) by (8.14.3/8.14.3/Submit) with ESMTP id q55GdfAV048022; Tue, 5 Jun 2012 09:39:41 -0700 (PDT) (envelope-from
Date: Tue, 05 Jun 2012 09:39:41 -0700
From: Lucy Lynch <>
Subject: Re: Making the Tao a web page
In-Reply-To: <>
Message-ID: <>
References: <> <CE474406564976FC0A885D95@PST.JCK.COM> <> <> <> <> <> <> <>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: IETF <>
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Jun 2012 16:39:48 -0000

On Mon, 4 Jun 2012, Dave Crocker wrote:

> On 6/4/2012 12:36 AM, SM wrote:
>> At 14:33 01-06-2012, Russ Housley wrote:
>>> So, I am left with a few questions:
>>> - What is the similar forcing function if we use a wiki?
>>> - Will the number of people that can make updates eliminate the need
>>> for such a forcing function?
>>> - Who designates the editor-in-chief of the wiki?
> ...
>>   ...  Instead of discussing the above questions it is easier
>> to create an Wiki page and leave it to anyone with a tools login who
>> cares to update it.
> In effect, the wiki construct becomes a form of incrementally-updatable 
> internet draft.  For documents involving procedures rather than products, 
> this well might be a better working base than I-Ds...
> But with the I-D model superimposed.
> That is, perhaps what makes this workable is imposing an editor role onto the 
> wiki and assign responsibility for monitoring changes to the editors?  (It 
> might even be worth integrating it into the rest of the I-D administration 
> environment?)
> Note that this still leaves a place for published snapshots as RFCs.

I like the idea of moving towards a more lively version of the Tao and I 
agree with all those who've voiced concerns about using to open of a 
process for group editing.

I have an alternate suggestion which tries to walk the "middle way". What 
is we create the Tao as a web page with one lead editor (an a possible 
second author as needed) who is responsible for regular review and updates 
and then spin up an etherpad version of the text which can be edited by 
anyone with a tools login? The editor could then track and incorporate 
suggested changes into the canonical web page and notify the list when 
major updates occur. This would use some familiar elements of our current 
document production process and tools we already have in place and would
give the editor a way to contact those with suggested changes if further
dialogue was needed.

One question for the Tools team - can etherpad handle a long lived 

- Lucy

> d/