[openssl-commits] [web] master update

[Rich Salz]

The branch master has been updated
       via  664e55d5a68aaf8cb986c065677737b34d7a89c2 (commit)
      from  24c3c743806fecc30e1c807cd04ce021d8d19f5b (commit)


- Log -----------------------------------------------------------------
commit 664e55d5a68aaf8cb986c065677737b34d7a89c2
Author: Rich Salz <rsalz at akamai.com>
Date:   Fri Nov 4 10:17:08 2016 -0400

    Missed updates to not use RT any more.

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

Summary of changes:
 community/index.html | 41 +++++++++++++++++++++--------------------
 docs/faq.txt         | 25 +------------------------
 2 files changed, 22 insertions(+), 44 deletions(-)

diff --git a/community/index.html b/community/index.html
index a9fe68f..8dfd6b4 100644
--- a/community/index.html
+++ b/community/index.html
@@ -40,27 +40,20 @@
 
             <h3><a href="#bugs">Reporting Bugs</a></h3>
 
+            <p>We are in the process of changing to do "everything" on
+            GitHub.  Please see our
+            <a
+              href="https://www.openssl.org/blog/blog/2016/10/12/f2f-rt-github/">blog post</a>
+            for some details and background.
+
 	    <p>If you think have found a security bug, please see our
 	    <a href="/news/vulnerabilities.html">vulnerabilities page</a>
 	    for information on how to report it.</p>
 
-	    <p>We have set up a request tracker at
-	    <a href="https://rt.openssl.org">https://rt.openssl.org</a>,
-	    with read-only access using <em>guest</em> as the name
-	    and password.
-	    Requests can be viewed on-line by using the following URL,
-	    replacing <em>NNNN</em> with the request number:
-	    https://rt.openssl.org/Ticket/Display.html?user=guest&pass=guest&id=<em>NNNN</em>
-	    </p>
-
-	    <p>The easiest way to respond to an existing request is to reply
-	    to the relevant message in <em>openssl-dev at openssl.org</em>.
-	    To help avoid duplicate copies, edit the recipient list so that
-	    only <em>rt at openssl.org</em> is listed and remove any quoted
-	    material.
-	    </p>
-
-	    <p>To report a bug or make an enhancement request, send email
+	    <p>To report a bug or make an enhancement request, please open
+            an issue on GitHub, by clicking "new issue" on this page:
+            <a
+              href="https://github.com/openssl/openssl/issues">https://github.com/openssl/openssl/issues</a>.
 	    to <a href="mailto:rt at openssl.org">rt at openssl.org</a>.
 	    In the subject line, please make sure to indicate if it's a
 	    bug or a fix, and a brief description of the issue.  In the
@@ -71,9 +64,17 @@
 
             <p>For more information about the best way to submit patches,
             please see the file CONTRIBUTING in the distribution.
-	    In short, making a
-	    <a href="https://github.com/openssl/openssl">GitHub</a>,
-            pull request is preferred.</p>
+            The short answer is 
+            <a
+              href="https://github.com/openssl/openssl/pulls">make a pull request</a>.
+            </p>
+
+            <p>Our backlog of <em>old bugs</em> is maintained with Request
+            Tracker, available at
+	    <a href="https://rt.openssl.org">https://rt.openssl.org</a>,
+	    with read-only access using <em>guest</em> as the name
+	    and password.
+	    </p>
 
 	  <footer>
 	    You are here: <a href="/">Home</a>
diff --git a/docs/faq.txt b/docs/faq.txt
index 0af0e9c..6caa5e3 100644
--- a/docs/faq.txt
+++ b/docs/faq.txt
@@ -754,30 +754,7 @@ LOT of false positives.
 
 * I'm SURE I've found a bug, how do I report it?
 
-To avoid duplicated reports check the mailing lists and release notes for the
-relevant version of OpenSSL to see if the problem has been reported already.
-
-Bug reports with no security implications should be sent to the request
-tracker. This can be done by mailing the report to <rt at openssl.org> (or its
-alias <openssl-bugs at openssl.org>), please note that messages sent to the
-request tracker also appear in the public openssl-dev mailing list.
-
-The report should be in plain text. Any patches should be sent as
-plain text attachments because some mailers corrupt patches sent inline.
-If your issue affects multiple versions of OpenSSL check any patches apply
-cleanly and, if possible include patches to each affected version.
-
-The report should be given a meaningful subject line briefly summarising the
-issue. Just "bug in OpenSSL" or "bug in OpenSSL 0.9.8n" is not very helpful.
-
-By sending reports to the request tracker the bug can then be given a priority
-and assigned to the appropriate maintainer. The history of discussions can be
-accessed and if the issue has been addressed or a reason why not. If patches
-are only sent to openssl-dev they can be mislaid if a team member has to
-wade through months of old messages to review the discussion.
-
-See also <URL: https://www.openssl.org/community>
-
+Please see <URL: https://www.openssl.org/community>
 
 * I've found a security issue, how do I report it?