Perhaps the easiest way to contribute to Qtile is to report any bugs you run into on the github issue tracker.
Useful bug reports are ones that get bugs fixed. A useful bug report normally has two qualities:
- Reproducible. If your bug is not reproducible it will never get fixed. You should clearly mention the steps to reproduce the bug. Do not assume or skip any reproducing step. Described the issue, step-by-step, so that it is easy to reproduce and fix.
- Specific. Do not write a essay about the problem. Be Specific and to the point. Try to summarize the problem in minimum words yet in effective way. Do not combine multiple problems even they seem to be similar. Write different reports for each problem.
To get started writing code for Qtile, check out our guide to :doc:`hacking`.
Our workflow is based on Vincent Driessen's successful git branching model:
masterbranch is our current release
developbranch is what all pull requests should be based against
- Feature branches are where new features, both major and minor, should be developed.
.. seqdiag:: /_static/diagrams/git-branching-strategy.diag
We also request that git commit messages follow the standard format.
Submit a pull request
Pull requests are not considered complete until they include all of the following:
- Code that conforms to PEP8.
- Unit tests that pass locally and in our CI environment.
- Documentation updates on an as needed basis.
Feel free to add your contribution (no matter how small) to the appropriate place in the CHANGELOG as well!