Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developers Meeting @ FOSDEM 2019
Date: Thu, 1 Nov 2018 14:31:13 +0100	[thread overview]
Message-ID: <20181101143113.201a6704@windsurf> (raw)

Hello,

The Buildroot Developers Meeting @ ELCE 2018 took place a bit less
than two weeks, and therefore it's already time to organize the next
Buildroot Developers Meeting, which traditionally takes place around
the FOSDEM conference.

Usually, the meeting takes place during two days *after* FOSDEM, i.e on
Monday and Tuesday. But before doing the exact same thing, I wanted to
start a poll and see:

 * who is interested ;

 * whether we should do the meeting before/after FOSDEM ;

 * whether we should keep the 2-day format or extend to a 3-day format.

If you think you will be attending this Buildroot Developers meeting,
it would be useful if you could fill in the poll below:

  https://framadate.org/3Ve43stIV6Wvebum

Notes:

 - If you are a regular Buildroot contributor, but unable to attend due
   to lack of travel funding, we may be able to cover travel costs for
   some attendees. Please contact me if you are in such a situation.

 - The FOSDEM this year will not have the usual Embedded and IoT
   Devrooms. Perhaps this will affect the usefulness/interest of the
   FOSDEM conference for some embedded developers.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

             reply	other threads:[~2018-11-01 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 13:31 Thomas Petazzoni [this message]
2018-11-14  9:49 ` [Buildroot] Buildroot Developers Meeting @ FOSDEM 2019 Thomas Petazzoni
2018-11-14 12:07   ` Romain Naour
2018-11-26 17:31 ` Yann E. MORIN

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=20181101143113.201a6704@windsurf \
    --to=thomas.petazzoni@bootlin.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