1 HOW TO CONTRIBUTE TO OpenSSL
2 ----------------------------
4 Development is coordinated on the openssl-dev mailing list (see
5 http://www.openssl.org for information on subscribing). If you
6 would like to submit a patch, send it to rt@openssl.org with
7 the string "[PATCH]" in the subject. Please be sure to include a
8 textual explanation of what your patch does.
10 You can also make GitHub pull requests. If you do this, please also send mail to
11 rt@openssl.org with a brief description and a link to the PR so that we can more
12 easily keep track of it.
14 If you are unsure as to whether a feature will be useful for the general
15 OpenSSL community please discuss it on the openssl-dev mailing list first.
16 Someone may be already working on the same thing or there may be a good
17 reason as to why that feature isn't implemented.
19 Patches should be as up to date as possible, preferably relative to the
20 current Git or the last snapshot. They should follow our coding style
21 (see https://www.openssl.org/policies/codingstyle.html) and compile without
22 warnings using the --strict-warnings flag. OpenSSL compiles on many
23 varied platforms: try to ensure you only use portable features.
25 Note: For legal reasons, contributions from the US can be accepted only
26 if a TSU notification and a copy of the patch are sent to crypt@bis.doc.gov
27 (formerly BXA) with a copy to the ENC Encryption Request Coordinator;
28 please take some time to look at
29 http://www.bis.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html [sic]
31 http://w3.access.gpo.gov/bis/ear/pdf/740.pdf (EAR Section 740.13(e))
32 for the details. If "your encryption source code is too large to serve as
33 an email attachment", they are glad to receive it by fax instead; hope you
34 have a cheap long-distance plan.
36 Our preferred format for changes is "diff -u" output. You might
37 generate it like this:
41 # ./Configure dist; make clean
43 # diff -ur openssl-orig openssl-work > mydiffs.patch