linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: linux-mm@kvack.org
Cc: "Christian Brauner" <christian@brauner.io>,
	"Stéphane Graber" <stgraber@stgraber.org>
Subject: FOSDEM 2025: Kernel Devroom CfP
Date: Sun, 27 Oct 2024 10:13:16 +0200	[thread overview]
Message-ID: <Zx32HLJAKlW-RZk6@kernel.org> (raw)

Hi all,

We are pleased to announce the Call for Participation (CfP) for the FOSDEM
2025 Kernel Devroom.

FOSDEM 2025 will be over the weekend of the 1st and 2nd of February in
Brussels, Belgium.  FOSDEM is a free and non-commercial event organised by
the community for the community.  The goal is to provide free and open
source software developers and communities a place to meet to:

- get in touch with other developers and projects;
- be informed about the latest developments in the free software world;
- be informed about the latest developments in the open source world;
- attend interesting talks and presentations on various topics by project
  leaders and committers;
- to promote the development and benefits of free software and open source
  solutions.
- Participation and attendance is totally free, though the organisers
  gratefully accept donations and sponsorship.

## Format

The Kernel Devroom will be running all day on Sunday 2nd of February.

We’re looking for talk or demo proposals in one of the following 4 sizes:

- 10 minutes (e.g., a short demo)
- 20 minutes (e.g., a project update)
- 30 minutes (e.g., introduction to a new technology or a deep dive on a
  complex feature)
- 40 minutes (e.g., a deep dive on a complex feature)

In all cases, please allow for at least 5 minutes of questions (10min
preferred for the 30min slots).  In general, shorter content will be more
likely to get approved as we want to cover a wide range of topics.

## Proposals

Proposals should be sent through the FOSDEM scheduling system at:
https://pretalx.fosdem.org/fosdem-2025/cfp

__The CfP deadline is Sunday, 1 December 2024.__

## Topics

The Kernel Devroom aims to cover a wide range of different topics so don't
be shy. The following list should just serve as an inspiration:

- Filesystems and Storage
- io_uring
- Tracing
- eBPF
- Fuzzing
- Memory management
- Rust in the Linux Kernel
- System Boot
- Security
- Virtualization

## Code of Conduct

We'd like to remind all speakers and attendees that all of the
presentations and discussions in our devroom are held under the guidelines
set in the [FOSDEM Code of
Conduct](https://fosdem.org/2025/practical/conduct/) and we expect
attendees, speakers, and volunteers to follow the CoC at all times.

If you submit a proposal and it is accepted, you will be required to
confirm that you accept the FOSDEM CoC. If you have any questions about the
CoC or wish to have one of the devroom organizers review your presentation
slides or any other content for CoC compliance, please email us and we will
do our best to assist you.

An up to date version of the CfP can always be found at
https://uapi-group.org/docs/conferences/2025-02-01_fosdem-kernel-devroom/

Thanks!
Christian Brauner
Mike Rapoport
Stéphane Graber


                 reply	other threads:[~2024-10-27  8:17 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=Zx32HLJAKlW-RZk6@kernel.org \
    --to=rppt@kernel.org \
    --cc=christian@brauner.io \
    --cc=linux-mm@kvack.org \
    --cc=stgraber@stgraber.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