public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: linux-kernel@vger.kernel.org, lwn@lwn.net
Subject: Linux Plumbers' Conference 2011: Call for Tracks
Date: Mon, 17 Jan 2011 11:06:21 -0800	[thread overview]
Message-ID: <20110117110621.7baf024f@jbarnes-desktop> (raw)

Linux Plumbers' Conference 2011 Call for Track Ideas

The Linux Plumbers' Conference will take place in Santa Rosa, CA,
September 7-9, 2011.  The structure of the conference remains the same
as in previous years; rather than focus on presenting completed work or
problems and solutions, we encourage BoF and brainstorming sessions that
gather experts from different parts of the Linux ecosystem to discuss
complex problems with implications for multiple systems, with an eye
toward making progress and reaching consensus on their solutions.  As in
past years, we aim to foster a workshop like atmosphere, where once
consensus is reached, attendees can spend time developing solutions in
real-time, sharing experience and evaluating trade-offs.

The program committee is now looking for track proposals.  The ideal
track proposal is focused enough to allow progress and attract the right
particpants, but also spans several components of the Linux technology
stack and a set of problems that can specifically benefit from face to
face discussion between the various teams involved.  Proposals should
include a list of projects involved, key contributors to lead
discussions, and an owner for the track.  The track owner is responsible
for facilitating and scheduling sessions and generally making sure the
track is successful (metrics for this will vary by track & discussion).

Track proposals should be sent to lpc-planning@linuxplumbersconf.org.

--
LPC 2011 Planning Committee

                 reply	other threads:[~2011-01-17 19:06 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=20110117110621.7baf024f@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    /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