From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developers Meeting: October 20-21 in Edinburgh
Date: Sat, 21 Jul 2018 23:18:00 +0200 [thread overview]
Message-ID: <20180721231800.484a65b7@windsurf> (raw)
Hello,
The next Buildroot Developers Meeting will take place on October 20-21
in Edinburgh, i.e the Saturday/Sunday before the Embedded Linux
Conference Europe 2018.
A wiki page has been started at:
https://elinux.org/Buildroot:DeveloperDaysELCE2018
and interested participants are invited to register by editing the Wiki
page. The meeting agenda can also be filled with items.
If you're not familiar with what the Buildroot Developers Meeting is
and the type of discussion we have, you can refer to the report of the
previous meeting:
https://elinux.org/Buildroot:DeveloperDaysFOSDEM2018
We are looking for companies willing to sponsor that event. Sponsorship
in the order of a few hundred EUR are sufficient for us, and would
allow to cover the following expenses:
- Meeting room
- Social dinner for the participants
- Possibly cover travel expenses for participants who are not covered
by their employer to participate to the Buildroot Developers meetitng
In exchange for the sponsoring, we offer visibility on the Buildroot
web site, in the Buildroot release e-mails, and on our Twitter/G+.
Please contact me if your company is interested in helping the
Buildroot project by sponsoring.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
reply other threads:[~2018-07-21 21:18 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=20180721231800.484a65b7@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