dri-devel.lists.freedesktop.org archive mirror
 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
Subject: Graphics DevRoom 26: Cfp.
Date: Wed, 5 Nov 2025 11:52:18 +0100	[thread overview]
Message-ID: <aQssYjyLgxAP67Cl@skynet.be> (raw)

20 years after the first X.org DevRoom at FOSDEM 2006, there will be the 
16th Graphics DevRoom at FOSDEM on Sunday the 1st of February 2026.

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.
* 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 7th of december, but do not count on this 
date, once the schedule has filled with enough solid talks, we will 
accept no more. Also, the best slots (afternoon) will be handed out on a 
first-come-first-serve basis.

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

Since this an open source community event, please refrain from turning 
in a talk that is a pure corporate or 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.

If you are unsure on whether you can come or not, 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.

Please put some time and effort in your talk proposal, especially in the 
title and at least abstract, and your own background. While there is no 
more printed schedule, your description is what will get people to watch 
your talk, and will remain online forever next to the recording of your 
talk.

We have a full day at our disposal, which runs from from 9:00 til 17:00, 
so we can fit anywhere between 8 and 16 talks. With 5 minutes for setup 
time, and 5 minutes of Q&A, full hour talks are actually 50 minutes, and 
half hour talks are 20 minutes. Depending on the amount of proposals, we 
might need to switch to 20 minute talks for everyone.

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/2026/practical/conduct/).

Submission tips:

When submitting at https://fosdem.org/submit, you can ignore the "You 
can enter proposals until 2025-11-16 22:00 (Europe/Brussels), 2 weeks 
from now." statement, as that is for Main track talks only, and not 
relevant for DevRooms.

Please put some time and effort in your talk proposal, especially in the 
title and at least abstract, and your own background. While there is no 
more printed schedule, your description is what will get people to watch 
your talk, and will remain online forever next to the recording of your 
talk.

On the first page, for track, select "Graphics". Please write your 
preferred slot length (20 or 50) in the submission notes. On page 2 you 
also need to provide a code license, this is a free-form field, so write 
what is appropriate.

If there are any issues, just email graphics-devroom-manager@fosdem.org, 
where you can reach the team of graphics devroom managers, Arek Hiler, 
Timur Kristóf and myself, who will also schedule and review your talk 
submissions.

We will be keeping a keen eye on submissions and scheduling, and hope to 
see you all at FOSDEM.

Thanks!

Luc Verhaegen.


                 reply	other threads:[~2025-11-05 10:52 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=aQssYjyLgxAP67Cl@skynet.be \
    --to=libv@skynet.be \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=graphics-devroom-manager@fosdem.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 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).