All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luc Verhaegen <libv@skynet.be>
To: xorg-devel@lists.x.org, members@x.org,
	dri-devel@lists.freedesktop.org, mesa-dev@lists.freedesktop.org,
	wayland-devel@lists.freedesktop.org
Subject: FOSDEM2013: DevRoom or not?
Date: Sun, 12 Aug 2012 15:50:16 +0200	[thread overview]
Message-ID: <20120812135016.GA18094@skynet.be> (raw)

Hi,

The FOSDEM organizers have sent out a call for devrooms. FOSDEM this 
year is on the weekend of the 2nd and 3rd of February 2013.

After the success of this formula last year, where, for the first time 
ever, we had a properly filled devroom schedule when the deadline hit, i 
am going to re-apply the same formula:
* By the 28th of september, i need 6 committed speakers, otherwise i 
  will not apply for a DevRoom. 6 people need to apply for a talk slot 
  who _definitely_ will come to FOSDEM on February 2nd and/or 3rd 2013. 
  This "definitely" means:
    * Don't knowingly plan anything else for this weekend.
    * Come to FOSDEM even if your corporation does not fund you (though 
      feel free to contact the board individually for funding)
    * Make sure that you are allowed to travel to the shengen area in 
      february.
    * Catastrophies excluded of course. Such catastrophies include 
      things like train-derailments and such, but explicitely excludes 
      hangovers :p
* Scheduling based on timeliness of application: the earlier you apply, 
  the better slot you get.
* FOSDEMs final deadline for the full schedule is likely around 15th of 
  january 2013. But do not count on that deadline, we will only do 
  hourly slots, to keep people from running around between devrooms like 
  headless chickens. Only 12-16 slots will be available, first come, 
  first serve.

I will set up a wiki page tonight, at http://wiki.x.org/wiki/fosdem2013 

I hope we get a nice devroom like we had last time. That new building we 
were in was really amazing, even though it took a while before all 
FOSDEM visitors found it.

Thanks,

Luc Verhaegen.

             reply	other threads:[~2012-08-12 13:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-12 13:50 Luc Verhaegen [this message]
     [not found] ` <20120812135016.GA18094-AgBVmzD5pcezQB+pC5nmwQ@public.gmane.org>
2012-08-12 16:54   ` FOSDEM2013: DevRoom or not? Alan Coopersmith
2012-09-21  9:35 ` Luc Verhaegen
2012-09-28 15:44   ` Luc Verhaegen
2012-09-28 16:07     ` Jesse Barnes
2012-09-28 17:41       ` Daniel Vetter
2012-09-28 20:18     ` Arthur Huillet
2012-09-28 21:51     ` Luc Verhaegen
     [not found]       ` <20120928215119.GD16074-AgBVmzD5pcezQB+pC5nmwQ@public.gmane.org>
2012-12-01  2:54         ` Michael Hasselmann
2012-12-26 16:56           ` David Herrmann

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=20120812135016.GA18094@skynet.be \
    --to=libv@skynet.be \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=members@x.org \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=wayland-devel@lists.freedesktop.org \
    --cc=xorg-devel@lists.x.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.