Bugfix Workflow

Bugfix Work Flow

This is a brief step by step description about a typical work flow of fixing a first Mixxx bug. Follow the links for more details.

Fork Mixxx on GitHub

The Mixxx repo is located here

https://help.github.com/articles/fork-a-repo

Create a Local Branch

Mixxx workflow with GitHub

Using Git for Mixxx Development

Build Mixxx

Choose a working environment

You can edit Mixxx's code in anything from a basic text editor to a professional IDE (Integrated Development Environment.) We've had good experiences with Eclipse, but some of our developers just use text editors that handle multiple files and support syntax highlighting such as Kate or Notepad++. If you're working from a text terminal, GNU Nano also supports syntax highlighting, though it's not quite as thorough as many of the graphical ones. See Developer Tools for more information.

Adopt an easy bug on Launchpad

List of bugs tagged as easy

More details you will find here: The Bug Tracker

Ask for hints and help

Ask your questions or discuss your ideas at

mixxx-devel (mailing list)
or at the Mixxx IRC Channel: #mixxx on Freenode

Fix it!

Happy coding :-)

And don't forget to ask if you get stuck!

Issue a pull request

https://help.github.com/articles/using-pull-requests

You can open a pull request before your code is ready to be merged with Mixxx to show others your code and ask for help, just make sure to say that your code is not ready for merging when you open the pull request.

Fix issues from code review

This is the most annoying part. Because we are sometimes nit pickers ;-) Don't take it personally if there are a lot of changes requested. Code review is important to make sure that Mixxx continues to run reliably and quickly. It is also important so that Mixxx remains maintainable so we can keep making it better without having to make huge changes.

Be sure that you code follows the Mixxx coding guidelines to avoid extra work.