All contributions are very welcome! You can contribute in many ways:
Join the python code quality mailing list and answer questions.
Report bugs on the GitHub issue tracker.
Submit pull requests on the GitHub repository. Ideally make a pull request to the develop branch, as I prefer to keep the master branch the same as the most recent release on PyPI. If you do this, be sure to add yourself to the CONTRIBUTORS.md file too!
As a code quality testing tool, it makes sense to strive to be a good example of good code! To that end, prospector is checked by Landscape and ideally when making a pull request, please take note of any decreases in quality.
Additionally, there is a pre-commit configuration to prevent various small problems before they are committed. Check the site for more information but the short version is to install it first before committing:
There are not a huge number of tests right now, as most of the code in Prospector is handling the output of other tools. However, please do run them before submitting a pull request:
Prospector targets Python 3.6, 3.7, 3.8, 3.9 and 3.10. You can use tox to test this locally, and all tests are run on github Actions.
Abdullah Hilson (@abumalick)
Adam Hodges (@ajhodges)
Amir Rachum (@Nurdok)
Angel Blasco (@alblasco)
Anthony Ricaud (@rik)
Bryce Guinta (@brycepg)
Carl Crowder (@carlio)
Carlos Coêlho (@chocoelho)
Carlos Cruz (@ccruz09)
Claudiu Popa (@PCManticore)
David J Pugh (@djpugh)
Eric Brown (@ericwb)
Florian Bruhin (@The-Compiler)
Ian Lee (@IanLee1521)
Ian Stapleton Cordasco (@sigmavirus24)
Joe Wallis (@Peilonrayz)
Jon Parise (@jparise)
Kristian Glass (@doismellburning)
Luke Hinds (@lukehinds)
Matt Seymour (@mattseymour)
Michael Tinsley (@michaeltinsley)
Phil Frost (@bitglue)
Phil Jones (@pgjones)
Pierre Sassoulas (@Pierre-Sassoulas)
Shachar Ohana (@shacharoo)
Stéphane Brunner (@sbrunner)
Steven Myint (@myint)
Yaroslav Kurlaev (@ykurlaev)