Re: [VOTE] Heron to enter Apache Incubator

[Nabarun Nag]

+1

On Fri, Jun 16, 2017 at 8:28 PM Jacques Nadeau  wrote:

> +1
>
> On Jun 16, 2017 7:26 PM, "Ashish"  wrote:
>
> +1 (non-binding)
>
> On Fri, Jun 16, 2017 at 1:41 PM, Bill Graham  wrote:
> > Hi,
> >
> > Based on the discussion on the incubator mailing list[1] I would like to
> > call a vote to add Heron to the Apache Incubator.
> >
> > The full proposal is available below, and is also available on the Apache
> > Incubator wiki at:
> > https://wiki.apache.org/incubator/HeronProposal
> >
> > Please vote:
> >   [ ] +1, bring Heron into Incubator
> >   [ ] -1, do not bring Heron into Incubator, because...
> >
> > The vote will open for 7 days until Friday June 23 at 14:00 PT.
> >
> > Thank you
> >
> > 1 -
> > https://lists.apache.org/thread.html/fb91f527ef479bb5df45bf2c9d93b7
> 786c3fa6cdbfeba3128599df79@%3Cgeneral.incubator.apache.org%3E
> >
> >
> >
> > = Heron Proposal =
> >
> > = Abstract =
> > Heron is a real-time, distributed, fault-tolerant stream processing
> engine
> > initially developed by Twitter.
> >
> > = Proposal =
> >
> > Heron is a real-time stream processing engine built for high performance,
> > ease of manageability, performance predictability and developer
> > productivity[1]. We wish to develop a community around Heron to increase
> > contributions and see Heron thrive in an open forum.
> >
> > = Background =
> >
> > Heron provides the ability for developers to compose directed acyclic
> > graphs (DAGs) of real-time query execution logic (i.e. a topology) and
> > submit the topology to execute on a pluggable job scheduling system
> (e.g.,
> > Apache Aurora, YARN, Marathon, etc). Users can employ either the native
> > Heron API or the Apache Storm API to develop the topology. Heron supports
> > the Storm API for ease of migration, but beyond that Heron’s architecture
> > differs considerably from Storm’s.
> >
> > Users submit a topology to the scheduler using the Heron client, which
> uses
> > the Heron binary libraries to deploy all daemons required to run and
> manage
> > the topology. The topology therefore has no reliance on centrally managed
> > Heron services, only on a generic job scheduling system, which lends
> itself
> > well to be run on top of Apache Aurora/Mesos or Apache Hadoop/YARN (among
> > others).
> >
> > The scheduler runs each topology as a job consisting of multiple
> > containers. One of the containers runs the topology master, responsible
> for
> > managing the topology. The remaining containers each runs a stream
> manager
> > responsible for data routing, a metrics manager that collects and reports
> > various metrics and a number of processes called Heron instances which
> run
> > the user-defined logic on the stream of tuples. Parallelism is achieved
> via
> > process-based isolation of Heron instances, which provides predictable
> > performance while simplifying debugging. The containers are allocated and
> > managed by the scheduler framework based on resource availability of
> nodes
> > in the cluster. The metadata for the topology, such as the physical plan
> > and execution details, are stored in the pluggable Heron State Manager
> > (e.g. Apache ZooKeeper).
> >
> > = Rationale =
> >
> > Heron is a general-purpose, modular and extensible platform that can be
> > leveraged to support common, real-time analytics use cases. There is an
> > increasing demand for open-source, scalable real-time analytics systems.
> We
> > believe that Heron can be leveraged by other organizations to build
> > streaming applications that can benefit from its robustness, high
> > performance, adaptability to cloud environments and ease of use.
> Moreover,
> > we hope that open-sourcing Heron will help to further evolve the
> technology
> > as the project attracts contributors with diverse backgrounds and areas
> of
> > expertise.
> >
> > We believe the Apache foundation is a great fit as the long-term home for
> > Heron, as it provides an established process for community-driven
> > development and decision making by consensus. This is exactly the model
> we
> > want for future Heron development.
> >
> > = Initial Goals =
> >
> >  * Move the existing codebase, website, documentation, and mailing lists
> to
> > Apache-hosted infrastructure.
> >  * Integrate with the Apache development process.
> >  * Ensure all dependencies are compliant with Apache License version 2.0.
> >  * Incrementally develop and release per Apache guidelines.
> >
> > = Current Status =
> >
> > Heron is a stable project used in production at Twitter since 2014 and
> open
> > sourced under the ASL v2 license in 2016. The Heron source code is
> > currently hosted at github.com (https://github.com/twitter/heron), which
> > will seed the Apache git repository.
> >
> > = Meritocracy =
> >
> > By submitting this incubator proposal, we’re expressing our intent to
> build
> > a diverse developer community around Heron that will conduct itself
> 

Re: [VOTE] Graduate Apache Geode (incubating)

[Nabarun Nag]

+1

On Mon, Nov 7, 2016 at 10:11 AM Mark Bretl <mbr...@apache.org> wrote:

> +1
>
> --Mark
>
> On Sun, Nov 6, 2016 at 11:07 PM, Avinash Dongre <adon...@apache.org>
> wrote:
>
> > +1
> >
> > On Mon, Nov 7, 2016 at 12:35 PM, Sergio Fernández <wik...@apache.org>
> > wrote:
> >
> > > +1
> > >
> > > good luck, guys!
> > >
> > > On Sun, Nov 6, 2016 at 11:42 PM, John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > On Nov 6, 2016 15:58, "Roman Shaposhnik" <ro...@shaposhnik.org>
> wrote:
> > > >
> > > > > Hi!
> > > > >
> > > > > after a very positive discussion in the Geode community
> > > > > and at the IPMC level:
> > > > > http://markmail.org/message/z4prj62hr7rn6cu6
> > > > > I'd like to bring the following resolution for a formal vote.
> > > > >
> > > > > Please vote on the resolution pasted below to graduate
> > > > > Apache Geode from the incubator to top level project.
> > > > >
> > > > > [ ] +1 Graduate Apache Geode from the Incubator.
> > > > > [ ] +0 Don't care.
> > > > > [ ] -1 Don't graduate Apache Geode from the Incubator because...
> > > > >
> > > > > This vote will be open for at least 72 hours.
> > > > >
> > > > > Many thanks to our mentors and everyone else for the support,
> > > > > Roman (on behalf of the Apache Geode PPMC).
> > > > >
> > > > > Resolution:
> > > > >
> > > > > Establish the Apache Geode Project
> > > > >
> > > > > WHEREAS, the Board of Directors deems it to be in the best
> > > > > interests of the Foundation and consistent with the
> > > > > Foundation's purpose to establish a Project Management
> > > > > Committee charged with the creation and maintenance of
> > > > > open-source software, for distribution at no charge to the
> > > > > public, related to a data management platform that provides
> > > > > real-time, consistent access to data-intensive applications
> > > > > throughout widely distributed cloud architectures.
> > > > >
> > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > > > > Committee (PMC), to be known as the "Apache Geode Project",
> > > > > be and hereby is established pursuant to Bylaws of the
> > > > > Foundation; and be it further
> > > > >
> > > > > RESOLVED, that the Apache Geode Project be and hereby is
> > > > > responsible for the creation and maintenance of software
> > > > > related to a data management platform that provides real-time,
> > > > > consistent access to data-intensive applications throughout
> > > > > widely distributed cloud architectures.
> > > > >
> > > > > RESOLVED, that the office of "Vice President, Apache Geode" be
> > > > > and hereby is created, the person holding such office to
> > > > > serve at the direction of the Board of Directors as the chair
> > > > > of the Apache Geode Project, and to have primary responsibility
> > > > > for management of the projects within the scope of
> > > > > responsibility of the Apache Geode Project; and be it further
> > > > >
> > > > > RESOLVED, that the persons listed immediately below be and
> > > > > hereby are appointed to serve as the initial members of the
> > > > > Apache Geode Project:
> > > > >
> > > > > * Anilkumar Gingade <aging...@apache.org>
> > > > > * Anthony Baker <aba...@apache.org>
> > > > > * Ashvin Agrawal <ash...@apache.org>
> > > > > * Avinash Dongre <adon...@apache.org>
> > > > > * Barry Oglesby < bogle...@apache.org>
> > > > > * Bruce Schuchardt <bschucha...@apache.org>
> > > > > * Dan Smith <upthewatersp...@apache.org>
> > > > > * Darrel Schneider <dschnei...@apache.org>
> > > > > * Dave Barnes <dbar...@apache.org>
> > > > > * Eric Shu <esh...@apache.org>
> > > > > * Greg Chase <gregch...@apache.org>
> > > > > * Hitesh Khamesra <hi

Fwd: Requesting permission for editing Incubator PMC report

[Nabarun Nag]

Hi Nick,
The "name"  which I use for loggin in to
https://wiki.apache.org/incubator/July2016 page is Nabarun Nag.

Please do let me know if you need any other information.

Regards
Nabarun Nag


*From:* Nick Burch <apa...@gagravarr.org>
*Date:* June 30, 2016 at 4:07:03 PM PDT
*To:* general@incubator.apache.org
*Subject:* *Re: Requesting permission for editing Incubator PMC report*
*Reply-To:* general@incubator.apache.org

On Thu, 30 Jun 2016, Nabarun Nag wrote:

Please grant me the permission to append the Apache Geode podling report to
the incubator PMC page (https://wiki.apache.org/incubator/July2016).


What is your username for the incubator wiki? (Note - the wiki doesn't use
Apache ldap credentials, so you need to register if you haven't already!)

Nick

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

Requesting permission for editing Incubator PMC report

[Nabarun Nag]

Hi,

Please grant me the permission to append the Apache Geode podling report to
the incubator PMC page (https://wiki.apache.org/incubator/July2016).

Please do let me know if you need any information from me.

Regards
Nabarun Nag

Name : Nabarun Nag
email ID: n...@apache.org / n...@pivotal.io