Contributing

This page is used as a starting point for contributing to the development of gazebo-yarp-plugins.

If you would like to contribute to the development of gazebo-yarp-plugins, please get in contact with the development team using GitHub issues.

The easiest way to contribute is to pick an issue and try to solve it. A list of issues a new developer can work on is available under the Volunteer needed tag.

If you need a new feature or to fix a bug, please fill a GitHub issue describing the feature or the bugfix you would like to implement.

Code style

We adopt a consistent code style. If you want to contribute to this project, we kindly ask you to conform to the code style guidelines.

We do not enforce the style (at least at the current stage) but we will probably offer scripts to ease the process in the future.

More precisely, we try to use the WebKit coding style (see WebKit page).

Patches and features contribution

The contribution follows the classical GitHub stages:

• open an issue (so we can discuss the problem and possible solutions);
• develop the changes;
• fork the project and submit the pull request.

Repository structure and releases management.

This part is mainly targeted to ''internal'' members.

Development of new features follows the GitHub Flow ( also know as Feature Branch Workflow ).

In a nutshell, development of new features/bugfixes happens in separated branch. When you believe your contribution is stable you can open a pull request against master, where your code will be review by other contributors prior to merging it.