You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Davor Bonaci <da...@apache.org> on 2016/12/02 19:36:26 UTC

[DISCUSS] Apache Beam podling graduation readiness

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 <ta...@apache.org>
         * Davor Bonaci <da...@apache.org>
         * Robert Bradshaw <ro...@apache.org>
         * Ben Chambers <bc...@apache.org>
         * Luke Cwik <lc...@apache.org>
         * Stephan Ewen <se...@apache.org>
         * Dan Halperin <dh...@apache.org>
         * Kenneth Knowles <ke...@apache.org>
         * Aljoscha Krettek <al...@apache.org>
         * Maximilian Michels <mx...@apache.org>
         * Jean-Baptiste Onofré <jb...@apache.org>
         * Frances Perry <fr...@apache.org>
         * Amit Sela <am...@apache.org>
         * Josh Wills <jw...@apache.org>
(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/

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Davor Bonaci <da...@google.com.INVALID>.
>
> I hate to be a PITA about it, but can you merge
> http://beam.incubator.apache.org/contribute/team/ into
> http://incubator.apache.org/projects/beam.html?
>

Done.

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by "John D. Ament" <jo...@apache.org>.
On Sun, Dec 4, 2016 at 11:13 AM Frances Perry <fj...@google.com.invalid>
wrote:

> In addition, since its not called out on your project page, which of these
> > are current PPMC members and which are just committers?  Everyone is
> listed
> > as committer on http://incubator.apache.org/projects/beam.html .
>
>
> You can find the PPMC/committer distinction on the Beam site:
> http://beam.incubator.apache.org/contribute/team/


Perfect responses on everything below.  Sounds good.

I hate to be a PITA about it, but can you merge
http://beam.incubator.apache.org/contribute/team/ into
http://incubator.apache.org/projects/beam.html ?  This way we have a clear
call out about who is on the PPMC right now.


>
>
> I'm a bit
> > worried about the "private/indirectly" comment made somewhere else (not
> > mixing public/private emails...)
>
>
> There are folks on the PPMC who were not active during incubation and have
> chosen to decline going forwards. I believe Davor's "private/indirect"
> comment referred to an offline discussion I had. There was an original PPMC
> member who never even signed up for the Beam mailing lists. I wanted to
> make sure he was aware call for folks to opt in to the resolution, so I
> told him in person to make sure he didn't miss a chance to respond in the
> affirmative.
>
>
> > If you include committers, that adds representation from DataTorrent and
> > > Smoking Hand, reducing Google representation to 53%.
> > >
> > >
> > I feel like this number.. the fact that it's being counted is a bit odd.
> > While we want to make sure the community is diverse, I would be hesitant
> to
> > add people just because it counters Google's direct influence on the
> > project.  Even if Google only makes up 20% of a proposed PMC, if it's
> > housing 90% of the active developers on the project that would still
> give a
> > single company higher influence.
> >
>
> I calculated this number for Beam when it came up during Geode's graduation
> discussion as something this group may pay attention to. Just trying to
> save folks the effort of digging it up themselves if interested ;-)
>
> I totally agree that affiliation is not a reason to add someone. But I do
> think that this is a sign of increasing diversity within the project when
> new folks from other projects and companies continue to get involved and
> make significant contributions.
>

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Frances Perry <fj...@google.com.INVALID>.
In addition, since its not called out on your project page, which of these
> are current PPMC members and which are just committers?  Everyone is listed
> as committer on http://incubator.apache.org/projects/beam.html .


You can find the PPMC/committer distinction on the Beam site:
http://beam.incubator.apache.org/contribute/team/

I'm a bit
> worried about the "private/indirectly" comment made somewhere else (not
> mixing public/private emails...)


There are folks on the PPMC who were not active during incubation and have
chosen to decline going forwards. I believe Davor's "private/indirect"
comment referred to an offline discussion I had. There was an original PPMC
member who never even signed up for the Beam mailing lists. I wanted to
make sure he was aware call for folks to opt in to the resolution, so I
told him in person to make sure he didn't miss a chance to respond in the
affirmative.


> If you include committers, that adds representation from DataTorrent and
> > Smoking Hand, reducing Google representation to 53%.
> >
> >
> I feel like this number.. the fact that it's being counted is a bit odd.
> While we want to make sure the community is diverse, I would be hesitant to
> add people just because it counters Google's direct influence on the
> project.  Even if Google only makes up 20% of a proposed PMC, if it's
> housing 90% of the active developers on the project that would still give a
> single company higher influence.
>

I calculated this number for Beam when it came up during Geode's graduation
discussion as something this group may pay attention to. Just trying to
save folks the effort of digging it up themselves if interested ;-)

I totally agree that affiliation is not a reason to add someone. But I do
think that this is a sign of increasing diversity within the project when
new folks from other projects and companies continue to get involved and
make significant contributions.

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by "John D. Ament" <jo...@gmail.com>.
Hi JB

It seems like podlings aren't tracking PPMC vs committers right now, at
least not consistently.  I did find one podling who does have it listed -
http://incubator.apache.org/projects/metron.html

Is the list of the "committers" as per
http://incubator.apache.org/projects/beam.html equivalent to the current
PPMC?  I'm wondering, looking at the make up of PMC vs who's in the
committers list, why don't they want to be on the PMC?

John

On Sun, Dec 4, 2016 at 9:52 AM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:

> Hi John,
>
> Not sure I fully understand you. What do you mean ?
>
> The proposed PMC members are already PPMC on the podling.
>
> Regards
> JB
>
> On 12/04/2016 02:47 PM, John D. Ament wrote:
> > My gut says graduate, however I have one comment below.
> >
> > On Sat, Dec 3, 2016 at 10:42 PM Frances Perry <fr...@apache.org>
> wrote:
> >
> >>>
> >>>>     * PMC composition:
> >>>>          * Tyler Akidau <ta...@apache.org>, Google
> >>>>          * Davor Bonaci <da...@apache.org>, Google
> >>>>          * Robert Bradshaw <ro...@apache.org>, Google
> >>>>          * Ben Chambers <bc...@apache.org>, Google
> >>>>          * Luke Cwik <lc...@apache.org>, Google
> >>>>          * Stephan Ewen <se...@apache.org>, data Artisans
> >>>>          * Dan Halperin <dh...@apache.org>, Google
> >>>>          * Kenneth Knowles <ke...@apache.org>, Google
> >>>>          * Aljoscha Krettek <al...@apache.org>, data Artisans
> >>>>          * Maximilian Michels <mx...@apache.org>, data Artisans
> >>>>          * Jean-Baptiste Onofré <jb...@apache.org>, Talend
> >>>>          * Frances Perry <fr...@apache.org>, Google
> >>>>          * Amit Sela <am...@apache.org>, PayPal
> >>>>          * Josh Wills <jw...@apache.org>, Slack
> >>>
> >>> Can you please provide current company affiliations of the proposed
> >>> PMC members?
> >>>
> >>
> >
> > In addition, since its not called out on your project page, which of
> these
> > are current PPMC members and which are just committers?  Everyone is
> listed
> > as committer on http://incubator.apache.org/projects/beam.html .  I'm a
> bit
> > worried about the "private/indirectly" comment made somewhere else (not
> > mixing public/private emails...)
> >
> >
> >
> >>
> >> (Added above)
> >>
> >> If you include committers, that adds representation from DataTorrent and
> >> Smoking Hand, reducing Google representation to 53%.
> >>
> >>
> > I feel like this number.. the fact that it's being counted is a bit odd.
> > While we want to make sure the community is diverse, I would be hesitant
> to
> > add people just because it counters Google's direct influence on the
> > project.  Even if Google only makes up 20% of a proposed PMC, if it's
> > housing 90% of the active developers on the project that would still
> give a
> > single company higher influence.
> >
> >
> >>
> >>> Question #2: who are you proposing as a PMC chair?
> >>>
> >>
> >> Davor Bonaci
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi John,

Not sure I fully understand you. What do you mean ?

The proposed PMC members are already PPMC on the podling.

Regards
JB

On 12/04/2016 02:47 PM, John D. Ament wrote:
> My gut says graduate, however I have one comment below.
>
> On Sat, Dec 3, 2016 at 10:42 PM Frances Perry <fr...@apache.org> wrote:
>
>>>
>>>>     * PMC composition:
>>>>          * Tyler Akidau <ta...@apache.org>, Google
>>>>          * Davor Bonaci <da...@apache.org>, Google
>>>>          * Robert Bradshaw <ro...@apache.org>, Google
>>>>          * Ben Chambers <bc...@apache.org>, Google
>>>>          * Luke Cwik <lc...@apache.org>, Google
>>>>          * Stephan Ewen <se...@apache.org>, data Artisans
>>>>          * Dan Halperin <dh...@apache.org>, Google
>>>>          * Kenneth Knowles <ke...@apache.org>, Google
>>>>          * Aljoscha Krettek <al...@apache.org>, data Artisans
>>>>          * Maximilian Michels <mx...@apache.org>, data Artisans
>>>>          * Jean-Baptiste Onofr� <jb...@apache.org>, Talend
>>>>          * Frances Perry <fr...@apache.org>, Google
>>>>          * Amit Sela <am...@apache.org>, PayPal
>>>>          * Josh Wills <jw...@apache.org>, Slack
>>>
>>> Can you please provide current company affiliations of the proposed
>>> PMC members?
>>>
>>
>
> In addition, since its not called out on your project page, which of these
> are current PPMC members and which are just committers?  Everyone is listed
> as committer on http://incubator.apache.org/projects/beam.html .  I'm a bit
> worried about the "private/indirectly" comment made somewhere else (not
> mixing public/private emails...)
>
>
>
>>
>> (Added above)
>>
>> If you include committers, that adds representation from DataTorrent and
>> Smoking Hand, reducing Google representation to 53%.
>>
>>
> I feel like this number.. the fact that it's being counted is a bit odd.
> While we want to make sure the community is diverse, I would be hesitant to
> add people just because it counters Google's direct influence on the
> project.  Even if Google only makes up 20% of a proposed PMC, if it's
> housing 90% of the active developers on the project that would still give a
> single company higher influence.
>
>
>>
>>> Question #2: who are you proposing as a PMC chair?
>>>
>>
>> Davor Bonaci
>>
>

-- 
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by "John D. Ament" <jo...@apache.org>.
My gut says graduate, however I have one comment below.

On Sat, Dec 3, 2016 at 10:42 PM Frances Perry <fr...@apache.org> wrote:

> >
> > >     * PMC composition:
> > >          * Tyler Akidau <ta...@apache.org>, Google
> > >          * Davor Bonaci <da...@apache.org>, Google
> > >          * Robert Bradshaw <ro...@apache.org>, Google
> > >          * Ben Chambers <bc...@apache.org>, Google
> > >          * Luke Cwik <lc...@apache.org>, Google
> > >          * Stephan Ewen <se...@apache.org>, data Artisans
> > >          * Dan Halperin <dh...@apache.org>, Google
> > >          * Kenneth Knowles <ke...@apache.org>, Google
> > >          * Aljoscha Krettek <al...@apache.org>, data Artisans
> > >          * Maximilian Michels <mx...@apache.org>, data Artisans
> > >          * Jean-Baptiste Onofré <jb...@apache.org>, Talend
> > >          * Frances Perry <fr...@apache.org>, Google
> > >          * Amit Sela <am...@apache.org>, PayPal
> > >          * Josh Wills <jw...@apache.org>, Slack
> >
> > Can you please provide current company affiliations of the proposed
> > PMC members?
> >
>

In addition, since its not called out on your project page, which of these
are current PPMC members and which are just committers?  Everyone is listed
as committer on http://incubator.apache.org/projects/beam.html .  I'm a bit
worried about the "private/indirectly" comment made somewhere else (not
mixing public/private emails...)



>
> (Added above)
>
> If you include committers, that adds representation from DataTorrent and
> Smoking Hand, reducing Google representation to 53%.
>
>
I feel like this number.. the fact that it's being counted is a bit odd.
While we want to make sure the community is diverse, I would be hesitant to
add people just because it counters Google's direct influence on the
project.  Even if Google only makes up 20% of a proposed PMC, if it's
housing 90% of the active developers on the project that would still give a
single company higher influence.


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

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Frances Perry <fr...@apache.org>.
>
> >     * PMC composition:
> >          * Tyler Akidau <ta...@apache.org>, Google
> >          * Davor Bonaci <da...@apache.org>, Google
> >          * Robert Bradshaw <ro...@apache.org>, Google
> >          * Ben Chambers <bc...@apache.org>, Google
> >          * Luke Cwik <lc...@apache.org>, Google
> >          * Stephan Ewen <se...@apache.org>, data Artisans
> >          * Dan Halperin <dh...@apache.org>, Google
> >          * Kenneth Knowles <ke...@apache.org>, Google
> >          * Aljoscha Krettek <al...@apache.org>, data Artisans
> >          * Maximilian Michels <mx...@apache.org>, data Artisans
> >          * Jean-Baptiste Onofré <jb...@apache.org>, Talend
> >          * Frances Perry <fr...@apache.org>, Google
> >          * Amit Sela <am...@apache.org>, PayPal
> >          * Josh Wills <jw...@apache.org>, 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

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Roman,

Stephan (Ewen) is also ASF member.

Regards
JB

On 12/04/2016 07:20 AM, Roman Shaposhnik wrote:
> On Sat, Dec 3, 2016 at 9:57 PM, Jean-Baptiste Onofr� <jb...@nanthrax.net> wrote:
>> Hi Roman,
>>
>> The affiliation for the proposed PMC members is:
>>
>> * Tyler Akidau <ta...@apache.org>: Google
>> * Davor Bonaci <da...@apache.org>: Google
>> * Robert Bradshaw <ro...@apache.org>: Google
>> * Ben Chambers <bc...@apache.org>: Google
>> * Luke Cwik <lc...@apache.org>: Google
>> * Stephan Ewen <se...@apache.org>: dataArtisan
>> * Dan Halperin <dh...@apache.org>: Google
>> * Kenneth Knowles <ke...@apache.org>: Google
>> * Aljoscha Krettek <al...@apache.org>: dataArtisan
>> * Maximilian Michels <mx...@apache.org>: dataArtisan
>> * Jean-Baptiste Onofr� <jb...@apache.org>: Talend
>> * Frances Perry <fr...@apache.org>: Google
>> * Amit Sela <am...@apache.org>: PayPal
>> * Josh Wills <jw...@apache.org>: 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-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

-- 
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Daniel Gruno <hu...@apache.org>.
On 12/04/2016 07:20 AM, Roman Shaposhnik wrote:
> On Sat, Dec 3, 2016 at 9:57 PM, Jean-Baptiste Onofr� <jb...@nanthrax.net> wrote:
>> Hi Roman,
>>
>> The affiliation for the proposed PMC members is:
>>
>> * Tyler Akidau <ta...@apache.org>: Google
>> * Davor Bonaci <da...@apache.org>: Google
>> * Robert Bradshaw <ro...@apache.org>: Google
>> * Ben Chambers <bc...@apache.org>: Google
>> * Luke Cwik <lc...@apache.org>: Google
>> * Stephan Ewen <se...@apache.org>: dataArtisan
>> * Dan Halperin <dh...@apache.org>: Google
>> * Kenneth Knowles <ke...@apache.org>: Google
>> * Aljoscha Krettek <al...@apache.org>: dataArtisan
>> * Maximilian Michels <mx...@apache.org>: dataArtisan
>> * Jean-Baptiste Onofr� <jb...@apache.org>: Talend
>> * Frances Perry <fr...@apache.org>: Google
>> * Amit Sela <am...@apache.org>: PayPal
>> * Josh Wills <jw...@apache.org>: 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?

sewen also - phonebook ftw! ;)

> 
> Thanks,
> Roman.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 


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

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Daniel Kulp <dk...@apache.org>.
> On Dec 4, 2016, at 1:20 AM, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
> 
> 
> Thanks -- that's very helpful information.
> 
> One last question -- at a quick glance you're the only ASF member on
> the PMC, correct?

I’m also following Beam closely (and have submitted several pull requests working toward becoming a committer).   Thus, there are at least 3 ASF members (with Stephan) that will be “keeping an eye on things”.    :)  That shouldn’t be a concern.


-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


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

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Sat, Dec 3, 2016 at 9:57 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi Roman,
>
> The affiliation for the proposed PMC members is:
>
> * Tyler Akidau <ta...@apache.org>: Google
> * Davor Bonaci <da...@apache.org>: Google
> * Robert Bradshaw <ro...@apache.org>: Google
> * Ben Chambers <bc...@apache.org>: Google
> * Luke Cwik <lc...@apache.org>: Google
> * Stephan Ewen <se...@apache.org>: dataArtisan
> * Dan Halperin <dh...@apache.org>: Google
> * Kenneth Knowles <ke...@apache.org>: Google
> * Aljoscha Krettek <al...@apache.org>: dataArtisan
> * Maximilian Michels <mx...@apache.org>: dataArtisan
> * Jean-Baptiste Onofré <jb...@apache.org>: Talend
> * Frances Perry <fr...@apache.org>: Google
> * Amit Sela <am...@apache.org>: PayPal
> * Josh Wills <jw...@apache.org>: 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-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Roman,

The affiliation for the proposed PMC members is:

* Tyler Akidau <ta...@apache.org>: Google
* Davor Bonaci <da...@apache.org>: Google
* Robert Bradshaw <ro...@apache.org>: Google
* Ben Chambers <bc...@apache.org>: Google
* Luke Cwik <lc...@apache.org>: Google
* Stephan Ewen <se...@apache.org>: dataArtisan
* Dan Halperin <dh...@apache.org>: Google
* Kenneth Knowles <ke...@apache.org>: Google
* Aljoscha Krettek <al...@apache.org>: dataArtisan
* Maximilian Michels <mx...@apache.org>: dataArtisan
* Jean-Baptiste Onofr� <jb...@apache.org>: Talend
* Frances Perry <fr...@apache.org>: Google
* Amit Sela <am...@apache.org>: PayPal
* Josh Wills <jw...@apache.org>: 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 <da...@apache.org> 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\u2019d 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\u2019ll 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\u2019s 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 <ta...@apache.org>
>>          * Davor Bonaci <da...@apache.org>
>>          * Robert Bradshaw <ro...@apache.org>
>>          * Ben Chambers <bc...@apache.org>
>>          * Luke Cwik <lc...@apache.org>
>>          * Stephan Ewen <se...@apache.org>
>>          * Dan Halperin <dh...@apache.org>
>>          * Kenneth Knowles <ke...@apache.org>
>>          * Aljoscha Krettek <al...@apache.org>
>>          * Maximilian Michels <mx...@apache.org>
>>          * Jean-Baptiste Onofr� <jb...@apache.org>
>>          * Frances Perry <fr...@apache.org>
>>          * Amit Sela <am...@apache.org>
>>          * Josh Wills <jw...@apache.org>
>> (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-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

-- 
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Fri, Dec 2, 2016 at 11:36 AM, Davor Bonaci <da...@apache.org> 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 <ta...@apache.org>
>          * Davor Bonaci <da...@apache.org>
>          * Robert Bradshaw <ro...@apache.org>
>          * Ben Chambers <bc...@apache.org>
>          * Luke Cwik <lc...@apache.org>
>          * Stephan Ewen <se...@apache.org>
>          * Dan Halperin <dh...@apache.org>
>          * Kenneth Knowles <ke...@apache.org>
>          * Aljoscha Krettek <al...@apache.org>
>          * Maximilian Michels <mx...@apache.org>
>          * Jean-Baptiste Onofré <jb...@apache.org>
>          * Frances Perry <fr...@apache.org>
>          * Amit Sela <am...@apache.org>
>          * Josh Wills <jw...@apache.org>
> (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-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Ted Dunning <te...@gmail.com>.
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 <jh...@apache.org> 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 <da...@apache.org> 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 <ta...@apache.org>
> >         * Davor Bonaci <da...@apache.org>
> >         * Robert Bradshaw <ro...@apache.org>
> >         * Ben Chambers <bc...@apache.org>
> >         * Luke Cwik <lc...@apache.org>
> >         * Stephan Ewen <se...@apache.org>
> >         * Dan Halperin <dh...@apache.org>
> >         * Kenneth Knowles <ke...@apache.org>
> >         * Aljoscha Krettek <al...@apache.org>
> >         * Maximilian Michels <mx...@apache.org>
> >         * Jean-Baptiste Onofré <jb...@apache.org>
> >         * Frances Perry <fr...@apache.org>
> >         * Amit Sela <am...@apache.org>
> >         * Josh Wills <jw...@apache.org>
> > (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-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Julian Hyde <jh...@apache.org>.
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 <da...@apache.org> 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 <ta...@apache.org>
>         * Davor Bonaci <da...@apache.org>
>         * Robert Bradshaw <ro...@apache.org>
>         * Ben Chambers <bc...@apache.org>
>         * Luke Cwik <lc...@apache.org>
>         * Stephan Ewen <se...@apache.org>
>         * Dan Halperin <dh...@apache.org>
>         * Kenneth Knowles <ke...@apache.org>
>         * Aljoscha Krettek <al...@apache.org>
>         * Maximilian Michels <mx...@apache.org>
>         * Jean-Baptiste Onofré <jb...@apache.org>
>         * Frances Perry <fr...@apache.org>
>         * Amit Sela <am...@apache.org>
>         * Josh Wills <jw...@apache.org>
> (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-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Davor Bonaci <da...@google.com.INVALID>.
(Not to leave the thread hanging -- all this has been done previously.)

On Fri, Dec 9, 2016 at 8:08 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:

> Davor, congrants on the votes passing.
>
> It is customary to conclude the vote (especially a more official one like
> this)
> with a summary email with a subject:
>     [RESULT][VOTE]...
> giving the tally of everyone who voted. Please consider doing that.
>
> Thanks,
> Roman.
>
> On Thu, Dec 8, 2016 at 3:34 PM, Davor Bonaci <da...@apache.org> wrote:
> > Since the discussion seems to have concluded and the formal vote has
> passed
> > unanimously [1], I'll submit the draft resolution to the Board for their
> > consideration (per graduation guide [2]).
> >
> > Thanks everyone!
> >
> > [1]
> > https://lists.apache.org/thread.html/71a1c63837a7d1506a10af9c70af1c
> 24db988451ac5b53fa2467b9b8@%3Cgeneral.incubator.apache.org%3E
> > [2]
> > http://incubator.apache.org/guides/graduation.html#top-
> level-board-proposal
> >
> > On Mon, Dec 5, 2016 at 10:13 AM, Davor Bonaci <da...@apache.org> wrote:
> >
> >> Since it seems we have a consensus, I'm going to start a formal vote.
> >>
> >> Please keep the discussion going, and vote only after you feel ready.
> >> (Regardless of the outcome, we’d love to hear specific feedback on what
> can
> >> be improved going forward.)
> >>
> >> On Sun, Dec 4, 2016 at 11:16 PM, Sergio Fernández <wi...@apache.org>
> >> wrote:
> >>
> >>> Out of personal technical interests, I've been following the podling
> quite
> >>> close.
> >>> They have made en enormous effort, both on the technical and community
> >>> sides.
> >>> I strongly believe the project is ready for graduation.
> >>>
> >>> On Fri, Dec 2, 2016 at 8:36 PM, Davor Bonaci <da...@apache.org> 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 <ta...@apache.org>
> >>> >          * Davor Bonaci <da...@apache.org>
> >>> >          * Robert Bradshaw <ro...@apache.org>
> >>> >          * Ben Chambers <bc...@apache.org>
> >>> >          * Luke Cwik <lc...@apache.org>
> >>> >          * Stephan Ewen <se...@apache.org>
> >>> >          * Dan Halperin <dh...@apache.org>
> >>> >          * Kenneth Knowles <ke...@apache.org>
> >>> >          * Aljoscha Krettek <al...@apache.org>
> >>> >          * Maximilian Michels <mx...@apache.org>
> >>> >          * Jean-Baptiste Onofré <jb...@apache.org>
> >>> >          * Frances Perry <fr...@apache.org>
> >>> >          * Amit Sela <am...@apache.org>
> >>> >          * Josh Wills <jw...@apache.org>
> >>> > (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/
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> Sergio Fernández
> >>> Partner Technology Manager
> >>> Redlink GmbH
> >>> m: +43 6602747925
> >>> e: sergio.fernandez@redlink.co
> >>> w: http://redlink.co
> >>>
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
Davor, congrants on the votes passing.

It is customary to conclude the vote (especially a more official one like this)
with a summary email with a subject:
    [RESULT][VOTE]...
giving the tally of everyone who voted. Please consider doing that.

Thanks,
Roman.

On Thu, Dec 8, 2016 at 3:34 PM, Davor Bonaci <da...@apache.org> wrote:
> Since the discussion seems to have concluded and the formal vote has passed
> unanimously [1], I'll submit the draft resolution to the Board for their
> consideration (per graduation guide [2]).
>
> Thanks everyone!
>
> [1]
> https://lists.apache.org/thread.html/71a1c63837a7d1506a10af9c70af1c24db988451ac5b53fa2467b9b8@%3Cgeneral.incubator.apache.org%3E
> [2]
> http://incubator.apache.org/guides/graduation.html#top-level-board-proposal
>
> On Mon, Dec 5, 2016 at 10:13 AM, Davor Bonaci <da...@apache.org> wrote:
>
>> Since it seems we have a consensus, I'm going to start a formal vote.
>>
>> Please keep the discussion going, and vote only after you feel ready.
>> (Regardless of the outcome, we’d love to hear specific feedback on what can
>> be improved going forward.)
>>
>> On Sun, Dec 4, 2016 at 11:16 PM, Sergio Fernández <wi...@apache.org>
>> wrote:
>>
>>> Out of personal technical interests, I've been following the podling quite
>>> close.
>>> They have made en enormous effort, both on the technical and community
>>> sides.
>>> I strongly believe the project is ready for graduation.
>>>
>>> On Fri, Dec 2, 2016 at 8:36 PM, Davor Bonaci <da...@apache.org> 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 <ta...@apache.org>
>>> >          * Davor Bonaci <da...@apache.org>
>>> >          * Robert Bradshaw <ro...@apache.org>
>>> >          * Ben Chambers <bc...@apache.org>
>>> >          * Luke Cwik <lc...@apache.org>
>>> >          * Stephan Ewen <se...@apache.org>
>>> >          * Dan Halperin <dh...@apache.org>
>>> >          * Kenneth Knowles <ke...@apache.org>
>>> >          * Aljoscha Krettek <al...@apache.org>
>>> >          * Maximilian Michels <mx...@apache.org>
>>> >          * Jean-Baptiste Onofré <jb...@apache.org>
>>> >          * Frances Perry <fr...@apache.org>
>>> >          * Amit Sela <am...@apache.org>
>>> >          * Josh Wills <jw...@apache.org>
>>> > (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/
>>> >
>>>
>>>
>>>
>>> --
>>> Sergio Fernández
>>> Partner Technology Manager
>>> Redlink GmbH
>>> m: +43 6602747925
>>> e: sergio.fernandez@redlink.co
>>> w: http://redlink.co
>>>
>>
>>

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

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Sergio Fernández <wi...@apache.org>.
Cool! Great work, guys!

On Fri, Dec 9, 2016 at 12:34 AM, Davor Bonaci <da...@apache.org> wrote:

> Since the discussion seems to have concluded and the formal vote has passed
> unanimously [1], I'll submit the draft resolution to the Board for their
> consideration (per graduation guide [2]).
>
> Thanks everyone!
>
> [1]
> https://lists.apache.org/thread.html/71a1c63837a7d1506a10af9c70af1c
> 24db988451ac5b53fa2467b9b8@%3Cgeneral.incubator.apache.org%3E
> [2]
> http://incubator.apache.org/guides/graduation.html#top-
> level-board-proposal
>
> On Mon, Dec 5, 2016 at 10:13 AM, Davor Bonaci <da...@apache.org> wrote:
>
> > Since it seems we have a consensus, I'm going to start a formal vote.
> >
> > Please keep the discussion going, and vote only after you feel ready.
> > (Regardless of the outcome, we’d love to hear specific feedback on what
> can
> > be improved going forward.)
> >
> > On Sun, Dec 4, 2016 at 11:16 PM, Sergio Fernández <wi...@apache.org>
> > wrote:
> >
> >> Out of personal technical interests, I've been following the podling
> quite
> >> close.
> >> They have made en enormous effort, both on the technical and community
> >> sides.
> >> I strongly believe the project is ready for graduation.
> >>
> >> On Fri, Dec 2, 2016 at 8:36 PM, Davor Bonaci <da...@apache.org> 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 <ta...@apache.org>
> >> >          * Davor Bonaci <da...@apache.org>
> >> >          * Robert Bradshaw <ro...@apache.org>
> >> >          * Ben Chambers <bc...@apache.org>
> >> >          * Luke Cwik <lc...@apache.org>
> >> >          * Stephan Ewen <se...@apache.org>
> >> >          * Dan Halperin <dh...@apache.org>
> >> >          * Kenneth Knowles <ke...@apache.org>
> >> >          * Aljoscha Krettek <al...@apache.org>
> >> >          * Maximilian Michels <mx...@apache.org>
> >> >          * Jean-Baptiste Onofré <jb...@apache.org>
> >> >          * Frances Perry <fr...@apache.org>
> >> >          * Amit Sela <am...@apache.org>
> >> >          * Josh Wills <jw...@apache.org>
> >> > (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/
> >> >
> >>
> >>
> >>
> >> --
> >> Sergio Fernández
> >> Partner Technology Manager
> >> Redlink GmbH
> >> m: +43 6602747925
> >> e: sergio.fernandez@redlink.co
> >> w: http://redlink.co
> >>
> >
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Davor Bonaci <da...@apache.org>.
Since the discussion seems to have concluded and the formal vote has passed
unanimously [1], I'll submit the draft resolution to the Board for their
consideration (per graduation guide [2]).

Thanks everyone!

[1]
https://lists.apache.org/thread.html/71a1c63837a7d1506a10af9c70af1c24db988451ac5b53fa2467b9b8@%3Cgeneral.incubator.apache.org%3E
[2]
http://incubator.apache.org/guides/graduation.html#top-level-board-proposal

On Mon, Dec 5, 2016 at 10:13 AM, Davor Bonaci <da...@apache.org> wrote:

> Since it seems we have a consensus, I'm going to start a formal vote.
>
> Please keep the discussion going, and vote only after you feel ready.
> (Regardless of the outcome, we’d love to hear specific feedback on what can
> be improved going forward.)
>
> On Sun, Dec 4, 2016 at 11:16 PM, Sergio Fernández <wi...@apache.org>
> wrote:
>
>> Out of personal technical interests, I've been following the podling quite
>> close.
>> They have made en enormous effort, both on the technical and community
>> sides.
>> I strongly believe the project is ready for graduation.
>>
>> On Fri, Dec 2, 2016 at 8:36 PM, Davor Bonaci <da...@apache.org> 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 <ta...@apache.org>
>> >          * Davor Bonaci <da...@apache.org>
>> >          * Robert Bradshaw <ro...@apache.org>
>> >          * Ben Chambers <bc...@apache.org>
>> >          * Luke Cwik <lc...@apache.org>
>> >          * Stephan Ewen <se...@apache.org>
>> >          * Dan Halperin <dh...@apache.org>
>> >          * Kenneth Knowles <ke...@apache.org>
>> >          * Aljoscha Krettek <al...@apache.org>
>> >          * Maximilian Michels <mx...@apache.org>
>> >          * Jean-Baptiste Onofré <jb...@apache.org>
>> >          * Frances Perry <fr...@apache.org>
>> >          * Amit Sela <am...@apache.org>
>> >          * Josh Wills <jw...@apache.org>
>> > (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/
>> >
>>
>>
>>
>> --
>> Sergio Fernández
>> Partner Technology Manager
>> Redlink GmbH
>> m: +43 6602747925
>> e: sergio.fernandez@redlink.co
>> w: http://redlink.co
>>
>
>

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Davor Bonaci <da...@apache.org>.
Since it seems we have a consensus, I'm going to start a formal vote.

Please keep the discussion going, and vote only after you feel ready.
(Regardless of the outcome, we’d love to hear specific feedback on what can
be improved going forward.)

On Sun, Dec 4, 2016 at 11:16 PM, Sergio Fernández <wi...@apache.org> wrote:

> Out of personal technical interests, I've been following the podling quite
> close.
> They have made en enormous effort, both on the technical and community
> sides.
> I strongly believe the project is ready for graduation.
>
> On Fri, Dec 2, 2016 at 8:36 PM, Davor Bonaci <da...@apache.org> 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 <ta...@apache.org>
> >          * Davor Bonaci <da...@apache.org>
> >          * Robert Bradshaw <ro...@apache.org>
> >          * Ben Chambers <bc...@apache.org>
> >          * Luke Cwik <lc...@apache.org>
> >          * Stephan Ewen <se...@apache.org>
> >          * Dan Halperin <dh...@apache.org>
> >          * Kenneth Knowles <ke...@apache.org>
> >          * Aljoscha Krettek <al...@apache.org>
> >          * Maximilian Michels <mx...@apache.org>
> >          * Jean-Baptiste Onofré <jb...@apache.org>
> >          * Frances Perry <fr...@apache.org>
> >          * Amit Sela <am...@apache.org>
> >          * Josh Wills <jw...@apache.org>
> > (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/
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>

Re: [DISCUSS] Apache Beam podling graduation readiness

Posted by Sergio Fernández <wi...@apache.org>.
Out of personal technical interests, I've been following the podling quite
close.
They have made en enormous effort, both on the technical and community
sides.
I strongly believe the project is ready for graduation.

On Fri, Dec 2, 2016 at 8:36 PM, Davor Bonaci <da...@apache.org> 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 <ta...@apache.org>
>          * Davor Bonaci <da...@apache.org>
>          * Robert Bradshaw <ro...@apache.org>
>          * Ben Chambers <bc...@apache.org>
>          * Luke Cwik <lc...@apache.org>
>          * Stephan Ewen <se...@apache.org>
>          * Dan Halperin <dh...@apache.org>
>          * Kenneth Knowles <ke...@apache.org>
>          * Aljoscha Krettek <al...@apache.org>
>          * Maximilian Michels <mx...@apache.org>
>          * Jean-Baptiste Onofré <jb...@apache.org>
>          * Frances Perry <fr...@apache.org>
>          * Amit Sela <am...@apache.org>
>          * Josh Wills <jw...@apache.org>
> (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/
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co