Re: [Errata-design] sanity notwithstanding...

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 23 December 2014 18:04 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: errata-design@rfc-editor.org
Delivered-To: errata-design@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 299DD181243; Tue, 23 Dec 2014 10:04:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QlzbpXcLVdBy; Tue, 23 Dec 2014 10:04:10 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by rfc-editor.org (Postfix) with ESMTP id 80CA818047D; Tue, 23 Dec 2014 10:04:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 88621BED5; Tue, 23 Dec 2014 18:04:45 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cG6x-wYjiZB3; Tue, 23 Dec 2014 18:04:44 +0000 (GMT)
Received: from [10.87.48.11] (unknown [86.46.22.20]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2E04FBECF; Tue, 23 Dec 2014 18:04:44 +0000 (GMT)
Message-ID: <5499AEBB.2050107@cs.tcd.ie>
Date: Tue, 23 Dec 2014 18:04:43 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>, "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
References: <5494555A.7010608@rfc-editor.org> <54949BFD.1040007@cs.tcd.ie> <54999DE8.7030104@rfc-editor.org> <CALaySJK09uEnaLQZT7XcaHVdZKB8-s8EeVMvfAE9StqQpoXKLw@mail.gmail.com>
In-Reply-To: <CALaySJK09uEnaLQZT7XcaHVdZKB8-s8EeVMvfAE9StqQpoXKLw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc: errata-design@rfc-editor.org
Subject: Re: [Errata-design] sanity notwithstanding...
X-BeenThere: errata-design@rfc-editor.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <errata-design.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/errata-design>, <mailto:errata-design-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/errata-design/>
List-Post: <mailto:errata-design@rfc-editor.org>
List-Help: <mailto:errata-design-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/errata-design>, <mailto:errata-design-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Dec 2014 18:04:12 -0000


On 23/12/14 17:39, Barry Leiba wrote:
>>> I'd suggest getting rid of the entire concept of errata and just
>>> allowing anyone to comment on RFCs but with a way for the RFC editor
>>> or stream controllers to mark some comments as important. (Someone
>>> would need to handle comment spam of course.) Such systems exist, we
>>> should just use them.
>>
>> I have a knee-jerk reaction against this one; errata are really important

We'll be fine to work around it, but no, I very much disagree.

Most RFCs are not important. And even fewer errata are important,
in fact most are utterly pointless. But feel free to show me the stats
as to how many errata are needed/read/anything.

Note, I count important as being something needed by implementers,
and I get that your view may properly put much more emphasis on the
integrity of the RFC series as a whole. But while some form of
comment/correction/errata *system* is important, almost none of
the actual errata are at all important - they are today a fairly
meaningless waste of time and effort and collectively they are a
real annoyance and a waste of significant time and effort for ADs.

>> and are a common thing to look for in technical publications.  Doing away
>> with them such that people have to hunt through a list of comments seems
>> less than idea.  However, you probably have a more detailed set of reasons
>> in your head on why this would be a good thing.  I suggest holding off
>> discussing this until January, when I should have the members of the design
>> team all on board.  Then you can make your case to all of the above, and
>> we'll see if I'm in the rough here.
> 
> While leaving most of the discussion for January, I'll just say that
> what Stephen wants and what Heather wants don't have to be mutually
> exclusive.  

Right. Happiness is entirely possible:-)

> Stephen's point isn't that there should be no errata
> posted, but that the system for having arbitrary people post errata
> should go away.  

No. The part I want to go away is that each posted erratum consumes
effort for folks other than the poster. (Incl. me:-) I do want anyone
(without needing authorization) to be able to post a comment.

> It's certainly workable that comments that stream
> controllers (or their delegates) mark as important could then be shown
> through an "errata" link.  My guess is that that'd make both Stephen
> and Heather happy (with the nice effect of making me happy as well).

That'd be fine. I'd prefer a vote-up/down system myself for anyone with
a datatracker account maybe (for IETF stream) but there are ways in
which this can be crowdsourced and produce a better outcome and still
use off the shelf open-source I bet.

S.


> 
> Barry
>