Contributing to Paho

Thanks for your interest in this project!

You can contribute bugfixes and new features by sending pull requests through GitHub.


In order for your contribution to be accepted, it must comply with the Eclipse Foundation IP policy.

Please read the Eclipse Foundation policy on accepting contributions via Git.

  1. Sign the Eclipse CLA
  2. Register for an Eclipse Foundation User ID. You can register here.
  3. Log into the Projects Portal, and click on the ‘Eclipse CLA’ link.
  4. Go to your account settings and add your GitHub username to your account.
  5. Make sure that you sign-off your Git commits in the following format: Signed-off-by: John Smith <> This is usually at the bottom of the commit message. You can automate this by adding the ‘-s’ flag when you make the commits. e.g. git commit -s -m "Adding a cool feature"
  6. Ensure that the email address that you make your commits with is the same one you used to sign up to the Eclipse Foundation website with.

Contributing a change

  1. Fork the repository on GitHub
  2. Clone the forked repository onto your computer: git clone<your username>/paho.mqtt.c.git
  3. Create a new branch from the latest develop branch with git checkout -b YOUR_BRANCH_NAME origin/develop
  4. Make your changes
  5. If developing a new feature, make sure to include JUnit tests.
  6. Ensure that all new and existing tests pass.
  7. Commit the changes into the branch: git commit -s Make sure that your commit message is meaningful and describes your changes correctly.
  8. If you have a lot of commits for the change, squash them into a single / few commits.
  9. Push the changes in your branch to your forked repository.
  10. Finally, go to and create a pull request from your “YOUR_BRANCH_NAME” branch to the develop one to request review and merge of the commits in your pushed branch.

What happens next depends on the content of the patch. If it is 100% authored by the contributor and is less than 1000 lines (and meets the needs of the project), then it can be pulled into the main repository. If not, more steps are required. These are detailed in the legal process poster.

Developer resources:

Information regarding source code management, builds, coding standards, and more.


Contact the project developers via the project's development mailing list.

Search for bugs:

This project uses GitHub Issues here: to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!