[openssl-commits] [web] master update

[Rich Salz]

The branch master has been updated
       via  7396e9b0e72bece0d79baa53e1459e8bdeb5cb76 (commit)
      from  c21a779e67328ae7b1e5037631f82bb91a532887 (commit)


- Log -----------------------------------------------------------------
commit 7396e9b0e72bece0d79baa53e1459e8bdeb5cb76
Author: Rich Salz <rsalz at akamai.com>
Date:   Wed Jul 29 16:13:35 2015 -0400

    update RT/bug email stuff

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

Summary of changes:
 support/rt.wml | 28 +++++++++++++++-------------
 1 file changed, 15 insertions(+), 13 deletions(-)

diff --git a/support/rt.wml b/support/rt.wml
index a10d09d..c3a705c 100644
--- a/support/rt.wml
+++ b/support/rt.wml
@@ -5,15 +5,13 @@
 
 <h1>OpenSSL Request Tracker</h1>
 
-The OpenSSL project has set up a request tracker at
+We have set up a request tracker at
 <a href="http://rt.openssl.org/">http://rt.openssl.org/</a>
 offering read-only access using the account <tt>guest</tt> with the
 password <tt>guest</tt>.
 
-The username and password can also be specified in the URL for example:
-<a href="http://rt.openssl.org/?user=guest&pass=guest&">http://rt.openssl.org/?user=guest&pass=guest</a>.
-
-A link to a specific bug can be created using for example:
+The username and password can also be specified in the URL, as can a link
+to a specific bug.  For example:
 <a href="http://rt.openssl.org/Ticket/Display.html?user=guest&pass=guest&id=1">
 http://rt.openssl.org/Ticket/Display.html?user=guest&pass=guest&id=1</a>
 
@@ -25,17 +23,20 @@ of new or open bugs and requests.
 
 <h2>Sending a Request</h2>
 
-New requests must be sent by email to
+To create a new bug or enhancement request, send email to
 <a href="mailto:rt at openssl.org">rt at openssl.org</a>, clearly indicating
 the type of request (bug report, patch, contribution, enhancement request,
 ...) the operating system and version of OpenSSL affected.
+If you have a patch or diff, please send it as an attachment, and not
+inline in the message body.
 
 The easiest way to respond to an existing request is to reply to the relevant
-message in <tt>openssl-dev at openssl.org</tt> and making sure you include
-<tt>rt at openssl.org</tt> in the list of recipients.
-
-If you do not have a copy of the existing request then you can create a new
-email including the ID in the subject line. For example to reply to ID #9999
+message in <tt>openssl-dev at openssl.org</tt>. To help avoid duplicate copies,
+edit the recipient list so that only
+<tt>rt at openssl.org</tt> is listed and remove any quoted material.
+You can also create a new email by having the subject line start with a
+special prefix.
+For example to reply to ID #9999
 you'd send a message to <tt>rt at openssl.org</tt> including <tt>[openssl.org #9999]</tt> in the subject.
 
 <h2>Gateways</h2>
@@ -44,10 +45,11 @@ Incoming requests are added to the request tracker. The request tracker
 automatically forwards incoming requests to the
 <tt>openssl-dev at openssl.org</tt>
 mailing list for information of the community and public discussion.
-Replys sent to <tt>rt at openssl.org</tt> keeping the ticket in the
+Replies sent to <tt>rt at openssl.org</tt> keeping the ticket in the
 subject line unchanged will be recorded and added to the ticket by the
 request tracker, then forwarded to <tt>openssl-dev at openssl.org</tt>.
 
 <h2>Request Tracker Software</h2>
+
 The request tracker is using the RT software, available from
-<a href="http://www.fsck.com/projects/rt/">http://www.fsck.com/projects/rt/</a>.
+<a href="http://www.bestpractical.com/rt/">http://www.bestpractical.com/rt/</a>.