Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways.
Report bugs at https://github.com/metinsay/docluster/issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Look through the GitHub issues for bugs. Anything tagged with "bug" and "help wanted" is open to whoever wants to implement it.
NOTE: Please check out Code Style before you start implementing.
After setting up your local repo of docluster
with Get Started, these are the things you can choose to do:
- Create a new
Model
(See model implementation). - Improve a
Model
that already exists in docluster. Perform the changes and send a pull request. - Contribute to any other core features (Contact maintainers).
The best way to send feedback is to file an issue at https://github.com/metinsay/docluster/issues.
Ready to contribute? Here's how to set up docluster
for local development.
-
Fork the
docluster
repo on GitHub. -
Clone your fork locally
$ git clone [email protected]:your_name_here/docluster.git
-
Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development.
$ mkvirtualenv docluster $ cd docluster/ $ python3 setup.py develop
-
Create a branch for local development.
$ git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
-
When you're done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox.
$ flake8 docluster tests $ python setup.py test or py.test $ tox
To get
flake8
andtox
, just pip install them into your virtualenv. -
Commit your changes and push your branch to GitHub.
$ git add . $ git commit -m "Your detailed description of your changes." $ git push origin name-of-your-bugfix-or-feature
-
Submit a pull request through the GitHub website.
Before you submit a pull request, check that it meets these guidelines:
- The pull request should include tests.
- If the pull request adds functionality, the docs should be updated.
- The pull request should work for Python 2.6, 2.7, 3.3, 3.4 and 3.5, and for PyPy. Check https://travis-ci.org/metinsay/docluster/pull_requests and make sure that the tests pass for all supported Python versions.