|
| 1 | +Contributing to Python |
| 2 | +====================== |
| 3 | + |
| 4 | +Build Status |
| 5 | +------------ |
| 6 | + |
| 7 | +- master |
| 8 | + |
| 9 | + + `Stable buildbots<http://buildbot.python.org/3.x.stable/>`_ |
| 10 | + |
| 11 | +- 3.6 |
| 12 | + |
| 13 | + + `Stable buildbots<http://buildbot.python.org/3.6.stable/>`_ |
| 14 | + |
| 15 | +- 3.5 |
| 16 | + |
| 17 | + + `Stable buildbots<http://buildbot.python.org/3.5.stable/>`_ |
| 18 | + |
| 19 | +- 2.7 |
| 20 | + |
| 21 | + + `Stable buildbots<http://buildbot.python.org/2.7.stable/>`_ |
| 22 | + |
| 23 | + |
| 24 | +Contribution Guidelines |
| 25 | +----------------------- |
| 26 | +Please read the `devguide<https://cpython-devguide.readthedocs.io/>`_ for |
| 27 | +guidance on how to contribute to this project. The documentation covers |
| 28 | +everything from how to build the code to submitting a pull request. There are |
| 29 | +also suggestions on how you can most effectively help the project. |
| 30 | + |
| 31 | +Please be aware that our workflow does deviate slightly from the typical GitHub |
| 32 | +project. Issues are tracked at https://bugs.python.org/ and should be mentioned |
| 33 | +in pull requests using the format of ``bpo-12345`` . If your pull request is in |
| 34 | +response to a specific issue then please mention it in the title, |
| 35 | +e.g. “bpo-12345: fix comment in tokenizer.c”. |
| 36 | + |
| 37 | +If you are making a code contribution or large documentation contribution, |
| 38 | +please feel free to add yourself to the ``Misc/ACKS`` file alphabetically. |
| 39 | + |
| 40 | + |
| 41 | +Code of Conduct |
| 42 | +--------------- |
| 43 | +All interactions for this project are covered by the |
| 44 | +`PSF Code of Conduct<https://www.python.org/psf/codeofconduct/>`_. Everyone is |
| 45 | +expected to be open, considerate, and respectful of others no matter their |
| 46 | +position within the project. |