If you want to contribute to Mopidy, here are some tips to get you started.
Please get in touch with us in one of these ways when requesting help with Mopidy and its extensions:
Before asking for help, it might be worth your time to read the Troubleshooting page, both so you might find a solution to your problem but also to be able to provide useful details when asking for help.
If you want to contribute to Mopidy, a great place to start is by helping other users on IRC and in the discussion forum. This is a contribution we value highly. As more people help with user support, new users get faster and better help. For your own benefit, you’ll quickly learn what users find confusing, difficult or lacking, giving you some ideas for where you may contribute improvements, either to code or documentation. Lastly, this may also free up time for other contributors to spend more time on fixing bugs or implementing new features.
Before spending any time on making a pull request:
Create a new branch, based on the develop branch, for every feature or bug fix. Keep branches small and on topic, as that makes them far easier to review. We often use the following naming convention for branches:
Follow the code style, especially make sure the flake8 linter does not complain about anything. Travis CI will check that your pull request is “flake8 clean”. See Style checking and linting.
Include tests for any new feature or substantial bug fix. See Running tests.
Include documentation for any new feature. See Writing documentation.
Feel free to include a changelog entry in your pull request. The changelog is in docs/changelog.rst.
Write good commit messages.
For more inspiration, feel free to read these blog posts:
Send a pull request to the develop branch. See the GitHub pull request docs for help.