[sv-bc] Technical Committees Operating Guidelines - as a Working Group

To all P1800 Technical Committees,

- Scope document

    At the last Working group meeting, a "scope document" was approved. This
    document outlines what activities the Technical Committees are now
    authorized to work on. A copy of that document is shown below.

- Voting Rights are being reset

    As you may have heard, the PAR has been approved by the IEEE. This signals
    a transition for the P1800 from a Study Group to a Working Group. It is
    customary for us to reset the voting rights for all of the Technical
    Committees at this point in the process. Everyone is allowed to vote in the
    first 3 meetings. The 2 out of last 3 meetings rule goes into effect after
    the first 3 meetings have been held.

- New IEEE participation rules

   There are some new rules that have been put in place by the IEEE with
   regards to participation rights. These new rules are being clarified.
   There will be a FAQ forthcoming which will help clarify these new rules.
   The Working Group will review the FAQ and determine what impact it will
   have on the Technical Committees. Until that occurs, we are continuing to
   allow everyone to participate, as we did while we were still a Study Group.

- Technical Committees

   There are now 6 Technical Committees in place:
   SV-AC, SV-BC, SV-CC, SV-DC, SV-EC, SV-FC.
   These are the same as we had for the last PAR, with the addition of the
   SV-DC and the SV-FC.

   SV-DC - discrete committee - will look at connections to verilog-ams.
   SV-FC - futures committee - will look at mantis items that span
                                multiple committees.

Neil

P1800 Scope Document
--------------------

All committees including SV-AC, SV-BC, SV-CC, SV-EC are authorized to begin
work on minor errata and clarifications.

The SV-AC is authorized to work on the top 12 categories from their list.

The SV-BC is authorized to work on the top 25 items from their list.

The SV-CC is authorized to work on the top 32 items from their list, and
additional work on language extensions as generated by the other committees.

The SV-DC is authorized to work on its roadmap.

The SV-EC is authorized to work on the top 25 items from their list.

See: http://www.eda.org/sv-ieee1800/hm/att-1054/AC_BC_CC_EC_mantis_2012.pdf
for a list of the specific mantis items that were authorized for the SV-AC,
SV-BC, SV-CC, SV-EC.

The SV-FC is authorized to consider Mantis items it would deem appropriate to
transfer to the SV-FC for future work. The SV-FC will drive the development of
a specification process to ensure that all cross committee and language design
issues are considered prior to changing the LRM.

Being authorized to work on an item is not a commitment for completion.

Further work, including minor enhancements, is not authorized until this
document is updated to reflect that authorization. Technical committees may
request the addition of items to this document. An update to this document is
achieved by the passing of a motion of the Working Group.

Last Modification approved 6/24/10

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.