public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: ksummit-2012-discuss@lists.linux-foundation.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2012-discuss] Organising Mini Summits within the Kernel Summit
Date: Fri, 13 Jul 2012 13:37:08 -0400	[thread overview]
Message-ID: <20120713173708.GB17109@thunk.org> (raw)
In-Reply-To: <1341994155.3522.16.camel@dabdike.int.hansenpartnership.com>

On Wed, Jul 11, 2012 at 09:09:15AM +0100, James Bottomley wrote:
> Hi All,
> 
> We have set aside the second day of the kernel summit (Tuesday 28
> August) as mini-summit day.  So far we have only the PCI mini summit on
> this day, so if you can think of other topics, please send them to the
> kernel summit discuss list:
> 
> ksummit-2012-discuss@lists.linux-foundation.org
> 
> Looking at the available rooms, we think we can run about four or five
> mini summits.
> 
> As an added incentive, mini summit organisers get to pick who they
> invite and all the people they pick will get an automatic invitation to
> the third day of the kernel summit (but not the core first day) and the
> evening events.

OK, so far I believe I've heard concrete suggestions from identified
(or fairly well identified :-) stuckees willing to organize
mini-summits for:

* ARM
* Media
* PCI
* memcg

I may have missed some, so if people could send a message to the
discuss list with [MINI-SUMMIT] in the subbject line and the name of
the proposed mini-summit, that would be really helpful.  Please
indicate whether you are volunteering to help organize the proposed
mini-summit, or identify someone you think can be volunteered.  :-)

Things that we will be asking the mini-summit chars to determine, in
addition to who should be given invites for Tuesday and Wednesday is
an estimate of how much time you need, and a list of sub-topics (and
who might lead the sub-topic discussion).  We will be asking you to
create a fairly well-defined schedule, with 30 and 60 minute slots, so
that we can publish a schedule and so that people who might need to
hop between mini-summits, have a chance to do so.  So please start
thinking about how long each of your sub-topics will need to be, and
who might be needed for a particular sub-topic's discussion to be
successful.  There may be a number of developers, with fingers in
multiple subsystem, where scheduling may become a bit of a challenge.

Thanks!!

						- Ted

      parent reply	other threads:[~2012-07-13 17:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11  8:09 Organising Mini Summits within the Kernel Summit James Bottomley
2012-07-11 11:28 ` ARM mini-summit Arnd Bergmann
2012-07-11 11:57   ` [Ksummit-2012-discuss] " Catalin Marinas
2012-07-11 12:35     ` Marc Zyngier
2012-07-12 22:08       ` Kukjin Kim
2012-07-13  7:18         ` Tony Lindgren
2012-07-27 13:57           ` Igor Grinberg
     [not found]   ` <CACxGe6vOXaJaTdob8MZ7NGw8v-QQ0wnycnYK6JTK+YT5vA2EfQ@mail.gmail.com>
2012-07-11 14:05     ` Konrad Rzeszutek Wilk
2012-07-11 19:27       ` Konrad Rzeszutek Wilk
2012-07-11 20:06         ` Arnd Bergmann
2012-07-11 20:11           ` Konrad Rzeszutek Wilk
2012-07-11 21:16           ` Marc Zyngier
2012-07-11 21:58             ` Rob Herring
2012-07-12 13:58             ` Stefano Stabellini
2012-07-12 13:31         ` Stefano Stabellini
2012-07-11 21:02   ` David Brown
2012-07-13  2:33   ` Olof Johansson
2012-07-11 18:32 ` wireless networking mini-summit John W. Linville
2012-07-13 17:37 ` Theodore Ts'o [this message]

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=20120713173708.GB17109@thunk.org \
    --to=tytso@mit.edu \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ksummit-2012-discuss@lists.linux-foundation.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