Bug reports and feature requests can be submitted to the Issue Tracker.
Some general guidelines to follow:
- Use an appropriate, descriptive title.
- Provide as many details as possible.
- Don't piggy-back. Keep separate topics in separate issues.
Patches are welcome. Keep your code consistent with the rest of the project. PEP8 is a good guide, but with the following specific exceptions to keep in mind for coding/linting:
- Tabs should be used for indentation of code.
- I don't have a set maximum line length. However, I do like to keep lines viewable in my editor when windowed (150).
Some linter errors may need to be ignored to accommodate these differences.
For simple, single file changes/additions, sending or linking your modified file is acceptable. For complex, multiple file changes, creating a diff file or using GitHub's Pull Request feature is preferable.
If you have any questions or concerns, contact me through the methods listed below.
You should create a separate feature branch in your fork to commit your changes to. Pull Requests will only be accepted if made from a feature branch and against the devel branch of this repository.
Commit messages should be written in a well-formed, consistent manner. See the commit log for acceptable examples.
Each commit should encompass the smallest logical changeset (e.g. changing two unrelated things in the same file would be two commits rather than one commit of "Change filename".) If you made a mistake in a commit in your Pull Request, you should amend or rebase to change your previous commit(s) then force push to the feature branch in your fork.
For anything else, contact me by e-mail at mail@thebigmunch.me or on IRC in #gmusicapi on irc.freenode.net