From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Buildroot Developers Meeting after FOSDEM 2025
Date: Wed, 2 Oct 2024 21:11:37 +0200 [thread overview]
Message-ID: <20241002211137.25c4c147@windsurf> (raw)
Hello,
The FOSDEM conference will take place on Feb 1-2, 2025 in Brussels.
Right after the conference, we are organizing on Feb 3-5 a 3-day
Buildroot Developers Meeting. We invite Buildroot developers and
contributors to join this meeting to work together on Buildroot,
discuss current topics, review and merge pending patches, and tackle
specific issues. The event is free, and it is not mandatory to
participate to all 3 days.
The event is kindly hosted by Smile, in a location conveniently
accessible by the Brussels metro.
If you're interested, you can register at:
https://elinux.org/Buildroot:DeveloperDaysFOSDEM2025
If you don't have an account on eLinux.org and don't want to create
one, just let us know that you intend to participate.
We really encourage those of you who are using Buildroot and attending
FOSDEM to at least consider attending the first day of the meeting, to
meet other Buildroot users and developers.
Do not hesitate to get back to me if you have any question or doubt
about the meeting, its organization, or contents.
I'm looking forward to meeting the Buildroot community in Brussels next
February!
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:[~2024-10-02 19:11 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=20241002211137.25c4c147@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.