Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developers meeting at FOSDEM, 6-7 Feb 2017
Date: Tue, 15 Nov 2016 22:19:08 +0100	[thread overview]
Message-ID: <20161115221908.3bd8a45e@free-electrons.com> (raw)

Hello,

The previous Buildroot Developers Meeting that took place last month in
Berlin was very productive, and it's already time to think about our
next meeting.

As usual, it will take place right after the FOSDEM conference, in
Brussels, Belgium. Since FOSDEM takes place on February 4-5 this year,
our meeting will take place on February 6-7 (Monday/Tuesday).

Google has once again agreed to sponsor our meeting, by hosting the
event, and offering lunch and refreshments to the participants. Thanks
to Google!

Attending the meeting is free of charge, but registration is required.
This meeting is for Buildroot developers and contributors, and is
generally a mix of discussions and hacking sessions.

I would really like to encourage developers who contribute to Buildroot
to consider attending this meeting. This meeting is really useful, it's
really nice to meet each other in person, and a lot of great work gets
done in such two days of meeting. And of course, since it's next to the
FOSDEM conference, you can attend this event as well.

See http://elinux.org/Buildroot:DeveloperDaysFOSDEM2017 for all details
about this meeting.

Thanks for your participation!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

                 reply	other threads:[~2016-11-15 21:19 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=20161115221908.3bd8a45e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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