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.7 12 13 + `Stable buildbots <http://buildbot.python.org/3.7.stable/>`_ 14 15 - 3.6 16 17 + `Stable buildbots <http://buildbot.python.org/3.6.stable/>`_ 18 19 - 2.7 20 21 + `Stable buildbots <http://buildbot.python.org/2.7.stable/>`_ 22 23 24 Thank You 25 --------- 26 First off, thanks for contributing to the maintenance of the Python programming 27 language and the CPython interpreter! Even if your contribution is not 28 ultimately accepted, the fact you put time and effort into helping out is 29 greatly appreciated. 30 31 32 Contribution Guidelines 33 ----------------------- 34 Please read the `devguide <https://devguide.python.org/>`_ for 35 guidance on how to contribute to this project. The documentation covers 36 everything from how to build the code to submitting a pull request. There are 37 also suggestions on how you can most effectively help the project. 38 39 Please be aware that our workflow does deviate slightly from the typical GitHub 40 project. Details on how to properly submit a pull request are covered in 41 `Lifecycle of a Pull Request <https://devguide.python.org/pullrequest/>`_. 42 We utilize various bots and status checks to help with this, so do follow the 43 comments they leave and their "Details" links, respectively. The key points of 44 our workflow that are not covered by a bot or status check are: 45 46 - All discussions that are not directly related to the code in the pull request 47 should happen on bugs.python.org 48 - Upon your first non-trivial pull request (which includes documentation changes), 49 feel free to add yourself to ``Misc/ACKS`` 50 51 52 Setting Expectations 53 -------------------- 54 Due to the fact that this project is entirely volunteer-run (i.e. no one is paid 55 to work on Python full-time), we unfortunately can make no guarantees as to if 56 or when a core developer will get around to reviewing your pull request. 57 If no core developer has done a review or responded to changes made because of a 58 "changes requested" review, please feel free to email python-dev to ask if 59 someone could take a look at your pull request. 60 61 62 Code of Conduct 63 --------------- 64 All interactions for this project are covered by the 65 `PSF Code of Conduct <https://www.python.org/psf/codeofconduct/>`_. Everyone is 66 expected to be open, considerate, and respectful of others no matter their 67 position within the project. 68