All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jolley, Stephen K" <stephen.k.jolley@intel.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Reminder: Yocto Project Technical Team Meeting - Tuesday, June 6, 2017 8:00 AM US Pacific Time
Date: Mon, 5 Jun 2017 17:43:09 +0000	[thread overview]
Message-ID: <9ADD3FDE8B189B4AA2F8A3C711F8155E8EE1E15E@fmsmsx111.amr.corp.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]

Tuesday, June 6, 2017 8:00 AM US Pacific Time



Agenda:



* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features

* Opens - 10 min

* Team Sharing - 10 min



We encourage people attending the meeting to logon the Yocto Project IRC channel during the meeting (optional):



Yocto IRC: http://webchat.freenode.net/?channels=#yocto

IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html


Conference Details:
Company:           WIND RIVER SYS

- dial into: 1-800-262-0778/404-397-1527

- enter the bridge number: 88748961#


For International numbers see: https://www.yoctoproject.org/tools-resources/community/monthly-technical-call


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:        (503) 712-0534
*    Cell:                              (208) 244-4460
* Email:                            stephen.k.jolley@intel.com<mailto:stephen.k.jolley@intel.com>

[-- Attachment #2: Type: text/html, Size: 9144 bytes --]

             reply	other threads:[~2017-06-05 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 17:43 Jolley, Stephen K [this message]
2017-07-10 16:16 Reminder: Yocto Project Technical Team Meeting - Tuesday, June 6, 2017 8:00 AM US Pacific Time Jolley, Stephen K

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=9ADD3FDE8B189B4AA2F8A3C711F8155E8EE1E15E@fmsmsx111.amr.corp.intel.com \
    --to=stephen.k.jolley@intel.com \
    --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.