CONTRIBUTING 3.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172
  1. HOW TO CONTRIBUTE TO OpenSSL
  2. ----------------------------
  3. (Please visit https://www.openssl.org/community/getting-started.html for
  4. other ideas about how to contribute.)
  5. Development is done on GitHub, https://github.com/openssl/openssl.
  6. To request new features or report bugs, please open an issue on GitHub
  7. To submit a patch, please open a pull request on GitHub. If you are thinking
  8. of making a large contribution, open an issue for it before starting work,
  9. to get comments from the community. Someone may be already working on
  10. the same thing or there may be reasons why that feature isn't implemented.
  11. To make it easier to review and accept your pull request, please follow these
  12. guidelines:
  13. 1. Anything other than a trivial contribution requires a Contributor
  14. License Agreement (CLA), giving us permission to use your code. See
  15. https://www.openssl.org/policies/cla.html for details. If your
  16. contribution is too small to require a CLA, put "CLA: trivial" on a
  17. line by itself in your commit message body.
  18. 2. All source files should start with the following text (with
  19. appropriate comment characters at the start of each line and the
  20. year(s) updated):
  21. Copyright 20xx-20yy The OpenSSL Project Authors. All Rights Reserved.
  22. Licensed under the OpenSSL license (the "License"). You may not use
  23. this file except in compliance with the License. You can obtain a copy
  24. in the file LICENSE in the source distribution or at
  25. https://www.openssl.org/source/license.html
  26. 3. Patches should be as current as possible; expect to have to rebase
  27. often. We do not accept merge commits, you will have to remove them
  28. (usually by rebasing) before it will be acceptable.
  29. 4. Patches should follow our coding style (see
  30. https://www.openssl.org/policies/codingstyle.html) and compile
  31. without warnings. Where gcc or clang is available you should use the
  32. --strict-warnings Configure option. OpenSSL compiles on many varied
  33. platforms: try to ensure you only use portable features. Clean builds
  34. via Travis and AppVeyor are required, and they are started automatically
  35. whenever a PR is created or updated.
  36. 5. When at all possible, patches should include tests. These can
  37. either be added to an existing test, or completely new. Please see
  38. test/README for information on the test framework.
  39. 6. New features or changed functionality must include
  40. documentation. Please look at the "pod" files in doc/man[1357] for
  41. examples of our style. Run "make doc-nits" to make sure that your
  42. documentation changes are clean.
  43. 7. For user visible changes (API changes, behaviour changes, ...),
  44. consider adding a note in CHANGES. This could be a summarising
  45. description of the change, and could explain the grander details.
  46. Have a look through existing entries for inspiration.
  47. Please note that this is NOT simply a copy of git-log oneliners.
  48. Also note that security fixes get an entry in CHANGES.
  49. This file helps users get more in depth information of what comes
  50. with a specific release without having to sift through the higher
  51. noise ratio in git-log.
  52. 8. For larger or more important user visible changes, as well as
  53. security fixes, please add a line in NEWS. On exception, it might be
  54. worth adding a multi-line entry (such as the entry that announces all
  55. the types that became opaque with OpenSSL 1.1.0).
  56. This file helps users get a very quick summary of what comes with a
  57. specific release, to see if an upgrade is worth the effort.