From: Samuel Ortiz <samuel@sortiz.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: Fri, 23 Mar 2012 16:29:38 +0100 [thread overview]
Message-ID: <1332516578.5884.7.camel@sortiz-mobl> (raw)
In-Reply-To: <20120322192406.GB2432@tuxdriver.com>
Hi John,
On Thu, 2012-03-22 at 15:24 -0400, John W. Linville wrote:
> A number of wireless developers reside in Europe, but our last few
> meetings have been held in North America. So, there is a strong desire
> to have a European location for this event. Initial contact with the
> Linux Foundation suggests that we can co-locate this event with the
> LinuxCon Europe event in Barcelona this November. Other suggestions
> are welcome as well, of course.
Barcelona sounds really good to me.
> If we join the LinuxCon Europe event, we would need to decide how to
> fund the event. One option would be to charge a separate entry fee for
> the mini-summit event, seperate from the LinuxCon EU fee. Those that
> do not wish to attend LinuxCon EU may find that attractive. OTOH,
> in the past we have simply said that all the mini-summit attendees
> had to register for the sponsoring event. That has worked reasonably
> well, especially since event speakers would be eligible to attend
> the mini-summit for no fee. I would lean toward keeping that approach.
I agree here as well.
> 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.
I can do an NFC talk. It would probably make sense to do a generic
presentation about the NFC kernel and userspace architecture, since this
is the first wireless summit where we have a kernel supporting NFC.
Cheers,
Samuel.
next prev parent reply other threads:[~2012-03-23 15:29 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 [this message]
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
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=1332516578.5884.7.camel@sortiz-mobl \
--to=samuel@sortiz.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 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).