THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
This page describes a proposed Samza Enhancement Proposal (SEP) process for proposing a major change to Apache Samza.
To create a SEP, click on "Create" at the top of Header and select "SEP Template" from the dialog to create a new page.
Why SEP ?
The purpose of SEP is to collate and document all planned major enhancement to Apache Samza. JIRA is still the tool for tracking bugs and progress, SEP give an accessible overview of the design proposal, discussions and final acceptance status of the proposal. SEP, in other words, is nothing but a central location for all design documents in Apache Samza.
...
We will be following the Apache voting guideline to drive our decisions regarding an SEP. Decisions will be made on the [VOTE] mailing thread for a particular SEP. All community members are encouraged to participate by replying to the VOTE mailing thread. The votes can have the following meaning:
| Vote | Meaning |
|---|---|
| +1 | 'Yes,' 'Agree,' or 'the action should be performed.' |
| 0 | Neutral about the proposed action (or mildly negative but not enough so to want to block it |
| -1 | This is a negative vote. On issues where consensus is required, this vote counts as a veto. All vetoes must contain an explanation of why the veto is appropriate. Vetoes with no explanation are void. It may also be appropriate for a -1 vote to include an alternative course of action. |
The criteria for acceptance of a SEP is lazy majority.
...
Here is the process for making a SEP:
1. Create a page which is a child of this one. Take the next available SEP number and give your proposal a descriptive heading. e.g. "SEP 73: Samza Standalone with ZK Coordination". If you don't have the necessary permissions for creating a new page, please ask on the development dev mailing list (dev@samza.apache.org).
2. Fill in the sections as described above.
3. Start a [DISCUSS] thread on the Apache mailing list. Please ensure that the subject of the thread is of the format [DISCUSS] SEP-{your SEP number} {your SEP heading} The discussion should happen on the mailing list and *not* on the wiki since the wiki comment system doesn't work well for larger discussions. In the process of the discussion you may update the proposal. You should let people know the changes you are making.
4. Once the proposal is finalized call a [VOTE] to have the proposal adopted. These proposals are more serious than code changes and more serious even than release votes. The criteria for acceptance is lazy majority.
5. **Please** update the SEP wiki page, and the index below, to reflect the current stage of the SEP after a vote. This acts as the permanent record indicating the result of the SEP (e.g., Accepted or Rejected). Also report the result of the SEP vote to the voting thread on the mailing list so the conclusion is clear.
SEP Number
Next SEP Number: 133
Use this number as the identifier for your FLIP SEP and increment this value.
SEP Index
...
| SEP |
|---|
...
| Status |
|---|
...
...