Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Buildroot Developers Meeting: September 17-18, in Dublin
Date: Fri, 3 Jun 2022 11:58:33 +0200	[thread overview]
Message-ID: <20220603115833.560e283f@windsurf> (raw)

Hello,

We are very happy to say that we will be organizing the next Buildroot
Developers Meeting on September 17-18 in Dublin, Ireland.

These dates have been chosen because they are just after the Embedded
Linux Conference Europe (September 13-16), which hopefully will allow
interested participants to combine the trip to ELC-E together with the
Buildroot Developers Meeting.

Participation to this Buildroot Developers Meeting is free, and open to
all Buildroot contributors. It is really a nice way to meet each other,
make progress on Buildroot topics, and have side discussions.

A Wiki page has been set up at:

  https://elinux.org/Buildroot:DeveloperDaysELCE2022

If you intend to participate, please indicate your name on this page,
so that we know how many people will participate and plan the logistics
accordingly.

The exact location has not been defined yet, but we will work on
finding a place that is located reasonably close to the Dublin city
center and/or the ELC-E conference location.

I'm looking forward to meeting Buildroot contributors during this
meeting!

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:[~2022-06-03  9: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=20220603115833.560e283f@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