Re: [hybi] email granularity, was: WebSockets feedback
Greg Wilkins <gregw@webtide.com> Fri, 16 April 2010 07:32 UTC
Return-Path: <gregw@webtide.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDCC73A6BE2 for <hybi@core3.amsl.com>; Fri, 16 Apr 2010 00:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKqUjGg1pDFj for <hybi@core3.amsl.com>; Fri, 16 Apr 2010 00:32:56 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by core3.amsl.com (Postfix) with ESMTP id 994C13A6BF3 for <hybi@ietf.org>; Fri, 16 Apr 2010 00:23:24 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id e12so133790fga.13 for <hybi@ietf.org>; Fri, 16 Apr 2010 00:23:14 -0700 (PDT)
Received: by 10.223.7.76 with SMTP id c12mr539260fac.42.1271402594435; Fri, 16 Apr 2010 00:23:14 -0700 (PDT)
Received: from [192.168.0.100] (host116-234-static.43-88-b.business.telecomitalia.it [88.43.234.116]) by mx.google.com with ESMTPS id p17sm2963987fka.16.2010.04.16.00.23.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 16 Apr 2010 00:23:13 -0700 (PDT)
Message-ID: <4BC8105F.5000006@webtide.com>
Date: Fri, 16 Apr 2010 09:23:11 +0200
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <B578CFED7FE85644A170F4F7C9D52692019544C5@ESESSCMS0361.eemea.ericsson.se> <3d5f2a811003150230sdeb4f78hbdece96e5c742cfc@mail.gmail.com> <de17d48e1003180316w3dda1a3fo7db8b357925ec3f8@mail.gmail.com> <p2o3d5f2a811003310031x5dce7e9cs86a5a8981cd23c1d@mail.gmail.com> <Pine.LNX.4.64.1004140032040.875@ps20323.dreamhostps.com> <w2y5821ea241004142323h949c0b07l771171500a625a6c@mail.gmail.com> <4BC6DD89.4060502@gmx.de> <r2x5821ea241004150244ud3cb79bt757049890bf3d9ab@mail.gmail.com> <Pine.LNX.4.64.1004151908320.23507@ps20323.dreamhostps.com> <4BC76724.5090307@gmx.de>
In-Reply-To: <4BC76724.5090307@gmx.de>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] email granularity, was: WebSockets feedback
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Apr 2010 07:32:57 -0000
As this thread is turning into a bit of vote, I'll state my preference for a mostly threaded model. However, some level of aggregation is OK, but what I didn't like about the last mega-feedback post was three fold: + it mixed significantly different topics, such as editing style for drafts, discussion of requirements and discussions of new features. + it spanned a significant time frame, so that topics that I thought we had well and truly dealt with have been raised again... so we are just going to go around and around again. Which is not to say that Ian should not have his say on those topics, but if it had been given in a more timely manner in the original thread - then it would have been more productive and less wasteful of the time of others. + How does one respond to such a mega post if you don't agree with it? Aggregation is fine for people who are silent and mostly reading for a summary. But if you are an active participant, then responding to such a mega thread is really difficult. Firstly it encourages point by point replies (of which I'm often guilty), which I think prolong disagreement and are not good for converging on consensus. Secondly any future discussion is disconnected from the thread of the past discussion, so context is lost, arguments revisited and we lather, rinse and repeat! Actually, my real preference is that we get started using trac to focus on individual issues and nail them down 1 by 1 to get a good statement of requirements. Without that, I think we will never converge on consensus, regardless of how we thread our emails. cheers
- [hybi] Revised WebSocket Feedback Vladimir Katardjiev
- Re: [hybi] Revised WebSocket Feedback Takeshi Yoshino
- Re: [hybi] Revised WebSocket Feedback Fumitoshi Ukai (鵜飼文敏)
- Re: [hybi] Revised WebSocket Feedback Takeshi Yoshino
- [hybi] WebSockets feedback Ian Hickson
- Re: [hybi] WebSockets feedback Pieter Hintjens
- Re: [hybi] WebSockets feedback Greg Wilkins
- [hybi] email granularity, was: WebSockets feedback Julian Reschke
- Re: [hybi] email granularity, was: WebSockets fee… Pieter Hintjens
- Re: [hybi] email granularity, was: WebSockets fee… Anne van Kesteren
- Re: [hybi] email granularity, was: WebSockets fee… Ian Hickson
- Re: [hybi] email granularity, was: WebSockets fee… Julian Reschke
- Re: [hybi] email granularity, was: WebSockets fee… Michael Carter
- Re: [hybi] email granularity, was: WebSockets fee… Justin Erenkrantz
- Re: [hybi] email granularity, was: WebSockets fee… Greg Wilkins
- Re: [hybi] email granularity, was: WebSockets fee… Julian Reschke
- Re: [hybi] email granularity, was: WebSockets fee… SM
- Re: [hybi] email granularity, was: WebSockets fee… Greg Wilkins
- Re: [hybi] email granularity, was: WebSockets fee… Tim Bray
- Re: [hybi] email granularity, was: WebSockets fee… Pieter Hintjens
- Re: [hybi] email granularity, was: WebSockets fee… SM
- Re: [hybi] email granularity, was: WebSockets fee… Ian Hickson
- Re: [hybi] email granularity, was: WebSockets fee… Maciej Stachowiak
- Re: [hybi] email granularity, was: WebSockets fee… Pieter Hintjens
- Re: [hybi] email granularity, was: WebSockets fee… Greg Wilkins
- Re: [hybi] email granularity, was: WebSockets fee… L.Wood