Contributions to the fix-orchestra project are welcome. They must attributed to an issue and be consistent with the project roadmap. They should be submitted as pull request.
They must conform to code style standards. All contributed implementation code must be accompanied by unit tests that demonstrate the proposed enhancement or defect resolution.
The style standard for this project is Google Java Style
Code formatters for popular IDEs are available in project google/styleguide
The Checkstyle tool has a profile for Google style.
Classes with many attributes should follow the Fluent Interface style.
No dependency injection framework is used. Rather, when many attributes must be set to form a viable object, use a dedicated Builder with fluent interface and inject the Builder into the object's constructor.
Code should be generated in the generate-sources phase of the Maven build into folder target/generated-sources.