Contributions are welcomed via pull requests on GitHub. Contact the HOOMD-blue developers before starting work to ensure it meshes well with the planned development direction and standards set for the project.
New features should be applicable to a variety of use-cases. The HOOMD-blue developers can assist you in designing flexible interfaces.
Expensive code paths should only execute when requested.
Write, test, and optimize your GPU kernels on the latest generation of GPUs.
- Base backwards compatible bug fixes on
trunk-patch. - Base additional functionality on
trunk-minor. - Base API incompatible changes on
trunk-major.
All changes in a pull request should be closely related. Multiple change sets that are loosely coupled should be proposed in separate pull requests.
All contributors must agree to the Contributor Agreement before their pull request can be merged.
The Code style section of the documentation sets the style guidelines for HOOMD-blue code.
Use doxygen header comments for classes, functions, etc. Also comment complex sections of code so that other developers can understand them.
Your changes should compile without warnings.
Add unit tests for all new functionality.
The developer should run research-scale simulations using the new functionality and ensure that it behaves as intended.
Document public-facing API with Python docstrings in Google style.
Add versionadded, versionchanged, and deprecated Sphinx directives to each user-facing Python class, method, etc., so that users will be aware of how functionality changes from version to version. Remove this when breaking APIs in major releases.
Update the credits documentation to list the name and affiliation of each individual that has contributed to the code.
Propose a concise entry describing the change in CHANGELOG.rst.