svn commit: r1349309 - /subversion/site/publish/docs/community-guide/issues.part.html

[hw...@apache.org]

Author: hwright
Date: Tue Jun 12 12:50:48 2012
New Revision: 1349309

URL: http://svn.apache.org/viewvc?rev=1349309&view=rev
Log:
* publish/docs/community-guide/issues.part.html
  (security): Add a link to the ASF guidelines, and some hidden thoughts about
    future content.

Modified:
    subversion/site/publish/docs/community-guide/issues.part.html

Modified: subversion/site/publish/docs/community-guide/issues.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/issues.part.html?rev=1349309&r1=1349308&r2=1349309&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/issues.part.html (original)
+++ subversion/site/publish/docs/community-guide/issues.part.html Tue Jun 12 12:50:48 2012
@@ -422,6 +422,21 @@ SASL or by the Apache HTTP Server and it
 degree that we can leverage the knowledge of security experts by using the
 third-party libraries and APIs they provide, we will continue to do so.</p>
 
+<p>This document describes the steps we take when receiving or finding an
+issue which may be classified as having security implications, and is meant to
+suppliment the
+<a href="http://www.apache.org/security/committers.html">Apache guidelines</a>
+to committers for the same.</p>
+
+<!-- Some thoughts about what to put here:
+  The types of security issues we commonly encounter.
+  When to request a CVE, and the process for doing so.
+  When to embargo release information, and the process for pre-notifying
+    interested parties.
+  Other stuff?
+-->
+
+
 </div> <!-- security -->
 
 </div> <!-- issues -->