lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <45BECEB4.6060905@sgi.com>
Date:	Tue, 30 Jan 2007 05:51:00 +0100
From:	Jes Sorensen <jes@....com>
To:	Dave Jones <davej@...hat.com>, Jes Sorensen <jes@....com>,
	Theodore Tso <tytso@....edu>,
	Sunil Naidu <akula2.shark@...il.com>,
	linux-kernel@...r.kernel.org, dirk.hohndel@...el.com,
	alan@...hat.com, ksummit-2007-discuss@...nk.org,
	David Miller <davem@...emloft.net>
Subject: Re: [Ksummit-2007-discuss] Re: [Ksummit-2006-discuss] 2007 Linux
 Kernel Summit

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ