From: Jes Sorensen <jes@sgi.com>
To: Dave Jones <davej@redhat.com>, Jes Sorensen <jes@sgi.com>,
Theodore Tso <tytso@mit.edu>,
Sunil Naidu <akula2.shark@gmail.com>,
linux-kernel@vger.kernel.org, dirk.hohndel@intel.com,
alan@redhat.com, ksummit-2007-discuss@thunk.org,
David Miller <davem@davemloft.net>
Subject: Re: [Ksummit-2007-discuss] Re: [Ksummit-2006-discuss] 2007 Linux Kernel Summit
Date: Tue, 30 Jan 2007 05:51:00 +0100 [thread overview]
Message-ID: <45BECEB4.6060905@sgi.com> (raw)
In-Reply-To: <20070130030430.GA21772@redhat.com>
Dave Jones wrote:
> > Then there is the issue of architectures, at least in my book KS should
> > focus on the ones that are really live and not in maintenance mode.
> > x86_64, x86_32, PPC, ia64, ARM seems to be the driving ones these days,
> > m68k, Sparc32, and others, somewhat less so .....
>
> Again, I don't recall us spending any time at all discussing m68k, or
> sparc, whilst the others you mention were well represented.
Hi Dave,
I'm not too bothered about the subjects, but rather the issue that we
keep seeing this strict "only this small group, which defines the most
important people in the community" thing. Thats where I think the
current model fails, even if someone has done a lot of work all over
Linux for years, doesn't mean said people are the ones driving things
this year.
Personally I think Andrew's suggestion is really good, turning it more
towards the traditional conference means people who have something they
want to say are more likely to push for things. If one doesn't have
something to say, then going to the KS is probably not the right thing.
> One of the problems with this approach is sometimes we don't know about
> subjects that become important to us all until the last minute, and
> others that seem important now will become moot by the time the summit comes around.
Thats true, and there should certainly be space for new subjects coming
in on short notice. However, I would suggest that at least a significant
portion of the summit applies this requirement. Most of the more
important issues are architectural and it's often not something that
shows up last minute.
> So far though, there's been nothing proposed at all, so feel free
> to throw your hat in the ring, if nothing else, it'll kickstart
> the process.
Actually I'm in the process of investigating launching a mini summit
cabal, which I think would cover most of my current issues :)
Cheers,
Jes
next prev parent reply other threads:[~2007-01-30 4:51 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 7:09 2007 Linux Kernel Summit Theodore Ts'o
2007-01-22 11:07 ` [Ksummit-2006-discuss] " Christoph Hellwig
2007-01-22 12:45 ` Alan Cox
2007-01-22 13:14 ` Theodore Tso
2007-01-22 13:17 ` Steven Whitehouse
2007-05-03 21:54 ` LinuxConf Europe 2007 [was Re: 2007 Linux Kernel Summit] Alasdair G Kergon
2007-01-22 13:34 ` [Ksummit-2006-discuss] 2007 Linux Kernel Summit Alan
2007-01-22 18:23 ` Rik van Riel
2007-01-23 17:57 ` David Miller
2007-01-23 19:18 ` +1 4 cz (Re: [Ksummit-2006-discuss] 2007 Linux Kernel Summit) Oleg Verych
2007-01-25 15:22 ` Vojtech Pavlik
2007-02-06 19:29 ` James Simmons
2007-02-06 20:00 ` Vojtech Pavlik
2007-02-06 20:10 ` James Simmons
2007-02-07 12:06 ` [Ksummit-2007-discuss] " Arnd Bergmann
2007-02-07 12:17 ` Markus Rechberger
2007-01-25 14:22 ` [Ksummit-2006-discuss] 2007 Linux Kernel Summit Dirk Hohndel
2007-01-25 20:51 ` David Miller
2007-01-25 20:59 ` Dirk Hohndel
2007-01-25 21:04 ` David Miller
2007-01-26 0:46 ` Sunil Naidu
2007-01-26 3:28 ` Theodore Tso
2007-01-26 4:39 ` Josh Boyer
2007-01-26 6:17 ` Greg KH
2007-01-26 8:15 ` David Miller
2007-01-26 15:04 ` Sunil Naidu
[not found] ` <20070126195024.GE14759@thunk.org>
2007-01-26 23:17 ` Luck, Tony
[not found] ` <20070127064534.GC9897@thunk.org>
2007-01-28 4:25 ` Jes Sorensen
2007-01-28 13:22 ` Mauro Carvalho Chehab
[not found] ` <45BE8BF9.6020204@sgi.com>
[not found] ` <20070130030430.GA21772@redhat.com>
2007-01-30 3:30 ` [Ksummit-2007-discuss] " Greg Ungerer
2007-01-30 3:41 ` Dave Jones
2007-01-30 3:57 ` Greg Ungerer
2007-01-30 4:01 ` Greg Ungerer
2007-01-30 4:08 ` Paul Mundt
2007-01-30 4:34 ` Dave Jones
2007-01-30 10:30 ` Christoph Hellwig
2007-01-30 16:48 ` James Bottomley
2007-01-30 16:53 ` Randy Dunlap
2007-01-30 17:12 ` James Bottomley
2007-01-31 8:18 ` Christoph Hellwig
2007-01-30 14:35 ` Alan
2007-01-30 4:10 ` Dave Jones
2007-01-30 4:22 ` Greg Ungerer
2007-01-30 4:25 ` [Ksummit-2007-discuss] Re: [Ksummit-2006-discuss] 2007 LinuxKernel Summit Dirk Hohndel
2007-01-30 4:24 ` Dirk Hohndel
2007-01-30 8:33 ` Arnd Bergmann
2007-01-30 5:11 ` [Ksummit-2007-discuss] Re: [Ksummit-2006-discuss] 2007 Linux Kernel Summit Andi Kleen
2007-01-30 5:21 ` Dave Jones
2007-01-30 6:18 ` Paul Mundt
2007-01-30 4:57 ` Jes Sorensen
2007-01-31 0:09 ` Greg Ungerer
2007-01-30 3:36 ` Greg Ungerer
2007-01-30 4:51 ` Jes Sorensen [this message]
2007-01-30 5:11 ` James Bottomley
2007-01-30 10:33 ` Christoph Hellwig
2007-01-30 13:30 ` Theodore Tso
2007-01-30 13:41 ` Peter Zijlstra
2007-01-30 13:51 ` Paul Mundt
2007-02-03 7:00 ` Len Brown
2007-01-30 5:19 ` Dave Jones
2007-01-30 5:47 ` Jes Sorensen
2007-01-30 5:03 ` Andi Kleen
2007-01-30 5:51 ` Jes Sorensen
2007-01-30 6:04 ` Andi Kleen
2007-01-30 6:11 ` Jes Sorensen
2007-01-30 18:21 ` Luck, Tony
2007-01-30 6:43 ` Muli Ben-Yehuda
2007-01-30 7:18 ` Dave Jones
2007-01-30 7:29 ` Muli Ben-Yehuda
2007-01-30 15:17 ` James Bottomley
[not found] ` <1170118042.3378.45.camel@mulgrave.il.steeleye.com>
[not found] ` <45BEF0C5.7090401@sgi.com>
[not found] ` <1170177057.3420.32.camel@mulgrave.il.steeleye.com>
2007-01-30 17:27 ` Matthew Wilcox
2007-01-30 17:37 ` James Bottomley
2007-01-30 21:24 ` Jes Sorensen
2007-01-31 0:42 ` James Bottomley
[not found] ` <20070130083025.1332a6ea.rdunlap@xenotime.net>
2007-01-31 0:52 ` Matt Domsch
2007-01-31 2:21 ` Jes Sorensen
2007-01-31 20:14 ` Dave Jones
2007-01-31 22:49 ` Jes Sorensen
2007-01-31 23:20 ` Gerrit Huizenga
2007-01-31 23:30 ` H. Peter Anvin
2007-01-31 23:52 ` Gerrit Huizenga
2007-02-01 5:41 ` [Ksummit-2007-discuss] Re: [Ksummit-2006-discuss] 2007 LinuxKernel Summit Dirk Hohndel
2007-01-31 23:20 ` [Ksummit-2007-discuss] Re: [Ksummit-2006-discuss] 2007 Linux Kernel Summit Alan
[not found] ` <20070129161445.0475d833@freekitty>
2007-01-31 22:53 ` Jes Sorensen
2007-01-26 17:29 ` Adrian Bunk
2007-01-30 9:09 ` [Ksummit-2007-discuss] " Oleg Verych
2007-01-30 9:44 ` Dave Airlie
2007-01-30 13:02 ` Oleg Verych
2007-01-30 9:22 ` hunting on open source developers (Re: [Ksummit-2006-discuss] 2007 Linux Kernel Summit) Oleg Verych
2007-01-26 12:23 ` [Ksummit-2006-discuss] 2007 Linux Kernel Summit Mauro Carvalho Chehab
2007-01-26 12:38 ` Bjørn Mork
2007-01-26 13:23 ` Ralf Baechle
2007-01-26 13:45 ` Alan
2007-01-23 19:52 ` Sunil Naidu
2007-01-23 21:25 ` James Morris
2007-01-23 21:39 ` Josh Boyer
2007-01-23 23:11 ` Sunil Naidu
2007-01-24 1:42 ` Theodore Tso
2007-01-24 8:49 ` Sunil Naidu
[not found] ` <8f3aa8d60701241018o6d4d8c37jb20ddb49f47e3eec@mail.gmail.com>
2007-01-24 18:27 ` Martin Bligh
2007-01-24 19:47 ` Scott Preece
2007-01-24 21:26 ` Alan Cox
2007-01-26 21:46 ` H. Peter Anvin
[not found] ` <E1H9pZc-0002J5-Na@flower>
2007-01-24 21:35 ` Scott Preece
2007-01-24 9:30 ` Benjamin Herrenschmidt
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=45BECEB4.6060905@sgi.com \
--to=jes@sgi.com \
--cc=akula2.shark@gmail.com \
--cc=alan@redhat.com \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=dirk.hohndel@intel.com \
--cc=ksummit-2007-discuss@thunk.org \
--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