From: "John W. Linville" <linville@tuxdriver.com>
To: Marcel Holtmann <marcel@holtmann.org>
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 10:54:34 -0400 [thread overview]
Message-ID: <20120326145433.GE13806@tuxdriver.com> (raw)
In-Reply-To: <1332698585.1870.88.camel@aeonflux>
On Sun, Mar 25, 2012 at 11:03:05AM -0700, Marcel Holtmann wrote:
> I am in favor of requiring attendees to register with the LinuxCon
> event. That has always worked out nicely for everybody. Especially if we
> want to have extra rooms for breakout sessions. Otherwise we have to
> figure out the room costs.
>
> Unless some company wants to step up and sponsor. Or sponsor a dinner
> event and get free attendance. I think we can figure something out to
> make this work if anybody is interested ;)
Sponsorship is always welcome, of course. :-)
> > 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?
> Any other thoughts?
>
> And while we are at it I am volunteering myself (or someone from our
> team) to give the "Bluetooth: State of the Union" talk.
Cool.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-03-26 14:54 UTC|newest]
Thread overview: 20+ 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 [this message]
2012-03-26 15:15 ` Marcel Holtmann
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 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: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=20120326145433.GE13806@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).