I guess they （core developers）lost their mission (or lost mind). You can just made tubemq as a sub module of a huge project.
It's not the business . Kafka is another mq. It's also an apache project. did you see they say. let's make a big project, make kafka as a sub project? Appreciate your time. ---------------------------- Netroby 赵磊 <[email protected]> 于2020年12月18日周五 上午10:04写道： > > > > > It was really such a big surprise. In recent months, i had made lots of > testing on tubemq and decide to use it in my solution. > > but if the project's goals and name changed ,can i use tubemq > independently? if so,will it take lots of workload? > > if the change is imperative when can we see the new architecture? > > > > > > > > > > > > > > > At 2020-12-17 20:17:58, "人间不值得" <[email protected]> wrote: > >It’s wired, if you want push another area, just named a new project, do you > >know hdfs and Hadoop? > > > >Force change project name and project main goals very wired. > >Let tubemq do one job please. It’s good and enough. > > > >发自我的iPad > > > >> 在 2020年12月14日，下午7:08，Goson zhang <[email protected]> 写道： > >> > >> Hi, Dev > >> > >> I'd like to raise a discussion about adjusting the project goals and > >> project name > >> > >> As the initiator of the project, after TubeMQ joined the Apache community, > >> we have been improving the features and functions in accordance with the > >> needs of the project, also, we have been promoting the evolution of the > >> project in the direction of "one-stop data access", providing technical > >> capabilities such as data collection, transmission, sorting, and landing > >> which covers big data scenario completely. For instance, we have recently > >> developed a module called tubemq-manager for cross-cluster management, > >> other modules such as agent and sorting will be added sooner in the future. > >> As TubeMq matures and strengthens, we found that it's not just a single MQ > >> service, but also a one-stop data access solution that covers the entire > >> data reporting service. If we continue to retain the suffix "mq" in the > >> project name, it may confuse our users or even those who follow up on our > >> project. > >> > >> We hope to present different project goals by modifying the project name. > >> We will retain and continue to develop the TubeMQ module to provide > >> messaging middleware service capabilities. At the same time, we will make > >> some capabilities such as data collection and data sorting open source, > >> the overall services in data reporting which provides people with all the > >> advantages in this field are also in our open-source plan. And of course, > >> such adjustment would have impact on everyone, after the project is > >> renamed, people need to include the main name of the new project in the > >> existing TubeMQ import path, from the previous "import > >> org.apache.tubemq.xxx" to "import org.apache.yyyyy.tubemq.xxx", but this > >> adjustment will enable us to provide them with more integrated components > >> on the data reporting service. > >> > >> Regarding the change of project goal && project name, we PPMCs have > >> conducted many offline and online discussions, we also consulted project > >> mentors to understand that: > >> 1. If the project must be renamed, do it as soon as possible, it will have > >> less impact on everyone ; > >> 2. There is one and only one chance to change the name before the project > >> incubation graduation; > >> 3. Before changing the name, we must inform everyone in the community and > >> listen to the opinions and suggestions. > >> > >> Therefore, we send this email to discuss the adjustment of goal and name, > >> and to obtain more opinions and suggestions towards it. > >> > >> Thanks! > >> > >> TubeMQ PPMCs
