From: Jeff Osier-Mixon <jefro@jefro.net>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Register Today - Yocto Project Developer Day Europe 2016
Date: Tue, 6 Sep 2016 18:52:02 -0700 [thread overview]
Message-ID: <CA+YB3rZUZ2GfAF4CZ8X3PviiiUPW=B+jQkWTJwqS8NRRf8Tdzg@mail.gmail.com> (raw)
Join us to learn more about Yocto Project’s open source, high-quality
infrastructure and tools. Build your own Linux distribution and choose
a development board to take home! Available options: MinnowBoard
Turbot, BeagleBone Black, or DragonBoard 410c.
Our trainers have prepared a preliminary agenda. Check it out below,
and if you have any topics that you want to see covered, reach out to
our community manager, Jefro.
Introductory Track
Introduction to the Yocto Project
Key Concepts
Build System Workflow
Examining Recipes
Standard Recipe Build Steps
Working with Layers
Build and Boot Your Custom Image
Working with Applications
Advanced Track
New workflows and features
Deep dive on WIC
Deep dive and class exercises on CROPS
Deep dive and class exercises on devtool and Extensible SDKs
Deep dive and class exercises on Toaster and Layer Index
Q and A, and Giveaways
More to come!
Date: Monday, October 10, 2016
Time: 9:00 am - 5:00 pm
Location: The Maritim Hotel in Berlin
Stauffenbergstraße 26, 10785 Berlin, Germany
EVENT DESCRIPTION:
https://www.yoctoproject.org/yocto-project-developer-day-europe-2016
From September 4 through the event, the registration fee will be US$249.
If you are already planning to attend ELCE, you can add Yocto Dev Day
to the Agenda section of your Embedded Linux Conference Europe
registration: https://www.regonline.com/register/login.aspx?eventID=1767449&MethodId=0&EventsessionId=&Email_Address=&membershipID=.
For those not planning to attend ELC Europe, individual registrations
can be purchased here: https://www.regonline.com/YPDevDayEU2016.
Thanks,
The Yocto Project Developer Day Team
reply other threads:[~2016-09-07 1: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='CA+YB3rZUZ2GfAF4CZ8X3PviiiUPW=B+jQkWTJwqS8NRRf8Tdzg@mail.gmail.com' \
--to=jefro@jefro.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.