Skip to content

Latest commit

 

History

History
45 lines (20 loc) · 2.13 KB

CONTRIBUTING.md

File metadata and controls

45 lines (20 loc) · 2.13 KB

How to contribute to D3A

Did you find a bug?

  • Ensure the bug was not already reported by searching on GitHub under Issues.

  • If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.

Did you write a patch that fixes a bug?

  • Open a new GitHub pull request with the patch.

  • Ensure the Pull Request description clearly describes the problem and solution. Include the relevant issue number if applicable.

Did you fix whitespace, format code, or make a purely cosmetic patch?

Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of the D3A will generally not be accepted.

Do you intend to add a new feature or change an existing one?

  • Suggest your change in an email to [email protected]

  • Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and fixes.

Do you have questions about the source code or the functionality of D3A?

License

By contributing to D3A, you agree that your contributions will be licensed under the GPLv3 License.

Each contributor has to sign our Contributor License Agreement. The purpose of the CLA is to ensure that the guardian of a project's outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen license. You can read and sign our full Contributor License Agreement before submitting a pull request.

Thanks!

D3A Team