Contributions are very welcome. Specially roles. If you implement a role that you think others might be using, please contribute.
To contribute head to opps’s github page, fork it and create a pull request.
We strive to keep the internal quality of opps to the best that we can; Therefore, it’s very important to keep some things in mind when contributing with code for opps:
- Test everything you can, with automated tests. If possible, please develop code with TDD. If you’re having a hard time building tests, don’t hesitate to ask for help in the opps mailing list. We are happy to help you keep your code well-covered by tests;
- When writing actual code, follow the conventions in PEP 8 (except for maximum line length, which we don’t follow because there are too many parts of the project that require large strings to be used);
- When writing docstrings, follow the conventions in PEP 257
(take a look at other docstrings in the project to get a feel of how we organize them);
- Also, when writing docstrings for the API, provide examples of how that method or class works. Having a code example of a part of the API is really helpful for the user.
Software required in OS:
- Redis Server
- Image Lib
Check out the code from the github project:
git clone git://github.com/opps/opps.git cd opps
mkvirtualenv opps pip install -r requirements_dev.txt python setup.py develop
Here is how to run the test suite:
Here is how to build the documentation:
cd docs make html
The core team¶
The core team behind opps (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/opps/opps/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!