linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: xorg@lists.freedesktop.org
Cc: libv@skynet.be, mesa-dev@lists.freedesktop.org,
	xorg-devel@lists.x.org, wayland-devel@lists.freedesktop.org,
	mir-devel@lists.ubuntu.com, directfb-dev@directfb.org,
	linux-fbdev@vger.kernel.org, linux-media@vger.kernel.org,
	xorg@lists.x.org, xorg-announce@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Subject: Re: FOSDEM15: Graphics DevRoom: call for speakers.
Date: Thu, 11 Dec 2014 15:53:27 +0000	[thread overview]
Message-ID: <20141211075327.453bfcbf@jbarnes-hsw> (raw)
In-Reply-To: <20141209143926.GB17341@skynet.be>

On Tue, 9 Dec 2014 15:39:26 +0100
Luc Verhaegen <libv@skynet.be> wrote:

> On Thu, Oct 02, 2014 at 07:44:57PM +0200, Luc Verhaegen wrote:
> > Hi,
> > 
> > At FOSDEM on the 31st of january and the 1st of February 2015, there 
> > will be another graphics DevRoom. URL: https://fosdem.org/2015/
> 
> > Slots will be handed out on a first come, first serve basis. The best 
> > slots will go to those who apply the earliest. The amount of slots is 
> > currently not known yet, but i expect there to be around 16 available (8 
> > on each day), so act quickly.
> 
> > As for deadlines, i hope to have a pretty much complete schedule between 
> > christmas and the new year. The rockhard printed schedule deadline is 
> > probably January 9th, after that you will not be featured in the booklet 
> > and you will have a lot less visitors. I will hopefully be able to lock 
> > down entries and descriptions after that date.
> 
> It's been more than 2 months since the original email, it's less than 
> two months away from the event, and one month away from what usually is 
> the deadline for the booklet. File your talk now, while there are still 
> some useful slots available.
> 
> Also, for those who have filed already but who have left their abstracts 
> open, please get those filed in ASAP. Your talk will be only be ordered 
> in when at least the basics are provided.

Hey Luc, thanks for the reminder.  I just submitted a talk myself;
hopefully there's still room on the schedule! :)

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2014-12-11 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 17:44 FOSDEM15: Graphics DevRoom: call for speakers Luc Verhaegen
2014-12-09 14:39 ` Luc Verhaegen
2014-12-11 15:53   ` Jesse Barnes [this message]
     [not found]   ` <20141209143926.GB17341-AgBVmzD5pcezQB+pC5nmwQ@public.gmane.org>
2015-01-13 12:14     ` Thierry Reding
2015-01-13 12:27       ` Luc Verhaegen

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=20141211075327.453bfcbf@jbarnes-hsw \
    --to=jbarnes@virtuousgeek.org \
    --cc=directfb-dev@directfb.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=libv@skynet.be \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=mir-devel@lists.ubuntu.com \
    --cc=wayland-devel@lists.freedesktop.org \
    --cc=xorg-announce@lists.freedesktop.org \
    --cc=xorg-devel@lists.x.org \
    --cc=xorg@lists.freedesktop.org \
    --cc=xorg@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 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).