The branch OpenSSL_1_0_2-stable has been updated
via 6b7d872e819449a19ea428386f25e90e5eaedc29 (commit)
from f0348c842e75a77f643e7d34cb88609145b2d320 (commit)
- Log -----------------------------------------------------------------
commit 6b7d872e819449a19ea428386f25e90e5eaedc29
Author: Rich Salz <[email protected]>
Date: Tue Jul 28 12:41:36 2015 -0400
Tweak README about rt and bug reporting.
Reviewed-by: Matt Caswell <[email protected]>
(cherry picked from commit 932af1617e277904bcca6e47729a420bba39785b)
-----------------------------------------------------------------------
Summary of changes:
README | 33 +++++++++++++++++++--------------
1 file changed, 19 insertions(+), 14 deletions(-)
diff --git a/README b/README
index ae17fb4..b6ffe9b 100644
--- a/README
+++ b/README
@@ -137,17 +137,23 @@
Email the report to:
- [email protected]
+ [email protected]
- Note that the request tracker should NOT be used for general assistance
- or support queries. Just because something doesn't work the way you expect
- does not mean it is necessarily a bug in OpenSSL.
+ In order to avoid spam, this is a moderated mailing list, and it might
+ take a day for the ticket to show up. (We also scan posts to make sure
+ that security disclosures aren't publically posted by mistake.) Mail to
+ this address is recorded in the public RT (request tracker) database (see
+ https://www.openssl.org/support/rt.html for details) and also forwarded
+ the public openssl-dev mailing list. Confidential mail may be sent to
+ [email protected] (PGP key available from the key servers).
- Note that mail to [email protected] is recorded in the public
- request tracker database (see https://www.openssl.org/support/rt.html
- for details) and also forwarded to a public mailing list. Confidential
- mail may be sent to [email protected] (PGP key available from
- the key servers).
+ Please do NOT use this for general assistance or support queries.
+ Just because something doesn't work the way you expect does not mean it
+ is necessarily a bug in OpenSSL.
+
+ You can also make GitHub pull requests. If you do this, please also send
+ mail to [email protected] with a link to the PR so that we can more easily
+ keep track of it.
HOW TO CONTRIBUTE TO OpenSSL
----------------------------
@@ -164,11 +170,10 @@
reason as to why that feature isn't implemented.
Patches should be as up to date as possible, preferably relative to the
- current Git or the last snapshot. They should follow the coding style of
- OpenSSL and compile without warnings. Some of the core team developer targets
- can be used for testing purposes, (debug-steve64, debug-geoff etc). OpenSSL
- compiles on many varied platforms: try to ensure you only use portable
- features.
+ current Git or the last snapshot. They should follow our coding style
+ (see http://openssl.org/about/codingstyle.txt) and compile without
+ warnings using the --strict-warnings flag. OpenSSL compiles on many
+ varied platforms: try to ensure you only use portable features.
Note: For legal reasons, contributions from the US can be accepted only
if a TSU notification and a copy of the patch are sent to [email protected]
_____
openssl-commits mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-commits
