Re: [VOTE] Release Apache Nemo (incubating) version 0.2-rc5

[Supun Kamburugamuva]

+1 (non-binding)

Best,
Supun..

On Thu, Mar 5, 2020 at 10:51 AM Markus Weimer  wrote:

> +1 (binding)
>
> What I checked:
>
>   * sha512
>   * `mvn clean install` passes
>   * `mvn apache-rat:rat` passes
>
> Markus
>
> On Tue, Mar 3, 2020 at 10:32 PM Justin Mclean 
> wrote:
> >
> > HI,
> >
> > BTW your download page [1] is missing the signatures and hashes for
> previous releases. See  [2]
> >
> > Thanks,
> > Justin
> >
> > 1. http://nemo.incubator.apache.org/pages/downloads/
> > 2. https://www.apache.org/dev/release-distribution.html#download-links
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Supun Kamburugamuve, PhD
Digital Science Center, Indiana University
Member, Apache Software Foundation; http://www.apache.org
E-mail: supun@apache.o rg;  Mobile: +1 812 219 2563

Re: Mentors wanted for projects

[Supun Kamburugamuva]

I have time to help with one project. I'm not an IPMC member. I will send a
request to join the IPMC.

Best,
Supun..

On Wed, Feb 19, 2020 at 9:47 PM Atri Sharma  wrote:

> I am available to help, not an IPMC member though
>
> On Thu, 20 Feb 2020 at 07:49, Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > I can help on one more project. May be Superset?
> >
> > I think Superset may also be graduating soon. BTW No need to ask me ask
> > the project. Just send them a email asking to help out as a mentor and if
> > they accept we’ll add you to the roster. I’m sure they will be happy to
> > have an extra mentor.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> Regards,
>
> Atri
> Apache Concerted
>


-- 
Supun Kamburugamuve, PhD
Digital Science Center, Indiana University
Member, Apache Software Foundation; http://www.apache.org
E-mail: supun@apache.o rg;  Mobile: +1 812 219 2563

Re: [VOTE] Accept YuniKorn into Apache Incubator

[Supun Kamburugamuva]

+1



On Mon, Jan 13, 2020 at 1:47 PM Arpit Agarwal 
wrote:

> +1
> (binding)
>
> > On Jan 13, 2020, at 9:44 AM, Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
> >
> > Hi,
> >
> > On Fri, Jan 10, 2020 at 6:47 PM Vinod Kumar Vavilapalli
> >  wrote:
> >> I'd like to call a vote on accepting YuniKorn into the Apache
> Incubator...
> >
> > +1
> >
> > I'm copying the proposal text below, we usually do that to get
> > complete mail archives.
> >
> > -Bertrand
> >
> >
> > YuniKorn proposal
> >
> > Abstract
> >
> > YuniKorn is a standalone resource scheduler responsible for scheduling
> > batch jobs and long-running services on large scale distributed
> > systems running in on-premises environments as well as different
> > public clouds.
> > Proposal
> >
> > YuniKorn ['ju:nikɔ:n] is a unified resource scheduler aiming to
> > achieve fine-grained resource sharing for various workloads
> > efficiently on a large scale, multi-tenant and cloud-native
> > environments. YuniKorn brings a unified, cross-platform scheduling
> > experience for mixed workloads, with support for but not limited to,
> > Apache™ Hadoop® YARN and Kubernetes. YuniKorn is a made-up word
> > (credit to Vinod Kumar Vavilapalli) - it’s made up of Y for Apache™
> > Hadoop® YARN, K for K8s, Uni for Unified, and its pronunciation is the
> > same as “Unicorn”
> >
> > Currently, YuniKorn is an open-source project with Apache 2.0 license.
> > The source code is hosted as a git-repo under github.com/cloudera
> > domain. We would like to share it with the ASF and expand the
> > community to a wider range of users and contributors.
> > Background
> >
> > Enterprise users run their workloads on different platforms such as
> > Apache™ Hadoop® YARN and Kubernetes. They need to work with different
> > resource schedulers in order to plan their workloads to run on these
> > platforms efficiently. The scheduler implementations are fragmented,
> > and not optimized to balance existing use-cases like batch workloads
> > along with new needs such as cloud-native architecture, autoscaling,
> > etc. We need a single resource planning/management framework to manage
> > resources on different platforms using the same semantics, in order to
> > address all the important resource management requirements.
> > Rationale
> >
> > There is no solution that exists now to address the needs of having a
> > unified resource scheduling experiences across platforms. That makes
> > it difficult to manage workloads running on different environments,
> > from on-premise to Cloud. YuniKorn aims to satisfy these needs.
> > YuniKorn is designed around the following principles:
> >
> > 1) Support different environments
> >
> > As the compute platforms are evolving quickly, there are more and more
> > challenges appears in on-prem, cloud or hybrid environments. YuniKorn
> > aims to bring unified scheduling experiences across multiple
> > environments with enhanced scheduling capabilities.
> >
> > 2) Support extensive type of workloads
> >
> > To improve the efficiency of the computing platform, a key idea is to
> > run different types of applications, like long-running services and
> > batch jobs, on shared resources. YuniKorn is an effort to address all
> > the scheduling features needed for such mixed workload environments.
> >
> > 3) Benefit both big-data and cloud-native communities
> >
> > A resource scheduler needs to be capable of supporting mixed
> > workloads, both batch and long-running services. This is the key to
> > improving cluster utilization, and to reduce the complexity of
> > dev-ops. By creating a common scheduler that is decoupled from the
> > container platforms underneath, it can benefit both Apache™ Hadoop®
> > YARN and the Kubernetes communities.
> > Initial Goals
> >
> > Initial goals are:
> >
> >Move the existing codebase, documentation to Apache hosted repo
> >Setup mailing lists, web-site, CI/CD pipeline under Apache
> infrastructure
> >Setup JIRA for issue tracking
> >Incremental development and releases according to Apache guidelines
> >Expand the community and bring more diversified contributors/users
> > to the community
> >
> > Current Status
> > Meritocracy
> >
> > Many of the initial developers of YuniKorn are already Apache
> > committers and PMC members from other Apache projects, such as Apache
> > Hadoop and Apache Submarine. Many of us have worked in the Apache
> > Hadoop community for years and know the Apache way well. We believe
> > strongly in meritocracy in electing committers and PMC members. We
> > believe that contributions can come in forms other than just code: for
> > example, one of our initial proposed committers has contributed solely
> > in the area of project documentation. We will encourage contributions
> > and participation of all types, and ensure that contributors are
> > appropriately recognized.
> > Community
> >
> > YuniKorn is a relatively new open source project, Cloudera is the
> > original 

Re: [VOTE] Accept NuttX into the Apache Incubator

[Supun Kamburugamuva]

+1 (non binding)

Best,
Supun..

On Wed, Dec 4, 2019 at 2:20 PM Anthony Merlino 
wrote:

> +1 (non-binding)
>
> On Wed, Dec 4, 2019, 1:04 PM Alan Carvalho de Assis 
> wrote:
>
> > +1 (non-binding)
> >
> > BR,
> >
> > Alan
> >
> > On 12/4/19, Abdelatif Guettouche  wrote:
> > > +1 (non-binding)
> > >
> > > Regards
> > >
> > >
> > > On Wed, Dec 4, 2019 at 5:14 PM Tianqi Chen 
> > > wrote:
> > >>
> > >> +1 (binding)
> > >>
> > >> TQ
> > >>
> > >> On Wed, Dec 4, 2019 at 8:40 AM David Sidrane  >
> > >> wrote:
> > >>
> > >> > +1 (non-binding)
> > >> >
> > >> > Thank you,
> > >> >
> > >> > David Sidrane
> > >> >
> > >> > -Original Message-
> > >> > From: 俊平堵 [mailto:junping...@apache.org]
> > >> > Sent: Tuesday, December 03, 2019 9:32 PM
> > >> > To: general@incubator.apache.org
> > >> > Subject: [VOTE] Accept NuttX into the Apache Incubator
> > >> >
> > >> > Hi folks,
> > >> >
> > >> >
> > >> > The [DISCUSS] thread on NuttX has died down.
> > >> >
> > >> >
> > >> > Accordingly, I would like to call a VOTE to accept NuttX into the
> > >> >
> > >> > Apache Incubator.
> > >> >
> > >> >
> > >> > Please cast your vote:
> > >> >
> > >> >
> > >> >   [ ] +1, bring NuttX into the Incubator
> > >> >
> > >> >   [ ] +0, I don't care either way
> > >> >
> > >> >   [ ] -1, do not bring NuttX into the Incubator, because...
> > >> >
> > >> >
> > >> > The vote will open at least for 72 hours and only votes from the
> > >> >
> > >> > Incubator PMC are binding, but votes from everyone are welcome.
> > >> >
> > >> >
> > >> > =Abstract=
> > >> >
> > >> > NuttX is a mature, real-time embedded operating system (RTOS).  It
> has
> > >> > wide
> > >> > usage in IoT projects, control systems, robotics, drones, and many
> > >> > other
> > >> > systems.  Unique properties of NuttX are its strict adherence to
> > >> > standards
> > >> > and its scalability. NuttX follows the Unix standards as defined
> > >> > by OpenGroup.org (POSIX, ANSI, and others).  This allows for a high
> > >> > degree
> > >> > of portability. Scalability is supported through a configuration
> > system
> > >> > that allows NuttX to run on the smallest embedded platforms and
> > through
> > >> > high end single board computers.
> > >> >
> > >> >
> > >> > =Proposal=
> > >> >
> > >> > NuttX was released under a BSD 3-Clause license on February 17,
> 2007.
> > >> > From
> > >> > that time until now it has been managed by a single person, Gregory
> > >> > Nutt.
> > >> > The user base of NuttX has grown to probably thousands of projects
> and
> > >> > perhaps a hundred active developments at any time.  The code base
> has
> > >> > grown
> > >> > to around 1.5 million lines of code (according to OpenHub.com).
> > >> >
> > >> > NuttX has benefited from this single person management because this
> > has
> > >> > resulted in a consistent architecture and controlled growth.  But
> now
> > it
> > >> > is
> > >> > time to open this project to the participation of others because
> this
> > >> > consistent architecture assures solid future growth, and because the
> > >> > magnitude of effort required to support the RTOS exceeds the
> > capability
> > >> > of
> > >> > a single person, but also because users of NuttX require a stable
> road
> > >> > map
> > >> > going forward that does not depend on a single person.
> > >> >
> > >> > For these reasons, I propose that NuttX enter the Apache Incubator
> as
> > a
> > >> > first step in opening the project to wider participation.
> > >> >
> > >> >
> > >> > =Initial Goals=
> > >> >
> > >> > The initial goal will be to move the existing BSD code base to
> Apache
> > >> > and
> > >> > integrate with the Apache development process and infrastructure. A
> > >> > primary
> > >> > goal of incubation will be to grow and diversify the NuttX
> community.
> > >> > We
> > >> > will convert that code base to the Apache license during incubation.
> > >> >
> > >> >
> > >> > =Current Status=
> > >> >
> > >> > As previously mentioned, NuttX is a mature, stable product in wide
> use
> > >> > in
> > >> > embedded products.
> > >> >
> > >> >
> > >> > ==Meritocracy==
> > >> >
> > >> > We value meritocracy and we understand that it is the basis for an
> > open
> > >> > community that encourages multiple companies and individuals to
> > >> > contribute
> > >> > and be invested in the project’s future. We will encourage and
> monitor
> > >> > participation and make sure to extend privileges and
> responsibilities
> > >> > to
> > >> > all contributors.
> > >> >
> > >> > Being a mature project, NuttX already has an extensive user base
> with
> > >> > many
> > >> > people who understand the software, who have committed hundreds of
> > >> > changes,
> > >> > and are happy to participate in the project.  I believe that with a
> > >> > little
> > >> > guidance and formalization, a PMC and a large group of experienced
> > >> > committers can quickly be established.
> > >> >
> > >> >
> > >> > ==Community==
> > >> >
> > >> > NuttX has a large, active community.  

Re: [VOTE] Heron to enter Apache Incubator

[Supun Kamburugamuva]

+1

Thanks,
Supun..

On Fri, Jun 16, 2017 at 4:59 PM, Sanjeev Kulkarni 
wrote:

> +1
>
> 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
> > according to The Apache Way and use a meritocratic means of 

Re: [PROPOSAL] Heron

[Supun Kamburugamuva]

Thanks Bill for bringing up the proposal. Should there be a sentence or two
describing how Heron compares with Storm?

Regards,
Supun..

On Thu, Jun 8, 2017 at 1:23 PM, Bill Graham  wrote:

> Dear Apache Incubator Community,
>
> We are excited to share our proposal for discussion and feedback
> for entering Apache Incubation. Heron is a real-time, distributed,
> fault-tolerant stream processing engine.
>
> Our proposal can be found at https://wiki.apache.org/
> incubator/HeronProposal
>  and is included below.
>
>
> Thank you,
>
> Bill Graham on behalf of the Heron developers
>
>
> # 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
> according to The Apache Way and use a meritocratic means of building it's
> committer base. Several companies and universities have already expressed
> interest in and contributed to Heron. Our goal is to grow the Heron
> community by encouraging open communication, contribution and participation
> of all types, and ensuring that contributors are recognized appropriately.
>
> ### Community
>
> Heron is currently being used by Twitter, Google, Machine Zone and
> ndustrial.io and has received significant contributions by 

Re: [VOTE] Accept Beam into the Apache Incubator

[Supun Kamburugamuva]

+1

Supun..

On Thu, Jan 28, 2016 at 11:43 AM, Daniel Kulp  wrote:

> +1
>
> Dan
>
>
>
> > On Jan 28, 2016, at 9:28 AM, Jean-Baptiste Onofré 
> wrote:
> >
> > Hi,
> >
> > the Beam proposal (initially Dataflow) was proposed last week.
> >
> > The complete discussion thread is available here:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3CCA%2B%3DKJmvj4wyosNTXVpnsH8PhS7jEyzkZngc682rGgZ3p28L42Q%40mail.gmail.com%3E
> >
> > As reminder the BeamProposal is here:
> >
> > https://wiki.apache.org/incubator/BeamProposal
> >
> > Regarding all the great feedbacks we received on the mailing list, we
> think it's time to call a vote to accept Beam into the Incubator.
> >
> > Please cast your vote to:
> > [] +1 - accept Apache Beam as a new incubating project
> > []  0 - not sure
> > [] -1 - do not accept the Apache Beam project (because: ...)
> >
> > Thanks,
> > Regards
> > JB
> > 
> > ## page was renamed from DataflowProposal
> > = Apache Beam =
> >
> > == Abstract ==
> >
> > Apache Beam is an open source, unified model and set of
> language-specific SDKs for defining and executing data processing
> workflows, and also data ingestion and integration flows, supporting
> Enterprise Integration Patterns (EIPs) and Domain Specific Languages
> (DSLs). Dataflow pipelines simplify the mechanics of large-scale batch and
> streaming data processing and can run on a number of runtimes like Apache
> Flink, Apache Spark, and Google Cloud Dataflow (a cloud service). Beam also
> brings DSL in different languages, allowing users to easily implement their
> data integration processes.
> >
> > == Proposal ==
> >
> > Beam is a simple, flexible, and powerful system for distributed data
> processing at any scale. Beam provides a unified programming model, a
> software development kit to define and construct data processing pipelines,
> and runners to execute Beam pipelines in several runtime engines, like
> Apache Spark, Apache Flink, or Google Cloud Dataflow. Beam can be used for
> a variety of streaming or batch data processing goals including ETL, stream
> analysis, and aggregate computation. The underlying programming model for
> Beam provides MapReduce-like parallelism, combined with support for
> powerful data windowing, and fine-grained correctness control.
> >
> > == Background ==
> >
> > Beam started as a set of Google projects (Google Cloud Dataflow) focused
> on making data processing easier, faster, and less costly. The Beam model
> is a successor to MapReduce, FlumeJava, and Millwheel inside Google and is
> focused on providing a unified solution for batch and stream processing.
> These projects on which Beam is based have been published in several papers
> made available to the public:
> >
> > * MapReduce - http://research.google.com/archive/mapreduce.html
> > * Dataflow model  - http://www.vldb.org/pvldb/vol8/p1792-Akidau.pdf
> > * FlumeJava - http://research.google.com/pubs/pub35650.html
> > * MillWheel - http://research.google.com/pubs/pub41378.html
> >
> > Beam was designed from the start to provide a portable programming
> layer. When you define a data processing pipeline with the Beam model, you
> are creating a job which is capable of being processed by any number of
> Beam processing engines. Several engines have been developed to run Beam
> pipelines in other open source runtimes, including a Beam runner for Apache
> Flink and Apache Spark. There is also a “direct runner”, for execution on
> the developer machine (mainly for dev/debug purposes). Another runner
> allows a Beam program to run on a managed service, Google Cloud Dataflow,
> in Google Cloud Platform. The Dataflow Java SDK is already available on
> GitHub, and independent from the Google Cloud Dataflow service. Another
> Python SDK is currently in active development.
> >
> > In this proposal, the Beam SDKs, model, and a set of runners will be
> submitted as an OSS project under the ASF. The runners which are a part of
> this proposal include those for Spark (from Cloudera), Flink (from data
> Artisans), and local development (from Google); the Google Cloud Dataflow
> service runner is not included in this proposal. Further references to Beam
> will refer to the Dataflow model, SDKs, and runners which are a part of
> this proposal (Apache Beam) only. The initial submission will contain the
> already-released Java SDK; Google intends to submit the Python SDK later in
> the incubation process. The Google Cloud Dataflow service will continue to
> be one of many runners for Beam, built on Google Cloud Platform, to run
> Beam pipelines. Necessarily, Cloud Dataflow will develop against the Apache
> project additions, updates, and changes. Google Cloud Dataflow will become
> one user of Apache Beam and will participate in the project openly and
> publicly.
> >
> > The Beam programming model has been designed with simplicity,
> scalability, and speed as key tenants. In the Beam model, 

Re: help needed ..

[Supun Kamburugamuva]

Hi Subhasis,

Do you have a working code base? I believe Apache incubator is favoring
projects with an initial code base.

Regards,
Supun..


On Tue, Feb 11, 2014 at 10:41 AM, Subhasis Gorai
subhasis.go...@gmail.comwrote:

 Hello,
 I have a project idea, while going through the
 http://incubator.apache.org/guides/proposal.html#formulating I came to
 know
 that before making the proposal the project need a champion who will help
 me out in the process. Can someone please let me know how I can get a
 champion.
 Apology - if I'm asking a very basic question here, actually I'm new to
 this.

 thanks much,
 -- Subhasis




-- 
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com

Re: help needed ..

[Supun Kamburugamuva]

Hi Subhasis,

I think the best way is to explain your project idea and your code base.
Then I'm sure someone from Apache who is interested in your project will
volunteer to mentor your project.

Thanks,
Supun..


On Tue, Feb 11, 2014 at 11:01 AM, Subhasis Gorai
subhasis.go...@gmail.comwrote:

 Hi Supun,
 Thanks for the prompt response ..
 Yes, I have a working initial code base ..

 Thanks,
 -- Subhasis


 On Tue, Feb 11, 2014 at 9:18 PM, Supun Kamburugamuva supu...@gmail.com
 wrote:

  Hi Subhasis,
 
  Do you have a working code base? I believe Apache incubator is favoring
  projects with an initial code base.
 
  Regards,
  Supun..
 
 
  On Tue, Feb 11, 2014 at 10:41 AM, Subhasis Gorai
  subhasis.go...@gmail.comwrote:
 
   Hello,
   I have a project idea, while going through the
   http://incubator.apache.org/guides/proposal.html#formulating I came to
   know
   that before making the proposal the project need a champion who will
 help
   me out in the process. Can someone please let me know how I can get a
   champion.
   Apology - if I'm asking a very basic question here, actually I'm new to
   this.
  
   thanks much,
   -- Subhasis
  
 
 
 
  --
  Supun Kamburugamuva
  Member, Apache Software Foundation; http://www.apache.org
  E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
  Blog: http://supunk.blogspot.com
 




-- 
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com

Re: help needed ..

[Supun Kamburugamuva]

Hi Subhasis,

I think this is the mailing list to explain your project idea.

Thanks,
Supun..


On Tue, Feb 11, 2014 at 11:13 AM, Subhasis Gorai
subhasis.go...@gmail.comwrote:

 Hi Supun,
 Thanks again - can I explain my project idea along with the github repo
 here in this mailing list?

 Thanks,
 -- Subhasis


 On Tue, Feb 11, 2014 at 9:38 PM, Supun Kamburugamuva supu...@gmail.com
 wrote:

  Hi Subhasis,
 
  I think the best way is to explain your project idea and your code base.
  Then I'm sure someone from Apache who is interested in your project will
  volunteer to mentor your project.
 
  Thanks,
  Supun..
 
 
  On Tue, Feb 11, 2014 at 11:01 AM, Subhasis Gorai
  subhasis.go...@gmail.comwrote:
 
   Hi Supun,
   Thanks for the prompt response ..
   Yes, I have a working initial code base ..
  
   Thanks,
   -- Subhasis
  
  
   On Tue, Feb 11, 2014 at 9:18 PM, Supun Kamburugamuva 
 supu...@gmail.com
   wrote:
  
Hi Subhasis,
   
Do you have a working code base? I believe Apache incubator is
 favoring
projects with an initial code base.
   
Regards,
Supun..
   
   
On Tue, Feb 11, 2014 at 10:41 AM, Subhasis Gorai
subhasis.go...@gmail.comwrote:
   
 Hello,
 I have a project idea, while going through the
 http://incubator.apache.org/guides/proposal.html#formulating I
 came
  to
 know
 that before making the proposal the project need a champion who
 will
   help
 me out in the process. Can someone please let me know how I can
 get a
 champion.
 Apology - if I'm asking a very basic question here, actually I'm
 new
  to
 this.

 thanks much,
 -- Subhasis

   
   
   
--
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com
   
  
 
 
 
  --
  Supun Kamburugamuva
  Member, Apache Software Foundation; http://www.apache.org
  E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
  Blog: http://supunk.blogspot.com
 




-- 
Tech Lead, WSO2 Inc
http://wso2.org
supunk.blogspot.com

Re: [VOTE] Phoenix for incubator project

[Supun Kamburugamuva]

/ashishpaliwal



 --
 Olivier Lamy
 Ecetera: http://ecetera.com.au
 http://twitter.com/olamy | http://linkedin.com/in/olamy

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




-- 
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com

Re: [VOTE] Accept Storm into the Incubator

[Supun Kamburugamuva]

 future, we will
  introduce Kerberos authentication.
* Tuple payload serialization plugins … Storm provides plugins for
  plain-object serialization and blowfish encryption.
 
  == Required Resources ==
 
  === Mailing lists ===
 
  * storm-user
  * storm-dev
  * storm-commits
  * storm-private (with moderated subscriptions)
 
  === Subversion Directory ===
 
  Git is the preferred source control system: git://git.apache.org/storm
 
 
  === Issue Tracking ===
 
  JIRA Storm (STORM)
 
  == Initial Committers ==
 
* Nathan Marz nathan at nathanmarz dot com
* James Xu xumingmingv at gmail dot com
* Jason Jackson jason at cvk dot ca
* Andy Feng afeng at yahoo-inc dot com
* Flip Kromer  flip at infochimps dot com
* David Lao davidlao at microsoft dot com
* P. Taylor Goetz ptgoetz at gmail dot com
 
  == Affiliations ==
 
* Nathan Marz - Nathan’s Startup
* James Xu - Alibaba
* Jason Jackson - Twitter
* Andy Feng - Yahoo!
* Flip Kromer - Infochimps
* David Lao - Microsoft
* P. Taylor Goetz - Health Market Science
 
  == Sponsors ==
 
 
  === Champion ===
 
* Doug Cutting  cutting at apache dot org
 
  === Nominated Mentors ===
 
   * Ted Dunning tdunning at maprtech dot com
   * Arvind Prabhakar arvind at apache dot org
   * Devaraj Das ddas at hortonworks dot com
   * Matt Franklin m.ben.franklin at gmail dot com
   * Benjamin Hindman benjamin.hindman at gmail dot com
 
  === Sponsoring Entity ===
 
  The Apache Incubator
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
 

 Craig L Russell
 Architect, Oracle
 http://db.apache.org/jdo
 408 276-5638 mailto:craig.russ...@oracle.com
 P.S. A good JDO? O, Gasp!


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




-- 
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com

Re: [PROPOSAL] Storm for Apache Incubator

[Supun Kamburugamuva]

   plugin (while keep 0MQ as an optional plugin).
  
   == Cryptography ==
  
   We do not expect Storm to be a controlled export item due to the use of
   encryption.
  
   Storm enable encryptions via 2 plugins:
  
 * SASL authentication plugins … Currently, we have provide “no-op”
   authentication and digest authentication. In near future, we will
  introduce
   Kerberos authentication.
 * Tuple payload serialization plugins … Storm provides plugins for
   plain-object serialization and blowfish encryption.
  
   == Required Resources ==
  
   === Mailing lists ===
  
   * storm-user
   * storm-dev
   * storm-private (with moderated subscriptions)
  
   === Subversion Directory ===
  
   Git is the preferred source control system: git://git.apache.org/storm
  
   === Issue Tracking ===
  
   JIRA Storm (STORM)
  
   == Initial Committers ==
  
 * Nathan Marz nathan at nathanmarz dot com
 * James Xu xumingmingv at gmail dot com
 * Jason Jackson jason at cvk dot ca
 * Andy Feng afeng at yahoo-inc dot com
 * Flip Kromer  flip at infochimps dot com
 * David Lao davidlao at microsoft dot com
 * P. Taylor Goetz ptgoetz at gmail dot com
  
   == Affiliations ==
  
 * Nathan Marz - Nathan’s Startup
 * James Xu - Alibaba
 * Jason Jackson - Twitter
 * Andy Feng - Yahoo!
 * Flip Kromer - Infochimps
 * David Lao - Microsoft
 * P. Taylor Goetz - Health Market Science
  
   == Sponsors ==
  
   === Champion ===
  
 * Doug Cutting  cutting at apache dot org
  
   === Nominated Mentors ===
  
* Ted Dunning tdunning at maprtech.com
* Arvind Prabhaker arvind at apache dot org
* Devaraj Das ddas at hortonworks dot com
  
   === Sponsoring Entity ===
  
   The Apache Incubator
  
 
 
 
  --
  
  Srinath Perera, Ph.D.
Director, Research, WSO2 Inc.
Visiting Faculty, University of Moratuwa
Member, Apache Software Foundation
Research Scientist, Lanka Software Foundation
Blog: http://srinathsview.blogspot.com/
Photos: http://www.flickr.com/photos/hemapani/
 Phone: 0772360902
 




-- 
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com

Re: [VOTE] Accept Stratos proposal as an incubating project

[Supun Kamburugamuva]

+1

Thanks,
Supun..


On Tue, Jun 18, 2013 at 7:02 AM, Noah Slater nsla...@apache.org wrote:

 +1


 On 14 June 2013 22:49, Ross Gardler rgard...@opendirective.com wrote:

  I would like to invite the IPMC vote to accept the Stratos proposal [1].
 
  I want to clarify that this vote is for the Stratos project to enter
  the incubator as a standard podling under the existing incubation
  policy. The acceptance or otherwise of the probationary TLP idea is a
  separate issue that will be explored during the first month of
  incubation, potentially resulting in a further IPMC vote.
 
  This vote is *only* for accepting the Stratos project as a podling.
 
  [ ] +1 Accept the Stratos project as an incubating project
  [ ] +0
  [ ] -1 Do not accept the Stratos project as an incubating project
  because... (provide reason)
 
  It's late on Friday evening here in the UK. I'll let this vote run
  well into next week to allow for the weekend.
 
  Thank you for your votes.
  Ross
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
 
 


 --
 NS




-- 
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com