RE: [DISCUSS] SAMZA-1141 - Apache Samza Development Process Improvements

[Garry Turkington]

Very much in favour of the proposed SEP process -- strong +1 from me.

-Original Message-
From: Navina Ramesh (Apache) [mailto:nav...@apache.org] 
Sent: Tuesday, March 14, 2017 10:16 PM
To: dev@samza.apache.org
Subject: [DISCUSS] SAMZA-1141 - Apache Samza Development Process Improvements

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 !

-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7998 / Virus Database: 4756/14112 - Release Date: 03/13/17

Re: [DISCUSS] SAMZA-1141 - Apache Samza Development Process Improvements

[Navina Ramesh]

Xinyu,
I considered doing that as an example. But I want to keep SEP to be only
for technical discussions and not process related proposals.

Navina

On Mar 14, 2017 17:23, "xinyu liu"  wrote:

> +1 on this proposal too. Could you actually put this proposal as the first
> SEP (like SEP-0), so it serves an example of how it will look like in
> practice?
>
> Xinyu
>
> On Tue, Mar 14, 2017 at 3:34 PM, Navina Ramesh
>  > wrote:
>
> > Just to clarify: The proposal for code and design process change is
> > attached as a PDF/markdown to the JIRA - SAMZA-1141.
> >
> > Also, please show your support specifically for code and design process.
> My
> > bad for not calling it out earlier :)
> >
> > Thanks!
> > Navina
> >
> > On Tue, Mar 14, 2017 at 3:30 PM, Jagadish Venkatraman <
> > jagadish1...@gmail.com> wrote:
> >
> > > Thanks for writing this up.
> > >
> > > I'm +1 on this proposal.
> > >
> > >
> > >
> > > On Tue, Mar 14, 2017 at 3:15 PM, Navina Ramesh (Apache) <
> > nav...@apache.org
> > > >
> > > wrote:
> > >
> > > > 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
> > > >  address the
> design
> > > > review process as well. Please review it too. I have already created
> a
> > > wiki
> > > > page
> > > >  > > > 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 !
> > > >
> > >
> > >
> > >
> > > --
> > > Jagadish V,
> > > Graduate Student,
> > > Department of Computer Science,
> > > Stanford University
> > >
> >
> >
> >
> > --
> > Navina R.
> >
>

Re: [DISCUSS] SAMZA-1141 - Apache Samza Development Process Improvements

[xinyu liu]

+1 on this proposal too. Could you actually put this proposal as the first
SEP (like SEP-0), so it serves an example of how it will look like in
practice?

Xinyu

On Tue, Mar 14, 2017 at 3:34 PM, Navina Ramesh  wrote:

> Just to clarify: The proposal for code and design process change is
> attached as a PDF/markdown to the JIRA - SAMZA-1141.
>
> Also, please show your support specifically for code and design process. My
> bad for not calling it out earlier :)
>
> Thanks!
> Navina
>
> On Tue, Mar 14, 2017 at 3:30 PM, Jagadish Venkatraman <
> jagadish1...@gmail.com> wrote:
>
> > Thanks for writing this up.
> >
> > I'm +1 on this proposal.
> >
> >
> >
> > On Tue, Mar 14, 2017 at 3:15 PM, Navina Ramesh (Apache) <
> nav...@apache.org
> > >
> > wrote:
> >
> > > 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
> > >  address the design
> > > review process as well. Please review it too. I have already created a
> > wiki
> > > page
> > >  > > 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 !
> > >
> >
> >
> >
> > --
> > Jagadish V,
> > Graduate Student,
> > Department of Computer Science,
> > Stanford University
> >
>
>
>
> --
> Navina R.
>

Re: [DISCUSS] SAMZA-1141 - Apache Samza Development Process Improvements

[Navina Ramesh]

Just to clarify: The proposal for code and design process change is
attached as a PDF/markdown to the JIRA - SAMZA-1141.

Also, please show your support specifically for code and design process. My
bad for not calling it out earlier :)

Thanks!
Navina

On Tue, Mar 14, 2017 at 3:30 PM, Jagadish Venkatraman <
jagadish1...@gmail.com> wrote:

> Thanks for writing this up.
>
> I'm +1 on this proposal.
>
>
>
> On Tue, Mar 14, 2017 at 3:15 PM, Navina Ramesh (Apache)  >
> wrote:
>
> > 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
> >  address the design
> > review process as well. Please review it too. I have already created a
> wiki
> > page
> >  > 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 !
> >
>
>
>
> --
> Jagadish V,
> Graduate Student,
> Department of Computer Science,
> Stanford University
>



-- 
Navina R.

Re: [DISCUSS] SAMZA-1141 - Apache Samza Development Process Improvements

[Jagadish Venkatraman]

Thanks for writing this up.

I'm +1 on this proposal.



On Tue, Mar 14, 2017 at 3:15 PM, Navina Ramesh (Apache) 
wrote:

> 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
>  address the design
> review process as well. Please review it too. I have already created a wiki
> page
>  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 !
>



-- 
Jagadish V,
Graduate Student,
Department of Computer Science,
Stanford University