Contributions are very welcome. Specially roles. If you implement a role that you think others might be using, please contribute.
To contribute head to provy’s github page, fork it and create a pull request.
We strive to keep the internal quality of provy to the best that we can; Therefore, it’s very important to keep some things in mind when contributing with code for provy:
$ mkvirtualenv provy
$ pip install -r REQUIREMENTS
$ make build
The command should run without accusing any error.
There are basically two commands we run, when developing.
When building code, you need to test it and check if the code format is OK with the conventions we use:
$ make build
This Makefile target essentially does these steps:
It’s also important to keep the codebase well documented. We use Sphinx to generate the documentation, which is also used when our docs go to Read The Docs.
To build the docs in your environment, in order to test it locally (this is very useful to see how your docs will look like when they are rolled out), first go to the provy/docs directory, then run:
$ make html
Some warnings may show up in the command output - you should listen to them, in order to spot possible documentation problems -.
The core team behind provy (in order of joining the project):
Other non-core members, but equally important, equally rocking, equally ass-kicking contributors can be seen in this list: https://github.com/python-provy/provy/network/members
There are also some more contributors that haven’t send code to the project, but who help in other ways, when and how they can. We’re very happy to have you, guys! :-)