[proto-team] Fwd: COMMENT: draft-ietf-proto-wgchair-doc-shepherding

Lars Eggert <lars.eggert@netlab.nec.de> Tue, 14 November 2006 12:47 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gjxgq-0007Tu-A1; Tue, 14 Nov 2006 07:47:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gjxgp-0007Ti-5T for proto-team@ietf.org; Tue, 14 Nov 2006 07:46:59 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gjxgj-0005kz-I9 for proto-team@ietf.org; Tue, 14 Nov 2006 07:46:59 -0500
Received: from lars.local (p54AD27C0.dip0.t-ipconnect.de [84.173.39.192]) by kyoto.netlab.nec.de (Postfix) with ESMTP id DC29F13CF82 for <proto-team@ietf.org>; Tue, 14 Nov 2006 13:49:41 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by lars.local (Postfix) with ESMTP id 805B1286A5B for <proto-team@ietf.org>; Tue, 14 Nov 2006 13:46:51 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v752.2)
To: proto-team@ietf.org
Message-Id: <F5BCDD4D-7E27-464C-A2B9-E01BCE0CE1BE@netlab.nec.de>
References: <E1GjlgO-00018y-Bp@ietf.org>
From: Lars Eggert <lars.eggert@netlab.nec.de>
Date: Tue, 14 Nov 2006 13:46:49 +0100
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Subject: [proto-team] Fwd: COMMENT: draft-ietf-proto-wgchair-doc-shepherding
X-BeenThere: proto-team@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process and Tools Team <proto-team.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>, <mailto:proto-team-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:proto-team@ietf.org>
List-Help: <mailto:proto-team-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>, <mailto:proto-team-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1054479056=="
Errors-To: proto-team-bounces@ietf.org


Begin forwarded message:

> From: Ted Hardie <hardie@qualcomm.com>
> Date: November 14, 2006 12:57:44 AM GMT+01:00
> To: iesg@ietf.org
> Cc: margaret@thingmagic.com, henrik@levkowetz.com, mankin@psg.com
> Subject: COMMENT: draft-ietf-proto-wgchair-doc-shepherding
>
> Comment:
> Nit:
>
> This parenthetical expression is not closed:
>
> (because it was created by the "PROcess
>    and TOols" or PROTO [PROTO] team,
>
> The document consistently says that the document
> shepherd should be a single person (see section 3.
> especially).  I have personally run PROTO with both
> working group chairs taking joint responsibility.  I
> think it works.  Softening the language on that to
> allow WG chairs to work in double harness would
> be valuable, in my opinion.
>
> Section 3.1 adds this section to the common write-up:
>
> Personnel
>              Who is the Document Shepherd for this document?  Who  
> is the
>              Responsible Area Director?
>
> above that, the document says:
>
>  A final sentence of the Document Announcement Write-Up, simply placed
>    as a line at the end of the "Document Quality" section, can  
> state the
>    names of the Document Shepherd and the Responsible Area Director,
>    because the announcement will not otherwise acknowledge them.  The
>    Document Shepherd SHOULD add this information and the Responsible
>    Area Director SHOULD add it if it is not already there.
>
> That seems to indicate that the same information goes in the  
> Document quality
> section, rather than in its own heading.  Resolving that seems to  
> me useful.
>
> On IANA actions, the document says:
>
>    In summary, the task of shepherding the IANA actions is overlooked
>    but is as important to coordinate and manage as all the other
>    document reviews the Document Shepherd has managed.  As with those,
>    the Document Shepherd contributes greatly to quality and timeliness
>    of the document by effective and responsive shepherding of the IANA
>    requests.
>
> Does this mean to say "is often overlooked"?
>
> In Section 6, the document says:
>
> 1.  Cases, where the Document Shepherd is the primary author or
>        editor of a large percentage of the documents produced by the
>        working group.
> 2.  Cases, where the Responsible Area Director expects communication
>        difficulties with the Document Shepherd (either due to
>        experience, strong views stated by the Document Shepherd, or
>        other issues).
>
>    3.  Cases, where the working group itself is either very old,  
> losing
>        energy, or winding down, i.e., cases, where it would not be
>        productive to initiate new processes or procedures.
>
> The syntax of these is hard to parse. I think the last of them applies
> only to working groups that pre-date PROTO (it would not introduce
> a new procedure to tired WGs that post-date PROTO).  As something
> that is either already dated or soon will be, should it be struck?
>
> Frankly, I would recommend cutting that whole section, and replacing
> it with "When the responsible area director or proposed PROTO shepherd
> feel that the process is not appropriate, the responsible area  
> director
> may server as document shepherd, as she or he does for non-WG
> documents."
>
>

Lars
-- 
Lars Eggert                                     NEC Network Laboratories


_______________________________________________
proto-team mailing list
proto-team@ietf.org
https://www1.ietf.org/mailman/listinfo/proto-team