Re: [VOTE] Release Apache Mynewt 0.8.0-b1-incubating

[Justin Mclean]

Hi,

+1 binding (carried over from dev list). Al my usual checks done.

If possible could someone double check the bundled software and LICENSE files 
as this was reasonably complex and I may of missed something.

Also just a note that getting the source packages to compile is a bit on the 
tricky side, but can be done and documentation will be improved in future 
releases.

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

[VOTE] Release Apache Mynewt 0.8.0-b1-incubating

[Christopher Collins]

Hello,

The Apache Mynewt Incubator PPMC has approved a proposal to release
Apache Mynewt 0.8.0-b1-incubating.  We now kindly request that the
Incubator PMC members review and vote on this incubator release.

Apache Mynewt is a community-driven, permissively licensed open source
initiative for constrained, embedded applications.  Mynewt provides a
real-time operating system, flash file system, network stacks, and
support utilities for real-world embedded systems.

This would be the first release of Apache Mynewt; what has changed since
the last release is: literally everything :).

[VOTE] thread:
http://mail-archives.apache.org/mod_mbox/incubator-mynewt-dev/201602.mbox/%3C20160224012927.GC14480%40iori.nightmare.heaven%3E

[VOTE RESULT] thread:
http://mail-archives.apache.org/mod_mbox/incubator-mynewt-dev/201602.mbox/%3C20160227021125.GO14480%40iori.nightmare.heaven%3E

[DISCUSS] thread:
http://mail-archives.apache.org/mod_mbox/incubator-mynewt-dev/201602.mbox/%3C20160224013028.GD14480%40iori.nightmare.heaven%3E

All automated tests in the mynewt test project for this release were
executed with no failures.  Testing was performed using the "sim"
architecture on an OS X 10.10.5 machine.

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-0.8.0-b1-incubating/

The commits under consideration are as follows:

larva:
repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva
commit: ba1586a4f2cbe47c25cf4d202fd3f999e47e0843

tadpole:
repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-tadpole
commit: a9723f015eb42edcd6e14e9b366d35fb7707fde8

newt:
repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt
commit: a8c2eb68eb1e9bc83e344f13410d4cb92c3fa12b

The release candidate is signed with a GPG key available at:
https://dist.apache.org/repos/dist/dev/incubator/mynewt/KEYS

The vote is open for at least 72 hours.

[ ] +1 Release this package
[ ]  0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...

Thanks,
Chris

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

Re: Project Kudu. .NET edition

[Todd Lipcon]

To be slightly more specific, we cleared it with the _legal team_ for
the .NET foundation (who runs the project that Roman spotted), not
just some engineers.

-Todd

On Fri, Feb 26, 2016 at 5:16 PM, Todd Lipcon  wrote:
> Hi Roman,
>
> Before we first publicly used the name, we were in touch with that
> project team, and got permission to do so. Additionally, I think the
> project scope/purpose is different enough that it wouldn't cause
> confusion. (fwiw based on tweets, I think there is also a fast food
> chain in Saudi Arabia named Kudu)
>
> If the ASF needs some documentation of this, I'll see what we can dig up.
>
> -Todd
>
> On Fri, Feb 26, 2016 at 5:10 PM, Roman Shaposhnik  
> wrote:
>> Hi!
>>
>> while working on some .NET Foundation
>> projects I've come across:
>> https://www.dotnetfoundation.org/kudu
>>
>> Not sure how much of a problem this could
>> be for Apache Kudu (incubating).
>>
>> Thanks,
>> Roman.
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera



-- 
Todd Lipcon
Software Engineer, Cloudera

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

Copyright sign offs

[Henri Yandell]

Haven't done this in a while :)

Thought I'd share that the following podlings have not yet signed off on
their Copyright sections in their status reports. I mention this because I
believe it's one of the first elements that should be signed off on the
status report and it's a worry if projects have not done so:

  cmda
  datafu
  horn
  johnzon
  odftoolkit
  openaz
  samoa
  slider
  streams
  taverna

I'd be interested to hear about any reasons why the above aren't able to
sign that element of their status file off.

(same, but for those who are < 6 months in the incubator, ie) still working
on it)

  beam
  concerted
  eagle
  fineract
  guacamole
  iota
  impala
  joshua
  metron
  milagro
  rya
  systemml
  toree
  unomi

Hen

Re: Project Kudu. .NET edition

[Todd Lipcon]

Hi Roman,

Before we first publicly used the name, we were in touch with that
project team, and got permission to do so. Additionally, I think the
project scope/purpose is different enough that it wouldn't cause
confusion. (fwiw based on tweets, I think there is also a fast food
chain in Saudi Arabia named Kudu)

If the ASF needs some documentation of this, I'll see what we can dig up.

-Todd

On Fri, Feb 26, 2016 at 5:10 PM, Roman Shaposhnik  wrote:
> Hi!
>
> while working on some .NET Foundation
> projects I've come across:
> https://www.dotnetfoundation.org/kudu
>
> Not sure how much of a problem this could
> be for Apache Kudu (incubating).
>
> Thanks,
> Roman.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>



-- 
Todd Lipcon
Software Engineer, Cloudera

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

Project Kudu. .NET edition

[Roman Shaposhnik]

Hi!

while working on some .NET Foundation
projects I've come across:
https://www.dotnetfoundation.org/kudu

Not sure how much of a problem this could
be for Apache Kudu (incubating).

Thanks,
Roman.

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

[ANNOUNCE] Apache Kudu (incubating) 0.7.0 released

[Jean-Daniel Cryans]

The Apache Kudu (incubating) team is happy to announce its first release as
part of the ASF Incubator, version 0.7.0!

Kudu is an open source storage engine for structured data which supports
low-latency random access together with efficient analytical access
patterns. It is designed within the context of the Apache Hadoop ecosystem
and supports many integrations with other data analytics projects both
inside and outside of the Apache Software Foundation.

This latest version adds limited support for Apache Spark, makes it
possible to build Kudu on more platforms, has a completely revamped Python
client, has improvements to both C++ and Java client libraries, and fixes
many bugs.

Download it here: *http://getkudu.io/releases/0.7.0/
*

Regards,

The Apache Kudu (incubating) team

===

Apache Kudu (incubating) is an effort undergoing incubation at The Apache
Software
Foundation (ASF), sponsored by the Apache Incubator PMC. 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: [DISCUSS] Gearpump incubation proposal

[Sean Zhong]

On Sat, Feb 27, 2016 at 12:56 AM, Sean Zhong  wrote:

> sting this.
>
>
If you want a direct look and feel of what it does, please see demo
http://demo.gearpump.io (user: guest, password: guest)

;)

Re: [VOTE] Accept Quarks into the Apache Incubator

[Julian Hyde]

+1 (binding)

> On Feb 26, 2016, at 10:36 AM, James Taylor  wrote:
> 
> +1
> 
> On Fri, Feb 26, 2016 at 8:47 AM, Arvind Prabhakar  wrote:
> 
>> +1 (binding)
>> 
>> Regards,
>> Arvind
>> 
>> On Wed, Feb 24, 2016 at 9:01 AM, Katherine Marsden 
>> wrote:
>> 
>>> The Quarks proposal has been discussed on the incubator list.  The
>>> discussion thread is at:
>>> 
>>> 
>> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3c56c27489.7090...@apache.org%3E
>>> 
>>> Feedback from the discussion including addition of mentor Justin Mclean
>>> has been incorporated into the proposal below and available on the wiki
>> at:
>>> https://wiki.apache.org/incubator/QuarksProposal
>>> 
>>> Please cast your vote to:
>>> [] +1 - accept Quarks as a new incubating project
>>> []  0 - not sure
>>> [] -1 - do not accept the Quarks project (because: ...)
>>> 
>>> Thanks,
>>> 
>>> Kathey Marsden
>>> 
>>> = Quarks Proposal =
>>> === Abstract ===
>>> Quarks is a stream processing programming model and lightweight runtime
>> to
>>> execute analytics at devices on the edge or at the gateway.
>>> 
>>> === Proposal ===
>>> . Quarks  is a programming model and runtime for streaming analytics at
>>> the edge.   Applications are developed using a functional flow api to
>>> define operations on data streams that is executed as a graph of "oplets"
>>> in a lightweight embeddable runtime.   The SDK provides capabilities like
>>> windowing, aggregation  and connectors with an extensible model for the
>>> community to expand its  capabilities.
>>> 
>>> === Background ===
>>> . Stream processing systems are commonly used to process  data from edge
>>> devices and there is a need to push some of the  streaming analytics to
>> the
>>> edge to reduce communication costs, react  locally and offload processing
>>> from the central systems.  Quarks was developed by IBM as an entirely new
>>> project to provide an SDK  and lightweight embeddable runtime for
>> streaming
>>> analytics at the edge.   Quarks was created to be an open source project
>>> that could provide edge  analytics to a broad community and foster
>>> collaboration on common  analytics and connectors across a broad
>> ecosystem
>>> of devices.
>>> 
>>> === Rationale ===
>>> . With the growth in number of connected devices (Internet of Things)
>>> there is a need to execute analytics at the edge in order to take local
>>> actions based upon sensor information and/or reduce the volume of data
>>> sent to back-end analytic systems to reduce communication cost.
>>> Quarks rationale is to provide  consistent and easy to use programming
>>> models to allow application developers to focus on their  application
>>> rather than issues like device connectivity, threading etc.   Quarks'
>>> functional data flow programming model is similar to systems  like Apache
>>> Flink, Beam (An incubating Apache project), Java 8 Streams & Apache
>> Spark.
>>> The API currently has language bindings for Java8, Java7 and Android.
>>> Quarks was developed to address requirements for analytics at the  edge
>> for
>>> IoT use cases that were not addressed by central analytic  solutions.  We
>>> believe that these capabilities will be useful to many  organizations and
>>> that the diverse nature of edge devices and use cases  is best addressed
>> by
>>> an open community. Therefore, we would like to contribute Quarks to the
>> ASF
>>> as an open source project and begin developing a community of developers
>>> and users within Apache.
>>> 
>>> === Initial Goals ===
>>> . Quarks initial code contribution provides:
>>> 
>>> * APIs for developing applications that execute  analytics using a
>>> per-event (data item) streaming paradigm including  support for windows
>>> against a stream for aggregation
>>> * A micro-kernel style runtime for execution.
>>> * Connectors for MQTT, HTTP, JDBC, File, Apache Kafka &  IBM Watson IoT
>>> Platform
>>> * Simple analytics aimed at device sensors (using Apache Common Math)
>>> * Development mode including a web-console to view the graph of running
>>> applications
>>> * Testing mechanism for Quarks applications that integrates with
>>> assertion based testing systems like JUnit
>>> * Android specific functionality such as producing a stream that
>> contains
>>> a phone's sensor events (e.g. ambient temperature, pressure)
>>> * JUnit tests
>>> .
>>> . All of the initial code is implemented using Java 8 and when built
>>> produces jars that can execute on Java 8, Java 7 and Android. The goal is
>>> to encourage community contributions in any area of Quarks, to  expand
>> the
>>> community (including new committers) and use of Quarks. We  expect
>>> contributions will be driven by real-world use of Quarks by  anyone
>> active
>>> in the IoT space such as auto manufactures, insurance  companies, etc. as
>>> well as individuals experimenting with devices such  as Raspberry Pis,
>>> Arduinos and/or smart phone apps etc. Contributions would be welcomed in
>>> any aspe

Re: [VOTE] Accept Quarks into the Apache Incubator

[James Taylor]

+1

On Fri, Feb 26, 2016 at 8:47 AM, Arvind Prabhakar  wrote:

> +1 (binding)
>
> Regards,
> Arvind
>
> On Wed, Feb 24, 2016 at 9:01 AM, Katherine Marsden 
> wrote:
>
> > The Quarks proposal has been discussed on the incubator list.  The
> > discussion thread is at:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3c56c27489.7090...@apache.org%3E
> >
> > Feedback from the discussion including addition of mentor Justin Mclean
> > has been incorporated into the proposal below and available on the wiki
> at:
> > https://wiki.apache.org/incubator/QuarksProposal
> >
> > Please cast your vote to:
> > [] +1 - accept Quarks as a new incubating project
> > []  0 - not sure
> > [] -1 - do not accept the Quarks project (because: ...)
> >
> > Thanks,
> >
> > Kathey Marsden
> >
> > = Quarks Proposal =
> > === Abstract ===
> > Quarks is a stream processing programming model and lightweight runtime
> to
> > execute analytics at devices on the edge or at the gateway.
> >
> > === Proposal ===
> >  . Quarks  is a programming model and runtime for streaming analytics at
> > the edge.   Applications are developed using a functional flow api to
> > define operations on data streams that is executed as a graph of "oplets"
> > in a lightweight embeddable runtime.   The SDK provides capabilities like
> > windowing, aggregation  and connectors with an extensible model for the
> > community to expand its  capabilities.
> >
> > === Background ===
> >  . Stream processing systems are commonly used to process  data from edge
> > devices and there is a need to push some of the  streaming analytics to
> the
> > edge to reduce communication costs, react  locally and offload processing
> > from the central systems.  Quarks was developed by IBM as an entirely new
> > project to provide an SDK  and lightweight embeddable runtime for
> streaming
> > analytics at the edge.   Quarks was created to be an open source project
> > that could provide edge  analytics to a broad community and foster
> > collaboration on common  analytics and connectors across a broad
> ecosystem
> > of devices.
> >
> > === Rationale ===
> >  . With the growth in number of connected devices (Internet of Things)
> > there is a need to execute analytics at the edge in order to take local
> > actions based upon sensor information and/or reduce the volume of data
> > sent to back-end analytic systems to reduce communication cost.
> >  Quarks rationale is to provide  consistent and easy to use programming
> > models to allow application developers to focus on their  application
> > rather than issues like device connectivity, threading etc.   Quarks'
> > functional data flow programming model is similar to systems  like Apache
> > Flink, Beam (An incubating Apache project), Java 8 Streams & Apache
> Spark.
> >  The API currently has language bindings for Java8, Java7 and Android.
> > Quarks was developed to address requirements for analytics at the  edge
> for
> > IoT use cases that were not addressed by central analytic  solutions.  We
> > believe that these capabilities will be useful to many  organizations and
> > that the diverse nature of edge devices and use cases  is best addressed
> by
> > an open community. Therefore, we would like to contribute Quarks to the
> ASF
> > as an open source project and begin developing a community of developers
> > and users within Apache.
> >
> > === Initial Goals ===
> >  . Quarks initial code contribution provides:
> >
> >  * APIs for developing applications that execute  analytics using a
> > per-event (data item) streaming paradigm including  support for windows
> > against a stream for aggregation
> >  * A micro-kernel style runtime for execution.
> >  * Connectors for MQTT, HTTP, JDBC, File, Apache Kafka &  IBM Watson IoT
> > Platform
> >  * Simple analytics aimed at device sensors (using Apache Common Math)
> >  * Development mode including a web-console to view the graph of running
> > applications
> >  * Testing mechanism for Quarks applications that integrates with
> > assertion based testing systems like JUnit
> >  * Android specific functionality such as producing a stream that
> contains
> > a phone's sensor events (e.g. ambient temperature, pressure)
> >  * JUnit tests
> >  .
> >  . All of the initial code is implemented using Java 8 and when built
> > produces jars that can execute on Java 8, Java 7 and Android. The goal is
> > to encourage community contributions in any area of Quarks, to  expand
> the
> > community (including new committers) and use of Quarks. We  expect
> > contributions will be driven by real-world use of Quarks by  anyone
> active
> > in the IoT space such as auto manufactures, insurance  companies, etc. as
> > well as individuals experimenting with devices such  as Raspberry Pis,
> > Arduinos and/or smart phone apps etc. Contributions would be welcomed in
> > any aspect of Quarks including:
> >  .
> >  * Support for additional programming languages used in devices

Re: [VOTE] Graduate Sentry

[Prasad Mujumdar]

  +1 (non-binding)

thanks
Prasad


On Wed, Feb 24, 2016, 11:20 AM Sravya Tirukkovalur 
wrote:

> Hi all,
>
> Following the positive discussion[1] and vote[2] in the Sentry
> community and a discussion[3] on the incubator list to graduate
> Sentry, I am calling a VOTE to graduate the project from the Incubator
> to a TLP. Please vote on the resolution pasted below.
>
> [ ] +1 Graduate Sentry from the Incubator
> [ ] +0 Don't care
> [ ] -1 Don't graduate Sentry from the Incubator (please specify reason)
>
> This vote will be open for at least 72 hours.
>
> References:
>
> [1] https://s.apache.org/dev_discuss
> [2] https://s.apache.org/dev_vote_result
> [3] https://s.apache.org/general_discuss
> Other:
> https://s.apache.org/general_notify
>
> https://cwiki.apache.org/confluence/display/SENTRY/Sentry+maturity+assessment
>
> Resolution to create a TLP from graduating Incubator podling:
>
> ==
>
>
> X. Establish the Apache Sentry Project
>
>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software, for distribution at no charge to
>   the public, related to Fine grained authorization to data and
> metadata in Hadoop.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Sentry Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Sentry Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to Fine grained authorization to data and metadata in Hadoop;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Sentry" be
>   and hereby is created, the person holding such office to
>   serve at the direction of the Board of Directors as the chair
>   of the Apache Sentry Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Sentry Project; and be it further
>
>   RESOLVED, that the persons listed immediately below be and
>   hereby are appointed to serve as the initial members of the
>   Apache Sentry Project:
>
> * Ali Rizvi 
>
>* Anne Yu 
>
>* Arun Suresh 
>
>* Brock Noland 
>
>* Chaoyu Tang 
>
>* Colin Ma 
>
>* Daisy Zhou 
>
>* Dapeng Sun 
>
>* David Nalley 
>
>* Erick Tryzelaar 
>
>* Gregory Chanan 
>
>* Guoquan Shen 
>
>* Hadi Nahari 
>
>* Hao Hao 
>
>* Jarek Jarcec Cecho 
>
>* Johnny Zhang 
>
>* Karthik Ramachandran 
>
>* Mark Grover 
>
>* Milo Polte 
>
>* Lenni Kuff 
>
>* Patrick Daly 
>
>* Patrick Hunt 
>
>* Prasad Mujumdar 
>
>* Raghu Mani 
>
>* Sean Mackrory 
>
>* Shreepadma Venugopalan 
>
>* Sravya Tirukkovalur 
>
>* Tuong Truong 
>
>* Vamsee Yarlagadda 
>
>* Xiaomeng Huang 
>
>* Xuefu Zhang 
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sravya Tirukkovalur
>   be appointed to the office of Vice President, Apache Sentry, to
>   serve in accordance with and subject to the direction of the
>   Board of Directors and the Bylaws of the Foundation until
>   death, resignation, retirement, removal or disqualification,
>   or until a successor is appointed; and be it further
>
>   RESOLVED, that the initial Apache Sentry PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Sentry Project; and be it further
>
>   RESOLVED, that the Apache Sentry Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Sentry podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Sentry podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.
>
> ==
>
>
> Regards,
> Sravya Tirukkovalur
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Gearpump incubation proposal

[Sean Zhong]

@Hen,

That is awesome summary! Thanks for posting this.


Sean

On Fri, Feb 26, 2016 at 5:39 PM, Henri Yandell  wrote:

> Thought I'd share a report I generated from some code of mine on the
> gearpump GitHub org (attached - though mail server may block).
>
> The highlights are:
>
> * 9 repos.
> * High number of pull requests resolved (1026/1030).
> * Fairly high number of issues resolved (853/951).
> * Pull requests are resolved very quickly, over half in an hour.
> * Issues a more classic 'nessie' curve. This is what I usually see for
> issue/pull-request response time.
> * Good balance of community and project for opening of
> issues/pull-requests, but my report is limited here as I go by the public
> members of the organization and I'm not analyzing where the reporters are
> coming from.
>
> Anyway - thought I'd share as I was impressed by the pull request activity.
>
> Hen
>
>
> On Thu, Feb 25, 2016 at 3:59 PM, Andrew Purtell 
> wrote:
>
>> Greetings,
>>
>> It is my pleasure to present the proposal to incubate the Gearpump project
>> at the Apache Software Foundation. Gearpump is a flexible, efficient, and
>> scalable micro-service based real-time big data streaming engine developed
>> up to this point by Intel Corporation as a GitHub project licensed under
>> the Apache License 2.0.
>>
>> The text of the proposal is included below and is also available at
>> https://wiki.apache.org/incubator/GearpumpProposal
>>
>> Best regards,
>>
>>- Andy​​
>>
>> -
>>
>> = Gearpump Proposal =
>>
>> === Abstract ===
>> Gearpump is a flexible, efficient and scalable micro-service based
>> real-time big data streaming engine developed by Intel Corporation which
>> has been licensed by Intel under the Apache License 2.0.
>>
>> === Proposal ===
>> Gearpump is a reactive real-time streaming engine; completely based on the
>> micro-service Actor model. Gearpump provides extremely high performance
>> stream processing while maintaining millisecond latency message delivery.
>> It enables reusable, composable flows or partial graphs that can be
>> remotely deployed and executed in a diverse set of environments, including
>> IoT edge devices. These flows may be deployed and modified at runtime -- a
>> capability few real time streaming frameworks provide today.
>>
>> The goal of this proposal is to incubate Gearpump as an Apache project in
>> order to build a diverse, healthy, and self-governed open source community
>> around this project.
>>
>> === Background ===
>> In past decade, there have been many advances within real-time streaming
>> frameworks. Despite many advances, users of streaming frameworks often
>> complain about flexibility, efficiency, and scalability. Gearpump
>> endeavors
>> to solve these challenges by adopting the micro-service Actor model. The
>> Actor model was proposed by Carl Hewitt in 1973. In the Actor model, each
>> actor is a message driven micro-service; actors are the basic building
>> blocks of concurrent computation. By leveraging Actor Model’s location
>> transparency feature, Gearpump allows a graph to be composed of several
>> partial graphs, where, for example, some parts may be deployed to remote
>> IoT edge devices, and other parts to a data center. This division and
>> deployment model can be changed at runtime to adapt to a changing physical
>> environment, providing extreme flexibility and elasticity in solving
>> various ingestion and analytics problems. We’ve found Actors to be a much
>> smaller computation unit compared with threads, where smaller usually
>> means
>> better concurrency, and potentially better CPU utilization.
>>
>> === Rationale ===
>> Gearpump tightly integrates and enhances the big data community of Apache
>> projects. Intel believes Gearpump can bring benefits to the Apache
>> community in a number of ways:
>>
>> 1. Gearpump complements many existing Apache projects, in particular,
>> those
>> commonly found within the big data space. Users of this project are also
>> users of other Apache projects, such as Hadoop ecosystem projects. It is
>> beneficial to align these projects under the ASF umbrella. In real-time
>> streaming, Gearpump offers some special features that are useful for
>> Apache
>> users, such as exactly-once processing with millisecond message level
>> latency and dynamic DAGs that allow online topology modifications.
>>
>> 2. Gearpump tightly integrates with Apache big data projects. It supports
>> for Apache HDFS, YARN, Kafka, and HBase. It uses Apache YARN for resource
>> scheduling and Apache HDFS as the essential distributed storage system.
>>
>> 3. The micro-service model of reusable flows that Gearpump has adopted is
>> very unique, and it may become common in the future. Gearpump sets a good
>> example about how distributed software can be implemented within a
>> micro-service model.  An open project is of best interest to our users. By
>> joining Apache, it will be a neutral infrastructure platform that will
>> benefit everyone.

Re: [VOTE] Graduate Sentry

[Arvind Prabhakar]

+1 (binding)

Regards,
Arvind

On Wed, Feb 24, 2016 at 11:20 AM, Sravya Tirukkovalur 
wrote:

> Hi all,
>
> Following the positive discussion[1] and vote[2] in the Sentry
> community and a discussion[3] on the incubator list to graduate
> Sentry, I am calling a VOTE to graduate the project from the Incubator
> to a TLP. Please vote on the resolution pasted below.
>
> [ ] +1 Graduate Sentry from the Incubator
> [ ] +0 Don't care
> [ ] -1 Don't graduate Sentry from the Incubator (please specify reason)
>
> This vote will be open for at least 72 hours.
>
> References:
>
> [1] https://s.apache.org/dev_discuss
> [2] https://s.apache.org/dev_vote_result
> [3] https://s.apache.org/general_discuss
> Other:
> https://s.apache.org/general_notify
>
> https://cwiki.apache.org/confluence/display/SENTRY/Sentry+maturity+assessment
>
> Resolution to create a TLP from graduating Incubator podling:
>
> ==
>
>
> X. Establish the Apache Sentry Project
>
>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software, for distribution at no charge to
>   the public, related to Fine grained authorization to data and
> metadata in Hadoop.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Sentry Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Sentry Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to Fine grained authorization to data and metadata in Hadoop;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Sentry" be
>   and hereby is created, the person holding such office to
>   serve at the direction of the Board of Directors as the chair
>   of the Apache Sentry Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Sentry Project; and be it further
>
>   RESOLVED, that the persons listed immediately below be and
>   hereby are appointed to serve as the initial members of the
>   Apache Sentry Project:
>
> * Ali Rizvi 
>
>* Anne Yu 
>
>* Arun Suresh 
>
>* Brock Noland 
>
>* Chaoyu Tang 
>
>* Colin Ma 
>
>* Daisy Zhou 
>
>* Dapeng Sun 
>
>* David Nalley 
>
>* Erick Tryzelaar 
>
>* Gregory Chanan 
>
>* Guoquan Shen 
>
>* Hadi Nahari 
>
>* Hao Hao 
>
>* Jarek Jarcec Cecho 
>
>* Johnny Zhang 
>
>* Karthik Ramachandran 
>
>* Mark Grover 
>
>* Milo Polte 
>
>* Lenni Kuff 
>
>* Patrick Daly 
>
>* Patrick Hunt 
>
>* Prasad Mujumdar 
>
>* Raghu Mani 
>
>* Sean Mackrory 
>
>* Shreepadma Venugopalan 
>
>* Sravya Tirukkovalur 
>
>* Tuong Truong 
>
>* Vamsee Yarlagadda 
>
>* Xiaomeng Huang 
>
>* Xuefu Zhang 
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sravya Tirukkovalur
>   be appointed to the office of Vice President, Apache Sentry, to
>   serve in accordance with and subject to the direction of the
>   Board of Directors and the Bylaws of the Foundation until
>   death, resignation, retirement, removal or disqualification,
>   or until a successor is appointed; and be it further
>
>   RESOLVED, that the initial Apache Sentry PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Sentry Project; and be it further
>
>   RESOLVED, that the Apache Sentry Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Sentry podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Sentry podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.
>
> ==
>
>
> Regards,
> Sravya Tirukkovalur
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Quarks into the Apache Incubator

[Flavio Junqueira]

+1 (binding), good project, everything looks good in the proposal.

-Flavio

> On 26 Feb 2016, at 15:09, chatz  wrote:
> 
> +1
> 
> On 26 February 2016 at 20:10, Phillip Rhodes 
> wrote:
> 
>> +1
>> On Feb 26, 2016 09:38, "Daniel J Debrunner"  wrote:
>> 
>>> +1  ( non-binding - member request to join IPMC is pending)
>>> Thanks,Dan.
>> 


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

Re: [VOTE] Accept Quarks into the Apache Incubator

[Arvind Prabhakar]

+1 (binding)

Regards,
Arvind

On Wed, Feb 24, 2016 at 9:01 AM, Katherine Marsden 
wrote:

> The Quarks proposal has been discussed on the incubator list.  The
> discussion thread is at:
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3c56c27489.7090...@apache.org%3E
>
> Feedback from the discussion including addition of mentor Justin Mclean
> has been incorporated into the proposal below and available on the wiki at:
> https://wiki.apache.org/incubator/QuarksProposal
>
> Please cast your vote to:
> [] +1 - accept Quarks as a new incubating project
> []  0 - not sure
> [] -1 - do not accept the Quarks project (because: ...)
>
> Thanks,
>
> Kathey Marsden
>
> = Quarks Proposal =
> === Abstract ===
> Quarks is a stream processing programming model and lightweight runtime to
> execute analytics at devices on the edge or at the gateway.
>
> === Proposal ===
>  . Quarks  is a programming model and runtime for streaming analytics at
> the edge.   Applications are developed using a functional flow api to
> define operations on data streams that is executed as a graph of "oplets"
> in a lightweight embeddable runtime.   The SDK provides capabilities like
> windowing, aggregation  and connectors with an extensible model for the
> community to expand its  capabilities.
>
> === Background ===
>  . Stream processing systems are commonly used to process  data from edge
> devices and there is a need to push some of the  streaming analytics to the
> edge to reduce communication costs, react  locally and offload processing
> from the central systems.  Quarks was developed by IBM as an entirely new
> project to provide an SDK  and lightweight embeddable runtime for streaming
> analytics at the edge.   Quarks was created to be an open source project
> that could provide edge  analytics to a broad community and foster
> collaboration on common  analytics and connectors across a broad ecosystem
> of devices.
>
> === Rationale ===
>  . With the growth in number of connected devices (Internet of Things)
> there is a need to execute analytics at the edge in order to take local
> actions based upon sensor information and/or reduce the volume of data
> sent to back-end analytic systems to reduce communication cost.
>  Quarks rationale is to provide  consistent and easy to use programming
> models to allow application developers to focus on their  application
> rather than issues like device connectivity, threading etc.   Quarks'
> functional data flow programming model is similar to systems  like Apache
> Flink, Beam (An incubating Apache project), Java 8 Streams & Apache Spark.
>  The API currently has language bindings for Java8, Java7 and Android.
> Quarks was developed to address requirements for analytics at the  edge for
> IoT use cases that were not addressed by central analytic  solutions.  We
> believe that these capabilities will be useful to many  organizations and
> that the diverse nature of edge devices and use cases  is best addressed by
> an open community. Therefore, we would like to contribute Quarks to the ASF
> as an open source project and begin developing a community of developers
> and users within Apache.
>
> === Initial Goals ===
>  . Quarks initial code contribution provides:
>
>  * APIs for developing applications that execute  analytics using a
> per-event (data item) streaming paradigm including  support for windows
> against a stream for aggregation
>  * A micro-kernel style runtime for execution.
>  * Connectors for MQTT, HTTP, JDBC, File, Apache Kafka &  IBM Watson IoT
> Platform
>  * Simple analytics aimed at device sensors (using Apache Common Math)
>  * Development mode including a web-console to view the graph of running
> applications
>  * Testing mechanism for Quarks applications that integrates with
> assertion based testing systems like JUnit
>  * Android specific functionality such as producing a stream that contains
> a phone's sensor events (e.g. ambient temperature, pressure)
>  * JUnit tests
>  .
>  . All of the initial code is implemented using Java 8 and when built
> produces jars that can execute on Java 8, Java 7 and Android. The goal is
> to encourage community contributions in any area of Quarks, to  expand the
> community (including new committers) and use of Quarks. We  expect
> contributions will be driven by real-world use of Quarks by  anyone active
> in the IoT space such as auto manufactures, insurance  companies, etc. as
> well as individuals experimenting with devices such  as Raspberry Pis,
> Arduinos and/or smart phone apps etc. Contributions would be welcomed in
> any aspect of Quarks including:
>  .
>  * Support for additional programming languages used in devices such as C,
> OpenSwift, Python etc.
>  * Specific device feature (e.g. Raspberry Pi, Android) or protocol (e.g.
> OBD-2) support
>  * Connectors for device to device (e.g. AllJoyn), device local data
> sources,  or to back-end systems (e.g. a IoT cloud service)
>  * Additional ana

Re: [VOTE] Accept Quarks into the Apache Incubator

[chatz]

+1

On 26 February 2016 at 20:10, Phillip Rhodes 
wrote:

> +1
> On Feb 26, 2016 09:38, "Daniel J Debrunner"  wrote:
>
> > +1  ( non-binding - member request to join IPMC is pending)
> > Thanks,Dan.
>

Re: [VOTE] Accept Quarks into the Apache Incubator

[Phillip Rhodes]

+1
On Feb 26, 2016 09:38, "Daniel J Debrunner"  wrote:

> +1  ( non-binding - member request to join IPMC is pending)
> Thanks,Dan.

Re: [VOTE] Accept Quarks into the Apache Incubator

[Daniel J Debrunner]

+1  ( non-binding - member request to join IPMC is pending) 
Thanks,Dan.

Re: [VOTE] Graduate Sentry

[Tom White]

+1 (binding)

Tom

On Wed, Feb 24, 2016 at 7:20 PM, Sravya Tirukkovalur  wrote:
> Hi all,
>
> Following the positive discussion[1] and vote[2] in the Sentry
> community and a discussion[3] on the incubator list to graduate
> Sentry, I am calling a VOTE to graduate the project from the Incubator
> to a TLP. Please vote on the resolution pasted below.
>
> [ ] +1 Graduate Sentry from the Incubator
> [ ] +0 Don't care
> [ ] -1 Don't graduate Sentry from the Incubator (please specify reason)
>
> This vote will be open for at least 72 hours.
>
> References:
>
> [1] https://s.apache.org/dev_discuss
> [2] https://s.apache.org/dev_vote_result
> [3] https://s.apache.org/general_discuss
> Other:
> https://s.apache.org/general_notify
> https://cwiki.apache.org/confluence/display/SENTRY/Sentry+maturity+assessment
>
> Resolution to create a TLP from graduating Incubator podling:
>
> ==
>
>
> X. Establish the Apache Sentry Project
>
>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software, for distribution at no charge to
>   the public, related to Fine grained authorization to data and
> metadata in Hadoop.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Sentry Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Sentry Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to Fine grained authorization to data and metadata in Hadoop;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Sentry" be
>   and hereby is created, the person holding such office to
>   serve at the direction of the Board of Directors as the chair
>   of the Apache Sentry Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Sentry Project; and be it further
>
>   RESOLVED, that the persons listed immediately below be and
>   hereby are appointed to serve as the initial members of the
>   Apache Sentry Project:
>
> * Ali Rizvi 
>
>* Anne Yu 
>
>* Arun Suresh 
>
>* Brock Noland 
>
>* Chaoyu Tang 
>
>* Colin Ma 
>
>* Daisy Zhou 
>
>* Dapeng Sun 
>
>* David Nalley 
>
>* Erick Tryzelaar 
>
>* Gregory Chanan 
>
>* Guoquan Shen 
>
>* Hadi Nahari 
>
>* Hao Hao 
>
>* Jarek Jarcec Cecho 
>
>* Johnny Zhang 
>
>* Karthik Ramachandran 
>
>* Mark Grover 
>
>* Milo Polte 
>
>* Lenni Kuff 
>
>* Patrick Daly 
>
>* Patrick Hunt 
>
>* Prasad Mujumdar 
>
>* Raghu Mani 
>
>* Sean Mackrory 
>
>* Shreepadma Venugopalan 
>
>* Sravya Tirukkovalur 
>
>* Tuong Truong 
>
>* Vamsee Yarlagadda 
>
>* Xiaomeng Huang 
>
>* Xuefu Zhang 
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sravya Tirukkovalur
>   be appointed to the office of Vice President, Apache Sentry, to
>   serve in accordance with and subject to the direction of the
>   Board of Directors and the Bylaws of the Foundation until
>   death, resignation, retirement, removal or disqualification,
>   or until a successor is appointed; and be it further
>
>   RESOLVED, that the initial Apache Sentry PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Sentry Project; and be it further
>
>   RESOLVED, that the Apache Sentry Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Sentry podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Sentry podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.
>
> ==
>
>
> Regards,
> Sravya Tirukkovalur
>
> -
> 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

Re: [DISCUSS] Gearpump incubation proposal

[Henri Yandell]

Thought I'd share a report I generated from some code of mine on the
gearpump GitHub org (attached - though mail server may block).

The highlights are:

* 9 repos.
* High number of pull requests resolved (1026/1030).
* Fairly high number of issues resolved (853/951).
* Pull requests are resolved very quickly, over half in an hour.
* Issues a more classic 'nessie' curve. This is what I usually see for
issue/pull-request response time.
* Good balance of community and project for opening of
issues/pull-requests, but my report is limited here as I go by the public
members of the organization and I'm not analyzing where the reporters are
coming from.

Anyway - thought I'd share as I was impressed by the pull request activity.

Hen


On Thu, Feb 25, 2016 at 3:59 PM, Andrew Purtell  wrote:

> Greetings,
>
> It is my pleasure to present the proposal to incubate the Gearpump project
> at the Apache Software Foundation. Gearpump is a flexible, efficient, and
> scalable micro-service based real-time big data streaming engine developed
> up to this point by Intel Corporation as a GitHub project licensed under
> the Apache License 2.0.
>
> The text of the proposal is included below and is also available at
> https://wiki.apache.org/incubator/GearpumpProposal
>
> Best regards,
>
>- Andy​​
>
> -
>
> = Gearpump Proposal =
>
> === Abstract ===
> Gearpump is a flexible, efficient and scalable micro-service based
> real-time big data streaming engine developed by Intel Corporation which
> has been licensed by Intel under the Apache License 2.0.
>
> === Proposal ===
> Gearpump is a reactive real-time streaming engine; completely based on the
> micro-service Actor model. Gearpump provides extremely high performance
> stream processing while maintaining millisecond latency message delivery.
> It enables reusable, composable flows or partial graphs that can be
> remotely deployed and executed in a diverse set of environments, including
> IoT edge devices. These flows may be deployed and modified at runtime -- a
> capability few real time streaming frameworks provide today.
>
> The goal of this proposal is to incubate Gearpump as an Apache project in
> order to build a diverse, healthy, and self-governed open source community
> around this project.
>
> === Background ===
> In past decade, there have been many advances within real-time streaming
> frameworks. Despite many advances, users of streaming frameworks often
> complain about flexibility, efficiency, and scalability. Gearpump endeavors
> to solve these challenges by adopting the micro-service Actor model. The
> Actor model was proposed by Carl Hewitt in 1973. In the Actor model, each
> actor is a message driven micro-service; actors are the basic building
> blocks of concurrent computation. By leveraging Actor Model’s location
> transparency feature, Gearpump allows a graph to be composed of several
> partial graphs, where, for example, some parts may be deployed to remote
> IoT edge devices, and other parts to a data center. This division and
> deployment model can be changed at runtime to adapt to a changing physical
> environment, providing extreme flexibility and elasticity in solving
> various ingestion and analytics problems. We’ve found Actors to be a much
> smaller computation unit compared with threads, where smaller usually means
> better concurrency, and potentially better CPU utilization.
>
> === Rationale ===
> Gearpump tightly integrates and enhances the big data community of Apache
> projects. Intel believes Gearpump can bring benefits to the Apache
> community in a number of ways:
>
> 1. Gearpump complements many existing Apache projects, in particular, those
> commonly found within the big data space. Users of this project are also
> users of other Apache projects, such as Hadoop ecosystem projects. It is
> beneficial to align these projects under the ASF umbrella. In real-time
> streaming, Gearpump offers some special features that are useful for Apache
> users, such as exactly-once processing with millisecond message level
> latency and dynamic DAGs that allow online topology modifications.
>
> 2. Gearpump tightly integrates with Apache big data projects. It supports
> for Apache HDFS, YARN, Kafka, and HBase. It uses Apache YARN for resource
> scheduling and Apache HDFS as the essential distributed storage system.
>
> 3. The micro-service model of reusable flows that Gearpump has adopted is
> very unique, and it may become common in the future. Gearpump sets a good
> example about how distributed software can be implemented within a
> micro-service model.  An open project is of best interest to our users. By
> joining Apache, it will be a neutral infrastructure platform that will
> benefit everyone.
>
> 4. The process and development philosophy of Apache will help Gearpump
> grow, and build a diverse, healthy, and self-governed open source
> community.
>
> === Initial Goals ===
> 1. Migrate the existing codebase to Apache.
>
> 2. Setup Jira, web