X-TagToolbar-Keys: D20110313155254911
Content-Type: multipart/alternative;
boundary="------------010505040806010008000205"
This is a multi-part message in MIME format.
--------------010505040806010008000205
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Just FYI for those not on the SV lists.
Does anyone know who the Accellera (Designated) representatives are, or what the process to become one is?
Kev.
-------- Original Message --------
Subject: [sv-dc] New rules for SystemVerilog Technical Committees
Date: Sat, 12 Mar 2011 20:41:10 -0800
From: Neil Korpusik <neil.korpusik@oracle.com>
To: sv-ac@server.eda.org <sv-ac@eda.org>, SV_BC List <sv-bc@eda.org>, SV-CC <sv-cc@eda.org>, sv-dc@eda.org, SV_EC List <sv-ec@eda.org>
CC: IEEE P1800 Working Group <ieee1800@eda.org>
To all P1800 Technical Committees,
The Working Group has reviewed the new IEEE participation policies and has
determined how they will affect the Working Group and the Technical
Committees. Below is a summary of the new policies.
These changes take effect immediately.
The aliases are in the process of being scrubbed. For now, we should continue
to use the set of aliases that are currently in place. A new set of aliases
will take effect when they are stabilized. Another email will be sent when we
should be switching over to them.
Pages 9, 10, 11 of the following document describe the rules for Entity
based standards. The P1800 is Entity based and will follow these rules.
http://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf
In addition to the rules described in the IEEE-SA bylaws document the
following rule is also in affect. Only employees of Entities that are
voting members of the Working group will be allowed to participate in
any of the Technical Committees. The Technical Committee chairs will need
to start policing their meetings to ensure that only employees of the
following companies are allowed to participate.
Cadence
Freescale
Intel
Marvel
Mentor
Oracle
Synopsys
Accellera (Designated Representatives, as opposed to employees)
Other companies may choose to become voting members of the Working Group.
If this happens, employees of those companies will also be allowed to
participate.
This is a big set of changes and there will be a noticeable impact on
various committees. We will most likely have more questions as we start
implementing them.
Neil
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--------------010505040806010008000205
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Just FYI for those not on the SV lists.<br>
<br>
Does anyone know who the Accellera (Designated) representatives are,
or what the process to become one is?<br>
<br>
Kev.<br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">Subject: </th>
<td>[sv-dc] New rules for SystemVerilog Technical Committees</td>
</tr>
<tr>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">Date: </th>
<td>Sat, 12 Mar 2011 20:41:10 -0800</td>
</tr>
<tr>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">From: </th>
<td>Neil Korpusik <a class="moz-txt-link-rfc2396E" href="mailto:neil.korpusik@oracle.com"><neil.korpusik@oracle.com></a></td>
</tr>
<tr>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:sv-ac@server.eda.org">sv-ac@server.eda.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:sv-ac@eda.org"><sv-ac@eda.org></a>, SV_BC List
<a class="moz-txt-link-rfc2396E" href="mailto:sv-bc@eda.org"><sv-bc@eda.org></a>, SV-CC <a class="moz-txt-link-rfc2396E" href="mailto:sv-cc@eda.org"><sv-cc@eda.org></a>,
<a class="moz-txt-link-abbreviated" href="mailto:sv-dc@eda.org">sv-dc@eda.org</a>, SV_EC List <a class="moz-txt-link-rfc2396E" href="mailto:sv-ec@eda.org"><sv-ec@eda.org></a></td>
</tr>
<tr>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">CC: </th>
<td>IEEE P1800 Working Group <a class="moz-txt-link-rfc2396E" href="mailto:ieee1800@eda.org"><ieee1800@eda.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>To all P1800 Technical Committees,
The Working Group has reviewed the new IEEE participation policies and has
determined how they will affect the Working Group and the Technical
Committees. Below is a summary of the new policies.
These changes take effect immediately.
The aliases are in the process of being scrubbed. For now, we should continue
to use the set of aliases that are currently in place. A new set of aliases
will take effect when they are stabilized. Another email will be sent when we
should be switching over to them.
Pages 9, 10, 11 of the following document describe the rules for Entity
based standards. The P1800 is Entity based and will follow these rules.
<a class="moz-txt-link-freetext" href="http://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf">http://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf</a>
In addition to the rules described in the IEEE-SA bylaws document the
following rule is also in affect. Only employees of Entities that are
voting members of the Working group will be allowed to participate in
any of the Technical Committees. The Technical Committee chairs will need
to start policing their meetings to ensure that only employees of the
following companies are allowed to participate.
Cadence
Freescale
Intel
Marvel
Mentor
Oracle
Synopsys
Accellera (Designated Representatives, as opposed to employees)
Other companies may choose to become voting members of the Working Group.
If this happens, employees of those companies will also be allowed to
participate.
This is a big set of changes and there will be a noticeable impact on
various committees. We will most likely have more questions as we start
implementing them.
Neil
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
</pre>
</body>
</html>
--------------010505040806010008000205--
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Sun Mar 13 15:54:15 2011
This archive was generated by hypermail 2.1.8 : Sun Mar 13 2011 - 15:54:30 PDT