All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Samuel Ortiz <samuel@sortiz.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	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: Sun, 25 Mar 2012 13:41:25 -0300	[thread overview]
Message-ID: <20120325164125.GE3106@joana> (raw)
In-Reply-To: <1332516578.5884.7.camel@sortiz-mobl>

Hi John,

* Samuel Ortiz <samuel@sortiz.org> [2012-03-23 16:29:38 +0100]:

> 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.

I agree with Barcelona too. If you wanna help to coordinate this with Linux
Foundation count on 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.

+1 to keep that approach, if this summit becomes bigger in the future we can
change it.

	Gustavo

  reply	other threads:[~2012-03-25 16:42 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 [this message]
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 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=20120325164125.GE3106@joana \
    --to=gustavo@padovan.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=samuel@sortiz.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 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.