[ANNOUNCE] Apache Doris (incubating) 0.11.0 Release
Hi All, We are pleased to announce the release of Apache Doris 0.11.0-incubating. Apache Doris (incubating) is an MPP-based interactive SQL data warehousing for reporting and analysis. The release is available at: http://www.apache.org/dist/incubator/doris/ Thanks to everyone who has contributed to this release, and the release note can be found here: https://github.com/apache/incubator-doris/issues/1891 Best Regards, On behalf of the Doris team, Zhao Chun DISCLAIMER: Apache Doris(incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
Re: [VOTE] Graudate Apache Weex (Incubating) as a Top Level Project
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
[jira] [Updated] (INCUBATOR-247) IP clearance for ServiceComb osa-validator
[ https://issues.apache.org/jira/browse/INCUBATOR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated INCUBATOR-247: --- Description: [chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster] is contributing the oas-validator to Apache ServiceComb. The clearance tasks are in progress and recorded at: [https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html] This issue is partly to track that and primarily to provide an official record of the code drop contribution. The contributed code is attached to this issue as oas-validator-apache.zip. MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 Github repo [https://github.com/NewCapec-Institute/oas-validator] Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199 was: [chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster] is contributing the oas-validator to Apache ServiceComb. The clearance tasks are in progress and recorded at: [https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html] This issue is partly to track that and primarily to provide an official record of the code drop contribution. The contributed code is attached to this issue as oas-validator-apache.zip. MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 Github repo [https://github.com/NewCapec-Institute/oas-validator] Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199 > IP clearance for ServiceComb osa-validator > -- > > Key: INCUBATOR-247 > URL: https://issues.apache.org/jira/browse/INCUBATOR-247 > Project: Incubator > Issue Type: Task >Reporter: Willem Jiang >Priority: Major > Attachments: oas-validator-apache.zip > > > > [chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster] > is contributing the oas-validator to Apache ServiceComb. > The clearance tasks are in progress and recorded at: > [https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html] > This issue is partly to track that and primarily to provide an official > record of the code drop contribution. The contributed code is attached to > this issue as oas-validator-apache.zip. > MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 > Github repo [https://github.com/NewCapec-Institute/oas-validator] > Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-247) IP clearance for ServiceComb osa-validator
[ https://issues.apache.org/jira/browse/INCUBATOR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated INCUBATOR-247: --- Description: [chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster] is contributing the oas-validator to Apache ServiceComb. The clearance tasks are in progress and recorded at: [https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html] This issue is partly to track that and primarily to provide an official record of the code drop contribution. The contributed code is attached to this issue as oas-validator-apache.zip. MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 Github repo [https://github.com/NewCapec-Institute/oas-validator] Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199 was: [chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster] is contributing the oas-validator to Apache ServiceComb. The clearance tasks are in progress and recorded at: [https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html] This issue is partly to track that and primarily to provide an official record of the code drop contribution. The contributed code is attached to this issue as oas-validator-apache.zip. MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 Github repo [https://github.com/NewCapec-Institute/oas-validator] Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199 > IP clearance for ServiceComb osa-validator > -- > > Key: INCUBATOR-247 > URL: https://issues.apache.org/jira/browse/INCUBATOR-247 > Project: Incubator > Issue Type: Task >Reporter: Willem Jiang >Priority: Major > Attachments: oas-validator-apache.zip > > > > [chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster] > is contributing the oas-validator to Apache ServiceComb. > The clearance tasks are in progress and recorded at: > [https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html] > This issue is partly to track that and primarily to provide an official > record of the code drop contribution. The contributed code is attached to > this issue as oas-validator-apache.zip. > MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 > Github repo [https://github.com/NewCapec-Institute/oas-validator] > Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Omid and Tephra
I agree with Justin, I think we get - at least in the Tephra community - a quorum. -Andreas On Mon, Oct 28, 2019 at 12: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 > >
Re: Omid and Tephra
Makes sense. I've replied to the discussion in the Phoenix community so we know what terms Tephra and Omid are voting on. As soon as I hear from them I'll start votes in both communities. Alan. On Tue, Oct 29, 2019 at 3:47 PM Andreas Neumann wrote: > I agree with Justin, I think we get - at least in the Tephra community - a > quorum. > -Andreas > > On Mon, Oct 28, 2019 at 12: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 > > > > >
Re: [DISCUSS] TubeMQ Proposal
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
[VOTE] Accept TubeMQ into the Apache Incubator
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, the prospective PPMC would be willing to agree to a target incubation period of 2 years or less, knowing that every Incubator projec
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+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 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== >
Re: [VOTE] Accept TubeMQ into the Apache Incubator
Thanks David for calling the vote! I am giving my binding +1. Thanks, Junping David Nalley 于2019年10月30日周三 上午9:48写道： > 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
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+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 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 communit
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+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 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 > > >
Re: [DISCUSS] TubeMQ Proposal
เมื่อ 30 ต.ค. 2019 8:41 AM "David Nalley" เขียนว่า > 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 > >
Re: [VOTE] Accept TubeMQ into the Apache Incubator
เมื่อ 30 ต.ค. 2019 8:48 AM "David Nalley" เขียนว่า > 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
Re: [ANNOUNCE] Apache Doris (incubating) 0.11.0 Release
เมื่อ 29 ต.ค. 2019 2:29 PM "Zhao Chun" เขียนว่า > Hi All, > > We are pleased to announce the release of Apache Doris 0.11.0-incubating. > > Apache Doris (incubating) is an MPP-based interactive SQL data warehousing > for reporting and analysis. > > The release is available at: > http://www.apache.org/dist/incubator/doris/ > > Thanks to everyone who has contributed to this release, and the release > note can be found here: > https://github.com/apache/incubator-doris/issues/1891 > > Best Regards, > On behalf of the Doris team, > Zhao Chun > > > DISCLAIMER: > Apache Doris(incubating) is an effort undergoing incubation at The Apache > Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is > required of all newly accepted projects until a further review indicates > that > the infrastructure, communications, and decision making process have > stabilized > in a manner consistent with other successful ASF projects. While incubation > status is not necessarily a reflection of the completeness or stability of > the > code, it does indicate that the project has yet to be fully endorsed by the > ASF. >
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding). good luck！ — *DolphinScheduler(Incubator) *PPMC *Lidong Dai * lidong@outlook.com — On Wed, Oct 30, 2019 at 10:30 AM 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 > > > >
Re: [VOTE] release datasketches-postgresql 1.3.0-incubating-rc2
เมื่อ 27 ต.ค. 2019 3:50 PM "Justin Mclean" เขียนว่า > Hi, > > +1 binding > > I checked: > - incubating in name > - signature and hashes correct > - No binary files in release > - DISCLAIMER exists > - LICENCE and NOTICE file are good > - This file is missing an ASF header [1] > - unable to compile on OSX but probably because I may not have right > environment setup or version of PostgreSQL installed > > Compile error is: > src/kll_float_sketch_c_adapter.cpp:26:10: fatal error: 'kll_sketch.hpp' > file not > found > #include > > Thanks, > Justin > > 1. apache-datasketches-postgresql-1.3.0-incubating-src/package.sh > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [IP CLEARANCE] ServiceComb toolkit contribution
เมื่อ 28 ต.ค. 2019 8:11 AM "Willem Jiang" เขียนว่า > 72 hours passed. We got none -1 vote. > > Based on lazy consensus, this vote passed. I will update the > ip-clearance page for the vote information. > > Willem Jiang > > On behalf of ServiceComb PMC. > > On Thu, Oct 24, 2019 at 9:58 AM Willem Jiang > wrote: > > > > Hi Incubator PMC, > > > > The TLP Apache ServiceComb toolkit[1] has been donated code for > > OpenAPI Specific Validator being referred to as > > `servicecomb-oas-validator`, old hostsd at [2]. > > > > This is the formal request for IP clearance to be checked as per [3]. > > The donated code can be found at [4] . > > > > Please check the ip-clearance filed here[5] for more information. > > The PMC has voted and passed to accept this donation[6]. > > The ICLA of major contributors, Daniel Qian has been filed. > > The SGA from NewCapec Institute has been filed. > > > > Please vote to approve this contribution. > > > > This majority vote is open for at least 72 hours and as usual lazy > > consensus applies. > > > > [1]https://github.com/apache/servicecomb-toolkit > > [2]https://github.com/NewCapec-Institute/oas-validator > > [3]https://incubator.apache.org/ip-clearance/ip-clearance- > template.html#form-filling > > [4]https://issues.apache.org/jira/browse/INCUBATOR-247 > > [5]https://incubator.apache.org/ip-clearance/servicecomb- > oas-validator.html > > [6]https://lists.apache.org/thread.html/704967302e2f3c093441bf197bfe83 > b7aee34c210e0c3bb3898d4170@%3Cdev.servicecomb.apache.org%3E > > > > Willem Jiang > > > > On behalf of ServiceComb PMC. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Doris 0.11.0-incubating-rc01
เมื่อ 27 ต.ค. 2019 8:46 AM "Dave Meikle" เขียนว่า > On Wed, 23 Oct 2019 at 10:11, Zhao Chun wrote: > > > The artifacts (source, signature and checksum) corresponding to this > > release > > candidate can be found here: > > https://dist.apache.org/repos/dist/dev/incubator/doris/0.11.0-rc1/ > > > > This has been signed with PGP key 983C9560, corresponding to > > zh...@apache.org. > > > > The vote will be open for at least 72 hours. > > > > From the PPMC Vote we cary over 1 binding IPMC Votes: > > > > +1 from Dave Fisher > > > > [ ] +1 Approve the release > > [ ] +0 No opinion > > [ ] -1 Do not release this package because ... > > > > > +1 (binding). I checked; name, sig and hashes, notice, license, source > headers, compiles from source (using Docker environment). > > As noted by Dave Fisher on the dev list - it is worth adding licence > headers to the markdown files. > > Cheers, > Dave >
Re: [DISCUSS] Maven account for publishing convience binary
เมื่อ 30 ก.ย. 2019 4:55 PM "申远" เขียนว่า > Hi, folks > > Recently, I am trying to publish convenience library of Weex to JCenter, a > seperate maven repositories for Android developers. I’d like to know > whether there is an Apache-wide JCenter account for publishing connivence > binary. It seems like each Apache project is allowed to create their own > Jcenter account [1] and publish convenience library as long as the account > is shared by PMC/PPMC. > > Please correct me if I am wrong, otherwise I shall create a jcenter > accounts shared by Weex PPMC. > > [1] https://bintray.com/cordova/maven/cordova-android > [2] https://bintray.com/bintray/jcenter/org.apache.commons:commons-lang3 > > Best Regards, > YorkShen > > 申远 >
Re: [jira] [Updated] (INCUBATOR-247) IP clearance for ServiceComb osa-validator
เมื่อ 29 ต.ค. 2019 3:36 PM "Willem Jiang (Jira)" เขียนว่า > > [ https://issues.apache.org/jira/browse/INCUBATOR-247? > page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > Willem Jiang updated INCUBATOR-247: > --- > Description: > [chanjarster|https://github.com/NewCapec-Institute/oas- > validator/commits?author=chanjarster] is contributing the oas-validator > to Apache ServiceComb. > > The clearance tasks are in progress and recorded at: [ > https://incubator.apache.org/ip-clearance/servicecomb- > osa-validator.html|https://incubator.apache.org/ip- > clearance/servicecomb-osa-validator.html] > > This issue is partly to track that and primarily to provide an official > record of the code drop contribution. The contributed code is attached to > this issue as oas-validator-apache.zip. > > MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 > > Github repo [https://github.com/NewCapec-Institute/oas-validator] > > Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7 > d2182d7199 > > > > > > was: > [chanjarster|https://github.com/NewCapec-Institute/oas- > validator/commits?author=chanjarster] is contributing the oas-validator > to Apache ServiceComb. > > The clearance tasks are in progress and recorded at: [ > https://incubator.apache.org/ip-clearance/servicecomb- > osa-validator.html|https://incubator.apache.org/ip- > clearance/servicecomb-toolkit.html] > > This issue is partly to track that and primarily to provide an official > record of the code drop contribution. The contributed code is attached to > this issue as oas-validator-apache.zip. > > MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 > > Github repo [https://github.com/NewCapec-Institute/oas-validator] > > Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7 > d2182d7199 > > > > > > > > IP clearance for ServiceComb osa-validator > > -- > > > > Key: INCUBATOR-247 > > URL: https://issues.apache.org/jira/browse/INCUBATOR-247 > > Project: Incubator > > Issue Type: Task > >Reporter: Willem Jiang > >Priority: Major > > Attachments: oas-validator-apache.zip > > > > > > [chanjarster|https://github.com/NewCapec-Institute/oas- > validator/commits?author=chanjarster] is contributing the oas-validator > to Apache ServiceComb. > > The clearance tasks are in progress and recorded at: [ > https://incubator.apache.org/ip-clearance/servicecomb- > osa-validator.html|https://incubator.apache.org/ip- > clearance/servicecomb-osa-validator.html] > > This issue is partly to track that and primarily to provide an official > record of the code drop contribution. The contributed code is attached to > this issue as oas-validator-apache.zip. > > MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 > > Github repo [https://github.com/NewCapec-Institute/oas-validator] > > Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7 > d2182d7199 > > > > > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) > > - > 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
เมื่อ 28 ต.ค. 2019 2:42 PM "Justin Mclean" เขียนว่า > Hi, > > > How can third party web sites be a "branding/trademark issue" for an > > Apache project? > > (P)PMC members are responsible for the project brands and that includes > making sure that 3rd parties use that brands and trademarks correctly. > > I suggest you read https://www.apache.org/foundation/marks/resources. > https://www.apache.org/foundation/marks/responsibility > https://www.apache.org/foundation/marks/guide > https://www.apache.org/foundation/marks/faq/ > > At ApacheCon Shane gavse a version of this talk which also may help: > http://shaneslides.com/fossbackstage/Who-Owns-That-FOSS-Brand.pdf > > (There was an updated version of this given at Apache EU last week) > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [RESULT][VOTE] Release Apache Doris 0.11.0-incubating-rc01
เมื่อ 29 ต.ค. 2019 1:13 PM "Zhao Chun" เขียนว่า > Hi all, > > Thanks to everyone, and the vote for releasing Apache Doris > 0.11.0-incubating-rc01 is now closed. > > It has passed with 3 +1 (binding) votes and no 0 or -1 votes. > > Binding: > +1 Dave Fisher > +1 Dave Meikle > +1 Willem Jiang > > The vote thread: > https://lists.apache.org/thread.html/d1cd04315b948e66a9f30b5102335a > c0770c8a9c62d0aab5cb50e0dc@%3Cgeneral.incubator.apache.org%3E > > Thanks, > Zhao Chun >
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding). Scheduler dolphin 于2019年10月30日周三 上午10:49写道： > +1 (non-binding). > good luck！ > > — > > *DolphinScheduler(Incubator) *PPMC > *Lidong Dai * > > lidong@outlook.com > > — > > On Wed, Oct 30, 2019 at 10:30 AM 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 compan
Re: [VOTE] Accept TubeMQ into the Apache Incubator
เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" เขียนว่า > +1 (non-binding). > good luck！ > > — > > *DolphinScheduler(Incubator) *PPMC > *Lidong Dai * > > lidong@outlook.com > > — > > On Wed, Oct 30, 2019 at 10:30 AM 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
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding) Best, tison. ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 上午11:01写道： > เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" > เขียนว่า > > > +1 (non-binding). > > good luck！ > > > > — > > > > *DolphinScheduler(Incubator) *PPMC > > *Lidong Dai * > > > > lidong@outlook.com > > > > — > > > > On Wed, Oct 30, 2019 at 10:30 AM 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. > > > > > > > > > > > > =
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 On Wed, Oct 30, 2019 at 11:09 AM tison wrote: > +1 (non-binding) > > Best, > tison. > > > ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 上午11:01写道： > > > เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" < > dolphinsched...@gmail.com> > > เขียนว่า > > > > > +1 (non-binding). > > > good luck！ > > > > > > — > > > > > > *DolphinScheduler(Incubator) *PPMC > > > *Lidong Dai * > > > > > > lidong@outlook.com > > > > > > — > > > > > > On Wed, Oct 30, 2019 at 10:30 AM 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 i
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 在 2019/10/30 上午10:00，“Dave Fisher” 写入: +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 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 wa
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding) ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 上午11:01写道： > > เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" > เขียนว่า > > > +1 (non-binding). > > good luck！ > > > > — > > > > *DolphinScheduler(Incubator) *PPMC > > *Lidong Dai * > > > > lidong@outlook.com > > > > — > > > > On Wed, Oct 30, 2019 at 10:30 AM 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= > > > > > > > > > > >
回复：[VOTE] Accept TubeMQ into the Apache Incubator
+1 (binding). Ted Liu, ASF Member, Incubator PMC Member 2019 年 10 月 30 日周三 9:48，David Nalley 写道： 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, the prospective PPMC would
Re: [VOTE] Accept TubeMQ into the Apache Incubator
Hi, +1 (binding) Kind Regards, Furkan KAMACI 30 Eki 2019 Çar, saat 06:12 tarihinde Junjie Chen şunu yazdı: > +1 (non-binding) > > > ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 上午11:01写道： > > > > เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" < > dolphinsched...@gmail.com> > > เขียนว่า > > > > > +1 (non-binding). > > > good luck！ > > > > > > — > > > > > > *DolphinScheduler(Incubator) *PPMC > > > *Lidong Dai * > > > > > > lidong@outlook.com > > > > > > — > > > > > > On Wed, Oct 30, 2019 at 10:30 AM 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 acco
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (binding) Good luck ! Regards JB On 30/10/2019 02:48, 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 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, the prospective PPMC would be willing to agree
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 > 发件人： 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
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding) -- Anu On Tue, Oct 29, 2019 at 9:59 PM 李响 wrote: > +1 > > > > 发件人： 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, sus
Re: [DISCUSS] TubeMQ Proposal
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] Accept TubeMQ into the Apache Incubator
+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 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 gradua
