mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Kossifidis <mickflemm@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Linux wireless mini-summit -- Berlin, June 2009
Date: Wed, 3 Jun 2009 15:35:14 +0300	[thread overview]
Message-ID: <40f31dec0906030535k3af1f6e7u68c82a4f984e7029@mail.gmail.com> (raw)
In-Reply-To: <20090403182724.GA7364@tuxdriver.com>

2009/4/3 John W. Linville <linville@tuxdriver.com>:
> Greetings,
>
> As you may know, we are planning on having a wireless summit meeting
> in Berlin, Germany this June.  This meeting is in cooperation with
> the Fedora FUDCon event, which will be accomodating us under the
> guise of a "hackfest".  This event also overlaps (and co-locates)
> with LinuxTag 2009.  Details are available here:
>
>        https://fedoraproject.org/wiki/FUDCon:Berlin_2009
>
> FUDCon's are typically self-organizing under the BarCamp model.
> However, I have secured a promise that we will be allocated space
> for 1-2 dozen people on at least Friday 26 June and Saturday 27 June
> for our wireless event.  I personally encourage everyone not only to
> attend LinuxTag but also to participate in the rest of FUDCon!
>
> So, here I open the floor for discussion of agenda items for our
> wireless meeting/hackfest.  What do we think is important to discuss
> face-to-face this year?  What isn't getting done?  What is getting
> done wrong?  What do we need that we didn't realize last year?
>
> Also, please consider making some sort of prepared presentation.
> Especially welcome would be topics that are accessible to those
> outside of the core wireless developer group, such as current
> projects on enhancing IBSS support, extended power savings, or any
> other user-visible topic.  I'll be happy to take such proposals in
> private email or you can post them as part of this thread.
>
> Hopefully this gets the discussion started...please comment!
>
> John
>
> P.S.  We are also planning a meeting in Portland this September for
> those unable or unwilling to travel outside of North America for
> whatever reason -- stay tuned.

Can we book a room on Holiday in
(http://fedoraproject.org/wiki/FUDCon:Berlin_2009_lodging) or is it
only for Fedora people ? What's the process ? I've managed to find
some funding for travel expenses but most hotels are really expensive
(i plan to come on 24 and leave on 29).


-- 
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick

  parent reply	other threads:[~2009-06-03 12:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 18:27 John W. Linville
2009-04-05 10:52 ` Rami Rosen
2009-04-05 12:03   ` Johannes Berg
2009-04-07  6:10     ` Mark Ryden
2009-05-08  9:18 ` Johannes Berg
2009-05-08 16:56   ` Kalle Valo
2009-05-08 17:14     ` Johannes Berg
2009-05-08 18:09       ` Helmut Schaa
2009-06-03 12:35 ` Nick Kossifidis [this message]
2009-06-03 12:39   ` John W. Linville
2009-06-24 10:19   ` 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=40f31dec0906030535k3af1f6e7u68c82a4f984e7029@mail.gmail.com \
    --to=mickflemm@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.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

all inboxes | Powered by JetHome®