🚀 FOSDEM 2027: Showcase Your Open-Source Project to the World
FOSDEM 2027 is happening on January 30–31, 2027, at ULB Brussels—and
your project could be part of it! As always, we’re offering free stands to
open-source projects to connect with the community.
What you can do at your stand
✔️ Present your project and engage with attendees
✔️ Demo your project live
✔️ Sell merchandise or collect donations
✔️ Hand out goodies and grow your contributor base
What we provide
✅ 1 table (180x80 cm) with chairs and a power socket
✅ Fast wireless internet for demos and presentations
✅ A spot for one or both days (choose what suits you best)
✅ Shared stands encouraged! (Joint submissions will be prioritized)
Proposals for developer rooms for FOSDEM 2027 can now be submitted!
Developer rooms are assigned to self-organizing groups to work together on open
source and free software projects, to discuss topics relevant to a broader
subset of the community, etc. Most content should take the form of
presentations. Proposals involving collaboration across project or domain
boundaries are strongly encouraged.
We want to continue to focus on promoting collaboration and community between
different projects in niches which don’t normally have their own spaces, rather
than large projects with significant corporate backing.
For inspiration, some example rooms along these lines from recent years: Modern
Email, Package Management, and Music Production.
As usual, we unfortunately have a very hard limit on the number of devrooms we
accept due to the realities of the physical space available to us. Every year
we must make difficult decisions about which great proposals must be rejected
(in the past we could have filled the entire conference with every devroom
about a different programming language!). If you submitted a proposal for a
devroom in the last few years and got rejected, don’t be disheartened and
submit anyway!
Devroom coordinators must enter a complete schedule into our conference system
by 7th December. It is particularly important to be available and to
respond promptly to emails about the schedule for about a week either side of
this date. We also require all proposals to be submitted directly by the
speakers into our system.
Saturday devroom schedules should contain between 7.5 and 8.5 hours of
content, beginning at 10.30 and running until between 18.00 and
19.00.
Sunday schedules should contain between 7 and 8 hours of content and
start between 09.00 and 10.00 and run through until 17.00.
No lunch breaks should be scheduled for devrooms.
If you don’t think you can fill a full day, please try to join up with another
project and submit a joint devroom application or indicate on the
submission form that you are requesting only
half-a-day and would like FOSDEM to try to pair you up with another similar
request for half-a-day.
Because our room capacity is limited, we will record and stream all devrooms
live. The recordings will be published under the same licence as all FOSDEM
content (CC-BY).
Devroom submissions will only be accepted with at least two named managers who
are responsible for the room.
If you have questions or need help crafting a good submission, contact us at
program@fosdem.org.
The deadline for submissions is 4th October.
Key dates:
04 October: deadline for developer room proposals
20 October: accepted developer rooms announced
27 October (or earlier): developer rooms issue Calls for Participation
07 December (or earlier): developer rooms publish complete schedules
Note that the submission form should only be used
by organisers of devrooms. If you want to submit a talk to a main track or
devroom, keep an eye on the website until their Call
for participation opens around October 27.
This post is a draft, so it is excluded from hugo build and from the RSS feed.
Preview it with hugo server --config hugo.landing.yaml -D. It exists to
exercise every element a news post can contain.
Images
Images live next to index.md in the post directory. Reference them by
filename. The render hook resolves them as page resources, generates a srcset
capped to the article width, and emits width/height to stop the layout
shifting.
Adding a quoted title turns the image into a figure with this caption.
Without the quoted title it renders as a bare image:
The feed picks a featured image for enclosure, media:content and
media:thumbnail, and the page reuses it for og:image. It defaults to the
first image in the directory. Set image: in front matter to choose another.
Text
Body text renders in DejaVu Sans. Bold and italic both work, as does
inline code, a link, and strikethrough.
Third level heading
Fourth level heading
Lists keep the body font:
First item
Second item, long enough to wrap onto a second line so the hanging indent is
visible against the paragraph above it
Third item
Nested item
Numbered item
Another numbered item
A blockquote sits flush with the text column rather than taking the browser
default side margins.
Callouts
An alert renders as a boxed callout. The type sets the class
(note, tip, important, warning, caution) and the text after it sets
the heading; without one the type is used as the heading. Put a TL;DR at the top
of a long post:
TL;DR
Callouts take any Markdown inside them, including bold and
links.
The heading after [!NOTE] is optional.
Warning
Without an explicit heading the alert type becomes the heading.
Calendars
Dates listed under events: in front matter, together with a calendar output format,
produce the .ics file and the widget at the end of this post. calendar-dates is the
generic one; a post wanting its own filename gets its own format.
Code blocks scroll horizontally instead of stretching the article:
outputs:home:- HTML- RSSsection:- HTML
Room
Capacity
Building
Janson
1400
K
K.1.105
400
K
UB2.252A
100
U
That horizontal rule and this closing paragraph are the last of it.
