From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux Embedded <linux-embedded@vger.kernel.org>
Subject: CFP: Embedded, mobile and automotive devroom FOSDEM 2016
Date: Mon, 23 Nov 2015 08:54:20 +0100 [thread overview]
Message-ID: <CAMuHMdUOfcWDCMeNLkpm4EKFbytUs7b8kQShs_qQpFr6YFcoZA@mail.gmail.com> (raw)
Call For Participation
Embedded, mobile and automotive devroom FOSDEM 2016
Devroom date: Saturday January 30st and Sunday 31st 2016 in Brussels,
Belgium
CFP deadline: Monday, December 7th 2015
Final speaker confirmation on Friday, December 18th 2015
CFP Introduction
---------------------------
Embedded software is transforming the world, and FOSS embedded software
is leading the way. From automotive to the Internet of Things,
launching rockets, messing with your phone or automating your toaster,
small devices, embedded systems, and automatons are everywhere
Join in and tell the world about your project!
NB: This year FOSDEM plans to record all presentations, no exceptions.
Please only propose a talk that you're really able and willing to share.
Topics Sought
------------------------
The embedded devroom seeks topics related to automotive, mobile,
autonomous, and generally small systems. Related areas are of course of
interest as
well and our definition of "embedded" is elastic.
CFP Schedule And Submission Details
-----------------------------------------------------------
Please submit proposals no later than the 7th of December.
Please use the following URL to submit your talk to FOSDEM 2016:
https://penta.fosdem.org/submission/FOSDEM16
and follow the following rules:
* If you do not have an account yet create one, if you have submitted
a talk in one of the previous years re-use your old account.
* Select as the Track "embedded devroom".
* Select as the Event Type "Lecture"
* Include a title. (Note that "Subtitle" entry doesn't appear on
all conference documents, so make sure "Title" can stand on its
own without "Subtitle" present.)
* Include an Abstract of about 500 characters and a full description
of any length you wish, but in both fields, please be concise, but
clear and descriptive.
* Indicate whether you seek a 25, or 50 minute slot.
* Use the "Links" sub-area to your past work in the field you'd like
to share.
* Also in the notes field, confirmation your availability to speak on
Saturday 30 January or 31 February 2016 in Brussels.
* Last but not least, make sure you have up to date contact info.
Feel free to send an email to the embedded mailing list should you have
any questions with the conference system.
Subscribe here: https://lists.fosdem.org/listinfo/embedded-devroom
About the devroom organizers
--------------------------------------------------
The co-organizers of the FOSDEM 2016 Embedded devroom are
(in alphabetical order by surname):
- Peter De Schrijver, Kernel engineer at Nvidia
- Philippe De Swert, HW adaptation engineer at Jolla
- Jeremiah C. Foster, GENIVI Community Manager
- Thomas Petazzoni, CTO Free Electrons
- Geert Uytterhoeven, Glider bvba
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
reply other threads:[~2015-11-23 7:54 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=CAMuHMdUOfcWDCMeNLkpm4EKFbytUs7b8kQShs_qQpFr6YFcoZA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-embedded@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).