Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 17 Apr 2001 21:08:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 17 Apr 2001 21:08:20 -0400 Received: from snowbird.megapath.net ([216.200.176.7]:9221 "EHLO megapathdsl.net") by vger.kernel.org with ESMTP id ; Tue, 17 Apr 2001 21:08:16 -0400 Message-ID: <3ADCE91A.3CB74F63@megapathdsl.net> Date: Tue, 17 Apr 2001 18:08:42 -0700 From: Miles Lane X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.4.3-ac7 i686) X-Accept-Language: en MIME-Version: 1.0 To: Theodore Tso CC: "David S. Miller" , linux-kernel@vger.kernel.org Subject: Re: Kernel 2.5 Workshop RealVideo streams -- next time, please get better audio. In-Reply-To: <3ADB922B.4DE1F9A4@megapathdsl.net> <15067.37887.604760.637443@pizda.ninka.net> <20010417205722.A3626@think> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Theodore Tso wrote: > > On Mon, Apr 16, 2001 at 05:53:19PM -0700, David S. Miller wrote: > > > > It does not work in a relaxed "people sit at tables and comment > > at arbitrary points in time during a talk" setting such as the > > kernel summit. Besides putting a microphone at every table (which > > isn't all that practical honestly) I can't come up with a solution. > > I suspect that if we're going to do this again, having a microphone at > each table is what we'd have to do, assuming that we can keep the > numbers of people at the workshop down to 60-70 (which will be a *lot* > harder next time, since everyone and his brother will want to show up, > and will therefore pester, whine, and otherwise beg the workshop > organizers to be included onto the invite list). > > If we have a lot more people, we'll probably have to go to the two > microphones in the aisle approach. But at that point a large part of > the workshop will be destroyed; so hopefully we'll just be able to > keep the numbers of people in the workshop to manageable number. Well, another option would be to have workshops on a more frequent basis, target the workshops on fewer areas and restrict the invitees to those doing work in fairly closely related areas. This would allow us to foster the synergy of teamwork. The only obvious downside to this IMHO would be the loss of the contribution of from those working in dissimilar areas. This might be a significant loss, since sometimes a great solution to a problem will come from someone who is thinking "outside the box" of the current development team. On the other hand, we could have the annual Kernel Workshop consist of the folks who were at this year summit and simply add other workshops that are more narrowly targetted. Miles - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/