Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
Types of Contributions¶
Report bugs at https://github.com/goerz/trajectorydata/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.
Fix Bugs / Implement Features¶
Look through the GitHub issues for bugs or feature requests. Anybody is welcome to submit a pull request for open issues.
TrajectoryData could always use more documentation, whether as part of the official TrajectoryData 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/goerz/trajectorydata/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 :)
Ready to contribute? Follow Aaron Meurer’s Git Workflow Notes (with
goerz/trajectorydata instead of
- Clone the repository from
- Fork the repo on GitHub to your personal account.
- Add your fork as a remote.
- Pull in the latest changes from the master branch.
- Create a topic branch
- Make your changes and commit them (testing locally)
- Push changes to the topic branch on your remote
- Make a pull request against the base master branch through the Github website of your fork.
The project contains a
Makefile to help with development tasts. In your checked-out clone, do
$ make help
to see the available make targets.
It is strongly recommended that you use the conda package manager. The
Makefile relies on conda to create local testing and documentation building
make test and
Alternatively, you may use
make develop-test and
make develop-docs to
run the tests or generate the documentation within your active Python
environment. You will have to ensure that all the necessary dependencies are
installed. Also, you will not be able to test the package against all supported
You still can (and should) look at https://travis-ci.org/goerz/trajectorydata/ to check that your commits pass all tests.
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.
- Check https://travis-ci.org/goerz/trajectorydata/pull_requests and make sure that the tests pass for all supported Python versions.