Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] Buildroot Meeting after Open Source Summit Europe, Aug 28/29, Amsterdam
Date: Fri, 16 May 2025 12:07:48 +0200	[thread overview]
Message-ID: <20250516120748.478a63a3@windsurf> (raw)

Hello!

The next Open Source Summit Europe will take place on Aug 25-27 in
Amsterdam, and will as usual include the "Embedded Linux Conference
Europe". We definitely recommend anyone working on Embedded Linux to
consider attending this event!

Not only because ELC has great talks, but also because we are
organizing right after ELC a Buildroot Developers Meeting, on August
28-29.

If you're using Buildroot, working on Buildroot, contributing to
Buildroot, or interested in contributing, you should also consider
joining our meeting.

See:

  https://elinux.org/Buildroot:DeveloperDaysELCE2025

for some initial details.

Note that we are looking for a location in Amsterdam to host the
meeting. If you know a company, hackerspace, organization that would
have a space for those 2 days for ~10 developers that would be amazing!

Thanks!

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-05-16 10:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 10:07 Thomas Petazzoni via buildroot [this message]
2025-07-09  7:25 ` [Buildroot] Buildroot Meeting after Open Source Summit Europe, Aug 28/29, Amsterdam Titouan Christophe via buildroot

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=20250516120748.478a63a3@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