[sv-bc] Agenda: SV-BC/SV-EC 1800 Scoping Meeting Feb 25 9-11am PST

From: Maidment, Matthew R <matthew.r.maidment@intel.com>
Date: Tue Feb 24 2015 - 15:29:14 PST
SV-BC/SV-EC 1800 Scoping Meeting
Date: Feb 25, 2015
Time: 09:00am-11:00am PST
Join online: https://meet.intel.com/matthew.r.maidment/6F695NSL
Join by Phone:
US: +1(916)356-2663
UK: +44 179340 2663
Choose bridge 5.
Conference ID: 702617185

*       Roll Call (5 min)

                2015
Rep     Company Feb 18  Feb 25
Matt Maidment   Intel   X
Brad Pierce     Synopsys        X
Ray Ryan        Mentor  X
Jonathan Bromley        Verilab X
Daniel Schostak ARM     X
Mark Hartoog    Synopsys        X
Neil Korpusik   Oracle  X
Arturo Salz     Synopsys        X
Shalom Bresticker       Intel   X
Dave Rich       Mentor  X
Francoise Martinolle    Cadence X
Stu Sutherland  SutherlandHDL   X
Sachin  Mentor  X

*       Review Previous Meeting Notes (5 min)
      http://www.eda.org/sv-bc/hm/11692.html
      http://www.eda.org/sv-ec/hm/8568.html

*       Patent Policy Reminder (5 min)
      http://standards.ieee.org/board/pat/pat-slideset.ppt

*       Mantis Review (60 min)
      Review items marked for P1800-201X
      http://tinyurl.com/q9jz7u9
      for trends and try to summarize type and scope of interest.

*       Continue capturing overall group summary (45 min)

      From Feb 18 meeting:
*       Consensus is to include for errata and clarification.  This could include minor enhancements for resolution.  Consensus from vendors and users.
*       If there are major enhancements they should be done with sufficient contributors.  Asking for many enhancements to be implemented by limited number of committee members will not succeed.
*       Would like to see global resolution of priority.  During 2012 effort, BC and EC members were pulled into AC/DC work.  Would like to ensure that AC/DC or any other major initiative is properly scoped.  Should consider impact of 1801, 1802, AC, AMS/DC, 1735 and others.
*       Difficult to make recommendations without timeframe.  Timeframe would influence scope.  BC/EC should suggest timeframe and factor this into their proposal (short vs medium vs long)  From Karen:  "I suggest making an estimate of what it will take to do the work your team feels is necessary."



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Tue Feb 24 15:29:37 2015

This archive was generated by hypermail 2.1.8 : Tue Feb 24 2015 - 15:29:46 PST