Hi everyone,

We switched to using Pull Requests for code reviews a few months back.
Clearly, there are some drawbacks to that model and we are trying to
address the shortcomings. I have gathered input from some of the committers
regarding what is missing the code review process and what can be improved.
Please take a look and provide feedback.

Additionally, we are considering moving to a KIP/FLIP-like model for
submitting design proposals (major changes to samza). Lately, there have
been some major feature discussions that are not documented consistently in
a centralized location. The proposal in SAMZA-1141
<https://issues.apache.org/jira/browse/SAMZA-1141> address the design
review process as well. Please review it too. I have already created a wiki
page
<https://cwiki.apache.org/confluence/display/SAMZA/Samza+Enhancement+Proposal>
describing the Samza Enhancement Proposal (SEP) process and an SEP
template. Going forward, let's start adding all major change proposals to
the wiki and discuss the design on the mailing list.

Your cooperation is highly appreciated during this period of transition in
the process :)

Feedbacks welcome!

Thanks!
-- 
Navina R

PS: Alternatives name suggestions for "SEP" are welcome !

Reply via email to