|
| 1 | +============ |
| 2 | +Contributing |
| 3 | +============ |
| 4 | + |
| 5 | +Contributions are welcome, and they are greatly appreciated! Every |
| 6 | +little bit helps, and credit will always be given. |
| 7 | + |
| 8 | +Types of Contributions |
| 9 | +---------------------- |
| 10 | + |
| 11 | +You can contribute in many ways: |
| 12 | + |
| 13 | +Report Bugs |
| 14 | +~~~~~~~~~~~ |
| 15 | + |
| 16 | +Report bugs at https://github.com/scikit-build/cmake-python-distributions/issues. |
| 17 | + |
| 18 | +If you are reporting a bug, please include: |
| 19 | + |
| 20 | +* Your operating system name and version. |
| 21 | +* Any details about your local setup that might be helpful in troubleshooting. |
| 22 | +* Detailed steps to reproduce the bug. |
| 23 | + |
| 24 | +Fix Bugs |
| 25 | +~~~~~~~~ |
| 26 | + |
| 27 | +Look through the GitHub issues for bugs. Anything tagged with "bug" |
| 28 | +is open to whoever wants to implement it. |
| 29 | + |
| 30 | +Implement Features |
| 31 | +~~~~~~~~~~~~~~~~~~ |
| 32 | + |
| 33 | +Look through the GitHub issues for features. Anything tagged with "feature" |
| 34 | +is open to whoever wants to implement it. |
| 35 | + |
| 36 | +Write Documentation |
| 37 | +~~~~~~~~~~~~~~~~~~~ |
| 38 | + |
| 39 | +The cmake-python-distributions project could always use more documentation. We welcome help |
| 40 | +with the official cmake-python-distributions docs, in docstrings, or even on blog posts and |
| 41 | +articles for the web. |
| 42 | + |
| 43 | +Submit Feedback |
| 44 | +~~~~~~~~~~~~~~~ |
| 45 | + |
| 46 | +The best way to send feedback is to file an issue at |
| 47 | +https://github.com/scikit-build/cmake-python-distributions/issues. |
| 48 | + |
| 49 | +If you are proposing a new feature: |
| 50 | + |
| 51 | +* Explain in detail how it would work. |
| 52 | +* Keep the scope as narrow as possible, to make it easier to implement. |
| 53 | +* Remember that this is a volunteer-driven project, and that contributions |
| 54 | + are welcome :) |
| 55 | + |
| 56 | + |
| 57 | +Get Started |
| 58 | +----------- |
| 59 | + |
| 60 | +Ready to contribute? Here's how to set up `cmake-python-distributions` for local development. |
| 61 | + |
| 62 | +1. Fork the `cmake-python-distributions` repo on GitHub. |
| 63 | +2. Clone your fork locally:: |
| 64 | + |
| 65 | + $ git clone [email protected]:your_name_here/cmake-python-distributions.git |
| 66 | + |
| 67 | +3. Install your local copy into a virtualenv. Assuming you have |
| 68 | + virtualenvwrapper installed (`pip install virtualenvwrapper`), this is how |
| 69 | + you set up your cloned fork for local development:: |
| 70 | + |
| 71 | + $ mkvirtualenv cmake-python-distributions |
| 72 | + $ cd cmake-python-distributions/ |
| 73 | + $ pip install -r requirements-dev.txt |
| 74 | + |
| 75 | +4. Create a branch for local development:: |
| 76 | + |
| 77 | + $ git checkout -b name-of-your-bugfix-or-feature |
| 78 | + |
| 79 | + Now you can make your changes locally. |
| 80 | + |
| 81 | +5. When you're done making changes, check that your changes pass flake8 and |
| 82 | + the tests:: |
| 83 | + |
| 84 | + $ flake8 |
| 85 | + $ python setup.py bdist_wheel |
| 86 | + $ python setup.py test |
| 87 | + |
| 88 | +6. Commit your changes and push your branch to GitHub:: |
| 89 | + |
| 90 | + $ git add . |
| 91 | + $ git commit -m "Your detailed description of your changes." |
| 92 | + $ git push origin name-of-your-bugfix-or-feature |
| 93 | + |
| 94 | +7. Submit a pull request through the GitHub website. |
| 95 | + |
| 96 | + |
| 97 | +Pull Request Guidelines |
| 98 | +----------------------- |
| 99 | + |
| 100 | +Before you submit a pull request, check that it meets these guidelines: |
| 101 | + |
| 102 | +1. The pull request should include tests. |
| 103 | + |
| 104 | +2. If the pull request adds functionality, the docs should be updated. Put |
| 105 | + your new functionality into a function with a docstring, and add the |
| 106 | + feature to the list in `README.rst`. |
| 107 | + |
| 108 | +3. The pull request should work for Python 2.7, and 3.3, 3.4, 3.5. |
| 109 | + Check `AppVeyor <https://ci.appveyor.com/project/scikit-build/cmake-python-distributions-f3rbb>`_, |
| 110 | + `CircleCI <https://circleci.com/gh/scikit-build/cmake-python-distributions>`_ |
| 111 | + and `TravisCi <https://travis-ci.org/scikit-build/cmake-python-distributions/pull_requests>`_ |
| 112 | + and make sure that the tests pass for all supported Python versions. |
| 113 | + |
| 114 | + |
| 115 | +Tips |
| 116 | +---- |
| 117 | + |
| 118 | +To run a subset of tests:: |
| 119 | + |
| 120 | + $ pytest tests/test_cmake.py |
0 commit comments