How to Contribute

Contributing to Spark-CEP doesn't just mean writing code. Testing releases, and improving documentation are also welcome. In fact, proposing significant code changes usually requires first gaining experience and credibility within the community by helping in other ways. This is also a guide to becoming an effective contributor.

Review Process

Spark-CEP development changes to the code are approved through consensus. We use a review-then-commit model, where at least one committer other than the patch author has to review and approve it before it gets merged, and any committer may vote against it. For certain modules, changes to the architecture and public API should also be reviewed by a committer for that module (which may or may not be the same as the main reviewer) before being merged.