Re: Adjustments to our work mode - please read

Mark Nottingham <> Wed, 07 October 2015 00:35 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 8F6BE1B2F9C for <>; Tue, 6 Oct 2015 17:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0b4mJv0Lclqb for <>; Tue, 6 Oct 2015 17:35:52 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 54A901B2F8C for <>; Tue, 6 Oct 2015 17:35:52 -0700 (PDT)
Received: from lists by with local (Exim 4.80) (envelope-from <>) id 1ZjcfX-0001hh-6h for; Wed, 07 Oct 2015 00:33:19 +0000
Resent-Date: Wed, 07 Oct 2015 00:33:19 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1ZjcfU-0001gt-BD for; Wed, 07 Oct 2015 00:33:16 +0000
Received: from ([]) by with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <>) id 1ZjcfS-0002pv-2a for; Wed, 07 Oct 2015 00:33:15 +0000
Received: from [] (unknown []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 32E8E22E262; Tue, 6 Oct 2015 20:32:49 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Mark Nottingham <>
In-Reply-To: <>
Date: Wed, 07 Oct 2015 11:32:46 +1100
Cc: HTTP Working Group <>, Barry Leiba <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <>
To: "Eliot Lear (elear)" <>
X-Mailer: Apple Mail (2.2104)
Received-SPF: pass client-ip=;;
X-W3C-Hub-Spam-Status: No, score=-8.3
X-W3C-Hub-Spam-Report: AWL=1.323, BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: 1ZjcfS-0002pv-2a dcea8f8f13de487fb7c11da991059735
Subject: Re: Adjustments to our work mode - please read
Archived-At: <>
X-Mailing-List: <> archive/latest/30337
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

> On 7 Oct 2015, at 11:07 am, Eliot Lear (elear) <> wrote:
> Where at that link do you discuss the interaction with the mailing list or anything else in that message?  Please quote because I can't find it, as I wrote. 

The points from my original e-mail were these:

> - Summarise (with links) the design issues closed by each draft when it is announced on this list

From [1]: "When a new draft is published, the design issues that have been closed since the last draft will be highlighted on the mailing list, to aid reviewers."

> - Allow issues to be re-opened when someone brings substantive new information (as always)

From [1]: "If substantive new information is brought to our attention, issues can be reopened by the Chair."

> - Allow those who do not wish to use the issues list to comment on this mailing list

From [1]: "Design issues require discussion and consensus in the Working Group. This discussion can happen both in the issue and on the Working Group mailing list."

> - Provide a separate, announce-only mailing list that is subscribed to every issue change, for those who do not want to use a github account to receive notifications. See: <>

This is not in [1]. Do you think it should be there? I was planning on adding it elsewhere on the site.

So what exactly can't you find -- are you looking for something else that isn't above, or did you just fail to find the link even though I gave the title, or...? Please be as precise as you can, as I'm getting frustrated pointing out the same information to you repeatedly, and I don't *think* you're enjoying this either.

I have no doubt that [1] can be improved -- indeed, after some offline discussion with Ted, there are a number of ways I think we can make it a more friendly and complete document -- especially around how decisions are made (which is more about reminding people how consensus works in the IETF and relating that to the work mode). However, most WGs don't have any such document, so I'm finding it a bit ironic to hear you rail about "transparency."



> Eliot
>> On Oct 6, 2015, at 8:02 PM, Mark Nottingham <> wrote:
>>> On 6 Oct 2015, at 11:05 pm, Eliot Lear (elear) <> wrote:
>>> Honestly if you put up that process on your GitHub home page I'd be satisfied (if it's there I can't find it).  Better to make clear through IETF mechanisms that people from other WGs are used to. 
>> I explained that in the e-mail that you're responding to:
>> """
>> It is documented, on our WG home page - <>, currently linked as "How to Contribute - start here" (as well as from the navigation bar from every page on that site). We regularly show the home page link at our meetings, it's easily found by any search engine, and it's linked from our charter.
>> """
>> If you have suggestions on how to improve the link's visibility, they're welcome.
>> --
>> Mark Nottingham

Mark Nottingham