From: Philip Balister <philip@balister.org>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core <openembedded-core@lists.openembedded.org>,
Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [yocto] FOSDEM 2014 Embedded dev room CFP
Date: Wed, 20 Nov 2013 07:35:05 -0500 [thread overview]
Message-ID: <528CAC79.3060709@balister.org> (raw)
In-Reply-To: <CANyK_8cMf+SodPNjtuavseZHMTd13T33c0sLJpNnhe45ixdTXg@mail.gmail.com>
On 11/20/2013 06:49 AM, Paul Barker wrote:
> On 7 November 2013 10:11, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
>> Hi all,
>>
>> I didn't notice if it was already announced here, but the CFP for the FOSDEM
>> Embedded dev room in 2014 is open:
>>
>> https://lists.fosdem.org/pipermail/fosdem/2013-October/001870.html
>>
>> It would be great to have some folks give OpenEmbedded/Yocto Project-related
>> presentation(s) this year - we usually manage at least one for FOSDEM. It
>> could be about a new feature you've worked on, a success story, a proposal for
>> a new direction, a related project etc.
>>
>
> I'm planning to attend FOSDEM 2014 and could look at giving a talk on
> how I've used OpenEmbedded in developing an underwater noise
> monitoring platform and how I've gone from there to contributing to OE
> and maintaining opkg. I'll throw together an abstract and see if it
> gets accepted.
>
> It should be good to meet a couple of other OpenEmbedded developers as well!
This is an excellent abstract. Build system talks tend to be pretty
dull, and only interesting to other build system people :) Talks about
cool things a build system lets you do are way more interesting.
Please submit an abstract.
Philip
>
> Thanks,
>
next prev parent reply other threads:[~2013-11-20 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 10:11 FOSDEM 2014 Embedded dev room CFP Paul Eggleton
2013-11-20 11:49 ` [yocto] " Paul Barker
2013-11-20 12:35 ` Philip Balister [this message]
2013-11-20 21:39 ` Ulf Samuelsson
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=528CAC79.3060709@balister.org \
--to=philip@balister.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=paul@paulbarker.me.uk \
--cc=yocto@yoctoproject.org \
/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