All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luc Verhaegen <libv@skynet.be>
To: xorg-devel@lists.x.org, xorg-announce@lists.freedesktop.org,
	mesa-dev@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	wayland-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
	fosdem@lists.fosdem.org
Cc: graphics-devroom-manager@fosdem.org
Subject: FOSDEM27: Graphics DevRoom CfP.
Date: Fri, 30 Oct 2026 14:08:52 +0100	[thread overview]
Message-ID: <auSW5B2PoKq0ml7o@skynet.be> (raw)

We are happy to announce that we will have our customary Graphics 
DevRoom at FOSDEM on Sunday the 31st of January 2027.

The talk topics of the graphics devroom encompass:
* graphics drivers: display, 2d engines, 3d engines, at bootloader, 
kernel and userspace levels.
* media/video drivers: camera/capture engines, hardware media encoders 
and decoders on all levels.
* input drivers for bootloaders, kernels and userspace on all levels.
* windowing systems (X, wayland, surfaceflinger, others) and window 
managers.
* graphics toolkits (QT, GTK, others).
* 3D and Compute APIs (OpenGL, Vulkan, DirectX, others), and 3d and game 
engines.
* Virtual reality hardware and toolkits.
* Artificial Intelligence HW acceleration.
* Media encode and decode applications.
And the tools needed to help configure and run the above.

Submission deadline is the 5th of december, but do not count on this 
date, once the schedule has filled with enough solid talks, we will 
accept no more.

You can submit your talk proposal here: https://fosdem.org/submit

Please put some time and effort in the title and the abstract of your 
talk, and in your personal bio. If you want an audience, then this 
information is what draws people in to watch your talk.

Since this an open source community event, please refrain from turning 
in a talk that is purely corporate or a product commercial. Also, this 
is a highly technical devroom on a conference aimed at developers and 
advanced users, so please only submit talks on a subject you actually 
worked on. These are the main reasons for talks not getting accepted; we 
want the actual developer who can go deep into the weeds with the 
audience.

If you are unsure on whether you can come or not, or perhaps you are 
unsure about corporate sponsorship of your travels (this is FOSDEM, why 
are you not there anyway?), wait with submitting your talk until you are 
certain that you can be present.

All talks will be recorded and made available as CC-By-Sa or CC-By. The 
FOSDEM CoC will have to be agreed as well 
(https://fosdem.org/2027/practical/conduct/)

If there are any issues, just email graphics-devroom-manager@fosdem.org, 
where you can reach the team of graphics devroom managers, Chema 
Casanova, Andrés Gómez, Ricardo Garcia, and myself, who will also 
schedule and review your talk submissions.

We will be keeping a keen eye on submissions and scheduling, and we hope 
to see you all at FOSDEM27!

Thanks!

Luc Verhaegen.

                 reply	other threads:[~2026-10-30 13:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=auSW5B2PoKq0ml7o@skynet.be \
    --to=libv@skynet.be \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fosdem@lists.fosdem.org \
    --cc=graphics-devroom-manager@fosdem.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=wayland-devel@lists.freedesktop.org \
    --cc=xorg-announce@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.