mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-kernel <linux-kernel@vger.kernel.org>, ksummit-2006-pc@thunk.org
Subject: Call for Presentations: Kernel Summit Dissenters Session
Date: Wed, 03 May 2006 16:07:50 -0500	[thread overview]
Message-ID: <1146690470.3346.80.camel@mulgrave.il.steeleye.com> (raw)

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.



                 reply	other threads:[~2006-05-03 21:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1146690470.3346.80.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=ksummit-2006-pc@thunk.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®