Re: [DISCUSS] Apache Beam podling graduation readiness

[Roman Shaposhnik]

On Sat, Dec 3, 2016 at 9:57 PM, Jean-Baptiste Onofré  wrote:
> Hi Roman,
>
> The affiliation for the proposed PMC members is:
>
> * Tyler Akidau : Google
> * Davor Bonaci : Google
> * Robert Bradshaw : Google
> * Ben Chambers : Google
> * Luke Cwik : Google
> * Stephan Ewen : dataArtisan
> * Dan Halperin : Google
> * Kenneth Knowles : Google
> * Aljoscha Krettek : dataArtisan
> * Maximilian Michels : dataArtisan
> * Jean-Baptiste Onofré : Talend
> * Frances Perry : Google
> * Amit Sela : PayPal
> * Josh Wills : Slack
>
> After discussing on our private mailing list, we are proposing Davor Bonaci
> as PMC Chair.
> I was really impressed by Davor commitment to build and extend the Beam
> community. He really understand the Apache way and we worked efficiently
> together. That's why I proposed Davor, and I think it's a obvious choice.
>
> I would like to mention that, I'm an active mentor on the podling, and I
> will highly active PMC member and committer on the TLP project.

Thanks -- that's very helpful information.

One last question -- at a quick glance you're the only ASF member on
the PMC, correct?

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Apache Beam podling graduation readiness

[Jean-Baptiste Onofré]

Hi Roman,

The affiliation for the proposed PMC members is:

* Tyler Akidau : Google
* Davor Bonaci : Google
* Robert Bradshaw : Google
* Ben Chambers : Google
* Luke Cwik : Google
* Stephan Ewen : dataArtisan
* Dan Halperin : Google
* Kenneth Knowles : Google
* Aljoscha Krettek : dataArtisan
* Maximilian Michels : dataArtisan
* Jean-Baptiste Onofré : Talend
* Frances Perry : Google
* Amit Sela : PayPal
* Josh Wills : Slack

After discussing on our private mailing list, we are proposing Davor 
Bonaci as PMC Chair.
I was really impressed by Davor commitment to build and extend the Beam 
community. He really understand the Apache way and we worked efficiently 
together. That's why I proposed Davor, and I think it's a obvious choice.


I would like to mention that, I'm an active mentor on the podling, and I 
will highly active PMC member and committer on the TLP project.


Regards
JB

On 12/04/2016 03:57 AM, Roman Shaposhnik wrote:

On Fri, Dec 2, 2016 at 11:36 AM, Davor Bonaci  wrote:

Hi everyone,
Apache Beam entered incubation in early February. Over the past 10 months,
the podling has made great progress across various areas: refactoring the
project to remove any special treatment given to a runner or a vendor,
building processes that encourage open development, evangelizing the
project, and growing the community.

Now, with the support of our mentors and overwhelming support from the
wider Beam community [1], I’d like start a discussion on the progress we
have made and a possible graduation recommendation as a new top-level
project.

To prepare for the discussion, we have published our self-assessment [2]
against the Apache Maturity Model. We tried to include links and evidence
whenever applicable. I’ll summarize the commonly asked questions here, but
please see the self-assessment for additional information, various details,
graphs, evidence, etc.


Releases?


Three -- all unanimously approved, all driven by different release
managers, across different organizations. A detailed release guide is
available on the website.


Community growth?


There has been a clear growth month-over-month. We have had 1500+ pull
requests on GitHub and 110+ individual code contributors. In terms of
mailing list activity, over the past 30 days, we have had 50+ individual
participants on dev@ and 35+ on user@.


Organizational influence?


We have worked hard to remove any special treatment given to any
organization. The bulk of the initial code donation came from Google, but
now both the project’s code and branding have a clean separation between
the project and Google Cloud Dataflow (which has become just one of many
runners that can be used within Beam).

While it is true that Googlers continue to provide the majority of commits,
over the last three months no single organization has had more than ~50% of
unique monthly contributors. (Please see the graph in the self-assessment.)
Diverse influences are also particularly clear when you look across modules
within the project. Beam has about ~22 large modules in the codebase, at
least 10 modules have been developed with little to no contribution from
Googlers.

Now, if we were to graduate, the Beam PPMC recommends the following
information for the Board resolution:
* Project name: Apache Beam
* Project description and scope: a unified programming model for both
batch and streaming data processing, enabling efficient execution across
diverse distributed execution engines and providing extensibility points
for connecting to different technologies and user communities.
* PMC composition:
 * Tyler Akidau 
 * Davor Bonaci 
 * Robert Bradshaw 
 * Ben Chambers 
 * Luke Cwik 
 * Stephan Ewen 
 * Dan Halperin 
 * Kenneth Knowles 
 * Aljoscha Krettek 
 * Maximilian Michels 
 * Jean-Baptiste Onofré 
 * Frances Perry 
 * Amit Sela 
 * Josh Wills 
(The ratification of the full text of the draft resolution is nearing
completion.)


Can you please provide current company affiliations of the proposed
PMC members?

Question #2: who are you proposing as a PMC chair?

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



--
Jean-Baptiste Onofré

Re: [DISCUSS] Apache Beam podling graduation readiness

[Frances Perry]

>
> > * PMC composition:
> >  * Tyler Akidau , Google
> >  * Davor Bonaci , Google
> >  * Robert Bradshaw , Google
> >  * Ben Chambers , Google
> >  * Luke Cwik , Google
> >  * Stephan Ewen , data Artisans
> >  * Dan Halperin , Google
> >  * Kenneth Knowles , Google
> >  * Aljoscha Krettek , data Artisans
> >  * Maximilian Michels , data Artisans
> >  * Jean-Baptiste Onofré , Talend
> >  * Frances Perry , Google
> >  * Amit Sela , PayPal
> >  * Josh Wills , Slack
>
> Can you please provide current company affiliations of the proposed
> PMC members?
>

(Added above)

If you include committers, that adds representation from DataTorrent and
Smoking Hand, reducing Google representation to 53%.


> Question #2: who are you proposing as a PMC chair?
>

Davor Bonaci

Re: [DISCUSS] Apache Beam podling graduation readiness

[Roman Shaposhnik]

On Fri, Dec 2, 2016 at 11:36 AM, Davor Bonaci  wrote:
> Hi everyone,
> Apache Beam entered incubation in early February. Over the past 10 months,
> the podling has made great progress across various areas: refactoring the
> project to remove any special treatment given to a runner or a vendor,
> building processes that encourage open development, evangelizing the
> project, and growing the community.
>
> Now, with the support of our mentors and overwhelming support from the
> wider Beam community [1], I’d like start a discussion on the progress we
> have made and a possible graduation recommendation as a new top-level
> project.
>
> To prepare for the discussion, we have published our self-assessment [2]
> against the Apache Maturity Model. We tried to include links and evidence
> whenever applicable. I’ll summarize the commonly asked questions here, but
> please see the self-assessment for additional information, various details,
> graphs, evidence, etc.
>
>> Releases?
>
> Three -- all unanimously approved, all driven by different release
> managers, across different organizations. A detailed release guide is
> available on the website.
>
>> Community growth?
>
> There has been a clear growth month-over-month. We have had 1500+ pull
> requests on GitHub and 110+ individual code contributors. In terms of
> mailing list activity, over the past 30 days, we have had 50+ individual
> participants on dev@ and 35+ on user@.
>
>> Organizational influence?
>
> We have worked hard to remove any special treatment given to any
> organization. The bulk of the initial code donation came from Google, but
> now both the project’s code and branding have a clean separation between
> the project and Google Cloud Dataflow (which has become just one of many
> runners that can be used within Beam).
>
> While it is true that Googlers continue to provide the majority of commits,
> over the last three months no single organization has had more than ~50% of
> unique monthly contributors. (Please see the graph in the self-assessment.)
> Diverse influences are also particularly clear when you look across modules
> within the project. Beam has about ~22 large modules in the codebase, at
> least 10 modules have been developed with little to no contribution from
> Googlers.
>
> Now, if we were to graduate, the Beam PPMC recommends the following
> information for the Board resolution:
> * Project name: Apache Beam
> * Project description and scope: a unified programming model for both
> batch and streaming data processing, enabling efficient execution across
> diverse distributed execution engines and providing extensibility points
> for connecting to different technologies and user communities.
> * PMC composition:
>  * Tyler Akidau 
>  * Davor Bonaci 
>  * Robert Bradshaw 
>  * Ben Chambers 
>  * Luke Cwik 
>  * Stephan Ewen 
>  * Dan Halperin 
>  * Kenneth Knowles 
>  * Aljoscha Krettek 
>  * Maximilian Michels 
>  * Jean-Baptiste Onofré 
>  * Frances Perry 
>  * Amit Sela 
>  * Josh Wills 
> (The ratification of the full text of the draft resolution is nearing
> completion.)

Can you please provide current company affiliations of the proposed
PMC members?

Question #2: who are you proposing as a PMC chair?

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Apache Beam podling graduation readiness

[Ted Dunning]

I have been very impressed with the efforts (and the success) of the Apache
Beam project in building community. This is definitely an example of Things
Done Right (tm).



On Sat, Dec 3, 2016 at 5:33 AM, Julian Hyde  wrote:

> The project looks to be ready to graduate. The traffic on the dev list
> shows a community that is in good shape. Thanks for completing the maturity
> assessment — it helped me assess the state of the project.
>
> Julian
>
>
> > On Dec 2, 2016, at 11:36 AM, Davor Bonaci  wrote:
> >
> > Hi everyone,
> > Apache Beam entered incubation in early February. Over the past 10
> months,
> > the podling has made great progress across various areas: refactoring the
> > project to remove any special treatment given to a runner or a vendor,
> > building processes that encourage open development, evangelizing the
> > project, and growing the community.
> >
> > Now, with the support of our mentors and overwhelming support from the
> > wider Beam community [1], I’d like start a discussion on the progress we
> > have made and a possible graduation recommendation as a new top-level
> > project.
> >
> > To prepare for the discussion, we have published our self-assessment [2]
> > against the Apache Maturity Model. We tried to include links and evidence
> > whenever applicable. I’ll summarize the commonly asked questions here,
> but
> > please see the self-assessment for additional information, various
> details,
> > graphs, evidence, etc.
> >
> >> Releases?
> >
> > Three -- all unanimously approved, all driven by different release
> > managers, across different organizations. A detailed release guide is
> > available on the website.
> >
> >> Community growth?
> >
> > There has been a clear growth month-over-month. We have had 1500+ pull
> > requests on GitHub and 110+ individual code contributors. In terms of
> > mailing list activity, over the past 30 days, we have had 50+ individual
> > participants on dev@ and 35+ on user@.
> >
> >> Organizational influence?
> >
> > We have worked hard to remove any special treatment given to any
> > organization. The bulk of the initial code donation came from Google, but
> > now both the project’s code and branding have a clean separation between
> > the project and Google Cloud Dataflow (which has become just one of many
> > runners that can be used within Beam).
> >
> > While it is true that Googlers continue to provide the majority of
> commits,
> > over the last three months no single organization has had more than ~50%
> of
> > unique monthly contributors. (Please see the graph in the
> self-assessment.)
> > Diverse influences are also particularly clear when you look across
> modules
> > within the project. Beam has about ~22 large modules in the codebase, at
> > least 10 modules have been developed with little to no contribution from
> > Googlers.
> >
> > Now, if we were to graduate, the Beam PPMC recommends the following
> > information for the Board resolution:
> >* Project name: Apache Beam
> >* Project description and scope: a unified programming model for both
> > batch and streaming data processing, enabling efficient execution across
> > diverse distributed execution engines and providing extensibility points
> > for connecting to different technologies and user communities.
> >* PMC composition:
> > * Tyler Akidau 
> > * Davor Bonaci 
> > * Robert Bradshaw 
> > * Ben Chambers 
> > * Luke Cwik 
> > * Stephan Ewen 
> > * Dan Halperin 
> > * Kenneth Knowles 
> > * Aljoscha Krettek 
> > * Maximilian Michels 
> > * Jean-Baptiste Onofré 
> > * Frances Perry 
> > * Amit Sela 
> > * Josh Wills 
> > (The ratification of the full text of the draft resolution is nearing
> > completion.)
> >
> > While we have made great progress across the board (thanks to so many of
> > you in this community), I’m sure there’s still plenty to do. We continue
> to
> > be focused on community growth, and processes that encourage open
> > development. Regardless of the outcome of this discussion, we’d love to
> get
> > specific feedback on what can be improved going forward.
> >
> > Any thoughts, comments, questions or concerns? Thank you.
> >
> > Davor
> >
> > [1]
> > https://lists.apache.org/thread.html/f133fb6bf2d1851d1bd5880c772e4b
> 050700154fa178fdb00a5b66bf@%3Cdev.beam.apache.org%3E
> > [2] http://beam.incubator.apache.org/contribute/maturity-model/
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: 

Re: [DISCUSS] Apache Beam podling graduation readiness

[Julian Hyde]

The project looks to be ready to graduate. The traffic on the dev list shows a 
community that is in good shape. Thanks for completing the maturity assessment 
— it helped me assess the state of the project.

Julian


> On Dec 2, 2016, at 11:36 AM, Davor Bonaci  wrote:
> 
> Hi everyone,
> Apache Beam entered incubation in early February. Over the past 10 months,
> the podling has made great progress across various areas: refactoring the
> project to remove any special treatment given to a runner or a vendor,
> building processes that encourage open development, evangelizing the
> project, and growing the community.
> 
> Now, with the support of our mentors and overwhelming support from the
> wider Beam community [1], I’d like start a discussion on the progress we
> have made and a possible graduation recommendation as a new top-level
> project.
> 
> To prepare for the discussion, we have published our self-assessment [2]
> against the Apache Maturity Model. We tried to include links and evidence
> whenever applicable. I’ll summarize the commonly asked questions here, but
> please see the self-assessment for additional information, various details,
> graphs, evidence, etc.
> 
>> Releases?
> 
> Three -- all unanimously approved, all driven by different release
> managers, across different organizations. A detailed release guide is
> available on the website.
> 
>> Community growth?
> 
> There has been a clear growth month-over-month. We have had 1500+ pull
> requests on GitHub and 110+ individual code contributors. In terms of
> mailing list activity, over the past 30 days, we have had 50+ individual
> participants on dev@ and 35+ on user@.
> 
>> Organizational influence?
> 
> We have worked hard to remove any special treatment given to any
> organization. The bulk of the initial code donation came from Google, but
> now both the project’s code and branding have a clean separation between
> the project and Google Cloud Dataflow (which has become just one of many
> runners that can be used within Beam).
> 
> While it is true that Googlers continue to provide the majority of commits,
> over the last three months no single organization has had more than ~50% of
> unique monthly contributors. (Please see the graph in the self-assessment.)
> Diverse influences are also particularly clear when you look across modules
> within the project. Beam has about ~22 large modules in the codebase, at
> least 10 modules have been developed with little to no contribution from
> Googlers.
> 
> Now, if we were to graduate, the Beam PPMC recommends the following
> information for the Board resolution:
>* Project name: Apache Beam
>* Project description and scope: a unified programming model for both
> batch and streaming data processing, enabling efficient execution across
> diverse distributed execution engines and providing extensibility points
> for connecting to different technologies and user communities.
>* PMC composition:
> * Tyler Akidau 
> * Davor Bonaci 
> * Robert Bradshaw 
> * Ben Chambers 
> * Luke Cwik 
> * Stephan Ewen 
> * Dan Halperin 
> * Kenneth Knowles 
> * Aljoscha Krettek 
> * Maximilian Michels 
> * Jean-Baptiste Onofré 
> * Frances Perry 
> * Amit Sela 
> * Josh Wills 
> (The ratification of the full text of the draft resolution is nearing
> completion.)
> 
> While we have made great progress across the board (thanks to so many of
> you in this community), I’m sure there’s still plenty to do. We continue to
> be focused on community growth, and processes that encourage open
> development. Regardless of the outcome of this discussion, we’d love to get
> specific feedback on what can be improved going forward.
> 
> Any thoughts, comments, questions or concerns? Thank you.
> 
> Davor
> 
> [1]
> https://lists.apache.org/thread.html/f133fb6bf2d1851d1bd5880c772e4b050700154fa178fdb00a5b66bf@%3Cdev.beam.apache.org%3E
> [2] http://beam.incubator.apache.org/contribute/maturity-model/


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[DISCUSS] Apache Beam podling graduation readiness

[Davor Bonaci]

Hi everyone,
Apache Beam entered incubation in early February. Over the past 10 months,
the podling has made great progress across various areas: refactoring the
project to remove any special treatment given to a runner or a vendor,
building processes that encourage open development, evangelizing the
project, and growing the community.

Now, with the support of our mentors and overwhelming support from the
wider Beam community [1], I’d like start a discussion on the progress we
have made and a possible graduation recommendation as a new top-level
project.

To prepare for the discussion, we have published our self-assessment [2]
against the Apache Maturity Model. We tried to include links and evidence
whenever applicable. I’ll summarize the commonly asked questions here, but
please see the self-assessment for additional information, various details,
graphs, evidence, etc.

> Releases?

Three -- all unanimously approved, all driven by different release
managers, across different organizations. A detailed release guide is
available on the website.

> Community growth?

There has been a clear growth month-over-month. We have had 1500+ pull
requests on GitHub and 110+ individual code contributors. In terms of
mailing list activity, over the past 30 days, we have had 50+ individual
participants on dev@ and 35+ on user@.

> Organizational influence?

We have worked hard to remove any special treatment given to any
organization. The bulk of the initial code donation came from Google, but
now both the project’s code and branding have a clean separation between
the project and Google Cloud Dataflow (which has become just one of many
runners that can be used within Beam).

While it is true that Googlers continue to provide the majority of commits,
over the last three months no single organization has had more than ~50% of
unique monthly contributors. (Please see the graph in the self-assessment.)
Diverse influences are also particularly clear when you look across modules
within the project. Beam has about ~22 large modules in the codebase, at
least 10 modules have been developed with little to no contribution from
Googlers.

Now, if we were to graduate, the Beam PPMC recommends the following
information for the Board resolution:
* Project name: Apache Beam
* Project description and scope: a unified programming model for both
batch and streaming data processing, enabling efficient execution across
diverse distributed execution engines and providing extensibility points
for connecting to different technologies and user communities.
* PMC composition:
 * Tyler Akidau 
 * Davor Bonaci 
 * Robert Bradshaw 
 * Ben Chambers 
 * Luke Cwik 
 * Stephan Ewen 
 * Dan Halperin 
 * Kenneth Knowles 
 * Aljoscha Krettek 
 * Maximilian Michels 
 * Jean-Baptiste Onofré 
 * Frances Perry 
 * Amit Sela 
 * Josh Wills 
(The ratification of the full text of the draft resolution is nearing
completion.)

While we have made great progress across the board (thanks to so many of
you in this community), I’m sure there’s still plenty to do. We continue to
be focused on community growth, and processes that encourage open
development. Regardless of the outcome of this discussion, we’d love to get
specific feedback on what can be improved going forward.

Any thoughts, comments, questions or concerns? Thank you.

Davor

[1]
https://lists.apache.org/thread.html/f133fb6bf2d1851d1bd5880c772e4b050700154fa178fdb00a5b66bf@%3Cdev.beam.apache.org%3E
[2] http://beam.incubator.apache.org/contribute/maturity-model/