Re: [VOTE] $podling.apache.org is the same as $podling.incubator.apache.org

[Amareshwari Sriramdasu]

+1

On Tue, Jun 28, 2016 at 7:58 PM, John D. Ament 
wrote:

> All,
>
> Its been discussed a few times, and I'd like to provide clear feedback to
> the infra team on how to implement going forward.
>
> Typically, the addresses $podling.apache.org and $
> podling.incubator.apache.org work, and have worked for a while.
>
> This is a call to vote on whether the IPMC agrees to this or not.  If they
> do, I will ask infra to further clean this up, as DNS seems to be an issue
> at times for podlings.  The benefit is that for SEO, the website URL does
> not change.
>
> I'm going to leave this open for 72 hours, at least and hope for some
> binding votes on this subject.
>
> [+1] I want the two URLs to both work the same.
> [+/- 0] Don't care
> [-1] I want the $podling.incubator.apache.org URL to be the one that
> works,
> including emails.
>
> John
>

Re: [VOTE] Release Eagle Version 0.3.0 RC3 (Incubating)

[Amareshwari Sriramdasu]

Replaying my vote from dev list :

+1 (Binding)

On Tue, Mar 29, 2016 at 5:35 AM, Dendukuri, Hemanth 
wrote:

> Hi all,
>
>The Apache Eagle community has voted on and approved the proposal
> to release "Apache Eagle 0.3.0 Release Candidate 3 (incubating)".
>The voting result is available at
> https://s.apache.org/eagle-0.3.0-result
>
>
>The Source file to be voted are located here:
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/
>
>Release Tag  :
> https://github.com/apache/incubator-eagle/releases/tag/release-0.3.0-rc3
>
> The commit to be voted upon:
> https://github.com/apache/incubator-eagle/commit/b1d0a87ac0df1cc881427faafc637c152c180872
>
>Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/hdendukuri.asc
>
>Here’s release notes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.3.0
>
>
>Note that this is a source only release and we are voting on the
> source. The hashes of the source are as follows:
>
>  apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md<
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md5>5
> a211a151d7f66c2516c5e41da1345128
>
>apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1<
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1>
> da7b4e60228cf1421dde4342c957aff16de81cbd
>
>
>
> The vote is open for a minimum of 72 hours or until the necessary
> number of votes (3 binding +1s) is reached.
>
> [ ] +1 Release this Eagle 0.3.0 Incubator Release Candidate 3.
>
> [ ]  0 I don't feel strongly about it, but I'm okay with the
> release
>
> [ ] -1 Do not release this package because...
>
> Please add "(binding)" if your vote is binding.
>
>
> Thanks,
>
> Hemanth Dendukuri
>

Single person developed project

[Amareshwari Sriramdasu]

Hi all,

Wanted to know if a single person developed project can get incubated in
Apache. Any doc links would be helpful as well.

Thanks
Amareshwari

Re: [VOTE] Accept Beam into the Apache Incubator

[Amareshwari Sriramdasu]

+1 (Binding)

On Thu, Jan 28, 2016 at 7:58 PM, 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, you only need to think about
> four top-level concepts when constructing your data processing job:
>
>  * Pipelines - The data processing job made of a series of computations
> including 

Re: [VOTE] Accept the iota project into the Apache Incubator

[Amareshwari Sriramdasu]

+1 (Binding)

On Sun, Jan 17, 2016 at 1:42 AM, Hadrian Zbarcea  wrote:

> Hi,
>
> The iota proposal [1] (initially Tempo) was proposed about 6 weeks ago.
>
> Because of the naming conflict that would have likely required to change
> name at graduation, the project name was changed to "Apache iota" (the
> greek letter), which resonates better with the IoT field the project
> targets and passed a summary podling name search.
>
> The code was made available in December for our review and answers on the
> general@ list have been answered.
>
> We think it's time to move to the next step, a formal vote. Therefore...
>
> Please cast your vote to:
> [] +1 - accept Apache iota as a new incubating project
> []  0 - not sure
> [] -1 - do not accept the Apache iota project (because: ...)
>
> Thanks,
> Hadrian
>
>
> [1] https://wiki.apache.org/incubator/IotaProposal
> [2] https://en.wikipedia.org/wiki/Iota
>
>
> -
>
> iota Proposal
>
> Abstract
>
> The Apache Foundation has been very successful in bringing together key
> software components that have enabled people to interact with each other
> via a variety of content platforms and it will no doubt continue to do so.
> At the same time modern society is becoming increasingly dependent on
> devices that interact with each other and with people. The amount of data
> that will be produced by devices will be orders of magnitude greater than
> what has been produced by humans in the past. In addition, the
> orchestration of devices and people will be an important area of growth for
> the foreseeable future. This new dynamic will eventually become manifest in
> a growing number of Apache projects that enable this to occur. Our wish is
> to contribute to this movement by contributing the iota system to the Open
> Source Community via the Apache Foundation. Apache iota is an open platform
> to interconnect any and all devices, sensors, people, and applications,
> henceforth referred to as points, through a scalable, secure, and modular
> architecture, enabling applications to generate analysis, create actions
> and/or add intelligence to their behaviors and patterns.
>
> Proposal
>
> Perhaps you are a homeowner configuring the interaction between your
> family and all the smart devices in your home. Or you might be a global
> company orchestrating millions of devices and people across different
> continents. Either way you face the same fundamental problem; namely, how
> do you manage many points in a secure robust and meaningful manner? Apache
> iota is an open source software system that enables homeowners and global
> companies to download a software system that provides secure and robust
> orchestration.
>
> The iota system consists of a variety of components:
>
> A basic but extensible desktop
> An extensible mechanism for capturing data from a variety of sources
> A set of translators that feed the data capture mechanism and a framework
> for the development of additional translators
> A secure means of moving data using digital envelopes based on symmetric
> and asymmetric encryption and decryption via Apache Kafka
> Optionally maintaining data encrypted in a datastore
> Support for a variety of data repositories
> Authentication and authorization using OAuth2
> Secure APIs for access to data and the system information
> User management
> Device management
> Automated software upgrades via Salt
> Configuration management
> Robust basic infrastructure based on Apache Mesos that enables scalability
> Dockerized applications
> Background
>
> We are in the midst of a revolution in which the Internet of Things (IoT)
> is poised to impact the development of our society in ways we can not even
> begin to imagine. Unfortunately, we know of no coherent OSS (Open Source
> Software) solution that can harness the potentialities of this increasingly
> important trend. Manufacturers of IoT devices, both in the consumer and
> industrial spaces, continue to develop proprietary systems. Apache iota is
> an open source IoT system that creates an open source solution enabling the
> orchestration of IoT devices that brings the benefits of OSS to this space.
> Apache iota was initially developed by Litbit and is deployed in a growing
> number of Industrial contexts, especially in the context of Data Center
> Infrastructure.
>
> Rationale
>
> Apache iota is a general platform for orchestrating IoT devices in both
> consumer and industrial contexts. It is complementary to the existing
> Apache projects and is itself built using of a number of Apache projects.
> Bringing iota into Apache is very beneficial to both the Apache community
> and the IoT community.
>
> The rapid growth of IoT needs to be harnessed in the Open Source
> Community. We believe the Apache Foundation is a great fit as the long-term
> home for iota, as it provides an established process for community-driven
> development and decision making by consensus. This is exactly the model 

Re: [VOTE] Accept Eagle into Apache Incubation

[Amareshwari Sriramdasu]

 substantial interest from various organizations.
>
> Reliance on Salaried Developers
> eBay invested in Eagle as the monitoring solution for Hadoop clusters and
> some of its key engineers are working full time on the project. In
> addition, since there is a growing need for securing sensitive data access
> we need a data activity monitoring solution for Hadoop, we look forward to
> other Apache developers and researchers to contribute to the project.
> Additional contributors, including Apache committers have plans to join
> this effort shortly. Also key to addressing the risk associated with
> relying on Salaried developers from a single entity is to increase the
> diversity of the contributors and actively lobby for Domain experts in the
> security space to contribute. Eagle intends to do this.
>
> Relationships with Other Apache Products
> Eagle has a strong relationship and dependency with Apache Hadoop, HBase,
> Spark, Kafka and Storm. Being part of Apache’s Incubation community, could
> help with a closer collaboration among these projects and as well as
> others. An Excessive Fascination with the Apache Brand Eagle is proposing
> to enter incubation at Apache in order to help efforts to diversify the
> committer-base, not so much to capitalize on the Apache brand. The Eagle
> project is in production use already inside eBay, but is not expected to be
> an eBay product for external customers. As such, the Eagle project is not
> seeking to use the Apache brand as a marketing tool.
>
> Documentation
> Information about Eagle can be found at https://github.com/eBay/Eagle.
> The following link provide more information about Eagle http://goeagle.io<
> http://goeagle.io/>.
>
> Initial Source
> Eagle has been under development since 2014 by a team of engineers at eBay
> Inc. It is currently hosted on Github.com under an Apache license 2.0 at
> https://github.com/eBay/Eagle. Once in incubation we will be moving the
> code base to apache git library.
>
> External Dependencies
> Eagle has the following external dependencies.
> Basic
> •JDK 1.7+
> •Scala 2.10.4
> •Apache Maven
> •JUnit
> •Log4j
> •Slf4j
> •Apache Commons
> •Apache Commons Math3
> •Jackson
> •Siddhi CEP engine
>
> Hadoop
> •Apache Hadoop
> •Apache HBase
> •Apache Hive
> •Apache Zookeeper
> •Apache Curator
>
> Apache Spark
> •Spark Core Library
>
> REST Service
> •Jersey
>
> Query
> •Antlr
>
> Stream processing
> •Apache Storm
> •Apache Kafka
>
> Web
> •AngularJS
> •jQuery
> •Bootstrap V3
> •Moment JS
> •Admin LTE
> •html5shiv
> •respond
> •Fastclick
> •Date Range Picker
> •Flot JS
>
> Cryptography
> Eagle will eventually support encryption on the wire. This is not one of
> the initial goals, and we do not expect Eagle to be a controlled export
> item due to the use of encryption. Eagle supports but does not require the
> Kerberos authentication mechanism to access secured Hadoop services.
>
> Required Resources
>
> Mailing List
> •eagle-private for private PMC discussions
> •eagle-dev for developers
> •eagle-commits for all commits
> •eagle-users for all eagle users
>
> Subversion Directory
> •Git is the preferred source control system.
>
> Issue Tracking
> •JIRA Eagle (Eagle)
>
> Other Resources
> The existing code already has unit tests so we will make use of existing
> Apache continuous testing infrastructure. The resulting load should not be
> very large.
>
> Initial Committers
> •Seshu Adunuthula 
> •Arun Manoharan 
> •Edward Zhang 
> •Hao Chen 
> •Chaitali Gupta 
> •Libin Sun 
> •Jilin Jiang 
> •Qingwen Zhao 
> •Hemanth Dendukuri 
> •Senthil Kumar 
>
>
> Affiliations
> The initial committers are employees of eBay Inc.
>
> Sponsors
>
> Champion
> •Henry Saputra  - Apache IPMC member
>
> Nominated Mentors
> •Owen O’Malley < omalley at apache dot org > - Apache IPMC member,
> Hortonworks
> •Henry Saputra  - Apache IPMC member
> •Julian Hyde  - Apache IPMC member,
> Hortonworks
> •Amareshwari Sriramdasu  - Apache IPMC
> member
> •Taylor Goetz  - Apache IPMC member, Hortonworks
>
> Sponsoring Entity
> We are requesting the Incubator to sponsor this project.
>
>

Re: [DISCUSS] Eagle incubator proposal

[Amareshwari Sriramdasu]

I would like to volunteer as mentor and help the project, if you are
looking for more mentors.

Thanks
Amareshwari

On Mon, Oct 19, 2015 at 9:03 PM, Manoharan, Arun 
wrote:

> Hello Everyone,
>
> My name is Arun Manoharan. Currently a product manager in the Analytics
> platform team at eBay Inc.
>
> I would like to start a discussion on Eagle and its joining the ASF as an
> incubation project.
>
> Eagle is a Monitoring solution for Hadoop to instantly identify access to
> sensitive data, recognize attacks, malicious activities and take actions in
> real time. Eagle supports a wide variety of policies on HDFS data and Hive.
> Eagle also provides machine learning models for detecting anomalous user
> behavior in Hadoop.
>
> The proposal is available on the wiki here:
> https://wiki.apache.org/incubator/EagleProposal
>
> The text of the proposal is also available at the end of this email.
>
> Thanks for your time and help.
>
> Thanks,
> Arun
>
> 
>
> Eagle
>
> Abstract
> Eagle is an Open Source Monitoring solution for Hadoop to instantly
> identify access to sensitive data, recognize attacks, malicious activities
> in hadoop and take actions.
>
> Proposal
> Eagle audits access to HDFS files, Hive and HBase tables in real time,
> enforces policies defined on sensitive data access and alerts or blocks
> user’s access to that sensitive data in real time. Eagle also creates user
> profiles based on the typical access behaviour for HDFS and Hive and sends
> alerts when anomalous behaviour is detected. Eagle can also import
> sensitive data information classified by external classification engines to
> help define its policies.
>
> Overview of Eagle
> Eagle has 3 main parts.
> 1.Data collection and storage - Eagle collects data from various hadoop
> logs in real time using Kafka/Yarn API and uses HDFS and HBase for storage.
> 2.Data processing and policy engine - Eagle allows users to create
> policies based on various metadata properties on HDFS, Hive and HBase data.
> 3.Eagle services - Eagle services include policy manager, query service
> and the visualization component. Eagle provides intuitive user interface to
> administer Eagle and an alert dashboard to respond to real time alerts.
>
> Data Collection and Storage:
> Eagle provides programming API for extending Eagle to integrate any data
> source into Eagle policy evaluation framework. For example, Eagle hdfs
> audit monitoring collects data from Kafka which is populated from namenode
> log4j appender or from logstash agent. Eagle hive monitoring collects hive
> query logs from running job through YARN API, which is designed to be
> scalable and fault-tolerant. Eagle uses HBase as storage for storing
> metadata and metrics data, and also supports relational database through
> configuration change.
>
> Data Processing and Policy Engine:
> Processing Engine: Eagle provides stream processing API which is an
> abstraction of Apache Storm. It can also be extended to other streaming
> engines. This abstraction allows developers to assemble data
> transformation, filtering, external data join etc. without physically bound
> to a specific streaming platform. Eagle streaming API allows developers to
> easily integrate business logic with Eagle policy engine and internally
> Eagle framework compiles business logic execution DAG into program
> primitives of underlying stream infrastructure e.g. Apache Storm. For
> example, Eagle HDFS monitoring transforms audit log from Namenode to object
> and joins sensitivity metadata, security zone metadata which are generated
> from external programs or configured by user. Eagle hive monitoring filters
> running jobs to get hive query string and parses query string into object
> and then joins sensitivity metadata.
> Alerting Framework: Eagle Alert Framework includes stream metadata API,
> scalable policy engine framework, extensible policy engine framework.
> Stream metadata API allows developers to declare event schema including
> what attributes constitute an event, what is the type for each attribute,
> and how to dynamically resolve attribute value in runtime when user
> configures policy. Scalable policy engine framework allows policies to be
> executed on different physical nodes in parallel. It is also used to define
> your own policy partitioner class. Policy engine framework together with
> streaming partitioning capability provided by all streaming platforms will
> make sure policies and events can be evaluated in a fully distributed way.
> Extensible policy engine framework allows developer to plugin a new policy
> engine with a few lines of codes. WSO2 Siddhi CEP engine is the policy
> engine which Eagle supports as first-class citizen.
> Machine Learning module: Eagle provides capabilities to define user
> activity patterns or user profiles for Hadoop users based on the user
> behaviour in the platform. These user profiles are modeled using Machine
> Learning algorithms and used for detection 

Re: [VOTE] Accept Concerted into the Apache Incubator

[Amareshwari Sriramdasu]

+1 (binding)

On Fri, Oct 9, 2015 at 5:55 PM, Atri Sharma  wrote:

> Hi all,
>
> Following the discussion about Concerted I would like to call a vote for
> accepting Concerted as a new incubator project.
>
> The proposal text is included below, and available on the wiki:
>
> https://wiki.apache.org/incubator/ConcertedProposal
>
> The vote is open for 72 hours:
>
> [ ] +1 accept Concerted in the Incubator
> [ ] ±0
> [ ] -1 (please give reason)
>
> Regards,
>
> Atri
>
> = Abstract =
>
> Concerted is an in memory write less read more engine aimed to provide
> extreme read performance with very high degree of concurrency and
> scalability and focus on minimizing own resource footprint.
>
> = Proposal =
> Concerted is built on the principal that a new type of workload is
> dominating the scene and is now needed to be supported. These are the large
> data set analytical workloads being analyzed or used on large clusters or
> high power machines. Large analytical workloads depend on the ability to
> query large data sets efficiently and in high concurrency while maintaining
> semantics such as immediate consistency. An in memory engine designed to
> support extreme read queries while providing support for aggregation
> through various features (such as multidimensional representation of
> tuples) will accelerate many usecases around large scale analytics.
>
> Concerted believes that best understanding of user application lies with
> user application developer. The need for massive read scaling should be on
> demand and should be flexible to the level that user can decide as to which
> representation and access of data suits his/her current requirements.
> Hence, Concerted is not built in a traditional client/server model.
> Concerted provides users with an API which can be used to load, read,
> update and delete data. User chooses which data structure has to be used
> for his current requirements. All API access is covered by Concerted's
> internal systems like lock manager, transaction manager and cache manager
> which ensure that reads scale to high level in every API call.
>
> Concerted is a Do It Yourself in memory platform for making in memory
> supporting engines. The use case we think of is supporting big data
> warehouses like Hive, but there are endless use cases for a custom, highly
> scalable in memory platform.
>
> The goal of this proposal is to leverage an existing code base available on
> Github and licensed under the Apache License 2.0 to build a community
> around the project. Currently the community consists of existing hackers of
> Concerted as well as people who have been following and associated with the
> project since a while as well as database experts who are excited about
> building a project like this. We are hoping that entering into Apache would
> help us attract more contributors as well as connect with existing big data
> projects like Apache Hive, Apache HAWQ, Apache Storm, Apache Tajo, Apache
> Spark, Apache Geode to leverage their community base while assisting in
> their use cases with Concerted. We had a discussion with founders of Apache
> Tajo and they showed interest in using Concerted for some of their use
> cases.
> = Background =
> Relational databases were built with the cost of physical memory in mind.
> The cost is no longer very relevant and physical memory is now available on
> demand. Another driving factor behind Concerted is that there is a paradigm
> shift with big data coming into picture. Disk IO speeds are more of a
> bottleneck than ever before. Combining the read dominance of analytical
> workload with the speed of in memory structures, Concerted fits the current
> scene. Also, supporting OLAP workloads with in memory support for faster
> read constant queries and joins will be useful.
>
> = Rationale =
> As explained above, large analytical workloads need an in memory
> lightweight engine which supports massive read concurrency, ground level
> support for aggregations and analytics, extreme scalability and high read
> performance, along with the engine being very light itself. Concerted aims
> to solve these needs. Concerted is designed and built with three goals as
> objectives:
>
>
> Performance
> To provide high performance access to data from a large number of rows,
> Concerted uses efficient representation and in memory indexing of data
> coupled with high performance transactions, custom transactions and
> lightweight locking and lockless techniques and an intelligent locking
> manager.
>
> Scalability
> Concerted is built with extreme concurrency and scalability in mind.
>
> Efficiency
> Concerted aims to give expected performance under vast variety of
> workloads and aims to have as low footprint as possible.
>
> = Initial Goals =
> The initial goal is to leverage an existing code base and invest in
> building a community around the project. We anticipate a lot of initial
> restructuring of the existing code so that it 

Re: [VOTE] Accept Horn into the ASF incubator

[Amareshwari Sriramdasu]

+1 (binding)

On Tue, Sep 1, 2015 at 4:43 AM, Edward J. Yoon 
wrote:

> Hi folks,
>
> I would like to call a vote to accept Horn, as a new Apache Incubator
> project. The full proposal is available at the end of this mail and as
> a https://wiki.apache.org/incubator/HornProposal (the changes from
> initial discussion draft are addition of 2 committers from cldi-kaist
> team and Rich as a mentor).
>
> The VOTE is open for at least the next 72 hours:
>
> [ ] +1 Accept Horn into the Apache Incubator
> [ ] 0
> [ ] -1 Do not accept Horn into the Apache Incubator bc ..
>
> I'd like to get the voting started w/ my own +1
>
> Thanks!
>
> == Abstract ==
>
> Horn [hɔ:n] (korean meaning of Horn is a "Spirit") is a neuron-centric
> programming APIs and execution framework for large-scale deep
> learning, built on top of Apache Hama.
>
> == Proposal ==
>
> It is a goal of the Horn to provide a neuron-centric programming APIs
> which allows user to easily define the characteristic of artificial
> neural network model and its structure, and its execution framework
> that leverages the heterogeneous resources on Hama and Hadoop YARN
> cluster.
>
> == Background ==
>
> The initial ANN code was developed at Apache Hama project by a
> committer, Yexi Jiang (Facebook) in 2013. The motivation behind this
> work is to build a framework that provides more intuitive programming
> APIs like Google's MapReduce or Pregel and supports applications
> needing large model with huge memory consumptions in distributed way.
>
> == Rationale ==
>
> While many of deep learning open source softwares such as Caffe,
> DeepDist, DL4j, and NeuralGiraph are still data or model parallel
> only, we aim to support both data and model parallelism and also
> fault-tolerant system design. The basic idea of data and model
> parallelism is use of the remote parameter server to parallelize model
> creation and distribute training across machines, and the BSP
> framework of Apache Hama for performing asynchronous mini-batches.
> Within single BSP job, each task group works asynchronously using
> region barrier synchronization instead of global barrier
> synchronization, and trains large-scale neural network model using
> assigned data sets in BSP paradigm. Thus, we achieve data and model
> parallelism. This architecture is inspired by Google's !DistBelief
> (Jeff Dean et al, 2012).
>
> == Initial Goals ==
>
> Some current goals include:
>
>  * builds new community
>  * provides more intuitive programming APIs
>  * needs both data and model parallelism support
>  * must run natively on both Hama and Hadoop2
>  * needs also GPUs and InfiniBand support (FPGAs if possible)
>
> == Current Status ==
>
> === Meritocracy ===
>
> The core developers understand what it means to have a process based
> on meritocracy. We will provide continuous efforts to build an
> environment that supports this, encouraging community members to
> contribute.
>
> === Community ===
>
> A small community has formed within the Apache Hama project community,
> universities, and companies such as deep learning startup, instant
> messenger service company, and mobile manufacturing company. And many
> people are interested in the large-scale deep learning platform
> itself. By bringing Horn into Apache, we believe that the community
> will grow even bigger.
>
> === Core Developers ===
>
> Edward J. Yoon, Thomas Jungblut, Jungin Lee, and Minho Kim
>
> == Known Risks ==
>
> === Orphaned Products ===
>
> Apache Hama is already a core open source component at Samsung
> Electronics, and Horn also will be used by Samsung Electronics and
> Cldi Inc., and so there is no direct risk for this project to be
> orphaned.
>
> === Inexperience with Open Source ===
>
> Some are very new and the others have experience using and/or working
> on Apache open source projects.
>
> === Homogeneous Developers ===
>
> The initial committers are from different organizations such as,
> Microsoft, Samsung Electronics, Seoul National University, Technical
> University of Munich, KAIST, LINE plus, and Cldi Inc.
>
> === Reliance on Salaried Developers ===
>
> Few will be worked as a full-time open source developer. Other
> developers will also start working on the project in their spare time.
>
> === Relationships with Other Apache Products ===
>
>  * Horn is based on Apache Hama
>  * Apache Zookeeper is used for distributed locking service
>  * Natively run on Apache Hadoop and Mesos
>  * Horn can be somewhat overlapped with Singa podling (If possible,
> we'd also like to use Singa or Caffe to do the heavy lifting part).
>
> === An Excessive Fascination with the Apache Brand ===
>
> Horn itself will hopefully have benefits from Apache, in terms of
> attracting a community and establishing a solid group of developers,
> but also the relation with Apache Hadoop, Zookeeper, and Hama. These
> are the main reasons for us to send this proposal.
>
> == Documentation ==
>
> Initial plan about Horn can be 

Re: [VOTE] Accept Apex into the Apache Incubator

[Amareshwari Sriramdasu]

+1 binding

On Thu, Aug 13, 2015 at 8:18 PM, P. Taylor Goetz ptgo...@apache.org wrote:

 Following the discussion thread [1], I would like to call a VOTE for
 Accepting Apex as a new Apache Incubator project.

 The proposal is available on the wiki [2] and is also attached below.

 The VOTE will be open for at least 72 hours.

 [ ] +1 Accept Apex into the Incubator
 [ ] ±0 No opinion
 [ ] -1 Do not accept Apex into the Incubator because…

 Thanks,

 -Taylor

 [1] http://s.apache.org/apex_discuss
 [2] https://wiki.apache.org/incubator/ApexProposal


 == Abstract ==
 Apex is an enterprise grade native YARN big data-in-motion platform that
 unifies stream processing as well as batch processing. Apex processes big
 data in-motion in a highly scalable, highly performant, fault tolerant,
 stateful, secure, distributed, and an easily operable way. It provides a
 simple API that enables users to write or re-use generic Java code, thereby
 lowering the expertise needed to write big data applications.

 Functional and operational specifications are separated. Apex is designed
 in a way to enable users to write their own code (aka user defined
 functions) as is and leave all operability to the platform. The API is very
 simple and is designed to allow users to drop in their code as is. The
 platform mainly deals with operability and treats functional code as a
 black box. Operability includes fault tolerance, scalability, security,
 ease of use, metrics api, webservices, etc. In other words there is no
 separation of UDF (user defined functions), as all functional code is UDF.
 This frees users to focus on functional development, and lets platform
 provide operability support. The same code runs as is with different
 operability attributes. The data-in-motion architecture of Apex unifies
 stream as well as batch processing in a single platform. Since Apex is a
 native YARN application, it leverages all the components of YARN without
 duplication. Apex was developed with YARN in mind and has no overlapping
 components/functionality with YARN.

 The Apex platform is supplemented by project Malhar, which is a library of
 operators that implement common business logic functions needed by
 customers who want to quickly develop applications. These operators provide
 access to HDFS, S3, NFS, FTP, and other file systems;  Kafka, ActiveMQ,
 RabbitMQ, JMS, and other message systems; MySql, Cassandra, MongoDB, Redis,
 HBase, CouchDB and other databases along with JDBC connectors. The Malhar
 library also includes a host of other common business logic patterns that
 help users to significantly reduce the time it takes to go into production.
 Ease of integration with all other big data technologies is one of the
 primary missions of Malhar.

 == Proposal ==
 The goal of this proposal is to establish the core engine of DataTorrent
 RTS product as an Apache Software Foundation (ASF) project in order to
 build a vibrant, diverse, and self-governed open source community around
 the technology. DataTorrent will continue to sell management tools,
 application building tools, easy to use big data applications, and custom
 high end business logic operators. This proposal covers the Apex source
 code (written in Java), Apex documentation and other materials currently
 available on https://github.com/DataTorrent/Apex. This proposal also
 covers the Malhar source code (written in Java), Malhar documentation, and
 other materials currently available on
 https://github.com/DataTorrent/Malhar. We have done a trademark check on
 the name Apex, and have concluded that the Apex name is likely to be a
 suitable project name.

 == Background ==
 DataTorrent RTS is a mature and robust product developed as a native YARN
 application. RTS 1.0 was launched in summer of 2014; RTS 2.0 was launched
 in Jan 2015. Both were well received by customers. RTS 3.0 was launched at
 end of July 2015. RTS is among the first enterprise grade platform that was
 developed from the ground up as native YARN application. DataTorrent RTS is
 currently maintained by engineers as a closed source project. Even though
 the engineers behind RTS are experienced software engineers and are
 knowledge leaders in data-in-motion platforms, they have had little
 exposure to the open source governance process. Customers are currently
 running applications based on DataTorrent RTS in production.

 == Rationale ==
 Big data applications written for non-Hadoop platforms typically require
 major rewrites  to get them to work with Hadoop. This rewriting creates a
 significant bottleneck in terms of resources (expertise) which in turn
 jeopardizes the viability of such an endeavour. It is hard enough to
 acquire big data expertise, demanding additional expertise to do a major
 code conversion makes it a very hard problem for projects to successfully
 migrate to Hadoop. Also, due to the batch processing nature of Hadoop’s
 MapReduce paradigm, users often have to wait tens of minutes to see 

[RESULT] [VOTE] Release of Apache Lens 2.2.0-beta-incubating

[Amareshwari Sriramdasu]

Hi all,

The vote is now closed and passed with 5 +1 votes (4 binding), no -1 votes
and no 0 votes.
We now have the required number of positive binding votes and will therefore
proceed with publishing this release.

Thank you all for voting.

Binding votes :
+1 Amareshwari Sriramadasu
+1 Justin Mclean
+1 Sharad Agarwal
+1 Chris Douglas

Non-binding votes :
+1 Jaideep Dhok

Vote on incubator list :
http://mail-archives.apache.org/mod_mbox/incubator-general/201507.mbox/%3CCAPYoVTh6CUCogVe2pP2ZFH8OSG4G6gUj%2BvbOUhEqh3wrZTZuqA%40mail.gmail.com%3E

Vote on dev list :
http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201507.mbox/%3CCAPYoVThzQCHdYVASR35zeYqHj_tWo93GuzTLzCrmRAq3qMjecg%40mail.gmail.com%3E

Thanks
Amareshwari

The vo
On Sun, Jul 12, 2015 at 8:39 AM, Jaideep Dhok jaideep.d...@inmobi.com
wrote:

 Hello everyone,

 This is the call for vote for the following RC to be released as official
 Apache Lens 2.2.0-beta-incubating release. This is our third release.

 Apache Lens provides an Unified Analytics interface. Lens aims to cut the
 Data Analytics silos by providing a single view of data across multiple
 tiered data stores and optimal execution environment for the analytical
 query. It seamlessly integrates Hadoop with traditional data warehouses to
 appear like one.

 Vote on dev list:

 http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201507.mbox/%3CCAPYoVThzQCHdYVASR35zeYqHj_tWo93GuzTLzCrmRAq3qMjecg%40mail.gmail.com%3E

 Result of vote on dev list:

 http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201507.mbox/%3CCAPYoVThOEAeMiNdtef%3D35QxRLetryRFKs3ED-oeCh2xi1KEqww%40mail.gmail.com%3E

 The commit id is 9c45f1cb4c69ec5de6fe3320abdd5bd85c250e9f
 
 https://git-wip-us.apache.org/repos/asf/incubator-lens/repo?p=incubator-lens.git;a=commit;h=9c45f1cb4c69ec5de6fe3320abdd5bd85c250e9f
 
  -

 https://git-wip-us.apache.org/repos/asf/incubator-lens/repo?p=incubator-lens.git;a=commit;h=9c45f1cb4c69ec5de6fe3320abdd5bd85c250e9f


 This corresponds to the tag: apache-lens-2.2.0-beta-incubating -

 https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=tag;h=refs/tags/apache-lens-2.2.0-beta-incubating


 The release archives (tar.gz/.zip), signature, and checksums are
 here:
 *
 https://dist.apache.org/repos/dist/dev/incubator/lens/apache-lens-2.2.0-beta-incubating-rc0/
 
 https://dist.apache.org/repos/dist/dev/incubator/lens/apache-lens-2.2.0-beta-incubating-rc0/
 *

 You can find the KEYS file here:
 * https://dist.apache.org/repos/dist/release/incubator/lens/KEYS

 The release candidate consists of the following source distribution
 archive:
 apache-lens-2.2.0-beta-incubating-source-release.zip

 In addition, the following supplementary binary distributions are
 provided for user convenience at the same location:
 apache-lens-2.2.0-beta-incubating-bin.tar.gz

 The licensing of bundled bits in the archives have not changed from
 previous release, which are
 documented
 https://cwiki.apache.org/confluence/display/LENS/Licensing+in+Apache+Lens

 The Nexus Staging URL:
 https://repository.apache.org/content/repositories/orgapachelens-1005

 Release notes available at


 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329586projectId=12315923


 Vote will be open for at least 72 hours

 [ ] +1 approve
 [ ] 0 no opinion
 [ ] -1 disapprove (and reason why)

 +1 from my side for the release.

 Thanks,
 Jaideep Dhok

 --
 _
 The information contained in this communication is intended solely for the
 use of the individual or entity to whom it is addressed and others
 authorized to receive it. It may contain confidential or legally privileged
 information. If you are not the intended recipient you are hereby notified
 that any disclosure, copying, distribution or taking any action in reliance
 on the contents of this information is strictly prohibited and may be
 unlawful. If you have received this communication in error, please notify
 us immediately by responding to this email and then delete it from your
 system. The firm is neither liable for the proper and complete transmission
 of the information contained in this communication nor for any delay in its
 receipt.

[ANNOUNCE] Aapche Lens 2.2.0-beta-incubating released

[Amareshwari Sriramdasu]

Hi all,

The Apache Lens team is proud to announce the release of Apache Lens
2.2.0-beta-incutaing.

Apache Lens provides an Unified Analytics interface. Lens aims to cut the
Data Analytics silos by providing a single view of data across multiple
tiered data stores and optimal execution environment for the analytical
query. It seamlessly integrates Hadoop with traditional data warehouses to
appear like one.

This release includes OLAP features like support for multiple expressions
and union queries, many CLI Improvements, Descriptive error codes,
integrates with Zeppelin and many more bug fixes and simple improvements.

The release artifacts are downloadable from
http://lens.incubator.apache.org/releases/download.html

Maven jar artifacts have also been made available on
https://repository.apache.org/content/repositories/releases/org/apache/lens/

Release notes available at
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329586projectId=12315923

More details on Apache Lens can be found at
http://lens.incubator.apache.org/

Getting started available at
http://lens.incubator.apache.org/lenshome/quick-start.html

We would like to thank all the contributors who made this release possible.

Thanks,
The Apache Lens team

Re: [VOTE] Release of Apache Lens 2.2.0-beta-incubating

[Amareshwari Sriramdasu]

+1 (binding).

Recasting my vote from dev list.

Thanks
Amareshwari

On Sun, Jul 12, 2015 at 8:39 AM, Jaideep Dhok jaideep.d...@inmobi.com
wrote:

 Hello everyone,

 This is the call for vote for the following RC to be released as official
 Apache Lens 2.2.0-beta-incubating release. This is our third release.

 Apache Lens provides an Unified Analytics interface. Lens aims to cut the
 Data Analytics silos by providing a single view of data across multiple
 tiered data stores and optimal execution environment for the analytical
 query. It seamlessly integrates Hadoop with traditional data warehouses to
 appear like one.

 Vote on dev list:

 http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201507.mbox/%3CCAPYoVThzQCHdYVASR35zeYqHj_tWo93GuzTLzCrmRAq3qMjecg%40mail.gmail.com%3E

 Result of vote on dev list:

 http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201507.mbox/%3CCAPYoVThOEAeMiNdtef%3D35QxRLetryRFKs3ED-oeCh2xi1KEqww%40mail.gmail.com%3E

 The commit id is 9c45f1cb4c69ec5de6fe3320abdd5bd85c250e9f
 
 https://git-wip-us.apache.org/repos/asf/incubator-lens/repo?p=incubator-lens.git;a=commit;h=9c45f1cb4c69ec5de6fe3320abdd5bd85c250e9f
 
  -

 https://git-wip-us.apache.org/repos/asf/incubator-lens/repo?p=incubator-lens.git;a=commit;h=9c45f1cb4c69ec5de6fe3320abdd5bd85c250e9f


 This corresponds to the tag: apache-lens-2.2.0-beta-incubating -

 https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=tag;h=refs/tags/apache-lens-2.2.0-beta-incubating


 The release archives (tar.gz/.zip), signature, and checksums are
 here:
 *
 https://dist.apache.org/repos/dist/dev/incubator/lens/apache-lens-2.2.0-beta-incubating-rc0/
 
 https://dist.apache.org/repos/dist/dev/incubator/lens/apache-lens-2.2.0-beta-incubating-rc0/
 *

 You can find the KEYS file here:
 * https://dist.apache.org/repos/dist/release/incubator/lens/KEYS

 The release candidate consists of the following source distribution
 archive:
 apache-lens-2.2.0-beta-incubating-source-release.zip

 In addition, the following supplementary binary distributions are
 provided for user convenience at the same location:
 apache-lens-2.2.0-beta-incubating-bin.tar.gz

 The licensing of bundled bits in the archives have not changed from
 previous release, which are
 documented
 https://cwiki.apache.org/confluence/display/LENS/Licensing+in+Apache+Lens

 The Nexus Staging URL:
 https://repository.apache.org/content/repositories/orgapachelens-1005

 Release notes available at


 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329586projectId=12315923


 Vote will be open for at least 72 hours

 [ ] +1 approve
 [ ] 0 no opinion
 [ ] -1 disapprove (and reason why)

 +1 from my side for the release.

 Thanks,
 Jaideep Dhok

 --
 _
 The information contained in this communication is intended solely for the
 use of the individual or entity to whom it is addressed and others
 authorized to receive it. It may contain confidential or legally privileged
 information. If you are not the intended recipient you are hereby notified
 that any disclosure, copying, distribution or taking any action in reliance
 on the contents of this information is strictly prohibited and may be
 unlawful. If you have received this communication in error, please notify
 us immediately by responding to this email and then delete it from your
 system. The firm is neither liable for the proper and complete transmission
 of the information contained in this communication nor for any delay in its
 receipt.

Re: [VOTE] Release Apache Atlas version 0.5-incubating

[Amareshwari Sriramdasu]

+1 (binding)

Verified the following :

   -  Checksums match.
   -  Signature looks good.
   -  Artifacts contain incubating word.
   -  DISCLAIMER exists.
   -  Top level LICENSE and NOTICE files look good.
   -  Built from source successfully.


Thanks
Amareshwari


On Thu, Jun 25, 2015 at 7:16 AM, Venkatesh Seetharam venkat...@apache.org
wrote:

 Hello folks,

 This is a call for a vote on the Apache Atlas 0.5 incubating release.

 A vote was held on developer mailing list and it passed with 9 +1's.

 Vote thread: http://s.apache.org/RyM
 Results thread: http://s.apache.org/f8S

 The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha):
 https://dist.apache.org/repos/dist/dev/incubator/atlas/0.5.0-incubating-rc0

 The commit id (318abdacd4c4d17a3d613c1cda04a58194042715) to ve voted upon:

 https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=318abdacd4c4d17a3d613c1cda04a58194042715

 The tag to be voted upon:

 https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=tag;h=refs/tags/release-0.5-rc0

 The list of fixed issues:

 https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=release-log.txt;h=df92e95d408469b2bea5b988fb9be3de802b9f2b;hb=318abdacd4c4d17a3d613c1cda04a58194042715

 Keys to verify the signature of the release artifact are available at:
 http://www.apache.org/dist/incubator/atlas/KEYS
 PGP release keys:
 http://pgp.mit.edu/pks/lookup?op=vindexsearch=0x1B16738C42C7A5EA

 Note that this is a source only release and we are voting on the source.

 Checksums:
 SHA1 (apache-atlas-0.5-incubating-sources.tar.gz =
 ab21ce037e488a8e5b8986353adb853dc515abd4)
 MD5 (apache-atlas-0.5-incubating-sources.tar.gz) =
 e358ed601233f7d00ba9eb1c64095f55

 Vote will be open for 72 hours.

 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)

 Thanks!

 Regards,
 Venkatesh

[ANNOUNCE] Apache Lens 2.1.0-beta-incubating released

[Amareshwari Sriramdasu]

Hi all,

The Apache Lens team is proud to announce the release of Apache Lens
2.1.0-beta-incutaing. This is the second release of Apache Lens.

Apache Lens provides an Unified Analytics interface. Its a platform
which enables multi-dimensional queries in a unified way over datasets
stored in multiple warehouses. Lens aims to cut the data Analytics
silos by providing a single view of data across multiple tiered data
stores and optimal execution environment for the analytical query. It
seamlessly integrates Hadoop with traditional data warehouses to
appear like one.

More details on Apache Lens can be found at http://lens.incubator.apache.org/

Getting started available at
http://lens.incubator.apache.org/lenshome/quick-start.html

The release artifacts are downloadable from
http://lens.incubator.apache.org/releases/download.html

Maven jar artifacts have also been made available on
https://repository.apache.org/content/repositories/releases/org/apache/lens/

Release notes available at
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315923version=12328991

We would like to thank all the contributors who made this release possible.

Thanks,
The Apache Lens team

-

DISCLAIMER

Apache Lens is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by  Apache Incubator. Incubation is
required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making
process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection
of the completeness or stability of the code, it does indicate that
the project has yet to be fully endorsed by the ASF.

Re: [VOTE] Release of Apache Lens 2.1.0-beta-incubating

[Amareshwari Sriramdasu]

+1 (binding) from my side for the release.

Thanks,
Amareshwari

On Thu, Apr 30, 2015 at 5:35 PM, Amareshwari Sriramdasu 
amareshw...@apache.org wrote:

 Hello everyone,

 This is the call for vote for the following RC to be released as official
 ApacheLens 2.1.0-beta-incubating release. This is our second release.

 Apache Lens provides an Unified Analytics interface. Lens aims to cut the
 Data Analytics silos by providing a single view of data across multiple
 tiered data stores and optimal execution environment for the analytical
 query. It seamlessly integrates Hadoop with traditional data warehouses to
 appear like one.
 Vote on dev list:

 http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201504.mbox/%3CCABJEuZfT4HDK3c4rKxPg0_Kkc8KDfRjUr%2BHmKaJH44H77OeU0g%40mail.gmail.com%3E

 Results of vote on dev list:

 http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201504.mbox/%3CCABJEuZe7rbjbwoiiOWKL8Lef%3Dsc%2BXcV173aiQ6Tpdwq7jz9ycQ%40mail.gmail.com%3E

 The commit id is fdd19b9c2b17e329465cbde62dbce6f8be435cec 
 :https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=commit;h=fdd19b9c2b17e329465cbde62dbce6f8be435cec

 This corresponds to the tag: apache-lens-2.1.0-beta-incubating 
 :https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=tag;h=refs/tags/apache-lens-2.1.0-beta-incubating

 The release archives (tar.gz/.zip), signature, and checksums are 
 here:https://dist.apache.org/repos/dist/dev/incubator/lens/apache-lens-2.1.0-beta-incubating-rc0

 You can find the KEYS file here:
 * https://dist.apache.org/repos/dist/release/incubator/lens/KEYS

 The release candidate consists of the following source distribution
 archive:
 apache-lens-2.1.0-beta-incubating-source-release.zip

 In addition, the following supplementary binary distributions are
 provided for user convenience at the same location:
 apache-lens-2.1.0-beta-incubating-bin.tar.gz

 The licensing of bundled bits in the archives have not changed from previous 
 release, which are documented at 
 https://cwiki.apache.org/confluence/display/LENS/Licensing+in+Apache+Lens

 The Nexus Staging URL:
 https://repository.apache.org/content/repositories/orgapachelens-1003

 Release notes available at 
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315923version=12328991


 Vote will be open for at least 72 hours . Please vote on releasing this RC

 [ ] +1 approve
 [ ] 0 no opinion
 [ ] -1 disapprove (and reason why)

 Thanks,
 Amareshwari

[VOTE] Release of Apache Lens 2.1.0-beta-incubating

[Amareshwari Sriramdasu]

Hello everyone,

This is the call for vote for the following RC to be released as official
ApacheLens 2.1.0-beta-incubating release. This is our second release.

Apache Lens provides an Unified Analytics interface. Lens aims to cut the
Data Analytics silos by providing a single view of data across multiple
tiered data stores and optimal execution environment for the analytical
query. It seamlessly integrates Hadoop with traditional data warehouses to
appear like one.
Vote on dev list:
http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201504.mbox/%3CCABJEuZfT4HDK3c4rKxPg0_Kkc8KDfRjUr%2BHmKaJH44H77OeU0g%40mail.gmail.com%3E

Results of vote on dev list:
http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201504.mbox/%3CCABJEuZe7rbjbwoiiOWKL8Lef%3Dsc%2BXcV173aiQ6Tpdwq7jz9ycQ%40mail.gmail.com%3E

The commit id is fdd19b9c2b17e329465cbde62dbce6f8be435cec
:https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=commit;h=fdd19b9c2b17e329465cbde62dbce6f8be435cec

This corresponds to the tag: apache-lens-2.1.0-beta-incubating
:https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=tag;h=refs/tags/apache-lens-2.1.0-beta-incubating

The release archives (tar.gz/.zip), signature, and checksums are
here:https://dist.apache.org/repos/dist/dev/incubator/lens/apache-lens-2.1.0-beta-incubating-rc0

You can find the KEYS file here:
* https://dist.apache.org/repos/dist/release/incubator/lens/KEYS

The release candidate consists of the following source distribution archive:
apache-lens-2.1.0-beta-incubating-source-release.zip

In addition, the following supplementary binary distributions are
provided for user convenience at the same location:
apache-lens-2.1.0-beta-incubating-bin.tar.gz

The licensing of bundled bits in the archives have not changed from
previous release, which are documented at
https://cwiki.apache.org/confluence/display/LENS/Licensing+in+Apache+Lens

The Nexus Staging URL:
https://repository.apache.org/content/repositories/orgapachelens-1003

Release notes available at
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315923version=12328991


Vote will be open for at least 72 hours . Please vote on releasing this RC

[ ] +1 approve
[ ] 0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
Amareshwari

Incubating into Apache

[Amareshwari Sriramdasu]

Hi all,

Its been nice woking for incubating Lens into Apache. Have created a doc at
https://cwiki.apache.org/confluence/display/LENS/Incubating+into+Apache
with respect to Lens work items. I thought it will be useful for new
projects incubating, so wanted to share with you all. We can improve the
document further and I can update the incubator doc itself with the
checklist if the doc looks fine.

Thanks
Amareshwari

Re: [VOTE] Accept Groovy into the Apache Incubator

[Amareshwari Sriramdasu]

+1 (non-binding)

On Thu, Mar 19, 2015 at 12:25 PM, Roman Shaposhnik r...@apache.org wrote:

 Following the discussion earlier in the thread:
http://s.apache.org/KWE

 I would like to call a VOTE for accepting Groovy
 as a new incubator project.

 The proposal is available at:
 https://wiki.apache.org/incubator/GroovyProposal
 and is also included at the bottom of this email.

 Vote is open until at least Saturday, 21st March 2015, 23:59:00 PST

  [ ] +1 accept Groovy in the Incubator
  [ ] ±0
  [ ] -1 because...

 Thanks,
 Roman.

 == Abstract ==
 Groovy is an object-oriented programming language for the Java
 platform. It is a language with features similar to those of Python,
 Ruby, Java, Perl, and Smalltalk.
 Groovy, if accepted by Incubator, will be a first major programming
 language developed under the umbrella of Apache Software Foundation.

 == Proposal ==
 Groovy is a programming language for the Java platform. It is a
 primarily dynamic language with features similar to those of Python,
 Ruby, Perl, and Smalltalk. It also has optional static type checking
 and static compilation facilities. It can be used as a scripting
 language for the Java Platform or to write complete applications, is
 compiled to Java Virtual Machine (JVM) bytecode, and interoperates
 with other Java code and libraries. Groovy uses a Java-like
 curly-bracket syntax. Most Java code is also syntactically valid
 Groovy, although semantics may be different. Groovy has long been
 developed under an Apache License v2.0 under an open governance
 community management process. However, so far Groovy has been a
 project mostly sponsored by a single company. This proposal aims at
 bringing Groovy community under the umbrella of the Apache Software
 Foundation.

 It must be explicitly noted, that a few sister projects such as Groovy
 Eclipse and others (some of them hosted under
 https://github.com/groovy and listed at
 http://groovy-lang.org/ecosystem.html) are not covered by this
 proposal. It is possible that these other projects will be joining ASF
 either independently or as sub-projects of Apache Groovy in the
 future. For now, we are only proposing groovy-core.

 == Background ==
 Groovy 1.0 was released on January 2, 2007, and Groovy 2.0 in July,
 2012. Groovy 2.5 is planned for release in 2015. Groovy 3.0 is planned
 for release in 2016, with support for a new Meta Object Protocol.
 Since version 2, Groovy can also be compiled statically, offering type
 inference and performance very close to that of Java. Groovy 2.4 will
 be the last major release under Pivotal Software's sponsorship, which
 is scheduled to end on March 31, 2015.

 == Rationale ==
 Groovy is a pretty mature language. After 12 years of development, it
 has grown from being primarily a dynamic scripting language on the JVM
 to an optionally statically compiled language allowing the same
 performance level as Java applications. With the release of Groovy
 2.4, the language targets the largest pool of mobile developers with
 native Android support. Groovy has been integrated in a large number
 of applications, including well known open-source projects like
 Jenkins, Gradle, ElasticSearch, Spring and more.

 There are multiple alternative languages on the JVM: Scala, Clojure,
 Ceylon, Kotlin, JRuby, Golo and others but Groovy is the only one
 which has proved to be very easy to integrate with Java in both ways:
 Groovy code using Java code, but also Java code using Groovy code.
 Groovy even provides a joint compiler which allows interdependent Java
 and Groovy classes to compile together. Groovy also supports dynamic
 code generation, that is to say classes at runtime, making it a
 perfect fit for scripting. With a very lightweight and malleable
 syntax, it is also easy to build internal Domain Specific Languages
 (DSLs) which integrate smoothly within applications.

 Groovy provides a number of unique features, like builders (Java 8 has
 lambdas but still has syntactic overhead and no notion of delegate),
 AST transformations (compile-time metaprogramming) or type checking
 extensions (which allows the developer to bring the compiler to levels
 of type checking and type inference that go far beyond what other
 languages do). Groovy also provides powerful integration options and
 customizations which set it apart from other languages. Groovy is also
 unique in the way it allows the developer to choose between various
 paradigms without compromise: functional vs object-oriented,
 statically compiled vs dynamic, scripting vs applications, etc.

 Despite all those advantages, and the fact that Groovy is widely
 adopted (4.5 million downloads in 2014 for Groovy alone), only a few
 Apache projects include Groovy and not a lot of them leverage its full
 power. Some developers tend to choose Scala for example to build DSLs
 without even knowing that the learning curve is much easier with
 Groovy, or that they can leverage powerful type inference in their own
 

[ANNOUNCE] Aapche Lens 2.0.1-beta-incubating release

[Amareshwari Sriramdasu]

Hi all,

The Apache Lens team is proud to announce the release of Apache Lens
2.0.1-beta-incutaing. This is the first release of Apache Lens.

Apache Lens provides an Unified Analytics interface. Lens aims to cut the
Data Analytics silos by providing a single view of data across multiple
tiered data stores and optimal execution environment for the analytical
query. It seamlessly integrates Hadoop with traditional data warehouses to
appear like one.

More details on Apache Lens can be found at
http://lens.incubator.apache.org/

Getting started available at
http://lens.incubator.apache.org/lenshome/quick-start.html

The release artifacts are downloadable from
http://lens.incubator.apache.org/releases/download.html

Maven jar artifacts have also been made available on
https://repository.apache.org/content/repositories/releases/org/apache/lens/

Release notes available at
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315923version=12328990

We would like to thank all the contributors who made this release possible.

Thanks,
The Apache Lens team

-

DISCLAIMER

Apache Lens is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by  Apache Incubator. Incubation is required of
all newly accepted projects until a further review indicates that the
infrastructure, communications, and decision making process have stabilized
in a manner consistent with other successful ASF projects. While incubation
status is not necessarily a reflection of the completeness or stability of
the code, it does indicate that the project has yet to be fully endorsed by
the ASF.

[RESULT] [VOTE] Release Apache Lens 2.0.1-beta-incubating

[Amareshwari Sriramdasu]

Hi all,

The vote is now closed and passed with 4 binding +1 votes, no -1 votes and
no 0 votes.
We now have the required number of positive binding votes and will therefore
proceed with publishing this release.

Thank you all for voting.

Binding votes :
+1 Justin Mclean
+1 Jean-Baptiste Onofré
+1 Jakob Homan
+1 *Chris Douglas*

Vote on incubator list :
http://mail-archives.apache.org/mod_mbox/incubator-general/201502.mbox/%3CCABJEuZc4%3DVAXxqQmYpqR9Zqo%2BGnZgmegcw%2BwEeJZKUK8TPNuuQ%40mail.gmail.com%3E

Vote on dev list :
http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201502.mbox/%3CCABJEuZfss9i52WrRQORMZTrfRmM-LNARFoccLow4k9oA2h3w_w%40mail.gmail.com%3E

Thanks
Amareshwari

On Wed, Mar 4, 2015 at 12:37 AM, Chris Douglas cdoug...@apache.org wrote:

 +1 (binding, reiterated from dev@lens) -C

 On Fri, Feb 27, 2015 at 9:20 AM, Amareshwari Sriramdasu
 amareshw...@apache.org wrote:
  Hello everyone,
 
  This is the call for vote for the following RC to be released as official
  Apache Lens 2.0.1-beta-incubating release. This is our first release.
 
  Apache Lens provides an Unified Analytics interface. Lens aims to cut the
  Data Analytics silos by providing a single view of data across multiple
  tiered data stores and optimal execution environment for the analytical
  query. It seamlessly integrates Hadoop with traditional data warehouses
 to
  appear like one.
  Vote on dev list:
 
 http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201502.mbox/%3CCABJEuZfss9i52WrRQORMZTrfRmM-LNARFoccLow4k9oA2h3w_w%40mail.gmail.com%3E
 
  Results of vote on dev list:
 
 http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201502.mbox/%3CCABJEuZd55sU08f-vhh8i1DjH9FAWaxWwY6CZTOACQ0Kgasqatw%40mail.gmail.com%3E
 
  The commit id is de64e1dbfca2c4be0f8829cec2012052c09fb1e5 :
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=commit;h=de64e1dbfca2c4be0f8829cec2012052c09fb1e5
 
  This corresponds to the tag: apache-lens-2.0.1-beta-incubating :
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=tag;h=refs/tags/apache-lens-2.0.1-beta-incubating
 
  The release archives (tar.gz/.zip), signature, and checksums are here:
 
 https://dist.apache.org/repos/dist/dev/incubator/lens/apache-lens-2.0.1-beta-incubating-rc1
 
  You can find the KEYS file here:
  * https://dist.apache.org/repos/dist/release/incubator/lens/KEYS
 
  The release candidate consists of the following source distribution
 archive:
  apache-lens-2.0.1-beta-incubating-source-release.zip
 
  In addition, the following supplementary binary distributions are
  provided for user convenience at the same location:
  apache-lens-2.0.1-beta-incubating-bin.tar.gz
 
  The licensing of bundled bits in the archives are documented at
 
 https://cwiki.apache.org/confluence/display/LENS/Licensing+in+Apache+Lens
 
  Release notes available at
 
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315923version=12328990
 
  Vote will be open for at least 72 hours . Please vote on releasing this
 RC
 
  [ ] +1 approve
  [ ] 0 no opinion
  [ ] -1 disapprove (and reason why)
 
  Thanks,
  Amareshwari

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

Re: [VOTE] Release Apache Lens 2.0.1-beta-incubating

[Amareshwari Sriramdasu]

Thanks Justin for your time. Can you please run 'mvn clean package' as
suggested by Srikanth.

Responding to the other issues reported inline here. Let us know if we have
to roll another candidate with those issues fixed or taking care of them in
next release version is sufficient.

On Sat, Feb 28, 2015 at 8:41 AM, Srikanth Sundarrajan srik...@hotmail.com
wrote:

 Hi Justin,
I am assuming you are attempting to compile with mvn compile.  I am
 guessing the build is failing since the server module is depending on
 test-jars meant to be built in lens-server-api module during test-compile,
 and the same isn't available. Can you please try with mvn clean compile
 test-compile or mvn package or anything that includes the test-compile
 phase.

 Regards
 Srikanth Sundarrajan

  Subject: Re: [VOTE] Release Apache Lens 2.0.1-beta-incubating
  From: jus...@classsoftware.com
  Date: Sat, 28 Feb 2015 11:33:35 +1100
  To: general@incubator.apache.org
 
  Hi,
 
  +0 for now (due to compilation issues). If resolved would vote +1
 
  For the source release:
  - signatures and hashes correct
  - disclaimer exists
  - incubating in release name
  - LICENSE good
  - NOTICE has minor issue (see below)
  - No unexpected binary files (but did notice two power point files -
 perhaps a more OS format could be used? As these are simple images why not
 just png?)

The source for png files started is in pptx. So, pptx files are checked in
source to update images.

 - All source code has headers
  - Can't compile from source
 
  Minor issues
  - No need to mention any of the JS libraries in NOTICE as they are MIT
 licensed [1]

Sure. Will remove.


  - It may be the that two power point files have embedded fonts as they
 contain Copyright 2007 Apple Inc., all rights reserved?

Will check if we can remove the copyright or remove the pptx fully.

 
  Currently I'm unable to get the source package to compile (on OSX using
 Java 1.7).
 
  [INFO]
 
  [INFO] Reactor Summary:
  [INFO]
  [INFO] Lens Checkstyle Rules . SUCCESS [
 0.862 s]
  [INFO] Lens .. SUCCESS [
 0.029 s]
  [INFO] Lens API .. SUCCESS [
 0.518 s]
  [INFO] Lens API for server and extensions  SUCCESS [
 1.246 s]
  [INFO] Lens Cube . SUCCESS [
 0.236 s]
  [INFO] Lens DB storage ... SUCCESS [
 0.140 s]
  [INFO] Lens Query Library  SUCCESS [
 0.127 s]
  [INFO] Lens Hive Driver .. SUCCESS [
 0.657 s]
  [INFO] Lens Driver for JDBC .. SUCCESS [
 0.157 s]
  [INFO] Lens Server ... FAILURE [
 11.472 s]
  [INFO] Lens client ... SKIPPED
  [INFO] Lens CLI .. SKIPPED
  [INFO] Lens Examples . SKIPPED
  [INFO] Lens Distribution . SKIPPED
  [INFO] Lens ML Lib ... SKIPPED
  [INFO] Lens Regression ... SKIPPED
  [INFO]
 
  [INFO] BUILD FAILURE
  [INFO]
 
  [INFO] Total time: 16.060 s
  [INFO] Finished at: 2015-02-28T10:48:24+10:00
  [INFO] Final Memory: 24M/58M
  [INFO]
 
  [ERROR] Failed to execute goal on project lens-server: Could not resolve
 dependencies for project
 org.apache.lens:lens-server:war:2.0.1-beta-incubating: Could not find
 artifact org.apache.lens:lens-driver-hive:jar:tests:2.0.1-beta-incubating
 in inmobi.repo (https://github.com/InMobi/mvn-repo/raw/master/releases)
 - [Help 1]
 
  Why does it appear that the Apache lens artefacts are publicly deployed
 here [2], are these pre Apache incubator versions of the software?

Yes. Some of them are pre-apache releases and some of them are from 1.x
line after incubating apache to support 1.x. Let us know if there are
issues with putting artifacts there.


  For the binary distribution (again all minor issues).
  -  I'm concerned by the inclusion of  LICENSE-GPLv3 and LICENSE-LGPL
 file. I assume these are there because of dual licensing. They should
 probably be removed.

Yes. They are because of dual licensing. They were put as discussed in
legal-discuss threads here :
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201501.mbox/%3CCAAS6%3D7jJoJMkzMRpSdJ6kAVSZCvSfC5aRD0eMyGzP_rzWyE73Q%40mail.gmail.com%3E
and
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201502.mbox/%3CCAAS6%3D7gzsAYZMT5mar_nfy9egXB1t3HendDQRMUpkA6dqvhr7w%40mail.gmail.com%3E

Let us know if we should remove them.

 - NOTICE 

[VOTE] Release Apache Lens 2.0.1-beta-incubating

[Amareshwari Sriramdasu]

Hello everyone,

This is the call for vote for the following RC to be released as official
Apache Lens 2.0.1-beta-incubating release. This is our first release.

Apache Lens provides an Unified Analytics interface. Lens aims to cut the
Data Analytics silos by providing a single view of data across multiple
tiered data stores and optimal execution environment for the analytical
query. It seamlessly integrates Hadoop with traditional data warehouses to
appear like one.
Vote on dev list:
http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201502.mbox/%3CCABJEuZfss9i52WrRQORMZTrfRmM-LNARFoccLow4k9oA2h3w_w%40mail.gmail.com%3E

Results of vote on dev list:
http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201502.mbox/%3CCABJEuZd55sU08f-vhh8i1DjH9FAWaxWwY6CZTOACQ0Kgasqatw%40mail.gmail.com%3E

The commit id is de64e1dbfca2c4be0f8829cec2012052c09fb1e5 :
https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=commit;h=de64e1dbfca2c4be0f8829cec2012052c09fb1e5

This corresponds to the tag: apache-lens-2.0.1-beta-incubating :
https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=tag;h=refs/tags/apache-lens-2.0.1-beta-incubating

The release archives (tar.gz/.zip), signature, and checksums are here:
https://dist.apache.org/repos/dist/dev/incubator/lens/apache-lens-2.0.1-beta-incubating-rc1

You can find the KEYS file here:
* https://dist.apache.org/repos/dist/release/incubator/lens/KEYS

The release candidate consists of the following source distribution archive:
apache-lens-2.0.1-beta-incubating-source-release.zip

In addition, the following supplementary binary distributions are
provided for user convenience at the same location:
apache-lens-2.0.1-beta-incubating-bin.tar.gz

The licensing of bundled bits in the archives are documented at
https://cwiki.apache.org/confluence/display/LENS/Licensing+in+Apache+Lens

Release notes available at
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315923version=12328990

Vote will be open for at least 72 hours . Please vote on releasing this RC

[ ] +1 approve
[ ] 0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
Amareshwari

Re: [VOTE] Accept Lens into the Apache Incubator (earlier called Grill)

[Amareshwari Sriramdasu]

+1

Thanks
Amareshwari

On Mon, Oct 6, 2014 at 9:10 PM, Jakob Homan jgho...@gmail.com wrote:

 +1 (binding)

 On Mon, Oct 6, 2014 at 6:59 AM, Alan D. Cabrera l...@toolazydogs.com
 wrote:

  +1 - binding
 
 
  Regards,
  Alan
 
  On Oct 6, 2014, at 4:51 AM, Sharad Agarwal sha...@apache.org wrote:
 
   Following the discussion earlier in the thread
  
 https://www.mail-archive.com/general@incubator.apache.org/msg45208.html
   I would like to call a Vote for accepting Lens as a new incubator
  project.
  
   The proposal is available at:
   https://wiki.apache.org/incubator/LensProposal
  
   Vote is open till Oct 09, 2014 4 PM PST.
  
   [ ] +1 accept Lens in the Incubator
   [ ] +/-0
   [ ] -1 because...
  
   Only Votes from Incubator PMC members are binding, but all are welcome
 to
   express their thoughts.
   I am +1 (non-binding).
  
   Thanks
   Sharad
 
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org