ตอบกลับ: Re: [VOTE] Accept TubeMQ into the Apache Incubator

[0989132858wyk]

ส่งจากสมาร์ทโฟน Samsung Galaxy ของฉัน
 ข้อความดั้งเดิม จาก: Kenneth Knowles  
วัน​ที่: 31/10/19  11:19  (GMT+07:00) ถึง: general 
 เรื่อง: Re: [VOTE] Accept TubeMQ into the Apache 
Incubator 
+1 (binding)

On Wed, Oct 30, 2019 at 8:07 PM Goson zhang  wrote:

>    +1（non-binding）
>
> 发件人： 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, 

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[Kenneth Knowles]

+1 (binding)

On Wed, Oct 30, 2019 at 8:07 PM Goson zhang  wrote:

>+1（non-binding）
>
> 发件人： 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 

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[Goson zhang]

   +1（non-binding）

发件人： 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 Risks=

==Orphaned Products==

Tencent is committed to the future development of TubeMQ and
understands that graduation to a TLP, while preferable, is not the
only positive outcome of incubation.

Should the TubeMQ project be accepted by the Incubator, 

Re: Write Access to Incubator Wiki

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

Re: Omid and Tephra

[Matt Sicker]

https://svn.apache.org/repos/private/documents/grants/caskdata-tephra

On Wed, 30 Oct 2019 at 15:16, Alan Gates  wrote:
>
> Regarding SGAs, here's the JIRA for Omid:
> https://issues.apache.org/jira/browse/OMID-2
> According to
> https://svn.apache.org/repos/private/foundation/officers/grants.txt Cask
> (original creators of Tephra) submitted a SGA for it and it's one file, but
> I don't know where the referenced file is kept.
>
> Alan.
>
> On Wed, Oct 30, 2019 at 10:32 AM Alan Gates  wrote:
>
> > Bertand, thanks for bringing this up.  I'll chase those down.
> >
> > Alan.
> >
> > On Wed, Oct 30, 2019 at 8:46 AM Bertrand Delacretaz <
> > bdelacre...@codeconsult.ch> wrote:
> >
> >> Hi,
> >>
> >> On Wed, Oct 30, 2019 at 3:55 PM Josh Elser  wrote:
> >> > ...My current expectation is that we'd just rename the existing Git
> >> > repositories and change the LDAP group which are used to determine write
> >> > access...
> >>
> >> From the Incubator's point of view, I think an additional step is to
> >> confirm and document if any Software Grants were needed for these
> >> projects code and if yes if they've been filed as needed.
> >>
> >> This can be just a jira or other ticket documenting the move and
> >> including this info.
> >>
> >> -Bertrand
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>



-- 
Matt Sicker 

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

Write Access to Incubator Wiki

[Dominik Riemer]

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

Re: Omid and Tephra

[Alan Gates]

Regarding SGAs, here's the JIRA for Omid:
https://issues.apache.org/jira/browse/OMID-2
According to
https://svn.apache.org/repos/private/foundation/officers/grants.txt Cask
(original creators of Tephra) submitted a SGA for it and it's one file, but
I don't know where the referenced file is kept.

Alan.

On Wed, Oct 30, 2019 at 10:32 AM Alan Gates  wrote:

> Bertand, thanks for bringing this up.  I'll chase those down.
>
> Alan.
>
> On Wed, Oct 30, 2019 at 8:46 AM Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
>
>> Hi,
>>
>> On Wed, Oct 30, 2019 at 3:55 PM Josh Elser  wrote:
>> > ...My current expectation is that we'd just rename the existing Git
>> > repositories and change the LDAP group which are used to determine write
>> > access...
>>
>> From the Incubator's point of view, I think an additional step is to
>> confirm and document if any Software Grants were needed for these
>> projects code and if yes if they've been filed as needed.
>>
>> This can be just a jira or other ticket documenting the move and
>> including this info.
>>
>> -Bertrand
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: Omid and Tephra

[Alan Gates]

Bertand, thanks for bringing this up.  I'll chase those down.

Alan.

On Wed, Oct 30, 2019 at 8:46 AM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Wed, Oct 30, 2019 at 3:55 PM Josh Elser  wrote:
> > ...My current expectation is that we'd just rename the existing Git
> > repositories and change the LDAP group which are used to determine write
> > access...
>
> From the Incubator's point of view, I think an additional step is to
> confirm and document if any Software Grants were needed for these
> projects code and if yes if they've been filed as needed.
>
> This can be just a jira or other ticket documenting the move and
> including this info.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Omid and Tephra

[Bertrand Delacretaz]

Hi,

On Wed, Oct 30, 2019 at 3:55 PM Josh Elser  wrote:
> ...My current expectation is that we'd just rename the existing Git
> repositories and change the LDAP group which are used to determine write
> access...

>From the Incubator's point of view, I think an additional step is to
confirm and document if any Software Grants were needed for these
projects code and if yes if they've been filed as needed.

This can be just a jira or other ticket documenting the move and
including this info.

-Bertrand

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

Re: Omid and Tephra

[Josh Elser]

I like the idea of opt-in for committership for the current podling 
membership (without any "time to respond" limitation). I don't foresee 
any concerns doing that, but will shout if that becomes an issue.


On 10/28/19 3:09 PM, Justin Mclean wrote:

Hi,


According to [4] the first step of graduating into a sub-project of an
existing TLP is a vote by the podling.  Given that both podlings have very
low activity I am not sure we will get the necessary votes to make this
happen.


I would try and see what happens - the mentors have binding votes so hopefully 
they will vote. If we don’t get enough votes or if someone raises an objection 
we’ll decide what to do then.


One question that I'd like to see resolved as part of this vote
is what status Phoenix plans to grant to Tephra and Omid committers and
PPMC members.


I would ask all PPMC and committers if they want to be part of Phoenix 
PMC/committers and grant those who reply. But if the Phoenix PMC has other 
ideas they could also be considered.

If someone at a later point decides to “opt-in” you may want to consider that 
as well.

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: Omid and Tephra

[Josh Elser]

(w/ VP Phoenix hat)

My current expectation is that we'd just rename the existing Git 
repositories and change the LDAP group which are used to determine write 
access. In other words, your Git repos will exist just as they do now, 
but only at different coordinates.


On 10/25/19 12:27 AM, Ohad Shacham wrote:

+1, Thanks Alan.
Just wanted to verify that adopt means Omid and Tephra will sit in the same
repo as Phoenix but will be able to checkout separately as well. I assume
this is Phoenix folks decision.
I know that in Yahoo Omid is used internally.

On Fri, Oct 25, 2019 at 2:36 AM Gary Helmling  wrote:


+1 this seems like the best option.

On Thu, Oct 24, 2019 at 2:29 PM Andrew Purtell 
wrote:


+1 this would be a good outcome. Both Tephra and OMID are good
technologies, with respective pros and cons, and Phoenix can make good

use

of both of them, should they choose to accept ownership of the code.

On Wed, Oct 23, 2019 at 11:26 AM Alan Gates 

wrote:



Justin and mentors of Omid and Tephra,

As Justin noted in his emails to these podlings this month both are

very

low activity, struggling to even file their reports, and appear to be
candidates for retirement.

The situation here is somewhat special because Phoenix uses one or both

of

these technologies (they are both transaction managers on top of

HBase),

so

they may have an interest in their continued survival.  Tephra briefly
discussed this last June[1], though nothing came of it.  My conclusion

is

there is not enough momentum left for these podlings to vote themselves
into Phoenix without an external push.

So before we push them into retirement I believe we should involve the
Phoenix PMC and see if they want to adopt either or both of these, with

the

knowledge that they will likely be getting minimal contributions from
current members of those projects going forward.  If others are ok with
this I can contact the Phoenix PMC and see if they wish to take any

action

on this.

Alan.

1.





https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E





--
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
- A23, Crosstalk







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

Re: [DISCUSS] TubeMQ Proposal

[ซ่อยค่อย ลืมเขาแน่]

เมื่อ 30 ต.ค. 2019 12:06 PM "Jean-Baptiste Onofré" 
เขียนว่า

> Thanks David !
>
> Regards
> JB
>
> On 30/10/2019 02:40, David Nalley wrote:
>
>> On Mon, Oct 21, 2019 at 7:50 AM Jean-Baptiste Onofré 
>> wrote:
>>
>>> Hi David,
>>>
>>> Very interesting proposal.
>>>
>>> How do you compare with Apache Kafka or Pulsar ?
>>> It sounds to address the same use cases, right ?
>>>
>>> I would be interested to be mentor on the proposal if you are looking
>>> for an additional one.
>>>
>>> Thanks for offering. We'll happily take you up on the offer.
>>
>> Thanks,
>>
>> --David
>>
>> -
>> 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] Graudate Apache Weex (Incubating) as a Top Level Project

[ซ่อยค่อย ลืมเขาแน่]

เมื่อ 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

[申远]

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

[ซ่อยค่อย ลืมเขาแน่]

เมื่อ 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

[申远]

>
> 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/ab1cdf009697ac261e10c8963ed9adfe226edeee056f0c7dabb780c0@%3Cdev.weex.apache.org%3E
[2]
https://lists.apache.org/thread.html/b53537fea384f1d75c9921f71e13d17780381504cff971e5f18bda96@%3Cgeneral.incubator.apache.org%3E
[3]
https://lists.apache.org/thread.html/8ebbd2fb5fb85c1da4328685859ae1bb365a8b6253772c9e06940a39@%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

[Justin Mclean]

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] Accept TubeMQ into the Apache Incubator

[Gosling Von]

+1, binding


Best Regards,
Von Gosling

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

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[Bertrand Delacretaz]

On Wed, Oct 30, 2019 at 2:48 AM David Nalley  wrote:
> ...I would like to call a VOTE to accept TubeMQ into the
> Apache Incubator

+1, binding

-Bertrand

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

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[Woonsan Ko]

+1 (binding)

Regards,

Woonsan

On Wed, Oct 30, 2019 at 10: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 to the future development of 

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

[申远]

It seems like there are two concerns around Weex, branding and independent
community.

For branding part, I understand this is a serious issue, and it takes me
months to solve this kinds of issues, like donating weex-loader[1],
weex-cli [2] to ASF, upgrading POM meta [3], changing package name [4],
etc..  Again, there are over 1 million pages of Weex in Google, I can't
promosie all of them are fine(without branding issue). And due to the fact
that Weex once belongs to a company, not ASF, there are some NPM/POM
publishing records reflects that Weex once belongs to a commnay, and I
can't undo or delete that history. But we shall fix the brand issues once
we know it, maybe we could also write down a brand protection procedure.

For independent community part, I think there are two issues need to solve,
and two issues to make it clear.

   - Many committers were coming from the same company, though some of them
   (3 or 4, including some 2 PPMC members) have resigned from the commany. But
   still to many, I guess.
   - We used to ignore the difference between committers and PPMC members,
   that's reason why so many new committers and so less PPMC members. We are
   tyring to fix this issue by inviting all committers to Weex PMC during its
   graduaiton procedure. But we could fix it in another way, if its' needed.
   - Though there are 13 committers according to the initial proposal [5],
   but many of them are not committers today. Even me, listed as an inital
   commiter of Weex, but actually joined Weex community 4 months aftter its
   into the incubator. Just take the committers on the initial proposal as an
   inacurrate records, there are some mistakes on this list. Actually, if you
   considered fact that Weex Joined the Incubator in Dec, 2016, there are 4
   committer account created at that time [6]. So I guess the four of them are
   actually the inital committers(or PPMC members), rest of them are not
   (including me).
   - There are developers out of the comany make their own tools around
   Weex, and try to donate it to Weex. Currently, we're trying to encourage
   them to go through the IP clearance procedure and then nominate them as
   committer [7]. I guess this is some kinds of proof for independency, or
   diverse and active community at least.

[1] https://incubator.apache.org/ip-clearance/weex_loader.html
[2] https://incubator.apache.org/ip-clearance/weex_cli.html
[3] https://bintray.com/weex/Android/sdk
[4] https://weex.apache.org/download/major_change.html#_0-28
[5]
https://lists.apache.org/thread.html/b53537fea384f1d75c9921f71e13d17780381504cff971e5f18bda96@%3Cgeneral.incubator.apache.org%3E
[6] https://whimsy.apache.org/roster/ppmc/weex
[7]
https://mail-archives.apache.org/mod_mbox/weex-dev/201910.mbox/%3Ctencent_EA5069E21326C37D64F20CC18D885B3BAE05%40qq.com%3E

Best Regards,
YorkShen

申远


Justin Mclean  于2019年10月29日周二 下午4:04写道：

> Hi,
>
> If the project can show they are acting independently of a single company
> that would help them convince the board/IPMC they can graduate. What has
> the project done to attract developers out side of that company to work on
> the project?
>
> Are there any barriers that hinders outside involvement? e.g. off list or
> internal communication or having synchronous meetings can be an issue. (I
> don’t know this is happening on this project. These are just suggestions to
> the type of things that might hinder outside involvement.)
>
> Of the committers voted in during incubation, do all work for the same
> company? Could any be considered as candidates for PPMC membership?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[Kevin A. McGrail]

+1 Binding

-KAM

On 10/30/2019 3:08 AM, Kevin Ratnasekera wrote:
> +1 ( binding )
>
> On Wed, Oct 30, 2019 at 10:38 AM vintagewang  wrote:
>
>> +1
>>
>> 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, 

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[Kevin Ratnasekera]

+1 ( binding )

On Wed, Oct 30, 2019 at 10:38 AM vintagewang  wrote:

> +1
>
> 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