Re: Reducing time to publication: was Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way toRFCwith Running Code) to Experimental RFC

t.p. <daedulus@btconnect.com> Fri, 01 February 2013 09:28 UTC

Return-Path: <daedulus@btconnect.com>
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 80F2A21F879B for <ietf@ietfa.amsl.com>; Fri, 1 Feb 2013 01:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O8cAOe+8daYY for <ietf@ietfa.amsl.com>; Fri, 1 Feb 2013 01:28:58 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe001.messaging.microsoft.com [216.32.181.181]) by ietfa.amsl.com (Postfix) with ESMTP id D341721F8464 for <ietf@ietf.org>; Fri, 1 Feb 2013 01:28:57 -0800 (PST)
Received: from mail132-ch1-R.bigfish.com (10.43.68.230) by CH1EHSOBE008.bigfish.com (10.43.70.58) with Microsoft SMTP Server id 14.1.225.23; Fri, 1 Feb 2013 09:28:56 +0000
Received: from mail132-ch1 (localhost [127.0.0.1]) by mail132-ch1-R.bigfish.com (Postfix) with ESMTP id A52AA3001DF; Fri, 1 Feb 2013 09:28:56 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zz98dI9371I936eI542I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz8275ch1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h304l1155h)
Received: from mail132-ch1 (localhost.localdomain [127.0.0.1]) by mail132-ch1 (MessageSwitch) id 135971093541951_31753; Fri, 1 Feb 2013 09:28:55 +0000 (UTC)
Received: from CH1EHSMHS005.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.248]) by mail132-ch1.bigfish.com (Postfix) with ESMTP id F291622028E; Fri, 1 Feb 2013 09:28:54 +0000 (UTC)
Received: from AMSPRD0710HT003.eurprd07.prod.outlook.com (157.56.249.85) by CH1EHSMHS005.bigfish.com (10.43.70.5) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 1 Feb 2013 09:28:53 +0000
Received: from DBXPRD0210HT005.eurprd02.prod.outlook.com (157.56.253.181) by pod51017.outlook.com (10.255.160.166) with Microsoft SMTP Server (TLS) id 14.16.263.1; Fri, 1 Feb 2013 09:28:49 +0000
Message-ID: <002101ce005e$23f04dc0$4001a8c0@gateway.2wire.net>
From: "t.p." <daedulus@btconnect.com>
To: SM <sm@resistor.net>
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp> <51030B76.2070401@cs.tcd.ie> <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net> <004901cdffac$1e04c7e0$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20130131073013.0aa87df0@resistor.net>
Subject: Re: Reducing time to publication: was Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way toRFCwith Running Code) to Experimental RFC
Date: Fri, 01 Feb 2013 09:24:01 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.181]
X-OriginatorOrg: btconnect.com
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: Fri, 01 Feb 2013 09:28:58 -0000

----- Original Message -----
From: "SM" <sm@resistor.net>
To: "t.p." <daedulus@btconnect.com>
Cc: <ietf@ietf.org>
Sent: Thursday, January 31, 2013 4:51 PM


> Hi Tom,
> At 04:04 31-01-2013, t.p. wrote:
> >Time to publication of an RFC can be reduced by cutting out the
pauses,
> >which could achieved by highlighting when they occur.
>
> [snip]
>
> >Such a list would shine a light on what is moving and what is not.
This
> >in turn would encourage, motivate, spur those on whom the draft is
> >waiting to progress it (and anyone else who could contribute).
>
> There was an interesting quote from #overlyhonestmethods.  I cannot
> locate it right now as the web site is whaling out.
>
> There is a Daily Dose web page (see http://tools.ietf.org/dailydose/
> ).  The web page provides a snapshot of what's being "published" in
> the IETF.  However, it does not provide a view of what is moving and
> what is not moving.  I don't have a view of what an area or what a
> working group is up to.
>
> Sometimes it come as a surprise when working group participants hear
> that their working group is being shut down.  It is possible to tell
> whether a working group might be shut down.  It is possible to
> identify some of the issues which can delay publication.  The data
> for what you suggested is available from the datatracker.  The data
> to identify WG activity is also available.  I don't know how to
> assess progress though.

Yes, this is all available on the datatracker (which is the home page on
my web browser) but it takes me several minutes to go there and absorb
the content, repeated for every Working Group in which I am involved.
The datatracker has too much information, I have to scroll up and down,
since each entry takes 5 or 10 lines.  My idea is a one line summary for
each I-D, in a defined sort order (I-D name).  And I know how much more
productive I am when I get gentle prompts about what is going on, be
they via SMS, e-mail or whatever.  Sensible organisations, from
libraries to garages, are making the most of this technology - we should
do the same.

Tom Petch

> Regards,
> -sm
>
>