From: Philip Balister <philip@balister.org>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>,
Yocto Project <yocto@yoctoproject.org>,
"openembedded-members@lists.openembedded.org"
<openembedded-members@lists.openembedded.org>
Subject: OEDAM, April 8 in San Diego after ELC
Date: Tue, 8 Mar 2016 11:10:39 -0500 [thread overview]
Message-ID: <56DEF97F.9070306@balister.org> (raw)
On the Friday after ELC in San Diego (Yocto Project Dev Day is
Thursday), we will have a developer meeting near the conference venue
(need to double check with Jefro about exact location).
http://openembedded.org/wiki/OEDAM_2016
At these meetings we try to follow an agenda we develop before hand on
the wiki page. I've created a rough agenda by posting notes from the
meeting in Dublin. Everyone, please go over the notes and add remarks
for completed items.
You can also bring up issues at the meeting. We only have one day
scheduled for the meeting, so a little pre-planning helps keep us on time.
Everyone involved in the project is welcome to attend, no how
knowledgeable in the overall OpenEmbedded project We like to hear from
people from many different use cases.
Thanks,
Philip
next reply other threads:[~2016-03-08 16:10 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 16:10 Philip Balister [this message]
2016-03-23 16:36 ` OEDAM, April 8 in San Diego after ELC akuster808
2016-03-23 16:36 ` [oe] " akuster808
2016-03-23 21:08 ` [OE-core] " Trevor Woerner
2016-03-23 21:08 ` [OE-core] [oe] " Trevor Woerner
2016-03-23 21:08 ` Trevor Woerner
2016-03-23 21:11 ` [OE-core] " Fred Ollinger
2016-03-23 21:39 ` [yocto] [OE-core] " Philip Balister
2016-03-23 21:39 ` [OE-core] [oe] " Philip Balister
2016-03-23 21:39 ` [yocto] " Philip Balister
2016-03-23 22:03 ` [OE-core] [yocto] " Jeff Osier-Mixon
2016-03-23 22:03 ` [OE-core] [oe] " Jeff Osier-Mixon
2016-03-23 22:03 ` [yocto] " Jeff Osier-Mixon
2016-03-23 22:11 ` [OE-core] [yocto] " akuster808
2016-03-23 22:11 ` [OE-core] [oe] " akuster808
2016-03-23 22:11 ` [yocto] " akuster808
2016-04-11 22:35 ` [yocto] [OE-core] " Rudolf J Streif
2016-04-11 22:35 ` [oe] " Rudolf J Streif
2016-04-11 22:35 ` [oe] [yocto] " Rudolf J Streif
2016-04-12 1:35 ` [yocto] [OE-core] " Denys Dmytriyenko
2016-04-12 1:35 ` [oe] " Denys Dmytriyenko
2016-04-12 1:35 ` [oe] [yocto] " Denys Dmytriyenko
2016-04-12 1:43 ` [yocto] [OE-core] " Philip Balister
2016-04-12 1:43 ` [oe] " Philip Balister
2016-04-12 1:43 ` [oe] [yocto] " Philip Balister
2016-04-12 1:48 ` [OE-core] " Tom King
2016-04-12 1:48 ` [OE-core] [oe] " Tom King
2016-04-12 1:48 ` [oe] [yocto] " Tom King
2016-04-12 2:32 ` [OE-core] " Ankur Tyagi
2016-04-12 2:32 ` [oe] [OE-core] " Ankur Tyagi
2016-04-12 3:25 ` [OE-core] [yocto] " Ankur Tyagi
2016-04-12 3:25 ` [oe] [OE-core] " Ankur Tyagi
2016-04-12 3:25 ` [oe] [yocto] " Ankur Tyagi
2016-04-12 15:24 ` [OE-core] " Jeff Osier-Mixon
2016-04-12 15:24 ` [OE-core] [oe] " Jeff Osier-Mixon
2016-04-12 15:24 ` [oe] [yocto] " Jeff Osier-Mixon
2016-03-23 22:16 ` [yocto] [OE-core] " Philip Balister
2016-03-23 22:16 ` [OE-core] [oe] " Philip Balister
2016-03-23 22:16 ` [yocto] " Philip Balister
2016-03-24 18:10 ` [yocto] [OE-core] " Philip Balister
2016-03-24 18:10 ` [OE-core] [oe] " Philip Balister
2016-03-24 18:10 ` [yocto] " Philip Balister
2016-03-24 18:36 ` [yocto] [OE-core] " Rudolf J Streif
2016-03-24 18:36 ` [oe] " Rudolf J Streif
2016-03-24 18:36 ` [oe] [yocto] " Rudolf J Streif
2016-03-25 20:32 ` [yocto] [OE-core] " Ryan Elkholy, PhD, PE
2016-03-25 20:37 ` Jeff Osier-Mixon
2016-03-25 20:37 ` [oe] " Jeff Osier-Mixon
2016-03-25 20:37 ` [oe] [yocto] " Jeff Osier-Mixon
2016-04-06 3:39 ` [yocto] [OE-core] " Jeff Osier-Mixon
2016-04-06 3:39 ` [oe] " Jeff Osier-Mixon
2016-04-06 3:39 ` [yocto] [oe] " Jeff Osier-Mixon
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=56DEF97F.9070306@balister.org \
--to=philip@balister.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-members@lists.openembedded.org \
--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.