Re: [VOTE] Accept StreamPipes into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On 07/11/2019 20:00, Dominik Riemer wrote:
> 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] Apache Ratis Thirdparty incubating Release 0.3.0 rc0

[Mohammad Asif Siddiqui]

+1 (binding)  
  
Checks Done:  
 - hashes and signature is okay  
 - incubating in name  
 - ASF heades in relevant files  
 - NOTICE, LICENSE and DISCLAIMER exists  
   
Regards  
Asif

On 2019/11/06 17:54:57, Furkan KAMACI  wrote: 
> Hi,
> 
> +1 from me (binding).
> 
> I checked:
> - Incubating in name
> - DISCLAIMER exists
> - LICENSE is fine
> - No unexpected binary files
> - Checked PGP signatures
> - Checked Checksums
> - Code compiles and tests successfully run
> 
> PS: NOTICE file has year as 2018 which should be 2019 as Justin said.
> 
> Kind Regards,
> Furkan KAMACI
> 
> On Wed, Nov 6, 2019 at 2:00 AM Justin Mclean 
> wrote:
> 
> > Hi,
> >
> > Opps forgot to say:
> > +1 (binding)
> >
> > Thanks,
> > Justin
> >
> > -
> > 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: [VOTE] Accept StreamPipes into the Apache Incubator

[Mohammad Asif Siddiqui]

+1 (binding)
  
Regards  
Asif

On 2019/11/07 21:52:24, Joe Witt  wrote: 
> +1(binding)
> 
> On Thu, Nov 7, 2019 at 4:45 PM Kevin Ratnasekera 
> wrote:
> 
> > +1 ( binding )
> >
> > On Fri, Nov 8, 2019 at 2:04 AM Bertrand Delacretaz <
> > bdelacre...@codeconsult.ch> wrote:
> >
> > > On Thu, Nov 7, 2019 at 8:00 PM Dominik Riemer  wrote:
> > > >   [X ] +1, bring StreamPipes into the Incubator..
> > >
> > > With 5 mentors for 5 initial committers you should be well taken care of
> > > ;-)
> > >
> > > -Bertrand
> > >
> > > -
> > > 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: [DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[申远]

So, what's the step?

   1. Call a normal Apache Vote
   2. Build the App and upload to App Store with ASF's Apple Developer
   Account using the code in step 1



Best Regards,
YorkShen

申远


Greg Stein  于2019年11月8日周五 上午8:57写道：

> We're trying to do better on what services are available, so consider this
> "step one" :-)
>
>
> On Thu, Nov 7, 2019 at 1:19 PM Julian Feinauer <
> j.feina...@pragmaticminds.de>
> wrote:
>
> > Thanks Greg, I didn't know that!
> >
> > Julian
> >
> > Am 07.11.19, 19:24 schrieb "Greg Stein" :
> >
> >
> >
> https://cwiki.apache.org/confluence/display/INFRA/Distribution+via+the+Apple+App+Store
> >
> > On Thu, Nov 7, 2019 at 12:14 PM Greg Stein  wrote:
> >
> > > An app signed by the Foundation is most definitely associated with
> > the
> > > ASF. The Foundation has an Apple Developer Account for exactly this
> > reason.
> > >
> > >
> > > On Thu, Nov 7, 2019 at 9:17 AM Justin Mclean <
> > jus...@classsoftware.com>
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> A binary convenance release needs to be created from released
> voted
> > on
> > >> code. [1]
> > >>
> > >> However if some 3rd party (not the PPMC) wants to use unreleased
> > code and
> > >> make a “release” from it and put that somewhere but it needs to be
> > clear
> > >> that this is not in anyway associated with the ASF and it needs to
> > respects
> > >> ASF branding and trademarks.Doing [1] is probably easier so I
> > suggest you
> > >> go down that path.
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> > >> 1.
> > http://www.apache.org/legal/release-policy.html#compiled-packages
> > >>
> > -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail:
> general-h...@incubator.apache.org
> > >>
> > >>
> >
> >
> >
>

Re: [DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[Greg Stein]

We're trying to do better on what services are available, so consider this
"step one" :-)


On Thu, Nov 7, 2019 at 1:19 PM Julian Feinauer 
wrote:

> Thanks Greg, I didn't know that!
>
> Julian
>
> Am 07.11.19, 19:24 schrieb "Greg Stein" :
>
>
> https://cwiki.apache.org/confluence/display/INFRA/Distribution+via+the+Apple+App+Store
>
> On Thu, Nov 7, 2019 at 12:14 PM Greg Stein  wrote:
>
> > An app signed by the Foundation is most definitely associated with
> the
> > ASF. The Foundation has an Apple Developer Account for exactly this
> reason.
> >
> >
> > On Thu, Nov 7, 2019 at 9:17 AM Justin Mclean <
> jus...@classsoftware.com>
> > wrote:
> >
> >> Hi,
> >>
> >> A binary convenance release needs to be created from released voted
> on
> >> code. [1]
> >>
> >> However if some 3rd party (not the PPMC) wants to use unreleased
> code and
> >> make a “release” from it and put that somewhere but it needs to be
> clear
> >> that this is not in anyway associated with the ASF and it needs to
> respects
> >> ASF branding and trademarks.Doing [1] is probably easier so I
> suggest you
> >> go down that path.
> >>
> >> Thanks,
> >> Justin
> >>
> >> 1.
> http://www.apache.org/legal/release-policy.html#compiled-packages
> >>
> -
> >> 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

[Joe Witt]

+1(binding)

On Thu, Nov 7, 2019 at 4:45 PM Kevin Ratnasekera 
wrote:

> +1 ( binding )
>
> On Fri, Nov 8, 2019 at 2:04 AM Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
>
> > On Thu, Nov 7, 2019 at 8:00 PM Dominik Riemer  wrote:
> > >   [X ] +1, bring StreamPipes into the Incubator..
> >
> > With 5 mentors for 5 initial committers you should be well taken care of
> > ;-)
> >
> > -Bertrand
> >
> > -
> > 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

[Kevin Ratnasekera]

+1 ( binding )

On Fri, Nov 8, 2019 at 2:04 AM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> On Thu, Nov 7, 2019 at 8:00 PM Dominik Riemer  wrote:
> >   [X ] +1, bring StreamPipes into the Incubator..
>
> With 5 mentors for 5 initial committers you should be well taken care of
> ;-)
>
> -Bertrand
>
> -
> 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

[Bertrand Delacretaz]

On Thu, Nov 7, 2019 at 8:00 PM Dominik Riemer  wrote:
>   [X ] +1, bring StreamPipes into the Incubator..

With 5 mentors for 5 initial committers you should be well taken care of ;-)

-Bertrand

-
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

[Felix Cheung]

+1
Great project!

On Thu, Nov 7, 2019 at 11:40 AM Christofer Dutz 
wrote:

> 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 data analytics for
> non-technical users.
> The whole StreamPipes code is currently on Github. To get a rough
> estimate of the project size:
> * 

Re: [VOTE] Accept StreamPipes into the Apache Incubator

[Furkan KAMACI]

Hi,

+1, good lucks!

Kind Regards,
Furkan KAMACI

7 Kas 2019 Per, saat 22:40 tarihinde Christofer Dutz <
christofer.d...@c-ware.de> şunu yazdı:

> 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 data analytics for
> non-technical users.
> The whole StreamPipes code is currently 

AW: [VOTE] Accept StreamPipes into the Apache Incubator

[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) 
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

Re: [VOTE] Accept StreamPipes into the Apache Incubator

[Julian Feinauer]

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) 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 

Re: [DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[Julian Feinauer]

Thanks Greg, I didn't know that!

Julian

Am 07.11.19, 19:24 schrieb "Greg Stein" :


https://cwiki.apache.org/confluence/display/INFRA/Distribution+via+the+Apple+App+Store

On Thu, Nov 7, 2019 at 12:14 PM Greg Stein  wrote:

> An app signed by the Foundation is most definitely associated with the
> ASF. The Foundation has an Apple Developer Account for exactly this 
reason.
>
>
> On Thu, Nov 7, 2019 at 9:17 AM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> A binary convenance release needs to be created from released voted on
>> code. [1]
>>
>> However if some 3rd party (not the PPMC) wants to use unreleased code and
>> make a “release” from it and put that somewhere but it needs to be clear
>> that this is not in anyway associated with the ASF and it needs to 
respects
>> ASF branding and trademarks.Doing [1] is probably easier so I suggest you
>> go down that path.
>>
>> Thanks,
>> Justin
>>
>> 1. http://www.apache.org/legal/release-policy.html#compiled-packages
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

[VOTE] Accept StreamPipes into the Apache Incubator

[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 that a community-driven development process is the best 
way to further develop StreamPipes. Finally, after having talked to committers 
from various Apache IoT-related projects and participation in spontaneous 
hacking sessions and being impressed 

Re: [DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[Greg Stein]

https://cwiki.apache.org/confluence/display/INFRA/Distribution+via+the+Apple+App+Store

On Thu, Nov 7, 2019 at 12:14 PM Greg Stein  wrote:

> An app signed by the Foundation is most definitely associated with the
> ASF. The Foundation has an Apple Developer Account for exactly this reason.
>
>
> On Thu, Nov 7, 2019 at 9:17 AM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> A binary convenance release needs to be created from released voted on
>> code. [1]
>>
>> However if some 3rd party (not the PPMC) wants to use unreleased code and
>> make a “release” from it and put that somewhere but it needs to be clear
>> that this is not in anyway associated with the ASF and it needs to respects
>> ASF branding and trademarks.Doing [1] is probably easier so I suggest you
>> go down that path.
>>
>> Thanks,
>> Justin
>>
>> 1. http://www.apache.org/legal/release-policy.html#compiled-packages
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[Greg Stein]

An app signed by the Foundation is most definitely associated with the ASF.
The Foundation has an Apple Developer Account for exactly this reason.


On Thu, Nov 7, 2019 at 9:17 AM Justin Mclean 
wrote:

> Hi,
>
> A binary convenance release needs to be created from released voted on
> code. [1]
>
> However if some 3rd party (not the PPMC) wants to use unreleased code and
> make a “release” from it and put that somewhere but it needs to be clear
> that this is not in anyway associated with the ASF and it needs to respects
> ASF branding and trademarks.Doing [1] is probably easier so I suggest you
> go down that path.
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/legal/release-policy.html#compiled-packages
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[Justin Mclean]

Hi,

A binary convenance release needs to be created from released voted on code. [1]

However if some 3rd party (not the PPMC) wants to use unreleased code and make 
a “release” from it and put that somewhere but it needs to be clear that this 
is not in anyway associated with the ASF and it needs to respects ASF branding 
and trademarks.Doing [1] is probably easier so I suggest you go down that path.

Thanks,
Justin

1. http://www.apache.org/legal/release-policy.html#compiled-packages
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[Julian Feinauer]

Hi,

I think this cannot be done as PMC or PPMC as it would be a "binary release" 
which we cannot do with the ASF policy.
So I think another entity than the ASF / the PMC would need to put the App in 
the store, and then you are also free with regards to releases.

Julian

Am 07.11.19, 14:34 schrieb "申远" :

I am OK with the normal release procedure if we have to.

But I'd like to know the boundary line here, why we don't need go though
the release procedure for Apache Project Website and why we need it for an
App built from Apache code. What's the difference here?

Best Regards,
YorkShen

申远


Jamie G.  于2019年11月7日周四 下午9:07写道：

> The App should follow a release process - vetting, vote, signatures,
> tag on source repository, etc.
>
> The community should approve its release.
>
> On Thu, Nov 7, 2019 at 9:29 AM 申远  wrote:
> >
> > Hi, there
> >
> > I'd like to know whether it's necessary to do an Apache Release if we
> > publish an App to Apple Store using the code of Apache Weex [1]. I
> > understand there is no need to do an Apache Release if we publish
> projects
> > website, but what if we publish an App to iOS Apple Store?
> >
> > [1] https://github.com/apache/incubator-weex-playground/tree/master/ios
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
>
> -
> 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: [DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[Jamie G.]

Releasing an Apache project (artifact) requires community oversight.
The released artifact going to an FTP server, Maven central. or other
location is a separate concern.

The website describing the projects, its news, etc is less of an
artifact - more of a living document about the community.

At Apache Karaf we keep our website code on a git repo
https://github.com/apache/karaf-site, with the appropriate lock downs
to ensure only those with the correct Karma can update the website.


On Thu, Nov 7, 2019 at 10:04 AM 申远  wrote:
>
> I am OK with the normal release procedure if we have to.
>
> But I'd like to know the boundary line here, why we don't need go though
> the release procedure for Apache Project Website and why we need it for an
> App built from Apache code. What's the difference here?
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Jamie G.  于2019年11月7日周四 下午9:07写道：
>
> > The App should follow a release process - vetting, vote, signatures,
> > tag on source repository, etc.
> >
> > The community should approve its release.
> >
> > On Thu, Nov 7, 2019 at 9:29 AM 申远  wrote:
> > >
> > > Hi, there
> > >
> > > I'd like to know whether it's necessary to do an Apache Release if we
> > > publish an App to Apple Store using the code of Apache Weex [1]. I
> > > understand there is no need to do an Apache Release if we publish
> > projects
> > > website, but what if we publish an App to iOS Apple Store?
> > >
> > > [1] https://github.com/apache/incubator-weex-playground/tree/master/ios
> > >
> > > Best Regards,
> > > YorkShen
> > >
> > > 申远
> >
> > -
> > 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: [DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[申远]

I am OK with the normal release procedure if we have to.

But I'd like to know the boundary line here, why we don't need go though
the release procedure for Apache Project Website and why we need it for an
App built from Apache code. What's the difference here?

Best Regards,
YorkShen

申远


Jamie G.  于2019年11月7日周四 下午9:07写道：

> The App should follow a release process - vetting, vote, signatures,
> tag on source repository, etc.
>
> The community should approve its release.
>
> On Thu, Nov 7, 2019 at 9:29 AM 申远  wrote:
> >
> > Hi, there
> >
> > I'd like to know whether it's necessary to do an Apache Release if we
> > publish an App to Apple Store using the code of Apache Weex [1]. I
> > understand there is no need to do an Apache Release if we publish
> projects
> > website, but what if we publish an App to iOS Apple Store?
> >
> > [1] https://github.com/apache/incubator-weex-playground/tree/master/ios
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[Jamie G.]

The App should follow a release process - vetting, vote, signatures,
tag on source repository, etc.

The community should approve its release.

On Thu, Nov 7, 2019 at 9:29 AM 申远  wrote:
>
> Hi, there
>
> I'd like to know whether it's necessary to do an Apache Release if we
> publish an App to Apple Store using the code of Apache Weex [1]. I
> understand there is no need to do an Apache Release if we publish projects
> website, but what if we publish an App to iOS Apple Store?
>
> [1] https://github.com/apache/incubator-weex-playground/tree/master/ios
>
> Best Regards,
> YorkShen
>
> 申远

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

[DISUCSS] Is there any neccessary to do an Apache Release if we publish an App to Apple Store?

[申远]

Hi, there

I'd like to know whether it's necessary to do an Apache Release if we
publish an App to Apple Store using the code of Apache Weex [1]. I
understand there is no need to do an Apache Release if we publish projects
website, but what if we publish an App to iOS Apple Store?

[1] https://github.com/apache/incubator-weex-playground/tree/master/ios

Best Regards,
YorkShen

申远

Re: [RESULT][VOTE] Release of Apache Tamaya 0.4-incubating

[Julian Feinauer]

Hi Anatole,

first, congratulations, nicely done (took some stamina to over several RCs...)!
Second, little commnt, the binding votes where from IPMC not PPMC : )

Julian

Am 07.11.19, 12:04 schrieb "Anatole Tresch" :

Thank you all vor voting. I will close this vote with a YES result:

Thank you for voting!

5 binding +1 votes (PPMC):
Julian Feinauer
Justin Mclean
Jean-Baptiste Onofré
Mohammad Asif Siddiqui
Furkan KAMACI

no non-binding +1 votes
no -1 votes

Have a nice day, Anatole



-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

[RESULT][VOTE] Release of Apache Tamaya 0.4-incubating

[Anatole Tresch]

Thank you all vor voting. I will close this vote with a YES result:

Thank you for voting!

5 binding +1 votes (PPMC):
Julian Feinauer
Justin Mclean
Jean-Baptiste Onofré
Mohammad Asif Siddiqui
Furkan KAMACI

no non-binding +1 votes
no -1 votes

Have a nice day, Anatole



-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*