Re: Re: [VOTE] Graduate Apache StreamPieps to a TLP

2022-11-18 Thread guo jiwei
+1 (non-binding)

Regards
Jiwei Guo (Tboy)


On Fri, Nov 18, 2022 at 10:30 PM KimmKing  wrote:

> +1 nobinding
>
>
>
>
> --
>
> Kimm King(kimmk...@apache.org/kimmk...@163.com)
> Apache Dubbo PMC Member
> github: kimmking


Re: [VOTE] Graduate Apache MXNet to a TLP

2022-08-22 Thread guo jiwei
+1 (non-binding)
Good luck


Regards
Jiwei Guo (Tboy)


On Mon, Aug 22, 2022 at 9:36 PM zhongyi tan  wrote:

> +1 (non-binding)
>
> On Mon, Aug 22, 2022 at 9:33 PM Calvin Kirs  wrote:
>
> > Hi,
> > Good luck. overall looks good.
> > I only got a question:
> > Six of the PPMC members are not subscribed to the private mailing list.
> >
> > 俊平堵  于2022年8月22日周一 21:02写道:
> > >
> > > +1 (binding). Good luck!
> > >
> > > Thanks,
> > >
> > > Junping
> > >
> > > Joe Evans  于2022年8月17日周三 22:41写道:
> > >
> > > > Hi Apache Incubator community,
> > > >
> > > > The Apache MXNet (incubating) community has discussed[1] graduating
> to
> > a
> > > > top level project and passed a community vote[2][3]. We have also
> > > > discussed[4] graduating in the Incubator community.
> > > >
> > > > In the incubator discussion, some branding issues[5] were brought up.
> > We
> > > > have fixed the issues[6] we were able to and discussed the others
> with
> > > > trademarks@. This work is ongoing. In addition, a few website
> > issues[7]
> > > > were brought up which were subsequently resolved[8].
> > > >
> > > > Based on the positive feedback from the incubator discussion, we
> would
> > like
> > > > to start a vote on graduating Apache MXNet (incubating) to a top
> level
> > > > project.
> > > >
> > > > Please cast your vote as one of the following options:
> > > >
> > > > [ ] +1 Yes, I support Apache MXNet (incubating) graduating from the
> > Apache
> > > > Incubator to a top level project.
> > > >
> > > > [ ] +0 No opinion.
> > > >
> > > > [ ] -1 No, the Apache MXNet (incubating) project is not ready to
> > graduate,
> > > > because ...
> > > >
> > > > This vote will remain open for at least 72 hours.
> > > >
> > > > Here is a brief overview of the progress of the Apache MXNet
> > (incubating)
> > > > project and community since entering the incubator:
> > > >
> > > > Community
> > > >
> > > >-
> > > >
> > > >38 new PPMC members were added, bringing the total number of PPMC
> > > >members to 51
> > > >-
> > > >
> > > >56 new committers were added (which include new PPMC members),
> > bringing
> > > >the total number of committers to 87
> > > >-
> > > >
> > > >The total number of contributors is now 870 and growing.
> > > >
> > > > Project
> > > >
> > > >-
> > > >
> > > >18 releases by 13 different release managers. All compliance
> issues
> > have
> > > >been resolved with the 1.9.0 and 2.0.beta releases.
> > > >-
> > > >
> > > >MXNet website is now compliant with Apache Project Website
> > requirements
> > > >-
> > > >
> > > >MXNet has completed the project maturity self assessment[9]
> > > >
> > > >
> > > > References:
> > > >
> > > > [1] https://lists.apache.org/thread/l9h2qgb2vqs2y0cm46wh83sgomr9w190
> > > >
> > > > [2] https://lists.apache.org/thread/py1nw6whov78sch5kkm1gcg7cv3zb2sv
> > > >
> > > > [3] https://lists.apache.org/thread/b8bngc6qcb33n0jo6m1rw0ylwlqzkmgx
> > > >
> > > > [4] https://lists.apache.org/thread/3rxzjcmo2y457y6r8ohz1j4qv49joyo6
> > > >
> > > > [5] https://lists.apache.org/thread/6brq4jg1x3hnt0sr3phboh2vwoo33db1
> > > >
> > > > [6] https://github.com/apache/incubator-mxnet/issues/21036
> > > >
> > > > [7] https://lists.apache.org/thread/j29jcv0zdkvx7vyy701qnfhnj09fzv8o
> > > >
> > > > [8] https://github.com/apache/incubator-mxnet/issues/21054
> > > >
> > > > [9]
> > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/MXNET/Apache+Maturity+Model+Assessment+for+MXNet
> > > >
> > > >
> > > > Here is the proposed resolution:
> > > >
> > > > —--
> > > >
> > > > Establish the Apache MXNet Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best interests
> of
> > > >
> > > > the Foundation and consistent with the Foundation's purpose to
> > establish
> > > >
> > > > a Project Management Committee charged with the creation and
> > maintenance
> > > >
> > > > of open-source software, for distribution at no charge to the public,
> > > >
> > > > related to a flexible and efficient library for Deep Learning.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > >
> > > > (PMC), to be known as the "Apache MXNet Project", be and hereby is
> > > >
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache MXNet Project be and hereby is responsible
> > for
> > > >
> > > > the creation and maintenance of software related to a flexible and
> > > >
> > > > efficient library for Deep Learning; and be it further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache MXNet" be and
> > > >
> > > > hereby is created, the person holding such office to serve at the
> > > >
> > > > direction of the Board of Directors as the chair of the Apache MXNet
> > > >
> > > > Project, and to have primary responsibility for management of the
> > > >
> > > > projects within the scope of 

Re: [DISCUSSION] Incubating Proposal of Uniffle

2022-05-25 Thread guo jiwei
+1 non-binding
Good luck


Regards
Jiwei Guo (Tboy)


On Wed, May 25, 2022 at 9:54 PM Zhankun Tang  wrote:

> +1 (Non-binding).
> Looking forward to see it grows a bigger community and possibly cover more
> scenarios like public cloud. :D
>
> BR,
> Zhankun
>
> Willem Jiang 于2022年5月25日 周三下午8:59写道:
>
> > +1 (binding).
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Wed, May 25, 2022 at 12:05 AM Jerry Shao  wrote:
> > >
> > > Hi all,
> > >
> > > Due to the name issue in thread (
> > > https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f), we
> > > figured out a new project name "Uniffle" and created a new Thread.
> Please
> > > help to discuss.
> > >
> > > We would like to propose Uniffle[1] as a new Apache incubator project,
> > you
> > > can find the proposal here [2] for more details.
> > >
> > > Uniffle is a high performance, general purpose Remote Shuffle Service
> for
> > > distributed compute engines like Apache Spark
> > > , Apache
> > > Hadoop MapReduce , Apache Flink
> > >  and so on. We are aiming to make
> Firestorm a
> > > universal shuffle service for distributed compute engines.
> > >
> > > Shuffle is the key part for a distributed compute engine to exchange
> the
> > > data between distributed tasks, the performance and stability of
> shuffle
> > > will directly affect the whole job. Current “local file pull-like
> shuffle
> > > style” has several limitations:
> > >
> > >1. Current shuffle is hard to support super large workloads,
> > especially
> > >in a high load environment, the major problem is IO problem (random
> > disk IO
> > >issue, network congestion and timeout).
> > >2. Current shuffle is hard to deploy on the disaggregated compute
> > >storage environment, as disk capacity is quite limited on compute
> > nodes.
> > >3. The constraint of storing shuffle data locally makes it hard to
> > scale
> > >elastically.
> > >
> > > Remote Shuffle Service is the key technology for enterprises to build
> big
> > > data platforms, to expand big data applications to disaggregated,
> > > online-offline hybrid environments, and to solve above problems.
> > >
> > > The implementation of Remote Shuffle Service -  “Uniffle”  - is heavily
> > > adopted in Tencent, and shows its advantages in production. Other
> > > enterprises also adopted or prepared to adopt Firestorm in their
> > > environments.
> > >
> > > Uniffle's key idea is brought from Salfish shuffle
> > > <
> >
> https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> > >,
> > > it has several key design goals:
> > >
> > >1. High performance. Firestorm’s performance is close enough to
> local
> > >file based shuffle style for small workloads. For large workloads,
> it
> > is
> > >far better than the current shuffle style.
> > >2. Fault tolerance. Firestorm provides high availability for
> > Coordinated
> > >nodes, and failover for Shuffle nodes.
> > >3. Pluggable. Firestorm is highly pluggable, which could be suited
> to
> > >different compute engines, different backend storages, and different
> > >wire-protocols.
> > >
> > > We believe that Uniffle project will provide the great value for the
> > > community if it is accepted by the Apache incubator.
> > >
> > > I will help this project as champion and many thanks to the 3 mentors:
> > >
> > >-
> > >
> > >Felix Cheung (felixche...@apache.org)
> > >- Junping du (junping...@apache.org)
> > >- Weiwei Yang (w...@apache.org)
> > >- Xun liu (liu...@apache.org)
> > >- Zhankun Tang (zt...@apache.org)
> > >
> > >
> > > [1] https://github.com/Tencent/Firestorm
> > > [2]
> > https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> > >
> > > Best regards,
> > > Jerry
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>


Re: [VOTE] Graduate Apache InLong(Incubating) as a TLP

2022-05-25 Thread guo jiwei
 added during incubating,
> they
> > > are
> > > > > > from
> > > > > > >
> > > > > > > 4 different organizations. All PPMCs and Committers are spread
> > > across 8
> > > > > > >
> > > > > > > different organizations [6].
> > > > > > >
> > > > > > >
> > > > > > > - 101 unique code developers [7].
> > > > > > >
> > > > > > >
> > > > > > > - Closed more than 2200 issues, with an average of 200 issues
> per
> > > > > version
> > > > > > >
> > > > > > > [8].
> > > > > > >
> > > > > > >
> > > > > > > - All the dependencies were reviewed and ensured they do not
> bring
> > > any
> > > > > > >
> > > > > > > license issues [9].
> > > > > > >
> > > > > > >
> > > > > > > - Evaluated the InLong project and self-checked the InLong
> maturity
> > > > > model
> > > > > > >
> > > > > > > [10] and the pre-graduation Check [11].
> > > > > > >
> > > > > > >
> > > > > > > - Well and Complete documentation for contributors and users
> [12].
> > > > > > >
> > > > > > >
> > > > > > > - Created channels like Email, Slack, Twitter, WeChat, and
> GitHub
> > > > > > >
> > > > > > > Discussions to communicate, with more than 650 subscribers.
> > > > > > >
> > > > > > >
> > > > > > > - Actively participated in or held more than 15 meetups to
> increase
> > > > > > >
> > > > > > > community influence.
> > > > > > >
> > > > > > >
> > > > > > > Please see the proposed board resolution below and let us know
> > > what you
> > > > > > >
> > > > > > > think. The initial PMC members were passed by the discussion
> and
> > > > > > invitation
> > > > > > >
> > > > > > > [13].
> > > > > > >
> > > > > > >
> > > > > > > [1]
> > > https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > > > >
> > > > > > > [2]
> > > https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > > > > >
> > > > > > > [3]
> > > https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > > > > >
> > > > > > > [4]
> > > https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > > > > > >
> > > > > > > [5] https://inlong.apache.org/download/main/
> > > > > > >
> > > > > > > [6] https://whimsy.apache.org/roster/ppmc/inlong
> > > > > > >
> > > > > > > [7]
> https://github.com/apache/incubator-inlong/graphs/contributors
> > > > > > >
> > > > > > > [8]
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > > > > >
> > > > > > > [9]
> > > https://github.com/apache/incubator-inlong/tree/master/licenses
> > > > > > >
> > > > > > > [10]
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > > > > >
> > > > > > > [11]
> > > > > > >
> > > > > > >
> > > > >
> > >
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > > > > > >
> > > > > > > [12] https://inlong.apache.org/docs/next/introduction
> > > > > > >
> > > > > > > [13]
> > > https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
> > > > > > >
> > > > > > &

Re: Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

2022-05-22 Thread guo jiwei
---
> > >
> > > Establish the Apache InLong Project
> > >
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > >
> > > the Foundation and consistent with the Foundation's purpose to
> establish
> > >
> > > a Project Management Committee charged with the creation and
> maintenance
> > >
> > > of open-source software, for distribution at no charge to the public,
> > >
> > > related to a one-stop data integration framework that provides
> > >
> > > automatic, secure, and reliable data transmission capabilities. InLong
> > >
> > > supports both batch and stream data processing at the same time, which
> > >
> > > offers great power to build data analysis, modeling, and other
> real-time
> > >
> > > applications based on streaming data.
> > >
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > >
> > > (PMC), to be known as the "Apache InLong Project", be and hereby is
> > >
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > >
> > > RESOLVED, that the Apache InLong Project be and hereby is responsible
> > >
> > > for the creation and maintenance of software related to a one-stop data
> > >
> > > integration framework that provides automatic, secure, and reliable
> data
> > >
> > > transmission capabilities. InLong supports both batch and stream data
> > >
> > > processing at the same time, which offers great power to build data
> > >
> > > analysis, modeling, and other real-time applications based on streaming
> > >
> > > data; and be it further
> > >
> > >
> > > RESOLVED, that the office of "Vice President, Apache InLong" be and
> > >
> > > hereby is created, the person holding such office to serve at the
> > >
> > > direction of the Board of Directors as the chair of the Apache InLong
> > >
> > > Project, and to have primary responsibility for management of the
> > >
> > > projects within the scope of responsibility of the Apache InLong
> > >
> > > Project; and be it further
> > >
> > >
> > > RESOLVED, that the persons listed immediately below be and hereby are
> > >
> > > appointed to serve as the initial members of the Apache InLong Project:
> > >
> > >
> > > * Aloys Zhang 
> > >
> > > * Charles Zhang 
> > >
> > > * Guangxu Cheng 
> > >
> > > * Guocheng Zhang 
> > >
> > > * Heal Chow 
> > >
> > > * Jean-Baptiste Onofré 
> > >
> > > * Jerry Shao 
> > >
> > > * Junjie Chen 
> > >
> > > * Junping Du 
> > >
> > > * Justin Mclean 
> > >
> > > * Lamber Liu 
> > >
> > > * Osgoo Li 
> > >
> > > * Peng Chen 
> > >
> > > * Zak Wu 
> > >
> > > * ZhongBo Wu 
> > >
> > > * Zili Chen 
> > >
> > > * Daniel Li 
> > >
> > > * Guo Jiwei 
> > >
> > > * Haiji Li 
> > >
> > > * Lizhen 
> > >
> > > * Yuanbo Liu 
> > >
> > > * Yuanhao Ji 
> > >
> > > * Zijie Lu 
> > >
> > > * Zirui Peng 
> > >
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Charles Zhang be appointed
> > >
> > > to the office of Vice President, Apache InLong, to serve in accordance
> > >
> > > with and subject to the direction of the Board of Directors and the
> > >
> > > Bylaws of the Foundation until death, resignation, retirement, removal
> > >
> > > or disqualification, or until a successor is appointed; and be it
> > >
> > > further
> > >
> > >
> > > RESOLVED, that the Apache InLong Project be and hereby is tasked with
> > >
> > > the migration and rationalization of the Apache Incubator InLong
> > >
> > > podling; and be it further
> > >
> > >
> > > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > >
> > > InLong podling encumbered upon the Apache Incubator PMC are hereafter
> > >
> > > discharged.
> > >
> > >
> > >
> > > --
> > > Best wishes,
> > > Charles Zhang
> > >
> >
> >
>


Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

2020-08-18 Thread guo jiwei
+1 (non-binding)

Regards
Jiwei Guo (Tboy)


On Wed, Aug 19, 2020 at 12:33 PM Ovilia  wrote:

> FYI.
> Apache ECharts (incubating) is running a community graduation vote now.
>
> Thanks
>
> *Ovilia*
>
> Forwarded Conversation
> Subject: [VOTE] Graduate Apache ECharts (incubating) as a top level project
> 
>
> From: Ovilia 
> Date: Mon, Aug 17, 2020 at 11:36 AM
> To: dev 
>
>
> Hi all,
>
> Hello all,
> After our discussion about readiness for graduation to TLP on the dev
> mailing list [8], I would like to call a VOTE for Apache ECharts graduating
> as a top level project.
>
> If this vote passes, the next step would be to submit the resolution below
> to the Incubator PMC, who would vote on sending it on to the Apache Board.
>
> Vote:
> [ ] +1 - Recommend graduation of Apache ECharts as a TLP
> [ ]  0 - I don't feel strongly about it, but don't object
> [ ] -1 - Do not recommend graduation of Apache ECharts because...
>
> The VOTE will open for at least 72 hours.
>
> -
>
> X. Establish the Apache ECharts Project
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to
> the public, related to a charting and data visualization
> library written in JavaScript.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache ECharts Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache ECharts Project be and hereby is
> responsible for the creation and maintenance of software
> related to a charting and data visualization
> library written in JavaScript; and be it further
>
> RESOLVED, that the office of "Vice President, Apache ECharts" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache ECharts Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache ECharts Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache ECharts Project:
>
> * Houjin Huang  
> * Deqing Li 
> * Dong Rui  
> * Kener Linfeng 
> * Kevin A. McGrail  
> * Wenli Zhang   
> * Shen Yi   
> * Shuang Su 
> * Siwen Su  
> * Junting Wang  
> * Zhongxiang Wang   
> * Dave Fisher   
> * Sheng Wu  
> * Zak Wu
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
> be appointed to the office of Vice President, Apache ECharts, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache ECharts PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache ECharts Project; and be it further
>
> RESOLVED, that the Apache ECharts Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator ECharts podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator ECharts podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
>
> -
>
> More information:
>
> - Assessment of the maturity model is available at [5].
> - A checklist of graduation is available at [6].
> - 3 new PPMCs and 6 new committers were elected and joined the community
> [1]
> since incubation and now we have committers working for more than 6
> different
> companies.
> - Our mailing list [2] is very active and we have 81 people subscribed to
> it.
> - Released 8 versions by 3 release managers [3] (and another version by
> another release manager is under voting stage); release guide is at [4].
> - 73 people have contributed to the project during incubation [10].
> - Branding issues have been solved and name searching has been completed
> [7].
> - Website [9] has been updated to meet up with Apache regulations.
>
> -
>
>
> [1] https://echarts.apache.org/en/committers.html
> [2] https://lists.apache.org/list.html?d...@echarts.apache.org
> [3] https://dist.apache.org/repos/dist/release/incubator/echarts/
> [4]
>
> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+ECharts+Release+Guide
> [5]
>
> 

Re: [VOTE] Graduate Apache APISIX (incubating) as a TLP

2020-06-16 Thread guo jiwei
+1 (non-binding)
Good luck


Regards
Jiwei Guo (Tboy)


On Wed, Jun 17, 2020 at 10:47 AM Juan Pan  wrote:

> Good luck, +1 non-binding
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere
> E-mail: panj...@apache.org
>
>
>
>
> On 06/16/2020 17:22,Ming Wen wrote:
> Hello all,
>
> We've got positive feedback on the DISCUSS thread, I'd like to start
> an official VOTE thread now.
>
> Please vote on the resolution pasted below to graduate Apache APISIX from
> the
> incubator to a Top Level Project.
>
> [ ] +1 Graduate Apache APISIX from the Incubator.
> [ ] +0
> [ ] -1 Don't graduate Apache APISIX from the Incubator because ...
>
> This vote will open for at least 72 hours.
> ---
>
> Establish the Apache APISIX Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to Apache APISIX is a cloud-native microservices API gateway,
> delivering the ultimate performance, security and scalable platform
> for APIs and microservices...
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache APISIX Project", be and hereby
> is established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache APISIX Project be and hereby is
> responsible for the creation and maintenance of software related to
> Apache APISIX is a cloud-native microservices API gateway,
> delivering the ultimate performance, security and scalable platform
> for APIs and microservices; and be it further
>
> RESOLVED, that the office of "Vice President, Apache APISIX" be
> and hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the ApacheAPISIX
> Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of the
> Apache APISIX Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache APISIX Project:
> * agile6v 
> * Ayeshmantha Perera  
> * Jarvis.Qiu 
> * jinwei 
> * junxu chen 
> * Justin Mclean 
> * Kevin Ratnasekera 
> * Lang Wang 
> * liling 
> * linsir 
> * Ming Wen 
> * Nirojan Selvanathan 
> * sheng wu 
> * spacewander 
> * Von Gosling  
> * Willem Ning Jiang 
> * yousa 
> * YuanSheng Wang 
> * Zhiyuan Ju  
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ming Wen be appointed to
> the office of Vice President, Apache APISIX, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache APISIX Project be and hereby is tasked
> with the migration and rationalization of the Apache IncubatorAPISIX
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> IncubatorAPISIX podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
> ---
>
> Thanks,
> Ming Wen, Apache APISIX & Apache SkyWalking
> Twitter: _WenMing
>


Re: [ANNOUNCE] Release Apache TubeMQ(incubating) 0.3.0-incubating

2020-06-07 Thread guo jiwei
Good news !!!

Regards
Jiwei Guo (Tboy)


On Mon, Jun 8, 2020 at 12:50 PM Guangxu Cheng  wrote:

> Hi all,
>
> The Apache TubeMQ community is pleased to announce that
> Apache TubeMQ 0.3.0-incubating has been released!
>
> Apache TubeMQ is a trillion-records-scale distributed messaging queue (MQ)
> system,
> focuses on data transmission and storage under massive data.
>
> Download Links:
> https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/
>
> Release Notes:
> https://github.com/apache/incubator-tubemq/blob/release-0.3.0/CHANGES.md
>
> Website: https://tubemq.apache.org/
>
> TubeMQ Resources:
> - Issue: https://issues.apache.org/jira/projects/TUBEMQ/issues
> - Mailing list: d...@tubemq.apache.org
>
> Thanks
> On behalf of Apache TubeMQ (incubating) community
> -
> Best Regards,
> Guangxu
>