Re: Adjustments to our work mode - please read
Willy Tarreau <w@1wt.eu> Tue, 06 October 2015 05:49 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D02B31B37FF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 5 Oct 2015 22:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gH5K5lUA-GDE for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 5 Oct 2015 22:49:13 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D05D71B37FE for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 5 Oct 2015 22:49:13 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ZjL4O-00044K-1b for ietf-http-wg-dist@listhub.w3.org; Tue, 06 Oct 2015 05:45:48 +0000
Resent-Date: Tue, 06 Oct 2015 05:45:48 +0000
Resent-Message-Id: <E1ZjL4O-00044K-1b@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <w@1wt.eu>) id 1ZjL4J-0003z7-WA for ietf-http-wg@listhub.w3.org; Tue, 06 Oct 2015 05:45:44 +0000
Received: from wtarreau.pck.nerim.net ([62.212.114.60] helo=1wt.eu) by lisa.w3.org with esmtp (Exim 4.80) (envelope-from <w@1wt.eu>) id 1ZjL4F-0005PO-Kh for ietf-http-wg@w3.org; Tue, 06 Oct 2015 05:45:42 +0000
Received: (from willy@localhost) by pcw.home.local (8.14.3/8.14.3/Submit) id t965jDRq002598; Tue, 6 Oct 2015 07:45:13 +0200
Date: Tue, 06 Oct 2015 07:45:13 +0200
From: Willy Tarreau <w@1wt.eu>
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, Barry Leiba <barryleiba@computer.org>
Message-ID: <20151006054513.GB2394@1wt.eu>
References: <9C939474-975C-4D12-8B78-E2A74264A9BD@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9C939474-975C-4D12-8B78-E2A74264A9BD@mnot.net>
User-Agent: Mutt/1.4.2.3i
Received-SPF: pass client-ip=62.212.114.60; envelope-from=w@1wt.eu; helo=1wt.eu
X-W3C-Hub-Spam-Status: No, score=-7.3
X-W3C-Hub-Spam-Report: AWL=1.276, BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1ZjL4F-0005PO-Kh 2ada150e9abbbc5235d697e1d7016c6c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Adjustments to our work mode - please read
Archived-At: <http://www.w3.org/mid/20151006054513.GB2394@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/30325
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Hi Mark! On Mon, Oct 05, 2015 at 11:47:55AM +1100, 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. (...) Interestingly, I think that the list provides *notifications*, something that is not provided at all by a web interface that you have to spontaneously visit to see if anything new was posted on each and every subject of interest. With e-mails you can process one at a time when you have some time. A few minutes several times a day. Emails can be marked read or moved to an archive for example. You can also easily see if you've responded already and you keep threading. I'm not seeing these possibilities with an issue tracker. To be honnest, I'm already predicting that I'll disappear from the discussions that I used to discover (like this one), because I've mostly been reacting to certain discussions, which will not happen anymore. But let's try. I'm also seeing something which I'm not sure will be easy to handle. Till now, some e-mail based discussions were split in several threads leading to multiple issues being created and addressed in parallel. I don't know if it will be possible to split issues into several ones, and even if possible I'm not sure it will be as easy to review the history of an issue as easily as it is with e-mail. But I welcome the experiment! If it is easier to deal with for certain participants (I'm still wondering how and why) and these participants provide more value than what we lose from other ones, it can in the end be positive. We don't know yet and that's the purpose of an experiment. In fact it raises an interesting point. It has always been difficult to track issues on the list, especially during "hot" discussions. It has happened several times that after things calmed down, some issues were restarted because someone (any of us) forgot the outcome due to many proposals made. We've seen this even more on hybi where it was very hard to agree on something and all of us were trying hard not to restart an issue by fear of losing the very small value we were seeing in the outcome. So it doesn't appear a bad idea at all to try to mix this with an issue tracker. If the experiment goes well, maybe we should switch to one which supports bidirectional e-mail. That provides everything we lose above plus the archival. For instance I've been dealing with some bugs handled by bugzilla on some sites and was using e-mail just as we do here, without having to check every day on the site if something new was posted regarding the issue I was interested in, nor searching it everywhere. In the mean time I have no idea if it's possible to configure github to automatically post an e-mail here (in addition to the new list dedicated to issues) to indicate that an issue was updated (and ideally with a copy of the contribution). Or maybe it would simply be better not to have a list dedicated to issues only. The current list is already for issues, that's what participants discuss all the day. I don't know either if it's possible to block edition to ensure we never lose any contents just because someone felt that something he said was stupid and preferred to remove it. The value is often in ideas initially considered as stupid :-) Overall this seems like a good idea to experiment with and the right timing to try it. There's no emergency to deliver anything critical right now, we can try different formats without the risk of losing people/value/time yet. Cheers, Willy
- Adjustments to our work mode - please read Mark Nottingham
- Re: Adjustments to our work mode - please read Eliot Lear (elear)
- Re: Adjustments to our work mode - please read Jason Greene
- Re: Adjustments to our work mode - please read Mark Nottingham
- Re: Adjustments to our work mode - please read Brian Smith
- Re: Adjustments to our work mode - please read Mark Nottingham
- Re: Adjustments to our work mode - please read Willy Tarreau
- Re: Adjustments to our work mode - please read Eliot Lear (elear)
- Re: Adjustments to our work mode - please read Eliot Lear (elear)
- Re: Adjustments to our work mode - please read Ted Hardie
- RE: Adjustments to our work mode - please read Mike Bishop
- Re: Adjustments to our work mode - please read Mark Nottingham
- Re: Adjustments to our work mode - please read Mark Nottingham
- Re: Adjustments to our work mode - please read Barry Leiba
- Re: Adjustments to our work mode - please read Eliot Lear (elear)
- Re: Adjustments to our work mode - please read Eliot Lear (elear)
- Re: Adjustments to our work mode - please read Eliot Lear (elear)
- Re: Adjustments to our work mode - please read Mark Nottingham