From: Jeff Osier-Mixon <jefro@jefro.net>
To: "openembedded-members@lists.openembedded.org"
<openembedded-members@lists.openembedded.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: OE general meeting before OEDEM next month.
Date: Fri, 22 Sep 2017 18:31:23 -0700 [thread overview]
Message-ID: <CA+YB3rYD8pggjS0dJbHuJvaA4jo7hcdDsavSNKuJhn5x0Y2MuQ@mail.gmail.com> (raw)
In-Reply-To: <01e52917-81d7-74c0-c899-b242e80d363c@gmail.com>
Ruslan asked - is it free to attend?
Yes, it is free - the space, including network access, coffee & lunch etc.
is donated by the Yocto project. All you need to do is make sure your name
is on the OEDEM list on the wiki here:
https://www.openembedded.org/wiki/OEDEM_2017
and bring your wit & charm as well as your ideas. Note that we may or may
not have a projector this year, so please also bring a laptop.
This is a community effort and one way to help is to help take notes during
the day. For the past few events, we have kept notes live in a Google doc
so many people could edit simultaneously. We will likely do that again this
year.
I am responsible for organizing the room and amenities. At this point we
have about 25% more people than we have had in the past, so if you add your
name please let me know personally at jefro@jefro.net and I will make sure
we have adequate space for you.
thanks
next prev parent reply other threads:[~2017-09-23 1:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 15:34 OE general meeting before OEDEM next month Sean Hudson
2017-09-19 16:54 ` Trevor Woerner
2017-09-19 19:13 ` Khem Raj
2017-09-20 18:24 ` Jeff Osier-Mixon
2017-09-20 20:08 ` Khem Raj
2017-09-21 0:57 ` akuster808
2017-09-22 20:50 ` Jeff Osier-Mixon
2017-09-23 0:26 ` akuster808
2017-09-23 1:31 ` Jeff Osier-Mixon [this message]
2017-09-25 4:45 ` Denys Dmytriyenko
2017-09-25 13:43 ` Sean Hudson
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+YB3rYD8pggjS0dJbHuJvaA4jo7hcdDsavSNKuJhn5x0Y2MuQ@mail.gmail.com \
--to=jefro@jefro.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-members@lists.openembedded.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.