Minutes of the April 10, 2004 SV-BC Meeting (Design Modeling Committee) 

1212 Day 
6406 
0000 Month 
8554 
0000 Year 
4444
 
a-a- Matt Maidment - Intel 
a-aa Brad Pierce - Synopsys 
aaaa Karen Pieper - Synopsys 
-aaa Johny Srouji - Intel 
aa-- Dan Jacobi - Intel 
-aaa Dave Rich - Synopsys 
aaa- Francoise Martinolle- Cadence 
---- Jay Lawrence - Cadence 
---- Dennis Brophy - Mentor 
aaaa Mark Hartoog - Synopsys 
-aaa Rishiyur Nikhil - Bluespec 
---a Cliff Cummings - Sunburst Design
a--- Steven Sharp - Cadence
a--- Mike MacNamera - Verisity

Review Meeting Minutes
Karen moves that we accept the meeting minutes of the May 24, 2004 
meeting.  Mark seconds.
No opposed.  Mac, Steve abstain.  Passes.

Discussion of the P1800.
The P1800 moved the SV committees over to operate under the Errata 
chair, Karen Pieper.  They passed a motion that all committees 
under the P1800 would vote as individuals.  Karen modified the 
Operating Guidelines document to reflect that this committee 
would not work only on Errata and all votes would be done as 
individuals.  The proposed guidelines are found at 

http://www.eda.org/sv-bc/Operating_Guideline.htm

The voting rules need to be updated to reflect the policies 
and procedures of the P1800.

If there is a potential enhancement that may be considered 
for the future that might require some adjustment to the 
current LRM, can they be considered as Errata now.  Karen 
believes that this is beyond the scope of our Errata charter.  

[AI] Karen will bring this up at the P1800.

Issue discussion:
================

13:  Brad moves that we accept the proposal.  Karen seconds
     No opposed.  No abstain.  Passes

73:  Brad moves that we accept the proposal.  Karen seconds.
     No opposed.  NO abstain.  Passes.

35:  This issue needs to be moved to the SV-EC.

84:  This issue needs to be moved to the SV-EC.

In the next meeting we should find owners for all of the issues 
so that we can attempt to drive them to closure as soon as we
can.  

[AI] Matt needs to identify high priority issues to assign
     owners to.

We could use confirmed to indicate that there is an owner,
and the assigned state to mean that there is a proposal.

[AI] Matt will create an email with suggested priority list

[AI] Matt will check to see if we can add a status between
assigned or resolved or if confirmed will be ok (i.e. can 
we overload it?)


New Action Items:
=============
[AI] Karen will bring this up at the P1800.

Next meeting will be on the 30th.  Meeting adjourns.