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/elfi-dev/elfi/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.
Look through the GitHub issues for features. Anything tagged with “enhancement” and “help wanted” is open to whoever wants to implement it.
ELFI could always use more documentation, whether as part of the official ELFI 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/elfi-dev/elfi/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.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
ELFI is a project with dozens of collaborators, so organization is key to making our contributions effective and avoid reword. Thus, in addition to the recommendations below we strongly recommend reading our Wiki to see what is the suggested git workflow procedure for your type of contribution.
Ready to contribute? Here’s how to set up ELFI for local development.
Fork the elfi repo on GitHub.
Clone your fork locally:
$ git clone email@example.com:your_name_here/elfi.git
$ conda -V $ python -V
Install your local copy and the development requirements into a conda environment. You may need to replace “3.6” in the first line with the python version printed in the previous step:
$ conda create -n elfi python=3.6 numpy $ source activate elfi $ cd elfi $ make dev
Create a branch for local development:
$ git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
Follow the Style Guidelines
When you’re done making changes, check that your changes pass flake8 and the tests:
$ make lint $ make test
You may run
make test-notslowinstead of
make testas long as your proposed changes are unrelated to BOLFI.
Also make sure that the docstrings of your code are formatted properly:
$ make docs
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.
The Python code in ELFI mostly follows PEP8, which is considered the de-facto code style guide for Python. Lines should not exceed 100 characters.
Docstrings follow the NumPy style.
Pull Request Guidelines¶
Before you submit a pull request, check that it meets these guidelines:
- The pull request should include tests that will be run automatically using Travis-CI.
- 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.6 and later. Check https://travis-ci.org/elfi-dev/elfi/pull_requests and make sure that the tests pass for all supported Python versions.
To run a subset of tests:
$ py.test tests.test_elfi