Re: Adjustments to our work mode - please read

"Eliot Lear (elear)" <> Mon, 05 October 2015 13:30 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 498E51ACD6A for <>; Mon, 5 Oct 2015 06:30:21 -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 dfh4C4sX14z5 for <>; Mon, 5 Oct 2015 06:30:18 -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 BA25F1A1AA3 for <>; Mon, 5 Oct 2015 06:30:18 -0700 (PDT)
Received: from lists by with local (Exim 4.80) (envelope-from <>) id 1Zj5mo-0007Eh-Rj for; Mon, 05 Oct 2015 13:26:38 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1Zj5mi-0007DS-Nk for; Mon, 05 Oct 2015 13:26:33 +0000
Received: from ([]) by with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1Zj5mh-0002ec-2j for; Mon, 05 Oct 2015 13:26:31 +0000
Received: from ([] helo=[]) by with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <>) id 1Zj5mg-0005Ms-Jd for; Mon, 05 Oct 2015 13:26:30 +0000
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
Content-Type: text/plain; charset="us-ascii"
To: Mark Nottingham <>
From: "Eliot Lear (elear)" <>
In-Reply-To: <>
Resent-From: Yves Lafon <>
Date: Mon, 05 Oct 2015 11:54:35 +0000
Cc: HTTP Working Group <>, Barry Leiba <>
Content-Transfer-Encoding: quoted-printable
Resent-Date: Mon, 05 Oct 2015 15:26:28 +0200
Message-Id: <>
X-Name-Md5: efe3dad792d606410c9cc49cedaffc94
References: <>
X-Mailer: Apple Mail (2.3094)
X-W3C-Hub-Spam-Status: No, score=-2.4
X-W3C-Hub-Spam-Report: ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, W3C_NW=0.5
X-W3C-Scan-Sig: 1Zj5mh-0002ec-2j 4e7cdf11191509fe4d3ba5b87bfd96d2
Subject: Re: Adjustments to our work mode - please read
Archived-At: <>
X-Mailing-List: <> archive/latest/30320
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>


On the whole I believe this is a reasonable experiment.

First, you are a chair and not a king. You should have proposed this to the group before acting.  Do other chairs get to pick and choose their rules?  

Had you consulted the group first, someone might have asked the question about how those coming into the group anew would understand the process. Others might have asked about whether GitHub is sufficient for archival purposes.  Others might have asked how easy it would be to manage two parallel discussions on the same issue.

Anyway, what I ask at this point is four things:

1.  The charter of the group should indicate the procedures being used. 

2. Those procedures should be documented in a draft.

3.  Before you close an issue in GitHub, you should give fair warning on *this* list with a pointer.

4.   Finally, you have repeatedly and needlessly used derogatory language toward those who have worked hard for *this* organization. I think you owe that group an apology. 


> On Oct 4, 2015, at 8:53 PM, Mark Nottingham <> wrote:
> Everyone,
> A number of folks have commented over the years about how it can be difficult to follow this mailing list. This is especially the case for HTTP implementers who don't have the time to focus on such a high-volume channel.
> I've been concerned about this for some time, since it can be seen as biasing participation towards "professional" standards people, and away from implementers and users. So, to see if we can improve matters for those folks without significantly disadvantaging current participants, I've been talking to our Area Director about experimenting with the group's working mode. 
> To that end, we're going to try allowing discussion and resolution of issues in the issue tracker itself, rather than requiring discussion there to be moved here -- thereby allowing people to participate without subscribing to the mailing list, if they don't want to. 
> For details, see:
> This takes effect immediately for our current deliverables, whose issue list is here:
> If you want to track conversations there and have a Github account, you can click "watch" at the top of the patch to be notified of new comments, etc.
> To make sure that those who don't wish to use the issue tracker aren't disadvantaged, we'll do a number of things, including:
> - Summarise (with links) the design issues closed by each draft when it is announced on this list
> - Allow issues to be re-opened when someone brings substantive new information (as always)
> - Allow those who do not wish to use the issues list to comment on this 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: <>
> We'll review this approach on a continuing basis to make sure it's working.
> Cheers,
> --
> Mark Nottingham