Mailing-List: contact dev-help@streams.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@streams.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <etPan.59421598.55d46d61.16631@apache.org>
References: <etPan.59382f21.1f1500d.6b42@apache.org> <pony-4f6911432c0e56d59d8abe5b65087e9956a6af1e-74af7c7cbddc9e3c102c266605b450e1f936ffea@dev.streams.apache.org>
 <etPan.593ead67.6c506942.a59b@apache.org> <etPan.59421598.55d46d61.16631@apache.org>
From: Suneel Marthi <suneel.marthi@gmail.com>
Date: Mon, 19 Jun 2017 16:38:25 +0200
Message-ID: <CAOtpBjiAOkPV4a7hnqFyFrqTFqGAbuEMD7Co6vJ0Bd27doOFAA@mail.gmail.com>
Subject: Re: [DISCUSS] Graduation?
To: dev@streams.incubator.apache.org
Content-Type: multipart/alternative; boundary="94eb2c14ec1474e54e055251162b"
archived-at: Mon, 19 Jun 2017 14:38:34 -0000

--94eb2c14ec1474e54e055251162b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I would go ahead and hold a formal PPMC vote on Graduation now.

Please go ahead and do it.

On Thu, Jun 15, 2017 at 7:05 AM, sblackmon <sblackmon@apache.org> wrote:

> To summarize, support for graduation exists among mentors, PPMC, and
> incubator leadership.
>
> No specific objections have been raised, but far fewer have expressed
> support in 7 days than currently hold PPMC votes.
>
> The next steps include drafting a charter and holding a formal PPMC [VOTE=
]
> on Graduation. (see [1] and [2] below)
>
> Feel free to reply to this thread with additional thoughts until a VOTE
> thread is opened.  If you have concerns that you expect may cause you to
> vote -1 or abstain, please voice them now.
>
> [1] https://incubator.apache.org/incubation/Incubation_
> Policy.html#Graduating+from+the+Incubator
> [2] http://incubator.apache.org/guides/graduation.html#requirements
> On June 12, 2017 at 10:03:59 AM, sblackmon (sblackmon@apache.org) wrote:
>
>
> John, responses to your comments in-line below.
>
> Steve
>
> On June 11, 2017 at 9:08:42 PM, John D. Ament (johndament@apache.org)
> wrote:
> Hey guys
>
> Steve asked me to look over the dependencies in Streams to see if there's
> any issues.
>
> I don't see any issues - the dependencies you have from a binary
> standpoint are all Cat-A/Cat-B so its no issue.
>
>
> Thanks for taking a look at the dependency tree.  Good to hear you didn=
=E2=80=99t
> find any red flags.
>
> I do have to question the scope of some of them though. If I were a user
> of Streams, it may be that Streams brings in too many dependencies. Just
> something to think about - can Streams be simplified?
>
>
> Overall we are definitely in a consolidation phase.  In the last two
> releases, the number of modules that depend on guava have dropped
> significantly, and we=E2=80=99ve gotten rid of third-party binary librari=
es
> twitter4j and jInstagram (and their transitive dependencies) in master
> branch.  We are well on the way to dropping all third-party libraries for
> which direct HTTP is a viable substitute.  This trend will continue and
> ultimately I expect we will be able to remove guava, typesafe, jackson,
> jodatime, and jsonschema2pojo from core modules (all not under
> streams-contrib).
>
> We=E2=80=99re also dropping modules from the project faster than new ones=
 are
> being added lately.  Third-party libraries that use binary protocols to
> connect with various databases are pretty well isolated from core
> functionality already.  If we manage to replace Streams interfaces and
> execution with Beam interfaces and execution, as has been discussed
> multiple times on the list with no dissenting voices, that would allow us
> to delete or migrate a lot of non-differentiated capabilities (runtimes a=
nd
> persisters) while overall increasing developer productivity around our
> primary use cases (providers and processors).
>
> https://paste.apache.org/p/Xvtl - this is the raw output from maven.
>
> For instance. It looks like you have a scala plugin, but all modules are
> dependent on scala. Is there maybe a bad dependency somewhere in the mix?
>
> The scala dependency is there to support serialization of scala
> primitives, lists, maps, and other objects.  It=E2=80=99s almost certainl=
y the case
> there is way we could make it optional.  I opened STREAMS-514 to address
> this.
>
> John
>
> On 2017-06-07 12:51 (-0400), sblackmon <sblackmon@apache.org> wrote:
> > Hello,
> >
> > I wanted to let everyone know that at ApacheCon Miami I received
> encouragement from quite a few IPMC members to graduate the project to TL=
P.
> >
> > The June board report stated that we=C3=A2=E2=82=AC=E2=84=A2ve complete=
d the AMMA, and have
> compiled a checklist of items that we might want or need to do before we
> graduation. =C3=82 The list is fairly short and contains few if any diffi=
cult or
> essential tasks.
> >
> > It also stated that we are likely to ask to graduate before our next
> IPMC report.=C3=82
> >
> > So I=C3=A2=E2=82=AC=E2=84=A2m opening a thread here to see if the commu=
nity thinks we are
> ready - and if we aren=C3=A2=E2=82=AC=E2=84=A2t for any reason, what do y=
ou think we should do
> before we ask the incubator to vote us to TLP?
> >
> > Thanks,
> > Steve
> >
> >
> > Here=C3=A2=E2=82=AC=E2=84=A2s the Streams section of the board report f=
or reference - copied
> from=C3=82 https://wiki.apache.org/incubator/June2017=C3=82 just now.
> >
> > --------------------
> > Streams
> >
> > Apache Streams (incubating) unifies a diverse world of digital profiles
> and
> > online activities into common formats and vocabularies, and makes these
> > datasets accessible across a variety of databases, devices, and
> platforms for
> > streaming, browsing, search, sharing, and analytics use-cases.
> >
> > Streams has been incubating since 2012-11-20.
> >
> > Three most important issues to address in the move towards graduation:
> >
> > 1. Community growth and PMC maturity.
> > 2. Demonstrate a consistent release schedule.
> > 3. Participation of project community within related standards-bodies
> and Apache projects.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
> > of?
> >
> > The community has completed an internal assessment using the Apache
> Maturity Model to identify gaps that should be addressed before graduatio=
n.
> >
> > The community is working against a task list of graduation TODOs:
> https://cwiki.apache.org/confluence/display/STREAMS/Graduation+TODOs
> >
> > It is likely that Streams will pursue graduation to TLP during the
> coming quarter.
> >
> > How has the community developed since the last report?
> >
> > Dev List
> > 57 emails sent by 12 people, divided into 20 topics
> >
> > Web Page
> > 820 Sessions (up ~75%), 508 Users (up ~50%), 1507 Pageviews (up ~30%).
> >
> > Public Slack: apachestreams.slack.com
> > 1202 Messages, 11 Files
> >
> > Committers Slack: the-asf.slack.com #dev-streams
> > 157 Messages, 3 Files
> >
> > How has the project developed since the last report?
> >
> > Source Control
> > https://github.com/apache/incubator-streams
> > Excluding merges, 4 authors have pushed 29 commits to master. On master=
,
> 165 files have changed and there have been 5,891 additions and 1,647
> deletions.
> >
> > https://github.com/apache/incubator-streams-examples
> > Excluding merges, 3 authors have pushed 4 commits to master. On master,
> 10 files have changed and there have been 18 additions and 72 deletions.
> >
> > JIRA
> >
> > 24 issues closed with 0.5-incubating release
> > 7 issues closed after 0.5-incubating release
> > 18 new issues opened this period
> >
> > Date of last release:
> >
> > 2017-03-20 : 0.5-incubating release
> >
> > When were the last committers or PMC members elected?
> >
> > 2017-04-14: Trevor Grant elected as committer / PPMC member
> >
> > Signed-off-by:
> >
> > [X](streams) Matt Franklin
> > Comments: The community is small, but diverse and dedicated. I look
> forward to seeing them move past the incubator and hopefully continuing t=
o
> add new contributors.
> > [X](streams) Ate Douma
> > Comments:
> > [X](streams) Suneel Marthi
> > Comments:
> >
> >
>

--94eb2c14ec1474e54e055251162b--