All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: RFC/CFP -- Linux Wireless (802.11/Bluetooth/NFC) Mini-Summit 2012 (Barcelona?)
Date: Mon, 26 Mar 2012 17:15:06 +0200	[thread overview]
Message-ID: <1332774906.1870.98.camel@aeonflux> (raw)
In-Reply-To: <20120326145433.GE13806@tuxdriver.com>

Hi John,

> > > Given the potential to expand this into a larger event, we would
> > > likely need to be somewhat more formal about having proposals for
> > > speaking slots.  In that case, we might require a program committee
> > > for reviewing proposals, etc.  Anyone interested in participating in
> > > speaking at the mini-summit or in reviewing speaking proposals should
> > > contact me or reply in this thread.
> > 
> > When you and I talked originally about this, we discussed the format a
> > little bit. In theory we have a bunch of options here. One of the
> > original thoughts was 1-2 day mini-conference and 1 day break-out
> > sessions. I assume 6 presentation per day is maximum. Is it enough to
> > just do 1 day?
> 
> I don't think that 1 day is enough.  2 might not be enough, depending
> on how we stage it.  Do you think that we would have more than one
> "track" (e.g. separate Blueooth/802.11/NFC sessions)?  A single
> "plenary" session?  Or some mix?

so what about 2 days single track and 1 day with breakout sessions. So
we could do 12 talks with morning and afternoon sessions on the 3rd day
as needed.

If we have many proposals for presentations, we can always go switch to
2 tracks. If we require LinuxCon registration, then it should be no
problem to get a second room. If not, I have to negotiate with Angela
next week ;)

Regards

Marcel



  reply	other threads:[~2012-03-26 15:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 19:24 RFC/CFP -- Linux Wireless (802.11/Bluetooth/NFC) Mini-Summit 2012 (Barcelona?) John W. Linville
2012-03-23 15:29 ` Samuel Ortiz
2012-03-25 16:41   ` Gustavo Padovan
2012-03-25 18:03 ` Marcel Holtmann
2012-03-26 14:54   ` John W. Linville
2012-03-26 15:15     ` Marcel Holtmann [this message]
2012-03-26 15:25       ` John W. Linville
2012-04-27 17:44         ` CFP -- Linux Wireless (802.11/Bluetooth/NFC) Mini-Summit 2012 (Barcelona!) John W. Linville
2012-04-27 21:40           ` Andrei Emeltchenko
2012-04-27 21:40             ` Andrei Emeltchenko
2012-04-27 22:30           ` Joao Paulo Rechi Vita
2012-04-27 22:30             ` Joao Paulo Rechi Vita
2012-04-28  5:58           ` Alexander Smirnov
2012-05-14  7:18           ` Johannes Berg
2012-05-14 13:14             ` John W. Linville
2012-07-23 19:20           ` 2nd " John W. Linville
2012-07-23 20:04             ` Johannes Berg
2012-07-24  9:21             ` Daniel Wagner
2012-07-25  9:20             ` Smirnov, Alexander
2012-07-25  9:20               ` Smirnov, Alexander
2012-07-25  9:36             ` Samuel Ortiz
2012-07-25 12:37               ` John W. Linville
2012-07-25 22:55             ` Nick Kossifidis

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=1332774906.1870.98.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.