From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Buildroot Developers Meeting @ FOSDEM 2026
Date: Thu, 4 Dec 2025 08:58:41 +0100 [thread overview]
Message-ID: <20251204085841.56bc9a69@windsurf> (raw)
Dear Buildroot community,
As many of you are probably aware, FOSDEM 2026 is going to take place
on Jan 31 and Feb 1, 2026 in Brussels. We obviously recommend to anyone
interested in open-source software to attend this excellent conference.
Right after FOSDEM, we are as usual organizing a "Buildroot Developers
Meeting", on Feb 2-3-4, also in Brussels. This is a 3-day gathering of
Buildroot maintainers, developers and contributors. If you're already a
Buildroot contributor and you're attending FOSDEM, we recommend that
you consider joining the Buildroot Developers Meeting.
Attending the event is free, after registration. It is not mandatory to
attend all 3 days. If you only want to attend on Monday (Feb 2) to meet
the Buildroot community, it's totally fine.
See:
https://elinux.org/Buildroot:DeveloperDaysFOSDEM2026
for more details about the event. Most of the maintainers, including
the maintainers of the LTS branch, are already planning on attending.
If you don't have an eLinux.org Wiki account to register, you can
contact me privately, and I'll add you to the list of participants.
Looking forward to meeting a number of Buildroot contributors in
Brussels!
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2025-12-04 7:58 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=20251204085841.56bc9a69@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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