Browse code

Improve "security reports" section in contribution docs.

Signed-off-by: Solomon Hykes <solomon@docker.com>

Solomon Hykes authored on 2014/11/10 00:16:19
Showing 1 changed files
... ...
@@ -6,17 +6,25 @@ feels wrong or incomplete.
6 6
 
7 7
 ## Topics
8 8
 
9
-* [Security Reports](#security-reports)
9
+* [Reporting Security Issues](#reporting-security-issues)
10 10
 * [Design and Cleanup Proposals](#design-and-cleanup-proposals)
11 11
 * [Reporting Issues](#reporting-issues)
12 12
 * [Build Environment](#build-environment)
13 13
 * [Contribution Guidelines](#contribution-guidelines)
14 14
 * [Community Guidelines](#docker-community-guidelines)
15 15
 
16
-## Security Reports
16
+## Reporting Security Issues
17 17
 
18
-Please **DO NOT** file an issue for security related issues. Please send your
19
-reports to [security@docker.com](mailto:security@docker.com) instead.
18
+The Docker maintainers take security very seriously. If you discover a security issue,
19
+please bring it to their attention right away!
20
+
21
+Please send your report privately to [security@docker.com](mailto:security@docker.com),
22
+please **DO NOT** file a public issue.
23
+
24
+Security reports are greatly appreciated and we will publicly thank you for it. We also
25
+like to send gifts - if you're into Docker shwag make sure to let us know :)
26
+We currently do not offer a paid security bounty program, but are not ruling it out in
27
+the future.
20 28
 
21 29
 ## Design and Cleanup Proposals
22 30