Governance
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.
Pull Request is a process to merge changes from contributors into main code branch. First, contributors are supposed to fork main branch using their own github account. Then, they make some changes relevant to specific issue on the forked project. After committing to the project, they can initiate the pull request. After reviewing the pull request by committers, changes will be merged into main code branch. For more information, please refer to Using pull request and Fork a repo.
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.
| Name | Organization |
|---|---|
| Jun-Seok Heo | Samsung Electronics Co., Ltd. |
| Dongwoo Kim | Samsung Electronics Co., Ltd. |
| Jaehoon Ko | Samsung Electronics Co., Ltd. |
| Ohchan Kwon | Samsung Electronics Co., Ltd. |
| Robert B. Kim | Samsung Electronics Co., Ltd. |
| Dongkyoung Kim | Samsung Electronics Co., Ltd. |
To get started contributing to Spark CEP, learn how to contribute – anyone can submit patches, documentation and examples to the project. The one of committers can recommends new candidates from the active contributors, based on their contributions to Spark CEP. And the candidates are promoted by voting among all committers. The qualifications for new committers include:
-
Sustained contributions to Spark: Committers should have a history of major contributions to Spark CEP. An ideal committer will have contributed broadly throughout the project, and have contributed at least one major component where they have taken an "ownership" role. An ownership role means that existing contributors feel that they should run patches for this component by this person.
-
Quality of contributions: Committers more than any other community member should submit simple, well-tested, and well-designed patches. In addition, they should show sufficient expertise to be able to review patches, including making sure they fit within Spark CEP's engineering practices (testability, documentation, API stability, code style, etc). The committership is collectively responsible for the software quality and maintainability of Spark.
-
Community involvement: Committers should have a constructive and friendly attitude in all community interactions. They should also be active on the dev and user list and help mentor newer contributors and users. In design discussions, committers should maintain a professional and diplomatic approach, even in the face of disagreement.