Contributing to ControlsFX
Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
Do you have a new cool feature that you'd like to contribute? Or a fix for a bug? Great! The ControlsFX project loves code contributions, improvements, and bug fixes, but we require that they follow a set of guidelines and that they are contributed in a specific way.
Before accepting your pull requests, we ask that you please read and sign our CLA.
All code contributed to the ControlsFX project tree should follow Code Conventions for the Java Programming Language, and should be have no tabs. All the tabs should be replaced with spaces.
ControlsFX is released under the 3-clause BSD license. It is required that all source code files have this license at the top of the file. It is suggested that you copy/paste the license from another source file in the ControlsFX project. Be sure to edit the copyright date at the top. The correct syntax is:
- If the source file is new, the date should just be the current year.
- If you are editing an existing source file, the format should be , . For example, if the file was created in 2012, and it is currently 2014, it should say '2012, 2014'.
The chance of getting your pull request accepted increases considerably if you adhere to the following rules in addition to the aforementioned formatting standards:
- Ensure that all contributed files have a valid copyright statement and an open-source license.
- Do not bundle commits that are unrelated to each other -- create separate pull requests instead.
- Clean up the commit history. The change-set should be as minimal as possible.
- Write a descriptive pull request message. Explain the advantages and disadvantages of your proposed changes.
- Before starting to work on a major contribution, discuss your idea with existing ControlsFX contributors in our mailing list, to avoid wasting time on things that have no chance of getting merged into ControlsFX.