All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: OEDAM: OpenEmbedded Developers (Americas) Meeting
Date: Thu, 20 Feb 2014 19:03:24 -0500	[thread overview]
Message-ID: <530697CC.5050402@balister.org> (raw)

The OpenEmbedded Project is holding a developers meeting May 2-3,
2014, in Santa Clara, CA. This meeting is immediately after the Embedded
Linux Conference North America. All active OpenEmbedded and Yocto
Project developers are invited to attend.

NOTE: this is a development meeting for the project itself, not a
training session.

May 2-3, 2014
time TBD

Ettus Research/National Instruments
4600 Patrick Henry Drive
Santa Clara, CA 95054 USA

Lunch will be provided on both days.

For more information and to add yourself to the list of attendees, see
the wiki page at
http://openembedded.org/wiki/OEDAM

Here are a couple of photos from 2009:

http://www.flickr.com/photos/32615155@N00/sets/72157622653686647/

I'd like to thank Jefro for help with this announcement. Any errors are
mine though.

Philip, OpenEmbedded eV Chair.


             reply	other threads:[~2014-02-21  0:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21  0:03 Philip Balister [this message]
2014-05-07 23:18 ` OEDAM: OpenEmbedded Developers (Americas) Meeting Denys Dmytriyenko
2014-05-12 23:19   ` Jeff Osier-Mixon
2014-05-12 23:19     ` [OE-core] " Jeff Osier-Mixon
2014-05-13 15:05     ` Mark Hatle
2014-05-20  0:57     ` Stephen Arnold
2014-05-20  0:57       ` [OE-core] " Stephen Arnold
2014-06-13 22:37       ` Jeff Osier-Mixon
2014-06-13 22:37         ` [OE-core] " 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=530697CC.5050402@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@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.