public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Theodore Tso <tytso@mit.edu>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.5 Workshop RealVideo streams -- next time, please get  better audio.
Date: Tue, 17 Apr 2001 18:08:42 -0700	[thread overview]
Message-ID: <3ADCE91A.3CB74F63@megapathdsl.net> (raw)
In-Reply-To: <3ADB922B.4DE1F9A4@megapathdsl.net> <15067.37887.604760.637443@pizda.ninka.net> <20010417205722.A3626@think>

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

  reply	other threads:[~2001-04-18  1:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17  0:45 Kernel 2.5 Workshop RealVideo streams -- next time, please get better audio Miles Lane
2001-04-17  0:53 ` David S. Miller
2001-04-17  1:37   ` Miles Lane
2001-04-18  0:57   ` Theodore Tso
2001-04-18  1:08     ` Miles Lane [this message]
2001-04-18  2:22     ` Joel Jaeggli
2001-04-18  2:46     ` Albert D. Cahalan
2001-04-18 11:58       ` Alan Cox
2001-04-18 15:07       ` Andrea Arcangeli
2001-04-17  1:53 ` Randolph Bentson
2001-04-17  1:56   ` Ben Ford
2001-04-17  3:43     ` Miles Lane
2001-04-17  4:47       ` Kernel 2.5 Workshop RealVideo streams -- next time, please get Albert D. Cahalan
2001-04-17  3:46   ` Kernel 2.5 Workshop RealVideo streams -- next time, please get better audio Miles Lane
2001-04-17  3:48     ` Larry McVoy
2001-04-17  3:54       ` Miles Lane
2001-04-17  3:56         ` Larry McVoy
2001-04-17  3:01           ` David Lang
2001-04-17  4:07           ` Miles Lane
2001-04-17 13:03             ` Mike A. Harris
2001-04-17 18:29               ` Kernel 2.5 Workshop RealVideo streams -- next time, please getbetter audio Miles Lane
2001-04-17 14:23             ` Kernel 2.5 Workshop RealVideo streams -- next time, please get better audio Jonathan Morton
2001-04-17 14:51               ` Kernel 2.5 Workshop RealVideo streams -- next time, please Alan Cox
2001-04-18 12:34 ` Kernel 2.5 Workshop RealVideo streams -- next time, please get better audio Eric W. Biederman
2001-04-18 12:44   ` Alan Cox
2001-04-18 18:29     ` Tim Wright

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ADCE91A.3CB74F63@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox