All,

I figured people on this list might be interested in this.  If you have
any concerns or suggestions about CWE, the upcoming months will be the
best time to raise them in a focused discussion forum, the CWE Researcher
List.

If you don't know what CWE is, then shame on me for not pimping it enough:
http://cwe.mitre.org

- Steve

------------------------------------------------------

MITRE has established a list for researchers and other parties who are
interested in detailed discussion of the Common Weakness Enumeration
(CWE).  CWE Draft 6 has over 600 nodes and is seeing increased usage. Over
the summer of 2007, MITRE has identified some themes within CWE that we'd
like to discuss with the community.  So, it's time for some focused
feedback.

Beginning next week, we will be using this CWE researcher list to conduct
in-depth technical discussions: where CWE is now, what are its strengths
and limitations, and where it needs to be.  We will bring up these larger
discussion points, solicit feedback, and modify CWE accordingly.  (Don't
worry, we won't bother you with the hundreds of minor edits we'll be
doing!)

We think that you could be an important contributor to the success of
CWE, so we are inviting you to join the list.  Your participation is
encouraged but not required.

To subscribe, see:

  http://cwe.mitre.org/community/registration.html

or just send an email to [EMAIL PROTECTED] with the command:

  subscribe CWE-RESEARCH-LIST

Note: posts to the list will be publicly archived.

We hope you can join!


Thank you,

Steve Christey
CWE Technical Lead

Bob Martin
CWE Project Lead
_______________________________________________
Secure Coding mailing list (SC-L) SC-L@securecoding.org
List information, subscriptions, etc - http://krvw.com/mailman/listinfo/sc-l
List charter available at - http://www.securecoding.org/list/charter.php
SC-L is hosted and moderated by KRvW Associates, LLC (http://www.KRvW.com)
as a free, non-commercial service to the software security community.
_______________________________________________

Reply via email to