date:20191110

Re: [VOTE] Accept StreamPipes into the Apache Incubator

2019-11-10 Thread Tim Mitsch

+1 (non-binding)

Great project & code-base

Good luck!

Am 07.11.19, 20:00 schrieb "Dominik Riemer" :

Hi all,

following up the [DISCUSS] thread on StreamPipes
(https://lists.apache.org/thread.html/1cf79ef65888f695b4b925fd67ef8a2b845f6b0931c251a0ff1115e1@%3Cgeneral.incubator.apache.org%3E),
I would like to call a VOTE to accept StreamPipes into the Apache Incubator.

Please cast your vote:

[ ] +1, bring StreamPipes into the Incubator
[ ] +0, I don't care either way
[ ] -1, do not bring StreamPipes into the Incubator, because...

The vote will open at least for 72 hours and only votes from the Incubator
PMC are binding, but votes from everyone are welcome.

Dominik

StreamPipes Proposal
(https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPipesProposal)

== Abstract ==
StreamPipes is a self-service (Industrial) IoT toolbox to enable
non-technical users to connect, analyze and explore (Industrial) IoT data
streams.

= Proposal =

The goal of StreamPipes (www.streampipes.org) is to provide an easy-to-use
toolbox for non-technical users, e.g., domain experts, to exploit data streams
coming from (Industrial) IoT devices. Such users are provided with an intuitive
graphical user interface with the Pipeline Editor at its core. Users are able
to graphically model processing pipelines based on data sources (streams), data
processors and data sinks. Data processors and sinks are self-contained
microservices, which implement either stateful or stateless processing logic
(e.g., a trend detection or image classifier). Their processing logic is
implemented using one of several provided wrappers (we currently have wrappers
for standalone/Edge-based processing, Apache Flink, Siddhi and working wrapper
prototypes for Apache Kafka Streams and Spark, in the future we also plan to
integrate with Apache Beam). An SDK allows to easily create new pipeline
elements. Pipeline elements can be installed at runtime. To support users in
creating pipelines, an underlying semantics-based data model enables pipeline
elements to express requirements on incoming data streams that need to be
fulfilled, thus reducing modeling errors.
Data streams are integrated by using StreamPipes Connect, which allows to
connect data sources (based on standard protocols, such as MQTT, Kafka, Pulsar,
OPC-UA and further PLC4X-supported protocols) without further programming using
a graphical wizard. Additional user-faced modules of StreamPipes are a Live
dashboard to quickly explore IoT data streams and a wizard that generates code
templates for new pipeline elements, a Pipeline Element Installer used to
extend the algorithm feature set at runtime.

=== Background ===
StreamPipes was started in 2014 by researchers from FZI Research Center for
Information Technology in Karlsruhe, Germany. The original prototype was funded
by an EU project centered around predictive analytics for the manufacturing
domain. Since then, StreamPipes was constantly improved and extended by public
funding mainly from federal German ministries. In early 2018, the source code
was officially released under the Apache License 2.0. At the same time, while
we focused on bringing the research prototype to a production-grade tool, the
first companies started to use StreamPipes. Currently, the primary goal is to
widen the user and developer base. At ApacheCon NA 2019, after having talked to
many people from the Apache Community, we finally decided that we would like to
bring StreamPipes to the Apache Incubator.

=== Rationale ===
The (Industrial) IoT domain is a highly relevant and emerging sector.
Currently, IoT platforms are offered by many vendors ranging from SMEs up to
large enterprises. We believe that open source alternatives are an important
cornerstone for manufacturing companies to easily adopt data-driven decision
making. From our point of view, StreamPipes fits very well into the existing
(I)IoT ecosystem within the ASF, with projects such as Apache PLC4X focusing on
connecting machine data from PLCs, or other tools we are also using either in
the core of StreamPipes or with integrations (Apache Kafka, Apache IoTDB,
Apache Pulsar). StreamPipes itself focuses on enabling self-service IoT data
analytics for non-technical users.
The whole StreamPipes code is currently on Github. To get a rough estimate
of the project size:
* streampipes: Backend and core modules, ~3300 commits
* streampipes-ui: User Interface, ~1300 commits
* streampipes-pipeline-elements: ~100 Pipeline Elements (data
processors/algorithms and sinks), ~500 Commits
* streampipes-connect-adapters: ~20 Adapters to connect data, ~100 commits
To achieve our goal to further extend the code base with new features, new
connectors and new algorithms and to grow both the user and developer
community, we believe

Re: [VOTE] Accept StreamPipes into the Apache Incubator

2019-11-10 Thread Ming Wen

+1 (non-binding)

Thanks,
Ming Wen, Apache APISIX
Twitter: _WenMing


Dominik Riemer  于2019年11月8日周五 上午3:00写道：

> Hi all,
>
> following up the [DISCUSS] thread on StreamPipes (
> https://lists.apache.org/thread.html/1cf79ef65888f695b4b925fd67ef8a2b845f6b0931c251a0ff1115e1@%3Cgeneral.incubator.apache.org%3E),
> I would like to call a VOTE to accept StreamPipes into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring StreamPipes into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring StreamPipes into the Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding, but votes from everyone are welcome.
>
> Dominik
>
> 
> StreamPipes Proposal (
> https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPipesProposal)
>
> == Abstract ==
> StreamPipes is a self-service (Industrial) IoT toolbox to enable
> non-technical users to connect, analyze and explore (Industrial) IoT data
> streams.
>
> = Proposal =
>
> The goal of StreamPipes (www.streampipes.org) is to provide an
> easy-to-use toolbox for non-technical users, e.g., domain experts, to
> exploit data streams coming from (Industrial) IoT devices. Such users are
> provided with an intuitive graphical user interface with the Pipeline
> Editor at its core. Users are able to graphically model processing
> pipelines based on data sources (streams), data processors and data sinks.
> Data processors and sinks are self-contained microservices, which implement
> either stateful or stateless processing logic (e.g., a trend detection or
> image classifier). Their processing logic is implemented using one of
> several provided wrappers (we currently have wrappers for
> standalone/Edge-based processing, Apache Flink, Siddhi and working wrapper
> prototypes for Apache Kafka Streams and Spark, in the future we also plan
> to integrate with Apache Beam). An SDK allows to easily create new pipeline
> elements. Pipeline elements can be installed at runtime. To support users
> in creating pipelines, an underlying semantics-based data model enables
> pipeline elements to express requirements on incoming data streams that
> need to be fulfilled, thus reducing modeling errors.
> Data streams are integrated by using StreamPipes Connect, which allows to
> connect data sources (based on standard protocols, such as MQTT, Kafka,
> Pulsar, OPC-UA and further PLC4X-supported protocols) without further
> programming using a graphical wizard. Additional user-faced modules of
> StreamPipes are a Live dashboard to quickly explore IoT data streams and a
> wizard that generates code templates for new pipeline elements, a Pipeline
> Element Installer used to extend the algorithm feature set at runtime.
>
> === Background ===
> StreamPipes was started in 2014 by researchers from FZI Research Center
> for Information Technology in Karlsruhe, Germany. The original prototype
> was funded by an EU project centered around predictive analytics for the
> manufacturing domain. Since then, StreamPipes was constantly improved and
> extended by public funding mainly from federal German ministries. In early
> 2018, the source code was officially released under the Apache License 2.0.
> At the same time, while we focused on bringing the research prototype to a
> production-grade tool, the first companies started to use StreamPipes.
> Currently, the primary goal is to widen the user and developer base. At
> ApacheCon NA 2019, after having talked to many people from the Apache
> Community, we finally decided that we would like to bring StreamPipes to
> the Apache Incubator.
>
> === Rationale ===
> The (Industrial) IoT domain is a highly relevant and emerging sector.
> Currently, IoT platforms are offered by many vendors ranging from SMEs up
> to large enterprises. We believe that open source alternatives are an
> important cornerstone for manufacturing companies to easily adopt
> data-driven decision making. From our point of view, StreamPipes fits very
> well into the existing (I)IoT ecosystem within the ASF, with projects such
> as Apache PLC4X focusing on connecting machine data from PLCs, or other
> tools we are also using either in the core of StreamPipes or with
> integrations (Apache Kafka, Apache IoTDB, Apache Pulsar). StreamPipes
> itself focuses on enabling self-service IoT data analytics for
> non-technical users.
> The whole StreamPipes code is currently on Github. To get a rough estimate
> of the project size:
> * streampipes: Backend and core modules, ~3300 commits
> * streampipes-ui: User Interface, ~1300 commits
> * streampipes-pipeline-elements: ~100 Pipeline Elements (data
> processors/algorithms and sinks), ~500 Commits
> * streampipes-connect-adapters: ~20 Adapters to connect data, ~100 commits
> To achieve our goal to further extend the code base with new features, new
> connectors and new algorithms and to grow both the user and developer
> community, we believe that a

Re: [VOTE] Accept StreamPipes into the Apache Incubator

2019-11-10 Thread YuanSheng Wang

+1


On Mon, Nov 11, 2019 at 8:32 AM Tan,Zhongyi  wrote:

> +1
>
> 在 2019/11/8 上午3:40，“Christofer Dutz” 写入:
>
> A big +1 (binding) from me
>
> Chris
> 
> Von: Julian Feinauer 
> Gesendet: Donnerstag, 7. November 2019 20:19:43
> An: general@incubator.apache.org 
> Betreff: Re: [VOTE] Accept StreamPipes into the Apache Incubator
>
> Hi Dominik,
>
> I like StreamPipes, as you know, thus my vote is
>
> +1 (binding)
>
> Julian
>
> Am 07.11.19, 20:00 schrieb "Dominik Riemer" :
>
> Hi all,
>
> following up the [DISCUSS] thread on StreamPipes (
> https://lists.apache.org/thread.html/1cf79ef65888f695b4b925fd67ef8a2b845f6b0931c251a0ff1115e1@%3Cgeneral.incubator.apache.org%3E),
> I would like to call a VOTE to accept StreamPipes into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring StreamPipes into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring StreamPipes into the Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the
> Incubator PMC are binding, but votes from everyone are welcome.
>
> Dominik
>
> 
> StreamPipes Proposal (
> https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPipesProposal)
>
> == Abstract ==
> StreamPipes is a self-service (Industrial) IoT toolbox to enable
> non-technical users to connect, analyze and explore (Industrial) IoT data
> streams.
>
> = Proposal =
>
> The goal of StreamPipes (www.streampipes.org<
> http://www.streampipes.org>) is to provide an easy-to-use toolbox for
> non-technical users, e.g., domain experts, to exploit data streams coming
> from (Industrial) IoT devices. Such users are provided with an intuitive
> graphical user interface with the Pipeline Editor at its core. Users are
> able to graphically model processing pipelines based on data sources
> (streams), data processors and data sinks. Data processors and sinks are
> self-contained microservices, which implement either stateful or stateless
> processing logic (e.g., a trend detection or image classifier). Their
> processing logic is implemented using one of several provided wrappers (we
> currently have wrappers for standalone/Edge-based processing, Apache Flink,
> Siddhi and working wrapper prototypes for Apache Kafka Streams and Spark,
> in the future we also plan to integrate with Apache Beam). An SDK allows to
> easily create new pipeline elements. Pipeline elements can be installed at
> runtime. To support users in creating pipelines, an underlying
> semantics-based data model enables pipeline elements to express
> requirements on incoming data streams that need to be fulfilled, thus
> reducing modeling errors.
> Data streams are integrated by using StreamPipes Connect, which
> allows to connect data sources (based on standard protocols, such as MQTT,
> Kafka, Pulsar, OPC-UA and further PLC4X-supported protocols) without
> further programming using a graphical wizard. Additional user-faced modules
> of StreamPipes are a Live dashboard to quickly explore IoT data streams and
> a wizard that generates code templates for new pipeline elements, a
> Pipeline Element Installer used to extend the algorithm feature set at
> runtime.
>
> === Background ===
> StreamPipes was started in 2014 by researchers from FZI Research
> Center for Information Technology in Karlsruhe, Germany. The original
> prototype was funded by an EU project centered around predictive analytics
> for the manufacturing domain. Since then, StreamPipes was constantly
> improved and extended by public funding mainly from federal German
> ministries. In early 2018, the source code was officially released under
> the Apache License 2.0. At the same time, while we focused on bringing the
> research prototype to a production-grade tool, the first companies started
> to use StreamPipes. Currently, the primary goal is to widen the user and
> developer base. At ApacheCon NA 2019, after having talked to many people
> from the Apache Community, we finally decided that we would like to bring
> StreamPipes to the Apache Incubator.
>
> === Rationale ===
> The (Industrial) IoT domain is a highly relevant and emerging
> sector. Currently, IoT platforms are offered by many vendors ranging from
> SMEs up to large enterprises. We believe that open source alternatives are
> an important cornerstone for manufacturing companies to easily adopt
> data-driven decision making. From our point of view, StreamPipes fits very
> well into the existing (I)IoT ecosystem within the ASF, with projects such
> as Apache PLC4X focusing on connecting machine data from PLCs, or other
> tools we are also using either in the core of StreamPipes or with
> integrations (Apache Kafka, Apache IoTDB, Apache Pulsar). StreamPipes
> itself focuses on enabling self-service IoT

Re: [VOTE] Accept StreamPipes into the Apache Incubator

2019-11-10 Thread Tan,Zhongyi

在 2019/11/8 上午3:40，“Christofer Dutz” 写入:

A big +1 (binding) from me

Chris

Von: Julian Feinauer
Gesendet: Donnerstag, 7. November 2019 20:19:43
An: general@incubator.apache.org
Betreff: Re: [VOTE] Accept StreamPipes into the Apache Incubator

Hi Dominik,

I like StreamPipes, as you know, thus my vote is

+1 (binding)

Julian

Am 07.11.19, 20:00 schrieb "Dominik Riemer" :

Hi all,

Please cast your vote:

[ ] +1, bring StreamPipes into the Incubator
[ ] +0, I don't care either way
[ ] -1, do not bring StreamPipes into the Incubator, because...

The vote will open at least for 72 hours and only votes from the
Incubator PMC are binding, but votes from everyone are welcome.

Dominik

StreamPipes Proposal
(https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPipesProposal)

== Abstract ==
StreamPipes is a self-service (Industrial) IoT toolbox to enable
non-technical users to connect, analyze and explore (Industrial) IoT data
streams.

= Proposal =

The goal of StreamPipes
(www.streampipes.org) is to provide an easy-to-use
toolbox for non-technical users, e.g., domain experts, to exploit data streams
coming from (Industrial) IoT devices. Such users are provided with an intuitive
graphical user interface with the Pipeline Editor at its core. Users are able
to graphically model processing pipelines based on data sources (streams), data
processors and data sinks. Data processors and sinks are self-contained
microservices, which implement either stateful or stateless processing logic
(e.g., a trend detection or image classifier). Their processing logic is
implemented using one of several provided wrappers (we currently have wrappers
for standalone/Edge-based processing, Apache Flink, Siddhi and working wrapper
prototypes for Apache Kafka Streams and Spark, in the future we also plan to
integrate with Apache Beam). An SDK allows to easily create new pipeline
elements. Pipeline elements can be installed at runtime. To support users in
creating pipelines, an underlying semantics-based data model enables pipeline
elements to express requirements on incoming data streams that need to be
fulfilled, thus reducing modeling errors.
Data streams are integrated by using StreamPipes Connect, which allows
to connect data sources (based on standard protocols, such as MQTT, Kafka,
Pulsar, OPC-UA and further PLC4X-supported protocols) without further
programming using a graphical wizard. Additional user-faced modules of
StreamPipes are a Live dashboard to quickly explore IoT data streams and a
wizard that generates code templates for new pipeline elements, a Pipeline
Element Installer used to extend the algorithm feature set at runtime.

=== Background ===
StreamPipes was started in 2014 by researchers from FZI Research Center
for Information Technology in Karlsruhe, Germany. The original prototype was
funded by an EU project centered around predictive analytics for the
manufacturing domain. Since then, StreamPipes was constantly improved and
extended by public funding mainly from federal German ministries. In early
2018, the source code was officially released under the Apache License 2.0. At
the same time, while we focused on bringing the research prototype to a
production-grade tool, the first companies started to use StreamPipes.
Currently, the primary goal is to widen the user and developer base. At
ApacheCon NA 2019, after having talked to many people from the Apache
Community, we finally decided that we would like to bring StreamPipes to the
Apache Incubator.

Re: [VOTE] Heron 0.20.2-incubating Release Candidate 1

2019-11-10 Thread Josh Fischer

Thanks Justin.  We will take note and address them in the next release.


- Josh

On Sun, Nov 10, 2019 at 2:42 PM Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> Thanks for fixing teh issues raised last time.
>
> I checked:
> - incubating in name
> - signatures and hashes are file
> - DISCLAIMER exists
> - LICENSE is OK. It would be god to see local links to the licenses as
> URLs content may change or they may die over time.
> - NOTICE is fine
> - All source files have ASF headers where needed
> - No unexpected binary files
> - I didn’t try compiling
>
> For LICENSE:
> - JQuery is incorrectly listed as ALv2 it’s MIT licensed
> - JSXTransformer is also listed as ALv2 and is actually MIT licensed
>
> For all BSD and MIT you need to include the full text of the license. It
> seems you are missing some license(s) for file that don’t include the
> header and are missing from the licenses directory e.g. JSXTransformer. I
> did not check them all.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Heron 0.20.2-incubating Release Candidate 1

2019-11-10 Thread Justin Mclean

Hi,

+1 (binding)

Thanks for fixing teh issues raised last time.

I checked:
- incubating in name
- signatures and hashes are file
- DISCLAIMER exists
- LICENSE is OK. It would be god to see local links to the licenses as URLs 
content may change or they may die over time.
- NOTICE is fine
- All source files have ASF headers where needed
- No unexpected binary files
- I didn’t try compiling

For LICENSE:
- JQuery is incorrectly listed as ALv2 it’s MIT licensed
- JSXTransformer is also listed as ALv2 and is actually MIT licensed

For all BSD and MIT you need to include the full text of the license. It seems 
you are missing some license(s) for file that don’t include the header and are 
missing from the licenses directory e.g. JSXTransformer. I did not check them 
all.

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

[VOTE] Heron 0.20.2-incubating Release Candidate 1

2019-11-10 Thread Josh Fischer

Hi,

The Apache Heron community has voted and approved the proposal to
release Apache Heron (Incubating) version 0.20.2-rc1.  We request the
IPMC members to review and vote on this incubator release.

The results of the Release Candidate 1 votes are below:

- Binded Approvals: 1

   * Dave Fisher

- Vote Thread

https://mail-archives.apache.org/mod_mbox/heron-dev/201911.mbox/%3CCAFkuAo2Am%2BEK7rg-W9bC9teTVvDcan%2B7P%3DaXHTp%3D%2B5s-2pkpeg%40mail.gmail.com%3E

- Vote Result Thread

https://mail-archives.apache.org/mod_mbox/heron-dev/201911.mbox/%3CCAFkuAo0UApkDrnTgX8owGNRbCerDAYfvLynM9Wqtpa5NpqMEaw%40mail.gmail.com%3E


*  The tag to be voted upon:0.20.2-incubating-rc1
(1dbf1ce1860725827004c7047bf714b87c9df6d7)
The full list of changes and release notes are available
at:https://github.com/apache/incubator-heron/releases/tag/0.20.2-incubating-rc1


Files can be found in dist.apache.org
Source: 
https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.2-incubating-candidate-1/

SHA-512
checksums:

30d1e5e20bfadb448607678d8d754ed95fb5960caa45744a161da62f34ceaa812ded7ed0052cd2663a58f841f94de01344709809f711e7afedc4b00cd9ffd865
 incubator-heron-0.20.2-incubating-rc1.tar.gz


Please download the source package, and follow the compiling guide
https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/
 to
setup the environment, build and run locally.

Note that currently Bazel 0.26.0 is required to build this version.  After
Bazel is set up and works correctly, you can use these release check scripts
https://github.com/apache/incubator-heron/blob/master/scripts/release_check/README.md#run-individual-release-checks
to
verify the build.  The vote will be open for at least 72 hours or until the
necessary number of votes are reached.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thank you,

The Apache Heron (Incubating) Team

Re: [IP CLEARANCE] Accepting Donation from Weex UI to Apache Weex

2019-11-10 Thread 申远

>
> I'm not 100% sure what you mean by that. Only the project has that right,
> the author (once the code is decorated) has no more or less rights than
> anyone else.
>

Rephrase myselft. After the donation, the project(Weex UI) could remain its
name as it is.

Best Regards,
YorkShen

申远


Justin Mclean  于2019年11月10日周日 上午5:08写道：

> Hi,
>
> > By donating, the author of Weex UI will have the right of using the
> trademark of Weex.
>
> I'm not 100% sure what you mean by that. Only the project has that right,
> the author (once the code is decorated) has no more or less rights than
> anyone else.
>
> > There are some other projects may violate the trademark of ASF, I'm
> really
> > appreciated if someone could help append the list [3] I created.
>
> Who are you asking here? As I’ve mentioned before this would be up to the
> Weex PMC not just you.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept StreamPipes into the Apache Incubator

Re: [VOTE] Accept StreamPipes into the Apache Incubator

Re: [VOTE] Accept StreamPipes into the Apache Incubator

Re: [VOTE] Accept StreamPipes into the Apache Incubator

Re: [VOTE] Heron 0.20.2-incubating Release Candidate 1

Re: [VOTE] Heron 0.20.2-incubating Release Candidate 1

[VOTE] Heron 0.20.2-incubating Release Candidate 1

Re: [IP CLEARANCE] Accepting Donation from Weex UI to Apache Weex

8 matches

Site Navigation

Mail list logo

Footer information