Re: Last Call: <draft-secretaries-good-practices-06.txt> (IETF Working Groups' Secretaries) to Best Current Practice

Robert Sparks <rjsparks@nostrum.com> Wed, 03 December 2014 14:27 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3853C1A1B05 for <ietf@ietfa.amsl.com>; Wed, 3 Dec 2014 06:27:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQqYXL0WWtud for <ietf@ietfa.amsl.com>; Wed, 3 Dec 2014 06:26:59 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E45C1A1A66 for <ietf@ietf.org>; Wed, 3 Dec 2014 06:26:59 -0800 (PST)
Received: from unnumerable.local ([173.64.248.98]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id sB3EQt3V062940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Dec 2014 08:26:55 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [173.64.248.98] claimed to be unnumerable.local
Message-ID: <547F1DAA.3000703@nostrum.com>
Date: Wed, 03 Dec 2014 08:26:50 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, 'Loa Andersson' <loa@pi.nu>, "'Murray S. Kucherawy'" <superuser@gmail.com>
Subject: Re: Last Call: <draft-secretaries-good-practices-06.txt> (IETF Working Groups' Secretaries) to Best Current Practice
References: <20140612132656.8100.57197.idtracker@ietfa.amsl.com> <CAL0qLwZEo-AN4Er0gmbCyWJwTqOKBUKKMHEMQ_YqhK+oB+pcgg@mail.gmail.com> <547E9DBA.9040703@pi.nu> <0c1001d00ee9$36598670$a30c9350$@olddog.co.uk>
In-Reply-To: <0c1001d00ee9$36598670$a30c9350$@olddog.co.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_UIZWB9j2vZ8xf5byTKsdwqG0Uk
Cc: 'ietf' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 03 Dec 2014 14:27:01 -0000

On 12/3/14 5:06 AM, Adrian Farrel wrote:
>>> The document makes reference to several tools or components of tools
>>> (the datatracker in particular) that I've never seen.  That's not to say
>>> they don't exist, but I haven't seen them and couldn't find them just
>>> now, so it makes me wonder if the tools team would have to do a bunch of
>>> work to get reality to match what's written here.  For example, I just
>>> went into the datatracker and as a working group co-chair I have
>>> privileges in that system with respect to my working groups.  However, I
>>> didn't see anywhere in there that I can declare a WG Secretary or
>>> delegate some or all of my powers to that person, despite the fact that
>>> Section 4 says such things "shall" be done.  Is this something that a
>>> co-chair would have to request of the Secretariat directly or via a
>>> sponsoring Area Director?  If not, does the tools team intend to add that?
>> Well - the tool team has to answer about their plans, but does hardly
>> effect progressing this document.
Exactly.
>>
>> Things like "delegation" are captured in the datatracker, and that is
>> what the document says: a lot of things are, some of them can only be
>> done by intervention of an AD or the Secreatariat or a combination
>> thereof. This document is not the place to describe the dynamics.
> As AD I can see the place to make these changes in the data tracker. It's possible that the permissions are not set to allow chairs to make these changes.
The ability for a chair to assign delegates has existed for a long time, 
but is currently broken (at least the navigation to it is broken).
We're tracking fixing it at 
<http://wiki.tools.ietf.org/tools/ietfdb/ticket/1546>.
Expect the ability to return to normal soon.

Pulling up to the spirit of the comment. I'm the assigned Gen-art 
reviewer for this document.
I don't remember seeing anything sticking out at me as requiring new 
tooling work beyond
our normal incremental style of improvement when I reviewed -06 last summer
  (see 
<https://mailarchive.ietf.org/arch/msg/gen-art/qUXolKK3UgJVX5xZMubFX36GgeU>).
That is, we can always make it _easier_ to do lots of these things.
And on a quick skim of -07, (I'll send a telechat review later),  I 
still don't see anything.

RjS
>
> datatracker
> sign in
> https://datatracker.ietf.org/wg/foowg/charter/
> "Edit group"  <<< possibly this you don't have access to as a chair?
> fill in the fields
>
> Adrian
>