From: Philip Balister <philip@balister.org>
To: akuster <akuster@mvista.com>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>,
"openembedded-members@lists.openembedded.org"
<openembedded-members@lists.openembedded.org>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [yocto] OpenEmbedded Developer America's Meeting
Date: Fri, 13 Mar 2015 12:55:43 -0400 [thread overview]
Message-ID: <5503168F.6080408@balister.org> (raw)
In-Reply-To: <55030897.6010403@mvista.com>
You can add yourself here (or drop me an email if you have trouble
logging in)
http://www.openembedded.org/wiki/OEDAM_2015
We plan to have a Hangout on the Air so people can follow along remotely.
Philip
On 03/13/2015 11:56 AM, akuster wrote:
> Hello Folks,
>
> OEDAM is nearing. If you have not signed up, please do so. It will help
> me with head count for badges.
>
> We also need more subject matter the Agenda. If you have any topics or
> ideas, please submit them.
>
> kind regards,
> Armin
>
> On 02/10/2015 12:27 PM, Philip Balister wrote:
>> We've scheduled a meeting in San Jose at a Monte Vista facility for
>> March 27-28. This is after ELC (also in San Jose). There is a Yocto
>> Project developer Day the day after ELC.
>>
>> I've made a page on the wiki to start collecting information:
>>
>> http://openembedded.org/wiki/OEDAM_2015
>>
>> To get an idea of what we cover, see the page from the prior year:
>>
>> http://openembedded.org/wiki/OEDAM_2014
>>
>> I apologize for the late notice. There were issues that led to a delay
>> with dates due to the YP Dev day.
>>
>> Philip
>>
>
>
next prev parent reply other threads:[~2015-03-13 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 20:27 OpenEmbedded Developer America's Meeting Philip Balister
2015-02-10 20:47 ` Denys Dmytriyenko
[not found] ` <55030897.6010403@mvista.com>
2015-03-13 16:55 ` Philip Balister [this message]
2015-03-13 17:06 ` [yocto] " Mark Hatle
2015-03-25 18:28 ` Mark Hatle
2015-03-25 20:54 ` Akuster808
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=5503168F.6080408@balister.org \
--to=philip@balister.org \
--cc=akuster@mvista.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox