All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Jeff Osier-Mixon <jefro@jefro.net>
Cc: "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 17:26:51 -0700	[thread overview]
Message-ID: <01e52917-81d7-74c0-c899-b242e80d363c@gmail.com> (raw)
In-Reply-To: <CA+YB3rZd0P6eVimXD5jN0UZMB=dH2h2mdScmeB8PtjSWLZNMfg@mail.gmail.com>



On 09/22/2017 01:50 PM, Jeff Osier-Mixon wrote:
> Up to 36 now. I am in touch with the venue. The table was originally
> set for 30 and could comfortably accommodate 34 in boardroom style.
> Given natural attrition of 10% I think we are okay in this regard,
> with latecomers seated around the edges. If we grow much larger I will
> either have to pay for a larger room or ask them to seat the room
> theater-style, where it can probably hold up to 50. I'll see how we do
> later in the cycle before deciding.

thanks Jefro

- armin
>
> On Wed, Sep 20, 2017 at 5:57 PM, akuster808 <akuster808@gmail.com
> <mailto:akuster808@gmail.com>> wrote:
>
>     Jefro,
>
>     We have 33 folks listed. Do we have room?
>
>     regards,
>
>     Armin
>
>
>     On 09/20/2017 11:24 AM, Jeff Osier-Mixon wrote:
>     > Zoom might be easier, as people can dial in or connect online.
>     We'll make
>     > it work.
>     >
>     > On Tue, Sep 19, 2017 at 12:13 PM, Khem Raj <raj.khem@gmail.com
>     <mailto:raj.khem@gmail.com>> wrote:
>     >
>     >> On Tue, Sep 19, 2017 at 9:54 AM, Trevor Woerner
>     <twoerner@gmail.com <mailto:twoerner@gmail.com>>
>     >> wrote:
>     >>> On Tue, Sep 19, 2017 at 11:34 AM, Sean Hudson
>     <sean_hudson@mentor.com <mailto:sean_hudson@mentor.com>>
>     >> wrote:
>     >>>>   Meeting information, including dial-in numbers, is on the
>     wiki. [2]
>     >>> In addition to the above, we could also make use of the
>     little-used
>     >>> #oe-meeting channel on freenode (?)
>     >> +1
>     >>
>     >> I can dial in. Or someone can setup a zoom meeting
>     >> --
>     >> _______________________________________________
>     >> Openembedded-devel mailing list
>     >> Openembedded-devel@lists.openembedded.org
>     <mailto:Openembedded-devel@lists.openembedded.org>
>     >>
>     http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>     <http://lists.openembedded.org/mailman/listinfo/openembedded-devel>
>     >>
>     >
>     >
>
>
>
>
> -- 
> Jeff Osier-Mixon - Open Source Community Manager, Intel Corporation



  reply	other threads:[~2017-09-23  0:26 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 [this message]
2017-09-23  1:31             ` Jeff Osier-Mixon
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=01e52917-81d7-74c0-c899-b242e80d363c@gmail.com \
    --to=akuster808@gmail.com \
    --cc=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.