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] Upcoming Buildroot Developers meeting in Brussels
Date: Mon, 29 Jan 2018 23:52:51 +0100	[thread overview]
Message-ID: <20180129235251.4c3a49ee@windsurf.lan> (raw)

Hello,

As many of you probably know, a Buildroot Developers Meeting will take
place next week, on Monday/Tuesday in Brussels, right after the FOSDEM
conference. See the event page at
https://elinux.org/Buildroot:DeveloperDaysFOSDEM2018.

We have 14 participants registered, which I believe is the highest
number of participants we've ever had for a Buildroot meeting.

I'd like to thank our sponsors Google and Mind. Google is sponsoring
the meeting location, as well as lunch for the attendees. Mind is
sponsoring the social event of Monday evening.

Also, I'm taking this opportunity to remind everyone, not only the
attendees, that this meeting is the best place to discuss patches and
topics that are outstanding, and for which decisions need to be taken.
We already have a list of topics listed on the event page, but don't
hesitate to add some more topics, even if you're not attending.

It would also be good if people who have proposed topics prepare some
kind of summary to present during the meeting, in order to kick-off the
discussion on the topic: what is the issue we are trying to solve? what
are the possible solutions? what are their respective advantages and
drawbacks? This can be prepared in the form of slides or simple notes,
but I believe some preparation will help make the discussion more
productive.

If you are interested in joining the event, but haven't registered yet,
let me know, it might still be possible.

I'm looking forward to meeting all the attendees next week in Brussels!

Best regards,

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

                 reply	other threads:[~2018-01-29 22:52 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=20180129235251.4c3a49ee@windsurf.lan \
    --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