CONTRIBUTING.rst 3.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  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 git configuration.
  20. #. See `Building CMake`_ for building CMake locally.
  21. #. See the `CMake Source Code Guide`_ for coding guidelines.
  22. #. Create a topic branch named suitably for your work.
  23. Base all new work on the upstream ``master`` branch.
  24. Base work on the upstream ``release`` branch only if it fixes a
  25. regression or bug in a feature new to that release.
  26. If in doubt, prefer ``master``. Reviewers may simply ask for
  27. a rebase if deemed appropriate in particular cases.
  28. #. Create commits making incremental, distinct, logically complete changes
  29. with appropriate `commit messages`_.
  30. #. Push the topic branch to a personal repository fork on GitLab.
  31. #. Create a GitLab Merge Request targeting the upstream ``master`` branch
  32. (even if the change is intended for merge to the ``release`` branch).
  33. Check the box labelled "Allow commits from members who can merge to the
  34. target branch". This will allow maintainers to make minor edits on your
  35. behalf.
  36. The merge request will enter the `CMake Review Process`_ for consideration.
  37. .. _`Kitware's GitLab Instance`: https://gitlab.kitware.com
  38. .. _`CMake Repository`: https://gitlab.kitware.com/cmake/cmake
  39. .. _`Utilities/SetupForDevelopment.sh`: Utilities/SetupForDevelopment.sh
  40. .. _`Building CMake`: README.rst#building-cmake
  41. .. _`CMake Source Code Guide`: Help/dev/source.rst
  42. .. _`commit messages`: Help/dev/review.rst#commit-messages
  43. .. _`CMake Review Process`: Help/dev/review.rst
  44. CMake Dashboard Client
  45. ======================
  46. The *integration testing* step of the `CMake Review Process`_ uses a set of
  47. testing machines that follow an integration branch on their own schedule to
  48. drive testing and submit results to the `CMake CDash Page`_. Anyone is
  49. welcome to provide testing machines in order to help keep support for their
  50. platforms working.
  51. See documentation on `CMake Testing Process`_ for more information.
  52. .. _`CMake CDash Page`: https://open.cdash.org/index.php?project=CMake
  53. .. _`CMake Testing Process`: Help/dev/testing.rst
  54. License
  55. =======
  56. We do not require any formal copyright assignment or contributor license
  57. agreement. Any contributions intentionally sent upstream are presumed
  58. to be offered under terms of the OSI-approved BSD 3-clause License.
  59. See `Copyright.txt`_ for details.
  60. .. _`Copyright.txt`: Copyright.txt