From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751234AbWECVH4 (ORCPT ); Wed, 3 May 2006 17:07:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751268AbWECVH4 (ORCPT ); Wed, 3 May 2006 17:07:56 -0400 Received: from accolon.hansenpartnership.com ([64.109.89.108]:51109 "EHLO accolon.hansenpartnership.com") by vger.kernel.org with ESMTP id S1751234AbWECVHz (ORCPT ); Wed, 3 May 2006 17:07:55 -0400 Subject: Call for Presentations: Kernel Summit Dissenters Session From: James Bottomley To: linux-kernel , ksummit-2006-pc@thunk.org Content-Type: text/plain Date: Wed, 03 May 2006 16:07:50 -0500 Message-Id: <1146690470.3346.80.camel@mulgrave.il.steeleye.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-4.fc4) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Do you think there is an area where the kernel developers are making a fundamental mistake? Is there a better path we should be taking? If you have a better idea - and are willing to argue your point in front of several dozen assembled kernel hackers - please consider writing a proposal for the 2006 Kernel Summit Dissenter's Session. The program committee will review submitted proposals, looking for those which seem most likely to result in an interesting and useful discussion. A selected proposal will entitle the author to a seat at the Summit (with the possibility of travel assistance if needed), and a 20-minute slot during the Dissenter's Session. A five-minute presentation will be given, followed by fifteen minutes of discussion. Ottawa has plenty of purveyors of good beer for recovery afterward. If you are interested in presenting at the summit, please put together a proposal of no more than 400 words and send it to the discussion list: ksummit-2006-discuss@thunk.org Proposals should describe the problem, how things should have been done differently, and what can be done to fix it now. Winning proposals will avoid topics which have been discussed into the ground (no devfs or C++, please), and will cover a topic of interest to a large subset of the development community. Proposals should be submitted by 20 May 2006.