Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAOfJQJ2XAdFVPvK-VR6L8gXk-3EAAtUm82ufFGUXyhDk0qDMiA@mail.gmail.com>
References: <CAMdX74_CQHmR6RECd9EnowSBaRkXh1mKtmq-5KgnTAd2Z0Z+Ng@mail.gmail.com>
 <CAOfJQJ2XAdFVPvK-VR6L8gXk-3EAAtUm82ufFGUXyhDk0qDMiA@mail.gmail.com>
From: Davor Bonaci <davor@apache.org>
Date: Mon, 5 Dec 2016 10:13:06 -0800
Message-ID: <CAMdX749VksmYjZz-mmE1afox=BYc1vR2BHqfXgHkcWr-TORmvg@mail.gmail.com>
Subject: Re: [DISCUSS] Apache Beam podling graduation readiness
To: general@incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11402d2eaffcd50542ed3f5b
archived-at: Mon, 05 Dec 2016 18:13:55 -0000

--001a11402d2eaffcd50542ed3f5b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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=E2=80=99d love to hear specific feedback on =
what can
be improved going forward.)

On Sun, Dec 4, 2016 at 11:16 PM, Sergio Fern=C3=A1ndez <wikier@apache.org> =
wrote:

> Out of personal technical interests, I've been following the podling quit=
e
> 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 <davor@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 t=
he
> > 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=E2=80=99d like start a discussion on the pr=
ogress 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 eviden=
ce
> > whenever applicable. I=E2=80=99ll summarize the commonly asked question=
s 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+ individua=
l
> > 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, b=
ut
> > now both the project=E2=80=99s code and branding have a clean separatio=
n between
> > the project and Google Cloud Dataflow (which has become just one of man=
y
> > 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, a=
t
> > least 10 modules have been developed with little to no contribution fro=
m
> > 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 bo=
th
> > batch and streaming data processing, enabling efficient execution acros=
s
> > diverse distributed execution engines and providing extensibility point=
s
> > for connecting to different technologies and user communities.
> >     * PMC composition:
> >          * Tyler Akidau <takidau@apache.org>
> >          * Davor Bonaci <davor@apache.org>
> >          * Robert Bradshaw <robertwb@apache.org>
> >          * Ben Chambers <bchambers@apache.org>
> >          * Luke Cwik <lcwik@apache.org>
> >          * Stephan Ewen <sewen@apache.org>
> >          * Dan Halperin <dhalperi@apache.org>
> >          * Kenneth Knowles <kenn@apache.org>
> >          * Aljoscha Krettek <aljoscha@apache.org>
> >          * Maximilian Michels <mxm@apache.org>
> >          * Jean-Baptiste Onofr=C3=A9 <jbonofre@apache.org>
> >          * Frances Perry <frances@apache.org>
> >          * Amit Sela <amitsela@apache.org>
> >          * Josh Wills <jwills@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 o=
f
> > you in this community), I=E2=80=99m sure there=E2=80=99s still plenty t=
o do. We continue
> to
> > be focused on community growth, and processes that encourage open
> > development. Regardless of the outcome of this discussion, we=E2=80=99d=
 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=C3=A1ndez
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>

--001a11402d2eaffcd50542ed3f5b--