Re: Write Access to Incubator Wiki

[Julian Feinauer]

Hi Kenn,

knowing the "core-team" behind it personally I agree with your point.
It is a small and not diverse community (from one institution currently) behind 
the project.
So an important part of the discussion here is also to get feedback from other 
individuals and communities what they think and if they are willing to be part 
of such a project.

We, in my company are currently evaluating the project and do a small meetup 
together with the guys to challenge it against our use cases and if we adopt 
it, I'm pretty sure that at least 2 people from us (one being me) will become 
active as contributors.

Julian

Am 31.10.19, 01:48 schrieb "Kenneth Knowles" :

Cool!

I see you have mentors lined up. I would love to also be involved as mentor.

The list of initial committers seems a little small. Browsing the commit
history it does seem to be dominated by just a couple of contributors. I
see this is acknowledged (at least implicitly) in the proposal. I expect a
principal challenge will be attracting diverse contributors, committers,
and PMC to ensure this project survives independent of any particular
entity (individual or corporate).

Kenn

On Wed, Oct 30, 2019 at 1:16 PM Dominik Riemer  wrote:

> Hi all,
>
>
>
> a short introduction to myself: My name is Dominik Riemer and I'm a
> co-initiator of StreamPipes, an open source self-service toolbox for
> analyzing IoT data streams. After presenting the tool at this year's
> ApacheCon NA, followed by very friendly and fruitful discussions with many
> people from the Apache community, we are sure that we'd like continue the
> development of StreamPipes as an Apache community project. Before we start
> a discussion process, I'd like to ask to get write access to the Incubator
> wiki (username: riemer). An initial draft of the proposal is attached 
below.
>
>
>
> Thanks for your help!
>
> Dominik
>
>
>
>
>
> 
>
>
>
> StreamPipes - Apache Incubator Proposal, Proposal Draft
>
>
>
> == 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.
> Cu

Re: Write Access to Incubator Wiki

[Christofer Dutz]

Hi Kenn,

I know a project that came to the incubator with even less initial committers 
and that's now a TLP ;-)

I agree that the number is small, but they want it to grow and that's one of 
the reasons they want to come to Apache.

I guess the committer-base size and diversity should be a barrier to go to TLP, 
not to come into the incubator.

Chris


Am 31.10.19, 11:01 schrieb "Julian Feinauer" :

Hi Kenn,

knowing the "core-team" behind it personally I agree with your point.
It is a small and not diverse community (from one institution currently) 
behind the project.
So an important part of the discussion here is also to get feedback from 
other individuals and communities what they think and if they are willing to be 
part of such a project.

We, in my company are currently evaluating the project and do a small 
meetup together with the guys to challenge it against our use cases and if we 
adopt it, I'm pretty sure that at least 2 people from us (one being me) will 
become active as contributors.

Julian

Am 31.10.19, 01:48 schrieb "Kenneth Knowles" :

Cool!

I see you have mentors lined up. I would love to also be involved as 
mentor.

The list of initial committers seems a little small. Browsing the commit
history it does seem to be dominated by just a couple of contributors. I
see this is acknowledged (at least implicitly) in the proposal. I 
expect a
principal challenge will be attracting diverse contributors, committers,
and PMC to ensure this project survives independent of any particular
entity (individual or corporate).

Kenn

On Wed, Oct 30, 2019 at 1:16 PM Dominik Riemer  wrote:

> Hi all,
>
>
>
> a short introduction to myself: My name is Dominik Riemer and I'm a
> co-initiator of StreamPipes, an open source self-service toolbox for
> analyzing IoT data streams. After presenting the tool at this year's
> ApacheCon NA, followed by very friendly and fruitful discussions with 
many
> people from the Apache community, we are sure that we'd like continue 
the
> development of StreamPipes as an Apache community project. Before we 
start
> a discussion process, I'd like to ask to get write access to the 
Incubator
> wiki (username: riemer). An initial draft of the proposal is attached 
below.
>
>
>
> Thanks for your help!
>
> Dominik
>
>
>
>
>
> 
>
>
>
> StreamPipes - Apache Incubator Proposal, Proposal Draft
>
>
>
> == 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 pi

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[吴中波]

  +1（non-binding）


>
> -- Forwarded message -
> 发件人： David Nalley 
> Date: 2019年10月30日周三 上午9:48
> Subject: [VOTE] Accept TubeMQ into the Apache Incubator
> To: 
>
>
> Hi folks,
>
> The [DISCUSS] thread on TubeMQ has died down.
>
> Accordingly, I would like to call a VOTE to accept TubeMQ into the
> Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring TubeMQ into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring TubeMQ into the Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the
> Incubator PMC are binding, but votes from everyone are welcome.
>
> =Abstract=
>
> TubeMQ is a distributed messaging queue (MQ) system developed by
> Tencent Big Data since 2013. It focuses on high-performance storage
> and transmission of massive data in big data scenarios.After nearly
> seven years of massive data precipitation, TubeMQ has certain
> advantages in production practice (stability + performance) and low
> cost compared to many open source MQ projects.
>
> =Proposal=
>
> TubeMQ is suitable for high concurrency, massive data and tolerates a
> small amount of data loss scenarios under abnormal conditions, such as
> massive log collection, indicator statistics and monitoring, etc.
> TubeMQ does not support highly reliable data transmission services
> yet. It could be on a future project roadmap, as many other MQs. but
> not today.
>
> =Rationale=
>
> Just like other message queue systems, TubeMQ is built on the
> publish-subscribe pattern, aka pub-sub.
> In this pattern, producers publish messages to topics while consumers
> subscribe to those topics. After incoming messages get proceeded,
> consumers send an acknowledgement back to producer. Once a
> subscription has been created, all messages will be tracked and
> retained by TubeMQ, even if the consumer go offline for some reasons.
> Retained messages will be discarded only when a consumer acknowledges
> that they've been successfully processed.
>
> Portal is responsible for interact with user and admin system which
> include two parts: API and web portal.
>
> Master is controller of the cluster, which include one or multiple
> master node(s) which is responsible for managing state of cluster,
> resource scheduling, authentication check and maintaining of metadata.
> As a reliable system, TubeMQ provides HA solution for master node.
>
> Broker is responsible for data store which include a cluster of broker
> nodes. Every broker node is managing a set of topics, include: append,
> delete, update, query of topic information. In TubeMQ, these brokers
> can be horizontal scaled and can be very large size for massive data
> case.
>
> Client is responsible for producing and consuming messages. When a
> pub-sub topic get setup, we can support two ways (push and pull) for
> delivering message from producers to consumers.
>
> Zookeeper is for storing offset of messages which is used to recover
> topic during some components get failed.
>
>
> =Initial Goals=
>
> The initial goal will be to move the current codebase in github’s
> repository under Tencent account to Apache and integrate with the
> Apache development process and infrastructure.
> A primary goal of incubation will be to grow and diversify the TubeMQ
> community. We are well aware that the project community is largely
> comprised of individuals from a single company. We aim to change that
> during incubation.
>
> =Current Status=
>
> As previously mentioned, TubeMQ is under active development at
> Tencent, and is being used in processing large volumes of data for
> most services and products.
>
> =Meritocracy=
>
> We value meritocracy and we understand that it is the basis for an
> open community that encourages multiple companies and individuals to
> contribute and be invested in the project’s future. We will encourage
> and monitor participation and make sure to extend privileges and
> responsibilities to all contributors.
>
> =Community=
>
> TubeMQ is currently being used by developers at Tencent and a growing
> number of users are actively using it in production environments.
> TubeMQ has received contributions from developers working outside of
> Tencent since it was open sourced on github in September 2019 By
> bringing TubeMQ to Apache we aim to assure current and future
> contributors that the TubeMQ community is neutral, meritocratic, and
> open, in order to broaden and diversity the user and developer
> community.
>
> =Core Developers=
>
> TubeMQ was initially developed at Tencent and is under active
> development. We believe Tencent will be of interest to a broad range
> of users and developers and that incubating the project at the ASF
> will help us build a diverse, sustainable community.
>
> =Alignment=
>
> TubeMQ utilizes other Apache projects such as Hadoop, HBase and
> Zookeeper. We anticipate integration with additional Apache projects
> as the TubeMQ community and interest in the project grows.
>
> =Known

Re: Write Access to Incubator Wiki

[Xiangdong Huang]

Hi,

It is an interesting project, I think. Maybe the @IoT mailing list guys
will like it. Look forward to integration with other IoT projects like
IoTDB incubating :D

By the way, is the project similar with MiNiFi? (maybe more friendly for
non-technical users.)

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Christofer Dutz  于2019年10月31日周四 下午6:04写道：

> Hi Kenn,
>
> I know a project that came to the incubator with even less initial
> committers and that's now a TLP ;-)
>
> I agree that the number is small, but they want it to grow and that's one
> of the reasons they want to come to Apache.
>
> I guess the committer-base size and diversity should be a barrier to go to
> TLP, not to come into the incubator.
>
> Chris
>
>
> Am 31.10.19, 11:01 schrieb "Julian Feinauer" <
> j.feina...@pragmaticminds.de>:
>
> Hi Kenn,
>
> knowing the "core-team" behind it personally I agree with your point.
> It is a small and not diverse community (from one institution
> currently) behind the project.
> So an important part of the discussion here is also to get feedback
> from other individuals and communities what they think and if they are
> willing to be part of such a project.
>
> We, in my company are currently evaluating the project and do a small
> meetup together with the guys to challenge it against our use cases and if
> we adopt it, I'm pretty sure that at least 2 people from us (one being me)
> will become active as contributors.
>
> Julian
>
> Am 31.10.19, 01:48 schrieb "Kenneth Knowles" :
>
> Cool!
>
> I see you have mentors lined up. I would love to also be involved
> as mentor.
>
> The list of initial committers seems a little small. Browsing the
> commit
> history it does seem to be dominated by just a couple of
> contributors. I
> see this is acknowledged (at least implicitly) in the proposal. I
> expect a
> principal challenge will be attracting diverse contributors,
> committers,
> and PMC to ensure this project survives independent of any
> particular
> entity (individual or corporate).
>
> Kenn
>
> On Wed, Oct 30, 2019 at 1:16 PM Dominik Riemer 
> wrote:
>
> > Hi all,
> >
> >
> >
> > a short introduction to myself: My name is Dominik Riemer and
> I'm a
> > co-initiator of StreamPipes, an open source self-service toolbox
> for
> > analyzing IoT data streams. After presenting the tool at this
> year's
> > ApacheCon NA, followed by very friendly and fruitful discussions
> with many
> > people from the Apache community, we are sure that we'd like
> continue the
> > development of StreamPipes as an Apache community project.
> Before we start
> > a discussion process, I'd like to ask to get write access to the
> Incubator
> > wiki (username: riemer). An initial draft of the proposal is
> attached below.
> >
> >
> >
> > Thanks for your help!
> >
> > Dominik
> >
> >
> >
> >
> >
> > 
> >
> >
> >
> > StreamPipes - Apache Incubator Proposal, Proposal Draft
> >
> >
> >
> > == 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
> 

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[Matt Sicker]

+1

On Tue, Oct 29, 2019 at 21:30, Saisai Shao  wrote:

> +1 (non-binding).
>
> Thanks
> Saisai
>
> Sheng Wu  于2019年10月30日周三 上午10:03写道：
>
> > +1 binding
> > Good luck.
> >
> > Dave Fisher 于2019年10月30日 周三上午7:30写道：
> >
> > > +1 (binding)
> > >
> > > Go TubeMQ.
> > >
> > > Regards,
> > > Dave
> > >
> > > Sent from my iPhone
> > >
> > > > On Oct 29, 2019, at 6:48 PM, David Nalley  wrote:
> > > >
> > > > Hi folks,
> > > >
> > > > The [DISCUSS] thread on TubeMQ has died down.
> > > >
> > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the
> > > > Apache Incubator.
> > > >
> > > > Please cast your vote:
> > > >
> > > >  [ ] +1, bring TubeMQ into the Incubator
> > > >  [ ] +0, I don't care either way
> > > >  [ ] -1, do not bring TubeMQ into the Incubator, because...
> > > >
> > > > The vote will open at least for 72 hours and only votes from the
> > > > Incubator PMC are binding, but votes from everyone are welcome.
> > > >
> > > > =Abstract=
> > > >
> > > > TubeMQ is a distributed messaging queue (MQ) system developed by
> > > > Tencent Big Data since 2013. It focuses on high-performance storage
> > > > and transmission of massive data in big data scenarios.After nearly
> > > > seven years of massive data precipitation, TubeMQ has certain
> > > > advantages in production practice (stability + performance) and low
> > > > cost compared to many open source MQ projects.
> > > >
> > > > =Proposal=
> > > >
> > > > TubeMQ is suitable for high concurrency, massive data and tolerates a
> > > > small amount of data loss scenarios under abnormal conditions, such
> as
> > > > massive log collection, indicator statistics and monitoring, etc.
> > > > TubeMQ does not support highly reliable data transmission services
> > > > yet. It could be on a future project roadmap, as many other MQs. but
> > > > not today.
> > > >
> > > > =Rationale=
> > > >
> > > > Just like other message queue systems, TubeMQ is built on the
> > > > publish-subscribe pattern, aka pub-sub.
> > > > In this pattern, producers publish messages to topics while consumers
> > > > subscribe to those topics. After incoming messages get proceeded,
> > > > consumers send an acknowledgement back to producer. Once a
> > > > subscription has been created, all messages will be tracked and
> > > > retained by TubeMQ, even if the consumer go offline for some reasons.
> > > > Retained messages will be discarded only when a consumer acknowledges
> > > > that they've been successfully processed.
> > > >
> > > > Portal is responsible for interact with user and admin system which
> > > > include two parts: API and web portal.
> > > >
> > > > Master is controller of the cluster, which include one or multiple
> > > > master node(s) which is responsible for managing state of cluster,
> > > > resource scheduling, authentication check and maintaining of
> metadata.
> > > > As a reliable system, TubeMQ provides HA solution for master node.
> > > >
> > > > Broker is responsible for data store which include a cluster of
> broker
> > > > nodes. Every broker node is managing a set of topics, include:
> append,
> > > > delete, update, query of topic information. In TubeMQ, these brokers
> > > > can be horizontal scaled and can be very large size for massive data
> > > > case.
> > > >
> > > > Client is responsible for producing and consuming messages. When a
> > > > pub-sub topic get setup, we can support two ways (push and pull) for
> > > > delivering message from producers to consumers.
> > > >
> > > > Zookeeper is for storing offset of messages which is used to recover
> > > > topic during some components get failed.
> > > >
> > > >
> > > > =Initial Goals=
> > > >
> > > > The initial goal will be to move the current codebase in github’s
> > > > repository under Tencent account to Apache and integrate with the
> > > > Apache development process and infrastructure.
> > > > A primary goal of incubation will be to grow and diversify the TubeMQ
> > > > community. We are well aware that the project community is largely
> > > > comprised of individuals from a single company. We aim to change that
> > > > during incubation.
> > > >
> > > > =Current Status=
> > > >
> > > > As previously mentioned, TubeMQ is under active development at
> > > > Tencent, and is being used in processing large volumes of data for
> > > > most services and products.
> > > >
> > > > =Meritocracy=
> > > >
> > > > We value meritocracy and we understand that it is the basis for an
> > > > open community that encourages multiple companies and individuals to
> > > > contribute and be invested in the project’s future. We will encourage
> > > > and monitor participation and make sure to extend privileges and
> > > > responsibilities to all contributors.
> > > >
> > > > =Community=
> > > >
> > > > TubeMQ is currently being used by developers at Tencent and a growing
> > > > number of users are actively using it in production environments.
> > > > TubeMQ has received contributions from developers working

RE: Write Access to Incubator Wiki

[Dominik Riemer]

Thank you very much Kenn, that's awesome!
I'll add you as a mentor once we got access to the wiki, afterwards I'll also 
start a separate DISCUSS thread to discuss our proposal.

Dominik

-Original Message-
From: Kenneth Knowles  
Sent: Thursday, October 31, 2019 1:49 AM
To: general 
Subject: Re: Write Access to Incubator Wiki

Cool!

I see you have mentors lined up. I would love to also be involved as mentor.

The list of initial committers seems a little small. Browsing the commit 
history it does seem to be dominated by just a couple of contributors. I see 
this is acknowledged (at least implicitly) in the proposal. I expect a 
principal challenge will be attracting diverse contributors, committers, and 
PMC to ensure this project survives independent of any particular entity 
(individual or corporate).

Kenn

On Wed, Oct 30, 2019 at 1:16 PM Dominik Riemer  wrote:

> Hi all,
>
>
>
> a short introduction to myself: My name is Dominik Riemer and I'm a 
> co-initiator of StreamPipes, an open source self-service toolbox for 
> analyzing IoT data streams. After presenting the tool at this year's 
> ApacheCon NA, followed by very friendly and fruitful discussions with 
> many people from the Apache community, we are sure that we'd like 
> continue the development of StreamPipes as an Apache community 
> project. Before we start a discussion process, I'd like to ask to get 
> write access to the Incubator wiki (username: riemer). An initial draft of 
> the proposal is attached below.
>
>
>
> Thanks for your help!
>
> Dominik
>
>
>
>
>
> 
>
>
>
> StreamPipes - Apache Incubator Proposal, Proposal Draft
>
>
>
> == 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)

Re: Write Access to Incubator Wiki

[Dave Fisher]

Hi -

I’ll point out that your champion and mentors do have access and they could 
easily do that for you.

Regards,
Dave

> On Nov 1, 2019, at 12:48 AM, Dominik Riemer  wrote:
> 
> Thank you very much Kenn, that's awesome!
> I'll add you as a mentor once we got access to the wiki, afterwards I'll also 
> start a separate DISCUSS thread to discuss our proposal.
> 
> Dominik
> 
> -Original Message-
> From: Kenneth Knowles  
> Sent: Thursday, October 31, 2019 1:49 AM
> To: general 
> Subject: Re: Write Access to Incubator Wiki
> 
> Cool!
> 
> I see you have mentors lined up. I would love to also be involved as mentor.
> 
> The list of initial committers seems a little small. Browsing the commit 
> history it does seem to be dominated by just a couple of contributors. I see 
> this is acknowledged (at least implicitly) in the proposal. I expect a 
> principal challenge will be attracting diverse contributors, committers, and 
> PMC to ensure this project survives independent of any particular entity 
> (individual or corporate).
> 
> Kenn
> 
> On Wed, Oct 30, 2019 at 1:16 PM Dominik Riemer  wrote:
> 
>> Hi all,
>> 
>> 
>> 
>> a short introduction to myself: My name is Dominik Riemer and I'm a 
>> co-initiator of StreamPipes, an open source self-service toolbox for 
>> analyzing IoT data streams. After presenting the tool at this year's 
>> ApacheCon NA, followed by very friendly and fruitful discussions with 
>> many people from the Apache community, we are sure that we'd like 
>> continue the development of StreamPipes as an Apache community 
>> project. Before we start a discussion process, I'd like to ask to get 
>> write access to the Incubator wiki (username: riemer). An initial draft of 
>> the proposal is attached below.
>> 
>> 
>> 
>> Thanks for your help!
>> 
>> Dominik
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> StreamPipes - Apache Incubator Proposal, Proposal Draft
>> 
>> 
>> 
>> == 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

Re: [VOTE] Graudate Apache Weex (Incubating) as a Top Level Project

[申远]

Hi, Justin.

After serious thinking these days, I decided to withindraw the graduation
vote. We need spend more time in Incubator, this graduation vote is a
little hurry.

I admitted your concerns about diverse and independent community have some
points, Weex still needs to impove in this apsect.

For branding part, I have some reservations about it, but I will see what I
can do to make things better.

Is there any other concerns you have about Weex towards graduation ?

FYI: Weex needs more active mentors, if possible. That would denifitely
help.

Best Regards,
YorkShen

申远


ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 下午9:20写道：

> เมื่อ 30 ต.ค. 2019 7:52 PM "申远"  เขียนว่า
>
> > FYI: If the initial committers really matter, maybe we could ask
> secretary
> > to help us find out how many individuals signed the ICLA when Weex
> entered
> > the Incubator.
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
> >
> >
> > ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 下午8:35写道：
> >
> > > เมื่อ 30 ต.ค. 2019 7:16 PM "申远"  เขียนว่า
> > >
> > > > >
> > > > > The PPMC needs to protect their brand in particular from their own
> > > > company.
> > > >
> > > >
> > > > Agree with that, and this is exactly why I am persuading project like
> > > > Weex-UI [1] donated to ASF instead of making them changing their name
> > to
> > > > "XXX powered by Apache Weex" and then pretend there is no problem.
> > > >
> > > > Anyone on the Initial list are committers I assume you mean they see
> > not
> > > > > contributing?
> > > > >
> > > >
> > > > No, some [2] of them are never committers of Weex according to our
> > > whimsy.
> > > > For example, the top 2 names on the initial developer list are not
> > > > committers of Weex according to whimsy and they didn't contribute, of
> > > > course. Some of other names, like me, are also on the initial
> developer
> > > > list, but I was actually elected as Weex committer four months after
> it
> > > > into incubator. There is a vote for nominating me as a Weex committer
> > > [3].
> > > > I don't know what happened here, as I am not the initial committer in
> > > fact.
> > > > But the initial developer list [2] is incorrect, I'm sure about that.
> > > >
> > > > [1]
> > > > https://lists.apache.org/thread.html/ab1cdf009697ac261e10c8963ed9ad
> > > > fe226edeee056f0c7dabb780c0@%3Cdev.weex.apache.org%3E
> > > > [2]
> > > > https://lists.apache.org/thread.html/b53537fea384f1d75c9921f71e13d1
> > > > 7780381504cff971e5f18bda96@%3Cgeneral.incubator.apache.org%3E
> > > > [3]
> > > > https://lists.apache.org/thread.html/8ebbd2fb5fb85c1da4328685859ae1
> > > > bb365a8b6253772c9e06940a39@%3Cprivate.weex.apache.org%3E
> > > >
> > > > Best Regards,
> > > > YorkShen
> > > >
> > > > 申远
> > > >
> > > >
> > > > Justin Mclean  于2019年10月30日周三 下午7:32写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > It seems like there are two concerns around Weex, branding and
> > > > independent
> > > > > > community.
> > > > > >
> > > > >
> > > > > I'd still like to hear what your mentors think. Are they active?
> > > > >
> > > > > For branding part, I understand this is a serious issue, and it
> takes
> > > me
> > > > > > months to solve this kinds of issues
> > > > > >
> > > > >
> > > > > This needs to be the PPMC not just you. I chose some of those links
> > on
> > > > > purpose as they belong to the company they belong to. The PPMC
> needs
> > to
> > > > > protect their brand in particular from their own company.
> > > > >
> > > > >- Though there are 13 committers according to the initial
> proposal
> > > > [5],
> > > > > >but many of them are not committers today.
> > > > >
> > > > >
> > > > > Anyone on the Initial list are committers I assume you mean they
> see
> > > not
> > > > > contributing?
> > > > >
> > > > > Just take the committers on the initial proposal as an inacurrate
> > > > records,
> > > > > > there are some mistakes on this list.
> > > > >
> > > > >
> > > > > This seems concerning.
> > > > >
> > > > > >
> > > > > >- There are developers out of the comany make their own tools
> > > around
> > > > > >Weex
> > > > > >
> > > > >
> > > > > Which is great but they are external to the project. Whats the
> > barriers
> > > > (if
> > > > > any) that stopped them from doing this development inside the
> > project?
> > > > >
> > > > > Thanks,
> > > > > Justin
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Graudate Apache Weex (Incubating) as a Top Level Project

[Dave Fisher]

Hi YorkShen,

> On Nov 1, 2019, at 10:33 AM, 申远  wrote:
> 
> Hi, Justin.
> 
> After serious thinking these days, I decided to withindraw the graduation
> vote. We need spend more time in Incubator, this graduation vote is a
> little hurry.
> 
> I admitted your concerns about diverse and independent community have some
> points, Weex still needs to impove in this apsect.
> 
> For branding part, I have some reservations about it, but I will see what I
> can do to make things better.

I replied earlier in the thread, but the response from Weex really should be to 
complete a Podling Name Search - https://incubator.apache.org/guides/names.html 


An issue is created here - 
https://issues.apache.org/jira/projects/PODLINGNAMESEARCH 


Someone on the Podling needs to do the research which should reveal any 
conflicts. The VP, Brand will approve or ask questions. It may be that some of 
these issues may require discussion about brand risk. Until the research is 
complete it is hard to know.

The Board is unlikely to approve graduation without the brand name being 
approved by the VP, Brand.

> 
> Is there any other concerns you have about Weex towards graduation ?

These are the two. They are important. You are to be congratulated for 
overcoming the LGPL issue!
> 
> FYI: Weex needs more active mentors, if possible. That would denifitely
> help.

Regards,
Dave
> 
> Best Regards,
> YorkShen
> 
> 申远
> 
> 
> ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 下午9:20写道：
> 
>> เมื่อ 30 ต.ค. 2019 7:52 PM "申远"  เขียนว่า
>> 
>>> FYI: If the initial committers really matter, maybe we could ask
>> secretary
>>> to help us find out how many individuals signed the ICLA when Weex
>> entered
>>> the Incubator.
>>> 
>>> Best Regards,
>>> YorkShen
>>> 
>>> 申远
>>> 
>>> 
>>> ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 下午8:35写道：
>>> 
 เมื่อ 30 ต.ค. 2019 7:16 PM "申远"  เขียนว่า
 
>> 
>> The PPMC needs to protect their brand in particular from their own
> company.
> 
> 
> Agree with that, and this is exactly why I am persuading project like
> Weex-UI [1] donated to ASF instead of making them changing their name
>>> to
> "XXX powered by Apache Weex" and then pretend there is no problem.
> 
> Anyone on the Initial list are committers I assume you mean they see
>>> not
>> contributing?
>> 
> 
> No, some [2] of them are never committers of Weex according to our
 whimsy.
> For example, the top 2 names on the initial developer list are not
> committers of Weex according to whimsy and they didn't contribute, of
> course. Some of other names, like me, are also on the initial
>> developer
> list, but I was actually elected as Weex committer four months after
>> it
> into incubator. There is a vote for nominating me as a Weex committer
 [3].
> I don't know what happened here, as I am not the initial committer in
 fact.
> But the initial developer list [2] is incorrect, I'm sure about that.
> 
> [1]
> https://lists.apache.org/thread.html/ab1cdf009697ac261e10c8963ed9ad
> fe226edeee056f0c7dabb780c0@%3Cdev.weex.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/b53537fea384f1d75c9921f71e13d1
> 7780381504cff971e5f18bda96@%3Cgeneral.incubator.apache.org%3E
> [3]
> https://lists.apache.org/thread.html/8ebbd2fb5fb85c1da4328685859ae1
> bb365a8b6253772c9e06940a39@%3Cprivate.weex.apache.org%3E
> 
> Best Regards,
> YorkShen
> 
> 申远
> 
> 
> Justin Mclean  于2019年10月30日周三 下午7:32写道：
> 
>> Hi,
>> 
>> It seems like there are two concerns around Weex, branding and
> independent
>>> community.
>>> 
>> 
>> I'd still like to hear what your mentors think. Are they active?
>> 
>> For branding part, I understand this is a serious issue, and it
>> takes
 me
>>> months to solve this kinds of issues
>>> 
>> 
>> This needs to be the PPMC not just you. I chose some of those links
>>> on
>> purpose as they belong to the company they belong to. The PPMC
>> needs
>>> to
>> protect their brand in particular from their own company.
>> 
>>   - Though there are 13 committers according to the initial
>> proposal
> [5],
>>>   but many of them are not committers today.
>> 
>> 
>> Anyone on the Initial list are committers I assume you mean they
>> see
 not
>> contributing?
>> 
>> Just take the committers on the initial proposal as an inacurrate
> records,
>>> there are some mistakes on this list.
>> 
>> 
>> This seems concerning.
>> 
>>> 
>>>   - There are developers out of the comany make their own tools
 around
>>>   Weex
>>> 
>> 
>> Which is great but they are external to the project. Whats the
>>> barriers

Re: Write Access to Incubator Wiki

[Kenneth Knowles]

FWIW, though I am mentoring other podlings, I don't seem to have the
ability to grant write permissions to others. (I double checked the
workflow for the Beam wiki, so I know what it looks like)

Kenn

On Thu, Oct 31, 2019 at 4:04 PM Dave Fisher  wrote:

> Hi -
>
> I’ll point out that your champion and mentors do have access and they
> could easily do that for you.
>
> Regards,
> Dave
>
> > On Nov 1, 2019, at 12:48 AM, Dominik Riemer  wrote:
> >
> > Thank you very much Kenn, that's awesome!
> > I'll add you as a mentor once we got access to the wiki, afterwards I'll
> also start a separate DISCUSS thread to discuss our proposal.
> >
> > Dominik
> >
> > -Original Message-
> > From: Kenneth Knowles 
> > Sent: Thursday, October 31, 2019 1:49 AM
> > To: general 
> > Subject: Re: Write Access to Incubator Wiki
> >
> > Cool!
> >
> > I see you have mentors lined up. I would love to also be involved as
> mentor.
> >
> > The list of initial committers seems a little small. Browsing the commit
> history it does seem to be dominated by just a couple of contributors. I
> see this is acknowledged (at least implicitly) in the proposal. I expect a
> principal challenge will be attracting diverse contributors, committers,
> and PMC to ensure this project survives independent of any particular
> entity (individual or corporate).
> >
> > Kenn
> >
> > On Wed, Oct 30, 2019 at 1:16 PM Dominik Riemer  wrote:
> >
> >> Hi all,
> >>
> >>
> >>
> >> a short introduction to myself: My name is Dominik Riemer and I'm a
> >> co-initiator of StreamPipes, an open source self-service toolbox for
> >> analyzing IoT data streams. After presenting the tool at this year's
> >> ApacheCon NA, followed by very friendly and fruitful discussions with
> >> many people from the Apache community, we are sure that we'd like
> >> continue the development of StreamPipes as an Apache community
> >> project. Before we start a discussion process, I'd like to ask to get
> >> write access to the Incubator wiki (username: riemer). An initial draft
> of the proposal is attached below.
> >>
> >>
> >>
> >> Thanks for your help!
> >>
> >> Dominik
> >>
> >>
> >>
> >>
> >>
> >> 
> >>
> >>
> >>
> >> StreamPipes - Apache Incubator Proposal, Proposal Draft
> >>
> >>
> >>
> >> == 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 produc

Re: Write Access to Incubator Wiki

[Dave Fisher]

Sorry I was not clear. Champions and Mentors can add the proposal to the wiki 
themselves. Now that we are using Confluence and Apache LDAP granting 
permissions to those with Apache IDs is easy. Those w/o it is not so easy and 
it adds useless sysadmin work.

If our current permission scheme makes it hard for IPMC members then that is a 
different problem.

Champions and mentors are here to make things easier for prospective podlings 
and not to add additional administrivia. This is especially true in the 
Incubator.

Guiding the proposal portion of the process is the champion’s task.

Chris Dutz?!

Regards (jet lagged in Shanghai),
Dave

Sent from my iPhone

> On Nov 1, 2019, at 11:55 AM, Kenneth Knowles  wrote:
> 
> FWIW, though I am mentoring other podlings, I don't seem to have the
> ability to grant write permissions to others. (I double checked the
> workflow for the Beam wiki, so I know what it looks like)
> 
> Kenn
> 
>> On Thu, Oct 31, 2019 at 4:04 PM Dave Fisher  wrote:
>> 
>> Hi -
>> 
>> I’ll point out that your champion and mentors do have access and they
>> could easily do that for you.
>> 
>> Regards,
>> Dave
>> 
 On Nov 1, 2019, at 12:48 AM, Dominik Riemer  wrote:
>>> 
>>> Thank you very much Kenn, that's awesome!
>>> I'll add you as a mentor once we got access to the wiki, afterwards I'll
>> also start a separate DISCUSS thread to discuss our proposal.
>>> 
>>> Dominik
>>> 
>>> -Original Message-
>>> From: Kenneth Knowles 
>>> Sent: Thursday, October 31, 2019 1:49 AM
>>> To: general 
>>> Subject: Re: Write Access to Incubator Wiki
>>> 
>>> Cool!
>>> 
>>> I see you have mentors lined up. I would love to also be involved as
>> mentor.
>>> 
>>> The list of initial committers seems a little small. Browsing the commit
>> history it does seem to be dominated by just a couple of contributors. I
>> see this is acknowledged (at least implicitly) in the proposal. I expect a
>> principal challenge will be attracting diverse contributors, committers,
>> and PMC to ensure this project survives independent of any particular
>> entity (individual or corporate).
>>> 
>>> Kenn
>>> 
 On Wed, Oct 30, 2019 at 1:16 PM Dominik Riemer  wrote:
>>> 
 Hi all,
 
 
 
 a short introduction to myself: My name is Dominik Riemer and I'm a
 co-initiator of StreamPipes, an open source self-service toolbox for
 analyzing IoT data streams. After presenting the tool at this year's
 ApacheCon NA, followed by very friendly and fruitful discussions with
 many people from the Apache community, we are sure that we'd like
 continue the development of StreamPipes as an Apache community
 project. Before we start a discussion process, I'd like to ask to get
 write access to the Incubator wiki (username: riemer). An initial draft
>> of the proposal is attached below.
 
 
 
 Thanks for your help!
 
 Dominik
 
 
 
 
 
 
 
 
 
 StreamPipes - Apache Incubator Proposal, Proposal Draft
 
 
 
 == 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 qui

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[Willem Jiang]

+1 (binding).

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Oct 30, 2019 at 9:48 AM David Nalley  wrote:
>
> Hi folks,
>
> The [DISCUSS] thread on TubeMQ has died down.
>
> Accordingly, I would like to call a VOTE to accept TubeMQ into the
> Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring TubeMQ into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring TubeMQ into the Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the
> Incubator PMC are binding, but votes from everyone are welcome.
>
> =Abstract=
>
> TubeMQ is a distributed messaging queue (MQ) system developed by
> Tencent Big Data since 2013. It focuses on high-performance storage
> and transmission of massive data in big data scenarios.After nearly
> seven years of massive data precipitation, TubeMQ has certain
> advantages in production practice (stability + performance) and low
> cost compared to many open source MQ projects.
>
> =Proposal=
>
> TubeMQ is suitable for high concurrency, massive data and tolerates a
> small amount of data loss scenarios under abnormal conditions, such as
> massive log collection, indicator statistics and monitoring, etc.
> TubeMQ does not support highly reliable data transmission services
> yet. It could be on a future project roadmap, as many other MQs. but
> not today.
>
> =Rationale=
>
> Just like other message queue systems, TubeMQ is built on the
> publish-subscribe pattern, aka pub-sub.
> In this pattern, producers publish messages to topics while consumers
> subscribe to those topics. After incoming messages get proceeded,
> consumers send an acknowledgement back to producer. Once a
> subscription has been created, all messages will be tracked and
> retained by TubeMQ, even if the consumer go offline for some reasons.
> Retained messages will be discarded only when a consumer acknowledges
> that they've been successfully processed.
>
> Portal is responsible for interact with user and admin system which
> include two parts: API and web portal.
>
> Master is controller of the cluster, which include one or multiple
> master node(s) which is responsible for managing state of cluster,
> resource scheduling, authentication check and maintaining of metadata.
> As a reliable system, TubeMQ provides HA solution for master node.
>
> Broker is responsible for data store which include a cluster of broker
> nodes. Every broker node is managing a set of topics, include: append,
> delete, update, query of topic information. In TubeMQ, these brokers
> can be horizontal scaled and can be very large size for massive data
> case.
>
> Client is responsible for producing and consuming messages. When a
> pub-sub topic get setup, we can support two ways (push and pull) for
> delivering message from producers to consumers.
>
> Zookeeper is for storing offset of messages which is used to recover
> topic during some components get failed.
>
>
> =Initial Goals=
>
> The initial goal will be to move the current codebase in github’s
> repository under Tencent account to Apache and integrate with the
> Apache development process and infrastructure.
> A primary goal of incubation will be to grow and diversify the TubeMQ
> community. We are well aware that the project community is largely
> comprised of individuals from a single company. We aim to change that
> during incubation.
>
> =Current Status=
>
> As previously mentioned, TubeMQ is under active development at
> Tencent, and is being used in processing large volumes of data for
> most services and products.
>
> =Meritocracy=
>
> We value meritocracy and we understand that it is the basis for an
> open community that encourages multiple companies and individuals to
> contribute and be invested in the project’s future. We will encourage
> and monitor participation and make sure to extend privileges and
> responsibilities to all contributors.
>
> =Community=
>
> TubeMQ is currently being used by developers at Tencent and a growing
> number of users are actively using it in production environments.
> TubeMQ has received contributions from developers working outside of
> Tencent since it was open sourced on github in September 2019 By
> bringing TubeMQ to Apache we aim to assure current and future
> contributors that the TubeMQ community is neutral, meritocratic, and
> open, in order to broaden and diversity the user and developer
> community.
>
> =Core Developers=
>
> TubeMQ was initially developed at Tencent and is under active
> development. We believe Tencent will be of interest to a broad range
> of users and developers and that incubating the project at the ASF
> will help us build a diverse, sustainable community.
>
> =Alignment=
>
> TubeMQ utilizes other Apache projects such as Hadoop, HBase and
> Zookeeper. We anticipate integration with additional Apache projects
> as the TubeMQ community and interest in the project grows.
>
> =Known Risks=
>
> ==Orphaned Products==
>
> Tencent is committed t

AW: Write Access to Incubator Wiki

[Christofer Dutz]

Sure,

Happy to take care of that.

Chris

Von: Dave Fisher 
Gesendet: Freitag, 1. November 2019 05:06:52
An: general@incubator.apache.org 
Betreff: Re: Write Access to Incubator Wiki

Sorry I was not clear. Champions and Mentors can add the proposal to the wiki 
themselves. Now that we are using Confluence and Apache LDAP granting 
permissions to those with Apache IDs is easy. Those w/o it is not so easy and 
it adds useless sysadmin work.

If our current permission scheme makes it hard for IPMC members then that is a 
different problem.

Champions and mentors are here to make things easier for prospective podlings 
and not to add additional administrivia. This is especially true in the 
Incubator.

Guiding the proposal portion of the process is the champion’s task.

Chris Dutz?!

Regards (jet lagged in Shanghai),
Dave

Sent from my iPhone

> On Nov 1, 2019, at 11:55 AM, Kenneth Knowles  wrote:
>
> FWIW, though I am mentoring other podlings, I don't seem to have the
> ability to grant write permissions to others. (I double checked the
> workflow for the Beam wiki, so I know what it looks like)
>
> Kenn
>
>> On Thu, Oct 31, 2019 at 4:04 PM Dave Fisher  wrote:
>>
>> Hi -
>>
>> I’ll point out that your champion and mentors do have access and they
>> could easily do that for you.
>>
>> Regards,
>> Dave
>>
 On Nov 1, 2019, at 12:48 AM, Dominik Riemer  wrote:
>>>
>>> Thank you very much Kenn, that's awesome!
>>> I'll add you as a mentor once we got access to the wiki, afterwards I'll
>> also start a separate DISCUSS thread to discuss our proposal.
>>>
>>> Dominik
>>>
>>> -Original Message-
>>> From: Kenneth Knowles 
>>> Sent: Thursday, October 31, 2019 1:49 AM
>>> To: general 
>>> Subject: Re: Write Access to Incubator Wiki
>>>
>>> Cool!
>>>
>>> I see you have mentors lined up. I would love to also be involved as
>> mentor.
>>>
>>> The list of initial committers seems a little small. Browsing the commit
>> history it does seem to be dominated by just a couple of contributors. I
>> see this is acknowledged (at least implicitly) in the proposal. I expect a
>> principal challenge will be attracting diverse contributors, committers,
>> and PMC to ensure this project survives independent of any particular
>> entity (individual or corporate).
>>>
>>> Kenn
>>>
 On Wed, Oct 30, 2019 at 1:16 PM Dominik Riemer  wrote:
>>>
 Hi all,



 a short introduction to myself: My name is Dominik Riemer and I'm a
 co-initiator of StreamPipes, an open source self-service toolbox for
 analyzing IoT data streams. After presenting the tool at this year's
 ApacheCon NA, followed by very friendly and fruitful discussions with
 many people from the Apache community, we are sure that we'd like
 continue the development of StreamPipes as an Apache community
 project. Before we start a discussion process, I'd like to ask to get
 write access to the Incubator wiki (username: riemer). An initial draft
>> of the proposal is attached below.



 Thanks for your help!

 Dominik





 



 StreamPipes - Apache Incubator Proposal, Proposal Draft



 == 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 standa