From: Daniel Borkmann <daniel@iogearbox.net>
To: netdev@vger.kernel.org
Cc: bpf@vger.kernel.org, xdp-newbies@vger.kernel.org,
brauner@kernel.org, rppt@kernel.org, stgraber@ubuntu.com
Subject: FOSDEM 2024: Kernel Devroom CfP
Date: Fri, 1 Dec 2023 10:28:02 +0100 [thread overview]
Message-ID: <3c3f4b40-0fdc-86ae-c88e-29c1a39a6759@iogearbox.net> (raw)
In-Reply-To: <20231130200641.GL636165@kernel.org>
Hi all,
We are pleased to announce the Call for Participation (CfP) for the FOSDEM
2024 Kernel Devroom.
FOSDEM 2024 will be over the weekend of the 3rd and 4th 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 an all day, exact day and time will be
clarified in the near future..
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-2024/cfp
Please select the "Kernel" as the __track__ and ensure you include the
following information when submitting a proposal:
| Section | Field | Notes |
| ------- | ------------ | ---------------------------------------------------------------------------------- |
| Person | Name(s) | Your first, last and public names. |
| Person | Abstract | A short bio. |
| Person | Photo | Please provide a photo. |
| Event | Event Title | *This is the title of your talk* - please be descriptive to encourage attendance. |
| Event | Abstract | Short abstract of one or two paragraphs. |
| Event | Duration | Please indicate the length of your talk; 10 min, 20 min, 30, or 40 min |
__The CfP deadline is Saturday, 10 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
- System Boot
- Security
- Virtualization
- Rust in the Linux Kernel
## 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/2024/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/2024-02-04_fosdem-kernel-devroom/
Thanks!
Christian Brauner
Daniel Borkmann
Mike Rapoport
Stéphane Graber
parent reply other threads:[~2023-12-01 9:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231130200641.GL636165@kernel.org>]
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=3c3f4b40-0fdc-86ae-c88e-29c1a39a6759@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=stgraber@ubuntu.com \
--cc=xdp-newbies@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).