From: Samuel Ortiz <samuel@sortiz.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "John W.Linville" <linville@tuxdriver.com>,
Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org, johannes@sipsolutions.net,
Gustavo Padovan <gustavo@padovan.org>,
linux-bluetooth@vger.kernel.org, linux-nfc@ml01.01.org
Subject: Re: Linux Wireless Mini-Summit in New Orleans -- 19-20 September
Date: Tue, 10 Sep 2013 11:46:55 +0200 [thread overview]
Message-ID: <1378806415.5017.1.camel@zurbaran> (raw)
In-Reply-To: <6D969CDD-C551-4C4C-A674-A7518B3EE0AC@holtmann.org>
Hi Marcel, John,
On Mon, 2013-09-09 at 13:48 -0700, Marcel Holtmann wrote:
> Hi John,
>
> >>>> Sorry, forgot to copy linux-bluetooth and linux-nfc...
> >>>>
> >>>> On Thu, Aug 08, 2013 at 02:54:11PM -0400, John W. Linville wrote:
> >>>>> Greetings!
> >>>>>
> >>>>> This is a reminder that we will have a Linux Wireless Mini-Summit in
> >>>>> New Orleans this year on 19-20 September. This will immediately follow
> >>>>> LinuxCon and will run concurrently with Linux Plumber's Conference.
> >>>>> This event includes Linux developers for wireless LAN (802.11),
> >>>>> Bluetooth, and NFC technologies. Both kernel and userland developers
> >>>>> are welcomed and heartily encouraged to attend!
> >>>>>
> >>>>> http://wireless.kernel.org/en/developers/Summits/New-Orleans-2013
> >>>>>
> >>>>> The link above is a Wiki. We are using it to collect discussion
> >>>>> topics and to negotiate agenda/scheduling options for the event.
> >>>>> Please go there to record your intent to attend the event and to
> >>>>> propopse topics for discussion.
> >>>>>
> >>>>> Please be aware that in order to attend the event above one must
> >>>>> register for either LinuxCon or for Linux Plumbers Conference.
> >>>>> Act now, before those events fill-up and close their registrations!
> >>>>>
> >>>>> We are allotted one "large" room (up to ~80 people "theater style"), and
> >>>>> two "small" rooms (up to ~25 people) for this event. Based on history
> >>>>> and the numbers of contributors, the larger room will primarily be
> >>>>> for the 802.11 discussions and any "plenary" topics while the smaller
> >>>>> rooms will be for Bluetooth, NFC, and any "breakout" topics.
> >>>>>
> >>>>> So...thoughts? Topics to discuss?
> >>>
> >>> Ping? We're now just 2 weeks away!
> >>>
> >>> Is our topic list complete? It looks a bit light...
> >>>
> >>> Anyone have any input on scheduling the topics? Are there any
> >>> overlapping LPC sessions that it would make sense to work around?
> >>
> >> I'm attending though I haven't put my name on the wiki yet.
> >>
> >> Random thoughts; it doesn't look like any of these are covered in the
> >> regular LinuxConf or LPC sessions.
> >>
> >> 1) State of the Union (maybe by multiple people in the same session per
> >> their expertise), since perhaps not everyone doing eg 802.11 stuff knows
> >> what's happening in BT or NFC land, or not everyone working on a
> >> specific driver may know what new stuff their driver might need to be
> >> fixed up for. Maybe 5 minutes or less for things like:
> >>
> >> * what's under the most active development right now?
> >> * upcoming new driver, hardware, and new capabilities
> >> * new 802.11 standards
> >> * and what's coming up in the next year from the standards orgs
> >> * what people will start working on soon
> >> * what will 3.13 or 3.14 look like from a wireless perspective?
> >> * 11s mesh status?
> >> * anything interesting in wpa_supplicant land?
> >> * anything new/interesting on the Android front?
> >>
> >> 2) Bluetooth - update about what's new and what's coming up in Bluez
> >> land, and interaction with kernel 802.11 if any,
> >>
> >> 3) NFC - update about what's new and what's coming up in NFC land, where
> >> it's getting used, what the stack looks like
> >>
> >> 4) What are users having the most problems with and how these problems
> >> be fixed better/more quickly? Are they driver bugs? Are they stack
> >> bugs? Supplicant bugs? NM/GUI/etc bugs? Is there anything in our
> >> development processes that's not working as smoothly as it could be?
> >
> > Thanks, Dan -- those all look like decent discussion points.
> > I've added most of the points above to the topic list:
> >
> > http://wireless.kernel.org/en/developers/Summits/New-Orleans-2013
> >
> > Now, we need a few volunteers...
> >
> > Gustavo, can you do a session on Bluetooth developments?
> >
> > Samuel, can you cover NFC?
>
> I can do the Bluetooth part and I am just volunteering Samuel for NFC ;)
Thanks Marcel for the initiative ;)
John, I'll do the NFC part, sorry for not being able to reply earlier.
Cheers,
Samuel.
next prev parent reply other threads:[~2013-09-10 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 18:54 Linux Wireless Mini-Summit in New Orleans -- 19-20 September (6 weeks from today!) John W. Linville
2013-08-08 19:04 ` John W. Linville
2013-09-05 13:39 ` John W. Linville
2013-09-05 16:04 ` Dan Williams
2013-09-09 19:23 ` Linux Wireless Mini-Summit in New Orleans -- 19-20 September John W. Linville
2013-09-09 21:50 ` Seth Forshee
2013-09-10 6:28 ` Luca Coelho
2013-09-10 7:59 ` Arend van Spriel
[not found] ` <6D969CDD-C551-4C4C-A674-A7518B3EE0AC@holtmann.org>
2013-09-10 9:46 ` Samuel Ortiz [this message]
2013-09-12 18:38 ` Daniel Wagner
2013-09-12 18:48 ` John W. Linville
2013-09-12 19:26 ` Dan Williams
2013-09-12 19:31 ` Daniel Wagner
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=1378806415.5017.1.camel@zurbaran \
--to=samuel@sortiz.org \
--cc=dcbw@redhat.com \
--cc=gustavo@padovan.org \
--cc=johannes@sipsolutions.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-nfc@ml01.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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