|
P1800 SV-EC Technical Committee |
|
|
|||
P1800 SV Operating Guidelines
|
SV-EC Operating GuidelinesThe following guidelines were approved in December 19th 2005 meeting. Committee
A. Address P1800 SV-EC Errata Goals/Objectives
A.
Resolve reported issues related to P1800 SV-EC Process
A.
Review all appropriate errata for P1800 SV-EC B.
All work will be voted on as per the voting guidelines C.
The SV-EC web site will be the primary repository or all
work and communication Donation/Proposals
Donations
not accepted at this time. Errata
All
changes to the existing LRM to fix errors, refine concepts, or clarify
descriptions will be handled as errata. All errata will be tracked via the SystemVerilog
Mantis data-base (http://www.eda.org/svdb). The committee will: A. review all submitted
issues B. resolve them as
appropriate C. generate change
notices for all changes D. notify submitter of
the resolution This
will require each errata to include the following information: A. Problem description B. Example of problem C. Submitters name D. Submitters email E. Section(s) of LRM
related to issue Voting
Structure
Voting
is used to resolve issues in a number of areas; process, technical
discussions, acceptance and approval of submissions, resolution of errata,
approving the LRM and sending it to the board, etc.
Member
based votes: These
votes are for issues that are primarily in technical in nature and do not
require P1800 membership. The following are examples of individual based
votes: A. Resolution of errata B. Technical decisions in
the review and refinement of submissions Voting Rules
Voting
guidelines are as follows: A. Attendance a.
Voting attendance is reset as of the first SV-EC Errata
Resolution Meeting. b.
Individuals that were eligible to vote at the end of the
P1800 Ballot Issue resolution process will be eligible to vote at the
beginning of P1800 Errata Resolution process (with the assumption that they
have 3 out of the last 4 SV-EC meetings attended). c.
Individuals must attend 3 out of the last 4 regularly
scheduled meetings to be eligible to vote or must have attended at least 75%
of the meetings during the Errata resolution effort. d.
Company votes are based on a designated individual’s
attendance record (including proxy specification). B. Committee Vote a.
All votes require majority of the eligible votes attending
the meeting to pass. Voting rights calculated based on meetings that have
been announced at least 1 week in advance. A quorum of 50% of the eligible
individuals must be present for individual votes. b.
The Chair of the committee is not eligible to vote on
individual votes unless there is a tie in which case the chairs vote is used
to break the tie. Co-chair can vote as an individual except in the case where
the co-chair is acting as the chair due to the chair not being present. c.
The Chair of the committee is not eligible to vote on
company votes (unless he is the only company representative on the
committee). If there is a tie then the TCC chairs vote is used to break the
tie. C. Email vote a.
A vote for email can be called by the chair/co-chair. b.
The period for response will be one week (can be adjusted
by agreement before the vote to a different period within committee). c.
Any negative vote will force the issue to be discussed and
voted on at a committee meeting. A negative vote must be accompanied with a
clear description of the reasoning behind it. d.
If there are no negative votes and half of the eligible
voters respond with an accept vote then the motion will be passed (the Chair
of the committee is not eligible to vote on email votes). e.
The purpose of the email-vote is to pass items that are
non-controversial and to reduce the time required to handle them in meetings. Milestones
A.
Ongoing to resolve P1800 Issues Deliverables
Update the resolved issues in the
SystemVerilog Mantis data-base (http://www.eda.org/svdb). |
|
|
|
|
|