You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

74 lines
2.9 KiB

  1. Contributing to CMake
  2. *********************
  3. The following summarizes the process for contributing changes.
  4. See documentation on `CMake Development`_ for more information.
  5. .. _`CMake Development`: Help/dev/README.rst
  6. Community
  7. =========
  8. CMake is maintained and supported by `Kitware`_ and developed in
  9. collaboration with a productive community of contributors.
  10. Please subscribe and post to the `CMake Developers List`_ to raise
  11. discussion of development topics.
  12. .. _`Kitware`: http://www.kitware.com/cmake
  13. .. _`CMake Developers List`: https://cmake.org/mailman/listinfo/cmake-developers
  14. Patches
  15. =======
  16. CMake uses `Kitware's GitLab Instance`_ to manage development and code review.
  17. To contribute patches:
  18. #. Fork the upstream `CMake Repository`_ into a personal account.
  19. #. Run `Utilities/SetupForDevelopment.sh`_ for local configuration.
  20. #. See the `CMake Source Code Guide`_ for coding guidelines.
  21. #. Base all new work on the upstream ``master`` branch.
  22. Base work on the upstream ``release`` branch only if it fixes a
  23. regression or bug in a feature new to that release.
  24. If in doubt, prefer ``master``. Reviewers may simply ask for
  25. a rebase if deemed appropriate in particular cases.
  26. #. Create commits making incremental, distinct, logically complete changes
  27. with appropriate `commit messages`_.
  28. #. Push a topic branch to a personal repository fork on GitLab.
  29. #. Create a GitLab Merge Request targeting the upstream ``master`` branch
  30. (even if the change is intended for merge to the ``release`` branch).
  31. Check the box labelled "Allow commits from members who can merge to the
  32. target branch". This will allow maintainers to make minor edits on your
  33. behalf.
  34. The merge request will enter the `CMake Review Process`_ for consideration.
  35. .. _`Kitware's GitLab Instance`: https://gitlab.kitware.com
  36. .. _`CMake Repository`: https://gitlab.kitware.com/cmake/cmake
  37. .. _`Utilities/SetupForDevelopment.sh`: Utilities/SetupForDevelopment.sh
  38. .. _`CMake Source Code Guide`: Help/dev/source.rst
  39. .. _`commit messages`: Help/dev/review.rst#commit-messages
  40. .. _`CMake Review Process`: Help/dev/review.rst
  41. CMake Dashboard Client
  42. ======================
  43. The *integration testing* step of the `CMake Review Process`_ uses a set of
  44. testing machines that follow an integration branch on their own schedule to
  45. drive testing and submit results to the `CMake CDash Page`_. Anyone is
  46. welcome to provide testing machines in order to help keep support for their
  47. platforms working.
  48. See documentation on `CMake Testing Process`_ for more information.
  49. .. _`CMake CDash Page`: https://open.cdash.org/index.php?project=CMake
  50. .. _`CMake Testing Process`: Help/dev/testing.rst
  51. License
  52. =======
  53. We do not require any formal copyright assignment or contributor license
  54. agreement. Any contributions intentionally sent upstream are presumed
  55. to be offered under terms of the OSI-approved BSD 3-clause License.
  56. See `Copyright.txt`_ for details.
  57. .. _`Copyright.txt`: Copyright.txt