[sv-bc] RE: Agenda: SV-BC/SV-EC Future Scope Meeting Feb 18 9-11am PST

From: Maidment, Matthew R <matthew.r.maidment@intel.com>
Date: Tue Feb 17 2015 - 16:45:54 PST
And 1 more Agenda Item:

o Seeking new chairperson for SV-EC. 

Matt 
--
Matt Maidment
mmaidmen@ichips.intel.com
 

>-----Original Message-----
>From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of
>Maidment, Matthew R
>Sent: Tuesday, February 17, 2015 4:38 PM
>To: sv-bc@eda.org; sv-ec@eda.org
>Subject: [sv-ec] RE: Agenda: SV-BC/SV-EC Future Scope Meeting Feb 18 9-
>11am PST
>
>Sorry for the confusion.  Here's the other necessary piece of information
>if dialing directly by phone:
>
>Conference ID: 148125963
>
>--
>Matt Maidment
>mmaidmen@ichips.intel.com
>
>
>>-----Original Message-----
>>From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of
>>Maidment, Matthew R
>>Sent: Tuesday, February 17, 2015 3:14 PM
>>To: sv-bc@eda.org; sv-ec@eda.org
>>Subject: [sv-ec] Agenda: SV-BC/SV-EC Future Scope Meeting Feb 18 9-11am
>>PST
>>
>>All.
>>
>>We will hold the first of 2 meetings to scope future work by SV-BC and
>>SV-EC committees on Feb 18, 9-11am PST.
>>
>>Agenda
>>o Roll Call (5 min)
>>
>>o General Direction Roll Call (30-45 min depending upon # of
>>participants): Participants propose high-level direction for possible
>>next PAR.  Examples include "Errata Only" or "Errata and clarifications"
>>or "all enhancements"  Please keep it brief.
>>
>>o Mantis Roll Call (45 min): Participants highlight Mantis
>>numbers/queries for consideration.  This should be a reasonably quick
>>collection of Mantis IDs of interest.
>>
>>o Non-Mantis Roll Call (remainder): Participants highlight
>>issues/requests not currently captured by Mantis
>>
>>Meeting Logistics:
>>
>>Join Online:
>>https://meet.intel.com/matthew.r.maidment/F77DRR7R
>>
>>Join by Phone
>>+1(916)356-2663 (or your local bridge access #) Choose bridge 5.
>>
>>Find a local number
>>https://dial.intel.com/
>>
>>
>>
>>--
>>Matt Maidment
>>mmaidmen@ichips.intel.com
>>
>>
>>
>>--
>>This message has been scanned for viruses and
>>dangerous content by MailScanner, and is
>>believed to be clean.
>>
>>
>
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
>
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Tue Feb 17 16:46:07 2015

This archive was generated by hypermail 2.1.8 : Tue Feb 17 2015 - 16:46:12 PST