To submit a patch, please open a pull request on GitHub. If you are thinking
of making a large contribution, open an issue for it before starting work,
to get comments from the community. Someone may be already working on
-the same thing or there may be reasons why that feature isn't implemented.
+the same thing, or there may be reasons why that feature isn't implemented.
To make it easier to review and accept your pull request, please follow these
guidelines:
(usually by rebasing) before it will be acceptable.
4. Patches should follow our [coding style] and compile without warnings.
- Where `gcc` or `clang` is available you should use the
+ Where `gcc` or `clang` is available, you should use the
`--strict-warnings` `Configure` option. OpenSSL compiles on many varied
- platforms: try to ensure you only use portable features. Clean builds
- via Travis and AppVeyor are required, and they are started automatically
+ platforms: try to ensure you only use portable features. Clean builds via
+ GitHub Actions and AppVeyor are required, and they are started automatically
whenever a PR is created or updated.
- [coding style]: https://www.openssl.org/policies/codingstyle.html
+ [coding style]: https://www.openssl.org/policies/technical/coding-style.html
5. When at all possible, patches should include tests. These can
either be added to an existing test, or completely new. Please see
specific release, to see if an upgrade is worth the effort.
9. Guidelines how to integrate error output of new crypto library modules
- can be found in [crypto/err/README.md](crypto/err/README.md).
\ No newline at end of file
+ can be found in [crypto/err/README.md](crypto/err/README.md).