All of lore.kernel.org
 help / color / mirror / Atom feed
From: theyoctoproject@gmail.com
To: yocto@yoctoproject.org
Subject: Canceled event with note: Yocto Project Technical Team Meeting / Engineering Sync @ Tue Oct 29, 2019 8am - 9am (PDT) (yocto@yoctoproject.org)
Date: Tue, 22 Oct 2019 15:05:10 +0000	[thread overview]
Message-ID: <0000000000006868ec05958120b4@google.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2640 bytes --]

This event has been canceled with this note:
"Due to ELC-E"

Title: Yocto Project Technical Team Meeting / Engineering Sync
The Yocto Project hosts a technical call. All community members are invited  
to join on both the call and in the IRC channel, which are used  
simultaneously.We encourage people attending the meeting to logon and  
announce themselves on the Yocto Project IRC chancel during the meeting  
(optional):Yocto IRC: http://webchat.freenode.net/?channels=#yoctoWiki:  
https://www.yoctoproject.org/public-virtual-meetings/Bridge is with Zoom  
at: https://zoom.us/j/990892712Tuesdays when we aren’t having the Monthly  
Technical Call The Yocto Project hosts a engineering sync by which the  
technical team discusses the current status of engineering topics,  
including the autobuilder, documentation, builds, and releases.
When: Tue Oct 29, 2019 8am – 9am Pacific Time - Los Angeles
Where: Zoom Meeting: https://zoom.us/j/990892712
Calendar: yocto@yoctoproject.org
Who:
     * theyoctoproject@gmail.com - organizer
     * khem_raj@comcast.com
     * nick.pongratz@singlewire.com
     * bruce.ashfield@gmail.com
     * hnje@triax.com
     * lazaros.lazaridis@atos.net
     * erik.hoogeveen@outlook.com
     * rudolf.streif@gmail.com
     * manjukum@xilinx.com
     * khem_raj@cable.comcast.com
     * rob.ranslam@windriver.com
     * bikram_bhola@mentor.com
     * yocto@yoctoproject.org
     * oandreasson@luxoft.com
     * yannick.koehler@hpe.com
     * stephen.k.jolley@intel.com
     * aseilis@ciena.com
     * jdmason@kudzu.us
     * jonathan.haws@sdl.usu.edu
     * dwatkins@sierrawireless.com
     * raj.khem@gmail.com
     * raymond.tan@intel.com
     * thore.boeckelmann@inoex.de
     * rcalhoun@shotspotter.com
     * nandojve@gmail.com
     * aravindhlalgss@embedur.com
     * sjolley.yp.pm@gmail.com
     * patrick.schneider@bhtronik.de


Invitation from Google Calendar: https://www.google.com/calendar/

You are receiving this courtesy email at the account yocto@yoctoproject.org  
because you are an attendee of this event.

To stop receiving future updates for this event, decline this event.  
Alternatively you can sign up for a Google account at  
https://www.google.com/calendar/ and control your notification settings for  
your entire calendar.

Forwarding this invitation could allow any recipient to send a response to  
the organizer and be added to the guest list, or invite others regardless  
of their own invitation status, or to modify your RSVP. Learn more at  
https://support.google.com/calendar/answer/37135#forwarding

[-- Attachment #1.2: Type: text/html, Size: 23368 bytes --]

[-- Attachment #1.3: Type: text/calendar, Size: 6322 bytes --]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20191029T080000
DTEND;TZID=America/Los_Angeles:20191029T090000
DTSTAMP:20191022T150510Z
ORGANIZER;CN=theyoctoproject@gmail.com:mailto:theyoctoproject@gmail.com
UID:74pj8d1h6op62b9j74omcb9kcpgjgb9oclhj0b9jcos3io9h61ijgd1nc4_R20190827T15
 0000@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=kh
 em_raj@comcast.com;X-NUM-GUESTS=0:mailto:khem_raj@comcast.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ni
 ck.pongratz@singlewire.com;X-NUM-GUESTS=0:mailto:nick.pongratz@singlewire.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=br
 uce.ashfield@gmail.com;X-NUM-GUESTS=0:mailto:bruce.ashfield@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=hn
 je@triax.com;X-NUM-GUESTS=0:mailto:hnje@triax.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=la
 zaros.lazaridis@atos.net;X-NUM-GUESTS=0:mailto:lazaros.lazaridis@atos.net
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=er
 ik.hoogeveen@outlook.com;X-NUM-GUESTS=0:mailto:erik.hoogeveen@outlook.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ru
 dolf.streif@gmail.com;X-NUM-GUESTS=0:mailto:rudolf.streif@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ma
 njukum@xilinx.com;X-NUM-GUESTS=0:mailto:manjukum@xilinx.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=kh
 em_raj@cable.comcast.com;X-NUM-GUESTS=0:mailto:khem_raj@cable.comcast.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ro
 b.ranslam@windriver.com;X-NUM-GUESTS=0:mailto:rob.ranslam@windriver.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=bi
 kram_bhola@mentor.com;X-NUM-GUESTS=0:mailto:bikram_bhola@mentor.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=yo
 cto@yoctoproject.org;X-NUM-GUESTS=0:mailto:yocto@yoctoproject.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=oa
 ndreasson@luxoft.com;X-NUM-GUESTS=0:mailto:oandreasson@luxoft.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ya
 nnick.koehler@hpe.com;X-NUM-GUESTS=0:mailto:yannick.koehler@hpe.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=st
 ephen.k.jolley@intel.com;X-NUM-GUESTS=0:mailto:stephen.k.jolley@intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=as
 eilis@ciena.com;X-NUM-GUESTS=0:mailto:aseilis@ciena.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jd
 mason@kudzu.us;X-NUM-GUESTS=0:mailto:jdmason@kudzu.us
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jo
 nathan.haws@sdl.usu.edu;X-NUM-GUESTS=0:mailto:jonathan.haws@sdl.usu.edu
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=dw
 atkins@sierrawireless.com;X-NUM-GUESTS=0:mailto:dwatkins@sierrawireless.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=theyoc
 toproject@gmail.com;X-NUM-GUESTS=0:mailto:theyoctoproject@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ra
 j.khem@gmail.com;X-NUM-GUESTS=0:mailto:raj.khem@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ra
 ymond.tan@intel.com;X-NUM-GUESTS=0:mailto:raymond.tan@intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=th
 ore.boeckelmann@inoex.de;X-NUM-GUESTS=0:mailto:thore.boeckelmann@inoex.de
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=rc
 alhoun@shotspotter.com;X-NUM-GUESTS=0:mailto:rcalhoun@shotspotter.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=na
 ndojve@gmail.com;X-NUM-GUESTS=0:mailto:nandojve@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ar
 avindhlalgss@embedur.com;X-NUM-GUESTS=0:mailto:aravindhlalgss@embedur.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=sj
 olley.yp.pm@gmail.com;X-NUM-GUESTS=0:mailto:sjolley.yp.pm@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=pa
 trick.schneider@bhtronik.de;X-NUM-GUESTS=0:mailto:patrick.schneider@bhtroni
 k.de
RECURRENCE-ID;TZID=America/Los_Angeles:20191029T080000
CREATED:20180524T181406Z
DESCRIPTION:<br>The Yocto Project hosts a technical call. All community mem
 bers are invited to join on both the call and in the IRC channel\, which ar
 e used simultaneously.<br>We encourage people attending the meeting to logo
 n and announce themselves on the Yocto Project IRC chancel during the meeti
 ng (optional):<br><br>Yocto IRC: <a href="http://webchat.freenode.net/?chan
 nels=#yocto">http://webchat.freenode.net/?channels=#yocto</a><br><br>Wiki: 
 <a href="https://www.yoctoproject.org/public-virtual-meetings/">https://www
 .yoctoproject.org/public-virtual-meetings/</a><br><br>Bridge is with Zoom a
 t: <a href="https://zoom.us/j/990892712" id="ow634" __is_owner="true">https
 ://zoom.us/j/990892712</a><br><br>Tuesdays when we aren’t having the Monthl
 y Technical Call The Yocto Project hosts a engineering sync by which the te
 chnical team discusses the current status of engineering topics\, including
  the autobuilder\, documentation\, builds\, and releases.
LAST-MODIFIED:20191022T150509Z
LOCATION:Zoom Meeting: https://zoom.us/j/990892712
SEQUENCE:3
STATUS:CANCELLED
SUMMARY:Yocto Project Technical Team Meeting / Engineering Sync
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H15M0S
END:VALARM
END:VEVENT
END:VCALENDAR

[-- Attachment #2: invite.ics --]
[-- Type: application/ics, Size: 6322 bytes --]

                 reply	other threads:[~2019-10-22 15:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0000000000006868ec05958120b4@google.com \
    --to=theyoctoproject@gmail.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.