Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Types of Contributions¶
Report bugs at https://github.com/mms-fcul/pypka/issues.
If you are reporting a bug, please include:
Your operating system name and version.
PypKa’s version and parameters used for the calculation
Origin of the input structure: Protein Data Bank or simulation (please specify the FF)
Look through the GitHub issues for bugs. Anything tagged with “bug” and “help wanted” is open to whoever wants to implement it.
Look through the GitHub issues for features. Anything tagged with “enhancement” and “help wanted” is open to whoever wants to implement it.
PypKa could always use more documentation, whether as part of the official PypKa docs, in docstrings, or even on the web in blog posts, articles, and such.
The best way to send feedback is to file an issue at https://github.com/mms-fcul/pypka/issues.
If you are proposing a feature:
Explain in detail how it would work.
Keep the scope as narrow as possible, to make it easier to implement.
Ready to contribute? Here’s how to set up pypka for local development.
Fork the pypka repo on GitHub.
Clone your fork locally:
$ git clone firstname.lastname@example.org:your_name_here/pypka.git
Install your local copy into a virtualenv. Assuming you have pipenv installed, this is how you set up your fork for local development:
$ cd pypka/ $ pipenv install pypka
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 the tests:
$ make tests
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.
Pull Request Guidelines¶
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. Put your new functionality into a function with a docstring, and add the feature to the list in README.rst.
The pull request should work for Python 3.5, 3.6, 3.7 and 3.8, and for PyPy.
A reminder for the maintainers on how to deploy. Make sure all your changes are committed. Then run:
$ bump2version patch # possible: major / minor / patch $ git push $ git push --tags