Re: [VOTE] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[Eason Chen]

+1(non-binding)

Enrico Olivelli  于 2024年1月8日周一 下午10:19写道：

> +1
>
> Enrico
>
> Il giorno lun 8 gen 2024 alle ore 14:59 张铎(Duo Zhang)
>  ha scritto:
> >
> > +1 (binding)
> >
> > Good luck!
> >
> > Huajie Wang  于2024年1月8日周一 19:02写道：
> > >
> > > +1 non-binding
> > >
> > >
> > > Best,
> > > Huajie Wang
> > >
> > >
> > >
> > > PJ Fanning  于2024年1月8日周一 17:45写道：
> > >
> > > > +1 (binding)
> > > >
> > > > I think the various issues that have been raised on this thread are
> > > > already addressed or can be addressed soon. The project seems ready
> to
> > > > graduate.
> > > >
> > > > Best of Luck.
> > > >
> > > > On 2024/01/08 04:53:49 Xiaoqiao He wrote:
> > > > > +1(binding).  Good luck!
> > > > >
> > > > > Best Regards,
> > > > > - He Xiaoqiao
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Jan 8, 2024 at 12:51 AM sebb  wrote:
> > > > >
> > > > > > On Sun, 7 Jan 2024 at 10:04, tison  wrote:
> > > > > > >
> > > > > > > Hi sebb,
> > > > > > >
> > > > > > > Thanks for your suggestion :D
> > > > > > >
> > > > > > > Would you provide some examples (perhaps from TLPs) for a
> proper
> > > > > > description?
> > > > > > >
> > > > > > > Also, this doesn't seem to be a blocker for graduation. So if
> it
> > > > takes
> > > > > > > a few conversations to polish, you may create an issue on [1]
> or
> > > > email
> > > > > > > to dev@opendal.a.o.
> > > > > >
> > > > > > I agree that it is not a blocker for graduation.
> > > > > >
> > > > > > It is merely unnecessary work for your users.
> > > > > >
> > > > > > "When downloading a release, please verify the OpenPGP compatible
> > > > > > signature (or failing that, check the SHA-512); these should be
> > > > > > fetched from the main Apache site."
> > > > > >
> > > > > > > Best,
> > > > > > > tison.
> > > > > > >
> > > > > > > [1] https://github.com/apache/incubator-opendal/issues/
> > > > > > >
> > > > > > > sebb  于2024年1月7日周日 17:11写道：
> > > > > > > >
> > > > > > > > Thanks, that looks fine.
> > > > > > > >
> > > > > > > > I just noticed that the text regarding the use of hashes and
> sigs
> > > > is
> > > > > > > > not quite correct.
> > > > > > > > There is no point checking both the hash and the sig.
> > > > > > > > Ideally check the sig, failing that check the hash.
> > > > > > > >
> > > > > > > > On Sun, 7 Jan 2024 at 02:58, Xuanwo 
> wrote:
> > > > > > > > >
> > > > > > > > > > There is a problem with the download page links; they do
> not
> > > > agree
> > > > > > > > > > with Infra rules [1]
> > > > > > > > >
> > > > > > > > > Hi, sebb
> > > > > > > > >
> > > > > > > > > Thank you for bringing this to our attention. We have
> resolved
> > > > all
> > > > > > issues
> > > > > > > > > with the links on the download page. It should now be fully
> > > > > > compliant with
> > > > > > > > > INFRA rules. Please take another look.
> > > > > > > > >
> > > > > > > > > On Sat, Jan 6, 2024, at 23:50, sebb wrote:
> > > > > > > > > > There is a problem with the download page links; they do
> not
> > > > agree
> > > > > > > > > > with Infra rules [1]
> > > > > > > > > >
> > > > > > > > > > Artifact links must use closer.lua
> > > > > > > > > > Hashes and sigs must use https://downloads.apache.org/
> > > > > > > > > >
> > > > > > > > > > Also Releases which are not currently maintained should
> be
> > > > dropped
> > > > > > [2]
> > > > > > > > > >
> > > > > > > > > > The KEYS file is correctly linked.
> > > > > > > > > >
> > > > > > > > > > [1]
> > > > > >
> https://infra.apache.org/release-download-pages.html#download-page
> > > > > > > > > > [2]
> > > > > > > > > >
> > > > > >
> > > >
> https://infra.apache.org/release-download-pages.html#current-and-older-releases
> > > > > > > > > >
> > > > > > > > > > Sebb
> > > > > > > > > > On Sat, 6 Jan 2024 at 15:45, Craig Russell <
> > > > apache@gmail.com>
> > > > > > wrote:
> > > > > > > > > >>
> > > > > > > > > >> +1 binding
> > > > > > > > > >>
> > > > > > > > > >> Good Luck,
> > > > > > > > > >> Craig
> > > > > > > > > >>
> > > > > > > > > >> > On Dec 28, 2023, at 16:21, Xuanwo 
> > > > wrote:
> > > > > > > > > >> >
> > > > > > > > > >> > Hello all,
> > > > > > > > > >> >
> > > > > > > > > >> > We've got positive feedback on the DISCUSS thread[1],
> I'd
> > > > like
> > > > > > to start an
> > > > > > > > > >> > official VOTE thread now.
> > > > > > > > > >> >
> > > > > > > > > >> > Below are some facts and project highlights from the
> > > > incubation
> > > > > > phase
> > > > > > > > > >> > as well as the draft resolution:
> > > > > > > > > >> >
> > > > > > > > > >> > - Currently, our community consists of 19 committers,
> > > > including
> > > > > > mentors,
> > > > > > > > > >> >  with 12 serving as PPMC members.
> > > > > > > > > >> > - At present, we boast 164 contributors.
> > > > > > > > > >> > - Throughout the incubation period, we've made 9
> > > > > > releases—averaging at
> > > > > > > > > >> >  least one per month.
> > > > > > > > > >> > - We've had 7 different release managers to date.
> > > > > > > > > >> > - 

Re: [VOTE] Accept Fury Into the ASF Incubator

[Eason Chen]

+1 (non-binding)

Eason Chen

On Mon, Dec 11, 2023 at 6:18 PM Yu Xiao  wrote:
>
> +1 binding
>
> Best wishes!
>
> Felix Cheung  于2023年12月11日周一 05:45写道：
> >
> > +1 binding
> >
> > On Sat, Dec 9, 2023 at 11:05 PM Ayush Saxena  wrote:
> >
> > > +1(Binding)
> > >
> > > -Ayush
> > >
> > > > On 10-Dec-2023, at 12:10 PM, zhongyi tan  wrote:
> > > >
> > > > +1 （binding）
> > > >
> > > >> On Fri, Dec 8, 2023 at 7:05 PM tison  wrote:
> > > >>
> > > >> Hi Incubator
> > > >>
> > > >> Following the discussion [DISCUSS] Incubating Proposal of Fury [1], I
> > > >> am starting this official vote for the Fury project.
> > > >>
> > > >> Here is their proposal:
> > > >> https://cwiki.apache.org/confluence/display/INCUBATOR/Fury+Proposal
> > > >>
> > > >> Please cast your vote:
> > > >>
> > > >> [ ] +1, bring into the Incubator
> > > >> [ ] +0, I don't care either way
> > > >> [ ] -1, do not bring Fury into the Incubator, because...
> > > >>
> > > >> The vote will open for one week from today, Dec. 8th, 2023
> > > >>
> > > >> Best,
> > > >> tison.
> > > >>
> > > >> [1] https://lists.apache.org/thread/jr3qwzxg2m6507zsll5fs8mopcco3ny3
> > > >>
> > > >> -
> > > >> 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
> > >
> > >
>
> -
> 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 Seata Into the ASF Incubator

[Eason Chen]

+1 (non-binding)

Good luck!

On Mon, Oct 23, 2023 at 11:24 AM Xin Wang  wrote:
>
> +1 (non-binding)
>
> Good luck!
>
> Xin Wang
>
> Jialin Qiao  于2023年10月23日周一 09:42写道：
>
> > +1, Good luck!
> > —
> > Jialin Qiao
> > Apache IoTDB PMC
> >
> > Huxing Zhang  于2023年10月23日周一 09:39写道：
> > >
> > > +1 (binding)
> > >
> > > Good luck!
> > >
> > > On Sat, Oct 21, 2023 at 8:51 PM Sheng Wu 
> > wrote:
> > > >
> > > > Hi Incubator
> > > >
> > > > Following the discussion from <[DISCUSS] Incubating Proposal of
> > Seata>[1],
> > > > I am starting this official vote for the Seata project.
> > > >
> > > > Here is their proposal,
> > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal
> > > >
> > > > Please cast your vote:
> > > >
> > > > [ ] +1, bring into the Incubator
> > > > [ ] +0, I don't care either way
> > > > [ ] -1, do not bring Seata into the Incubator, because...
> > > >
> > > > The vote will open for one week from today, Oct. 21st, 2023
> > > >
> > > > [1] https://lists.apache.org/thread/jtg7tt725r9mf35gqxph65vz8gdbwq94
> > > >
> > > >
> > > > Sheng Wu 吴晟
> > > > Twitter, wusheng1108
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > >
> > > --
> > > Best Regards！
> > > Huxing
> > >
> > > -
> > > 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
> >
> >

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

Re: Re:[VOTE] Accept Answer into the Apache Incubator

[Eason Chen]

+1

On Sat, Oct 7, 2023 at 9:34 AM Yu Xiao  wrote:
>
> + 1 (binding)
>
> Best wishes!
>
>
> KimmKing  于2023年10月5日周四 14:59写道：
> >
> > There will be some preferred names for discussion or not? My Suggestion is 
> > OpenAnswer/Openswer.
> >
> >
> >
> >
> > --
> >
> > Kimm King(kimmk...@apache.org/kimmk...@163.com)
> > Apache Dubbo PMC Member
> > github: kimmking
> >
> >
> >
> >
> >
> > At 2023-10-05 14:55:27, "KimmKing"  wrote:
> > >+1， nobinding
> > >
> > >
> > >
> > >
> > >--
> > >
> > >Kimm King(kimmk...@apache.org/kimmk...@163.com)
> > >Apache Dubbo PMC Member
> > >github: kimmking
> > >
> > >
> > >
> > >
> > >
> > >At 2023-10-03 08:17:16, "Willem Jiang"  wrote:
> > >>Following up the [DISCUSS] thread on Answer [1] I would like to call a
> > >>VOTE to accept into the Apache Incubator.
> > >>
> > >>Answer is a question-and-answer (Q) platform software for teams at
> > >>any scale to build a help center, knowledge base, community forum,
> > >>etc.
> > >>
> > >>Please cast your vote:
> > >>
> > >>  [ ] +1, bring into the Incubator
> > >>  [ ] +0, I don't care either way
> > >>  [ ] -1, do not bring Answer 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.
> > >>
> > >>Please check out the Answer Proposal from the incubator wiki[2].
> > >>
> > >>[1]https://lists.apache.org/thread/42tvz3rqfy4w5poqgslh71sm1o1td7zn
> > >>[2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal
> > >>
> > >>Best Regards,
> > >>
> > >>Willem Jiang
> > >>
> > >>Twitter: willemjiang
> > >>Weibo: 姜宁willem
> > >>
> > >>-
> > >>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
>

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

Re: [VOTE] Accept OpenDAL into the Apache Incubator

[Eason Chen]

+1 non-binding

Good Luck!

Eason Chen
Apache EventMesh

On Fri, Feb 24, 2023 at 1:21 PM Furkan KAMACI  wrote:
>
> Hi,
>
> +1 (binding)
>
> Kind regards,
> Furkan Kamaci
>
> On Thu, Feb 23, 2023 at 2:47 PM Yu Xiao  wrote:
>
> > +1 non-binding
> >
> > Best wishes!
> >
> > Yu Xiao
> > Apache ShenYu
> >
> > Charles Zhang  于2023年2月23日周四 18:33写道：
> > >
> > > +1 (non-binding)
> > > Good luck.
> > >
> > > Best wishes,
> > > Charles Zhang
> > > from Apache InLong
> > >
> > >
> > > Kaijie Chen  于2023年2月23日周四 17:56写道：
> > >
> > > > +1 (non-binding)
> > > > Good luck.
> > > >
> > > > Kaijie
> > > >
> > > > On 2023/02/23 07:47:24 Enrico Olivelli wrote:
> > > > > +1 (non binding)
> > > > >
> > > > > In the future maybe this project may add some java bindings and work
> > as a
> > > > > replacement for the retiring JClouds project
> > > > >
> > > > > Enrico
> > > > >
> > > > > Il Gio 23 Feb 2023, 06:14 li gang  ha scritto:
> > > > >
> > > > > > +1 (binding)
> > > > > > Good luck.
> > > > > >
> > > > > > tison  于2023年2月21日周二 21:24写道：
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Following up on the [DISCUSS] thread on OpenDAL[1], I would like
> > to
> > > > call
> > > > > > a
> > > > > > > VOTE to accept OpenDAL into the Apache Incubator, please check
> > out
> > > > the
> > > > > > > OpenDAL Proposal from the incubator wiki[2].
> > > > > > >
> > > > > > > Please cast your vote:
> > > > > > >
> > > > > > > [ ] +1, bring OpenDAL into the Incubator
> > > > > > > [ ] +0, I don't care either way
> > > > > > > [ ] -1, do not bring OpenDAL into the Incubator, because...
> > > > > > >
> > > > > > > The vote will open at least for 72 hours, and only votes from the
> > > > > > Incubator
> > > > > > > PMC members are binding, but votes from everyone are welcome.
> > > > > > >
> > > > > > > [1]
> > https://lists.apache.org/thread/px7wjcjy3rd4s59d4d3ll1x6y11d240r
> > > > > > > [2]
> > > > > >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal
> > > > > > >
> > > > > > > Best,
> > > > > > > tison.
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best Regards
> > > > > >
> > > > > > DolphinScheduler PMC
> > > > > > Gang Li 李岗
> > > > > >
> > > > > > lgcar...@apache.org
> > > > > >
> > > > >
> > > >
> > > > -
> > > > 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
> >
> >

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

[RESULT][VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

Dear Apache Incubator Community and IPMC members,
The vote for graduating Apache EventMesh(incubating) to a TLP[1] has
passed. There are 8 binding +1 votes, 41 non-binding +1 votes, and no
+0 or -1 votes.

+1 Binding (8)
PJ Fanning
Willem Jiang
Jerry Tan
li gang
fpapon
vongosling
Jean-Baptiste Onofré
Junping Du

+1 Non-binding (41)
mikexue
Mengyang Tang
majorhe
vnbear
wqliang
Yu Xiao
Carl Gan
jay Taylor
walleliu
nicolchen
Kaifeng Liu
Jon Yang
Yongshe Feng
Wentong Shi
YuanXin Hu
Wei Liu
Jianbo Mai
walterzywei
chenzhou
ShanPeng Qing
Pengcheng Ma
heng du
Xiaoyang Liu
ShannonDing
wenjun
Zhang Yonglun
Huajie Wang
Huimin Li
sanchen
bingyan
xiong mengfei
Xin Wang
Qiang Yin
Alex Luo
Xiaoshuang Li
Mark Li
Jialin Sun
Ronghua Liang
Shuai Di
Eason Chen
Jaskey Lam

+0: none

-1: none

Thanks all for participating in the vote. Thanks to the Incubator, the
EventMesh community, our mentors, and everyone who helped throughout
the journey. We will proceed and submit the graduation proposal to the
ASF board.

Best regards,
Eason Chen

[1] https://lists.apache.org/thread/z7rgf0qxyr53wgp9cgfgthl96qwjpr10

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

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

With my +1, As an Event First Fully Serverless Platform, EventMesh is
becoming better and better, good luck!

On Wed, Feb 15, 2023 at 9:50 AM 俊平堵  wrote:
>
> I believe EventMesh is good to go!
> +1. Binding.
>
> Thanks,
>
> Junping
>
> Eason Chen  于2023年2月10日周五 10:32写道：
>
> > Dear Apache Incubator Community and IPMC members,
> >
> > After having the graduation discussion in the EventMesh community [1],
> > we passed the vote within the EventMesh community [2] and the vote
> > result was published[3].
> > We then discussed the graduation for EventMesh in the Apache Incubator
> > Community [4], where no issues were raised and positive replies were
> > received.
> >
> > I would like to start this voting thread to request graduating Apache
> > EventMesh(incubating) from Apache Incubator as a Top Level Project.
> >
> > Please provide your vote accordingly:
> > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > Apache Incubator.
> > [ ] +0 No opinion.
> > [ ] -1 No, the EventMesh project is not ready to graduate, because...
> >
> > Thank you for participating in the vote. This vote will stay open for
> > at least 72 hours.
> >
> > Here is an overview of the Apache EventMesh(incubating) to help with the
> > vote.
> >
> > *Community*
> >
> > ● 5 new PPMC members were added, bringing the total number of PPMC
> > members to 14 from at least 9 different organizations.
> > ● 20 new Committers were added, bringing the total number of
> > committers to 42 from at least 30 different organizations.
> > ● 220+ new contributors participate in the community. The number of
> > contributors is now 250+ and growing.
> > ● 20 Bi-weekly online meetings were held among the committers,
> > contributors, and users. The meeting minutes are recorded on the
> > mailing list[5] and cwiki [6].
> > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > ● We've confirmed the VP, PMC, and Committers in the preparation
> > discussion at private@eventmesh [7]. Eason
> > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> >
> > *Project*
> >
> > ● Apache EventMesh(incubating) builds a fully serverless platform for
> > distributed event-driven applications.
> > ● Project maturity model is detailed in [8].
> > ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> > ● EventMesh community released a total of 7 Apache releases [10] by 6
> > different release managers from 5 different organizations.
> > ● 1300+ issues created, and 1100+ issues closed [11].
> > ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > 2500+ commits added.
> > ● The release cadence is about 3 months, with an average of 180+
> > issues and 230+ pull requests per release.
> > ● Please refer to the EventMesh project incubation status [13][14] for
> > more information.
> >
> > *Brands, License, and Copyright*
> >
> > ● We applied the brand [15], which has been reviewed and approved.
> > ● EventMesh community maintains project code on GitHub and all modules
> > code is under Apache 2.0 license. We have reviewed all the
> > dependencies and ensured they do not bring any license issues [16].
> > All the status files, license headers, and copyright are up to date.
> > ● EventMesh official website [17] is compliant with Apache Foundation
> > requirements[18].
> >
> > -
> > BEGINNING OF DRAFT RESOLUTION
> > -
> >
> > Establish the Apache EventMesh 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 fully serverless platform used to build distributed
> > event-driven applications.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> > for the creation and maintenance of software related to a fully
> > serverless platform used to build distributed event-driven applications;
> > and be it further
> >
> &g

[VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

Dear Apache Incubator Community and IPMC members,

After having the graduation discussion in the EventMesh community [1],
we passed the vote within the EventMesh community [2] and the vote
result was published[3].
We then discussed the graduation for EventMesh in the Apache Incubator
Community [4], where no issues were raised and positive replies were
received.

I would like to start this voting thread to request graduating Apache
EventMesh(incubating) from Apache Incubator as a Top Level Project.

Please provide your vote accordingly:
[ ] +1 Yes, I support the EventMesh project to graduate from the
Apache Incubator.
[ ] +0 No opinion.
[ ] -1 No, the EventMesh project is not ready to graduate, because...

Thank you for participating in the vote. This vote will stay open for
at least 72 hours.

Here is an overview of the Apache EventMesh(incubating) to help with the vote.

*Community*

● 5 new PPMC members were added, bringing the total number of PPMC
members to 14 from at least 9 different organizations.
● 20 new Committers were added, bringing the total number of
committers to 42 from at least 30 different organizations.
● 220+ new contributors participate in the community. The number of
contributors is now 250+ and growing.
● 20 Bi-weekly online meetings were held among the committers,
contributors, and users. The meeting minutes are recorded on the
mailing list[5] and cwiki [6].
● The dev@eventmesh mailing list currently has 117 subscribers.
● We've confirmed the VP, PMC, and Committers in the preparation
discussion at private@eventmesh [7]. Eason
Chen(chenguangsh...@apache.org) was recommended as Vice President.

*Project*

● Apache EventMesh(incubating) builds a fully serverless platform for
distributed event-driven applications.
● Project maturity model is detailed in [8].
● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
● EventMesh community released a total of 7 Apache releases [10] by 6
different release managers from 5 different organizations.
● 1300+ issues created, and 1100+ issues closed [11].
● 1600+ pull requests created, and 1600+ pull requests closed [12],
2500+ commits added.
● The release cadence is about 3 months, with an average of 180+
issues and 230+ pull requests per release.
● Please refer to the EventMesh project incubation status [13][14] for
more information.

*Brands, License, and Copyright*

● We applied the brand [15], which has been reviewed and approved.
● EventMesh community maintains project code on GitHub and all modules
code is under Apache 2.0 license. We have reviewed all the
dependencies and ensured they do not bring any license issues [16].
All the status files, license headers, and copyright are up to date.
● EventMesh official website [17] is compliant with Apache Foundation
requirements[18].

-
BEGINNING OF DRAFT RESOLUTION
-

Establish the Apache EventMesh 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 fully serverless platform used to build distributed
event-driven applications.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache EventMesh Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache EventMesh Project be and hereby is responsible
for the creation and maintenance of software related to a fully
serverless platform used to build distributed event-driven applications;
and be it further

RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache EventMesh
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 EventMesh
Project:

 * Alex Luo 
 * Du Heng      
 * Eason Chen   
 * Francois Papon   
 * Jean-Baptiste Onofré 
 * Junping Du   
 * Justin Mclean
 * ShannonDing  
 * Von Gosling  
 * Weiqiang Liang   
 * Wenjun Ruan  
 * XiaoShuang Li
 * Xue Weiming  
 * Yuwei Zhu

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eason Chen be appointed to
the office of Vice President, Apache EventMesh, 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 disqua

[CANCEL][VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

Dear Apache Incubator Community and IPMC members,

I need to cancel this vote and fix the description in the DRAFT
RESOLUTION, another vote will be called later, thank you for your
understanding.

Best Regards
Eason Chen

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

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

Sure, I will fix it and cancel this vote.

On Fri, Feb 10, 2023 at 1:26 AM sebb  wrote:
>
> On Thu, 9 Feb 2023 at 12:21, Eason Chen  wrote:
> >
> > Dear Apache Incubator Community and IPMC members,
> >
> > After having the graduation discussion in the EventMesh community [1],
> > we passed the vote within the EventMesh community [2] and the vote
> > result was published[3].
> > We then discussed the graduation for EventMesh in the Apache Incubator
> > Community [4], where no issues were raised and positive replies were
> > received.
> >
> > I would like to start this voting thread to request graduating Apache
> > EventMesh(incubating) from Apache Incubator as a Top Level Project.
> >
> > Please provide your vote accordingly:
> > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > Apache Incubator.
> > [ ] +0 No opinion.
> > [ ] -1 No, the EventMesh project is not ready to graduate, because...
> >
> > Thank you for participating in the vote. This vote will stay open for
> > at least 72 hours.
> >
> > Here is an overview of the Apache EventMesh(incubating) to help with the 
> > vote.
> >
> > *Community*
> >
> > ● 5 new PPMC members were added, bringing the total number of PPMC
> > members to 14 from at least 9 different organizations.
> > ● 20 new Committers were added, bringing the total number of
> > committers to 42 from at least 30 different organizations.
> > ● 220+ new contributors participate in the community. The number of
> > contributors is now 250+ and growing.
> > ● 20 Bi-weekly online meetings were held among the committers,
> > contributors, and users. The meeting minutes are recorded on the
> > mailing list[5] and cwiki [6].
> > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > ● We've confirmed the VP, PMC, and Committers in the preparation
> > discussion at private@eventmesh [7]. Eason
> > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> >
> > *Project*
> >
> > ● Apache EventMesh(incubating) is a fully serverless platform used to
> > build distributed event-driven applications.
> > ● Project maturity model is detailed in [8].
> > ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> > ● EventMesh community released a total of 7 Apache releases [10] by 6
> > different release managers from 5 different organizations.
> > ● 1300+ issues created, and 1100+ issues closed [11].
> > ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > 2500+ commits added.
> > ● The release cadence is about 3 months, with an average of 180+
> > issues and 230+ pull requests per release.
> > ● Please refer to the EventMesh project incubation status [13][14] for
> > more information.
> >
> > *Brands, License, and Copyright*
> >
> > ● We applied the brand [15], which has been reviewed and approved.
> > ● EventMesh community maintains project code on GitHub and all modules
> > code is under Apache 2.0 license. We have reviewed all the
> > dependencies and ensured they do not bring any license issues [16].
> > All the status files, license headers, and copyright are up to date.
> > ● EventMesh official website [17] is compliant with Apache Foundation
> > requirements[18].
> >
> > -
> > BEGINNING OF DRAFT RESOLUTION
> > -
> >
> > Establish the Apache EventMesh 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 fully serverless platform used to build distributed
> > event-driven applications.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> > for the creation and maintenance of software related to EventMesh is a
> > fully serverless platform used to build distributed event-driven
> > applications; and be it further
>
> The above sentence does not make sense; need to drop ' EventMesh is'
>
> > RESOLVED, that the office of "Vice 

[VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

Dear Apache Incubator Community and IPMC members,

After having the graduation discussion in the EventMesh community [1],
we passed the vote within the EventMesh community [2] and the vote
result was published[3].
We then discussed the graduation for EventMesh in the Apache Incubator
Community [4], where no issues were raised and positive replies were
received.

I would like to start this voting thread to request graduating Apache
EventMesh(incubating) from Apache Incubator as a Top Level Project.

Please provide your vote accordingly:
[ ] +1 Yes, I support the EventMesh project to graduate from the
Apache Incubator.
[ ] +0 No opinion.
[ ] -1 No, the EventMesh project is not ready to graduate, because...

Thank you for participating in the vote. This vote will stay open for
at least 72 hours.

Here is an overview of the Apache EventMesh(incubating) to help with the vote.

*Community*

● 5 new PPMC members were added, bringing the total number of PPMC
members to 14 from at least 9 different organizations.
● 20 new Committers were added, bringing the total number of
committers to 42 from at least 30 different organizations.
● 220+ new contributors participate in the community. The number of
contributors is now 250+ and growing.
● 20 Bi-weekly online meetings were held among the committers,
contributors, and users. The meeting minutes are recorded on the
mailing list[5] and cwiki [6].
● The dev@eventmesh mailing list currently has 117 subscribers.
● We've confirmed the VP, PMC, and Committers in the preparation
discussion at private@eventmesh [7]. Eason
Chen(chenguangsh...@apache.org) was recommended as Vice President.

*Project*

● Apache EventMesh(incubating) is a fully serverless platform used to
build distributed event-driven applications.
● Project maturity model is detailed in [8].
● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
● EventMesh community released a total of 7 Apache releases [10] by 6
different release managers from 5 different organizations.
● 1300+ issues created, and 1100+ issues closed [11].
● 1600+ pull requests created, and 1600+ pull requests closed [12],
2500+ commits added.
● The release cadence is about 3 months, with an average of 180+
issues and 230+ pull requests per release.
● Please refer to the EventMesh project incubation status [13][14] for
more information.

*Brands, License, and Copyright*

● We applied the brand [15], which has been reviewed and approved.
● EventMesh community maintains project code on GitHub and all modules
code is under Apache 2.0 license. We have reviewed all the
dependencies and ensured they do not bring any license issues [16].
All the status files, license headers, and copyright are up to date.
● EventMesh official website [17] is compliant with Apache Foundation
requirements[18].

-
BEGINNING OF DRAFT RESOLUTION
-

Establish the Apache EventMesh 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 fully serverless platform used to build distributed
event-driven applications.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache EventMesh Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache EventMesh Project be and hereby is responsible
for the creation and maintenance of software related to EventMesh is a
fully serverless platform used to build distributed event-driven
applications; and be it further

RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache EventMesh
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 EventMesh
Project:

 * Alex Luo 
 * Du Heng      
 * Eason Chen   
 * Francois Papon   
 * Jean-Baptiste Onofré 
 * Junping Du   
 * Justin Mclean
 * ShannonDing  
 * Von Gosling  
 * Weiqiang Liang   
 * Wenjun Ruan  
 * XiaoShuang Li
 * Xue Weiming  
 * Yuwei Zhu

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eason Chen be appointed
to the office of Vice President, Apache EventMesh, 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

[CANCEL][VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

Hi, Apache Incubator Community and IPMC members

I need to cancel this vote due to not proper description in DRAFT
RESOLUTION, another vote will be called later.

Best Regards,
Eason Chen

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

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

Thank you sebb, I will fix it and relaunch the vote.

On Thu, Feb 9, 2023 at 7:46 PM sebb  wrote:
>
> On Thu, 9 Feb 2023 at 09:44, Eason Chen  wrote:
> >
> > Dear Apache Incubator Community and IPMC members,
> >
> > After having the graduation discussion in the EventMesh community [1],
> > we passed the vote within the EventMesh community [2] and the vote
> > result was published[3].
> > We then discussed the graduation for EventMesh in the Apache Incubator
> > Community [4], where no issues were raised and positive replies were
> > received.
> >
> > I would like to start this voting thread to request graduating Apache
> > EventMesh(incubating) from Apache Incubator as a Top Level Project.
> >
> > Please provide your vote accordingly:
> > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > Apache Incubator.
> > [ ] +0 No opinion.
> > [ ] -1 No, the EventMesh project is not ready to graduate, because...
> >
> > Thank you for participating in the vote. This vote will stay open for
> > at least 72 hours.
> >
> > Here is an overview of the Apache EventMesh(incubating) to help with the 
> > vote.
> >
> > *Community*
> >
> > ● 5 new PPMC members were added, bringing the total number of PPMC
> > members to 14 from at least 9 different organizations.
> > ● 20 new Committers were added, bringing the total number of
> > committers to 42 from at least 30 different organizations.
> > ● 220+ new contributors participate in the community. The number of
> > contributors is now 250+ and growing.
> > ● 20 Bi-weekly online meetings were held among the committers,
> > contributors, and users. The meeting minutes are recorded on the
> > mailing list[5] and cwiki [6].
> > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > ● We've confirmed the VP, PMC, and Committers in the preparation
> > discussion at private@eventmesh [7]. Eason
> > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> >
> > *Project*
> >
> > ● Apache EventMesh(incubating) is a fully serverless platform used to
> > build distributed event-driven applications.
> > ● Project maturity model is detailed in [8].
> > ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> > ● EventMesh community released a total of 7 Apache releases [10] by 6
> > different release managers from 5 different organizations.
> > ● 1300+ issues created, and 1100+ issues closed [11].
> > ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > 2500+ commits added.
> > ● The release cadence is about 3 months, with an average of 180+
> > issues and 230+ pull requests per release.
> > ● Please refer to the EventMesh project incubation status [13][14] for
> > more information.
> >
> > *Brands, License, and Copyright*
> >
> > ● We applied the brand [15], which has been reviewed and approved.
> > ● EventMesh community maintains project code on GitHub and all modules
> > code is under Apache 2.0 license. We have reviewed all the
> > dependencies and ensured they do not bring any license issues [16].
> > All the status files, license headers, and copyright are up to date.
> > ● EventMesh official website [17] is compliant with Apache Foundation
> > requirements[18].
> >
> > -
> > BEGINNING OF DRAFT RESOLUTION
> > -
> >
> > Establish the Apache EventMesh 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 EventMesh is a fully serverless platform used to build
> > distributed event-driven applications.
>
> The last phrase does not make sense; need to drop the words 'EventMesh is"
>
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> > for the creation and maintenance of software related to EventMesh is a
> > fully serverless platform used to build distributed event-driven
> > applications; and be it further
>
> The last phrase does not make

[VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

Dear Apache Incubator Community and IPMC members,

After having the graduation discussion in the EventMesh community [1],
we passed the vote within the EventMesh community [2] and the vote
result was published[3].
We then discussed the graduation for EventMesh in the Apache Incubator
Community [4], where no issues were raised and positive replies were
received.

I would like to start this voting thread to request graduating Apache
EventMesh(incubating) from Apache Incubator as a Top Level Project.

Please provide your vote accordingly:
[ ] +1 Yes, I support the EventMesh project to graduate from the
Apache Incubator.
[ ] +0 No opinion.
[ ] -1 No, the EventMesh project is not ready to graduate, because...

Thank you for participating in the vote. This vote will stay open for
at least 72 hours.

Here is an overview of the Apache EventMesh(incubating) to help with the vote.

*Community*

● 5 new PPMC members were added, bringing the total number of PPMC
members to 14 from at least 9 different organizations.
● 20 new Committers were added, bringing the total number of
committers to 42 from at least 30 different organizations.
● 220+ new contributors participate in the community. The number of
contributors is now 250+ and growing.
● 20 Bi-weekly online meetings were held among the committers,
contributors, and users. The meeting minutes are recorded on the
mailing list[5] and cwiki [6].
● The dev@eventmesh mailing list currently has 117 subscribers.
● We've confirmed the VP, PMC, and Committers in the preparation
discussion at private@eventmesh [7]. Eason
Chen(chenguangsh...@apache.org) was recommended as Vice President.

*Project*

● Apache EventMesh(incubating) is a fully serverless platform used to
build distributed event-driven applications.
● Project maturity model is detailed in [8].
● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
● EventMesh community released a total of 7 Apache releases [10] by 6
different release managers from 5 different organizations.
● 1300+ issues created, and 1100+ issues closed [11].
● 1600+ pull requests created, and 1600+ pull requests closed [12],
2500+ commits added.
● The release cadence is about 3 months, with an average of 180+
issues and 230+ pull requests per release.
● Please refer to the EventMesh project incubation status [13][14] for
more information.

*Brands, License, and Copyright*

● We applied the brand [15], which has been reviewed and approved.
● EventMesh community maintains project code on GitHub and all modules
code is under Apache 2.0 license. We have reviewed all the
dependencies and ensured they do not bring any license issues [16].
All the status files, license headers, and copyright are up to date.
● EventMesh official website [17] is compliant with Apache Foundation
requirements[18].

-
BEGINNING OF DRAFT RESOLUTION
-

Establish the Apache EventMesh 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 EventMesh is a fully serverless platform used to build
distributed event-driven applications.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache EventMesh Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache EventMesh Project be and hereby is responsible
for the creation and maintenance of software related to EventMesh is a
fully serverless platform used to build distributed event-driven
applications; and be it further

RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache EventMesh
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 EventMesh
Project:

 * Alex Luo 
 * Du Heng      
 * Eason Chen   
 * Francois Papon   
 * Jean-Baptiste Onofré 
 * Junping Du   
 * Justin Mclean
 * ShannonDing  
 * Von Gosling  
 * Weiqiang Liang   
 * Wenjun Ruan  
 * XiaoShuang Li
 * Xue Weiming  
 * Yuwei Zhu

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eason Chen be appointed
to the office of Vice President, Apache EventMesh, to serve in
accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation,

Re: [DISCUSS] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

Thank you PJ for your advice, We'd like to have a discussion with the
incubator community and get more feedback, and we will start the VOTE
thread after the discussion is closed.

On Mon, Feb 6, 2023 at 11:32 PM PJ Fanning  wrote:
>
> I think this thread might need to be started again. If we are going to
> vote, the email subject should be:
>
> [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project
>
> Example: https://lists.apache.org/thread/k9gj4hh2fbrkf41o3211gkt49p87nhvy
>
> My vote is +1 (binding) regardless.
>
> On Mon, 6 Feb 2023 at 16:27, Alex Luo  wrote:
> >
> > +1 non-binding
> >
> > Alex Luo
> >
> > On 2023/02/06 14:09:50 李晓双 wrote:
> > > +1 non-binding
> > >
> > > 李晓双  于2023年2月6日周一 21:05写道：
> > >
> > > > +1 binding
> > > >
> > > > peacewong  于2023年2月6日周一 19:48写道：
> > > >
> > > >> +1 (non-binding)
> > > >>
> > > >> Congratulations!
> > > >>
> > > >> Wei Liu  于2023年2月6日周一 19:26写道：
> > > >>
> > > >> > +1
> > > >> >
> > > >> > Congratulations!
> > > >> >
> > > >> > On 2023/02/06 09:27:26 Eason Chen wrote:
> > > >> > > Dear Apache Incubator Community,
> > > >> > >
> > > >> > > Apache EventMesh has been incubating [1] since 2021-02-18 for over 
> > > >> > > 23
> > > >> > > months. The EventMesh community has grown rapidly under the 
> > > >> > > guidance
> > > >> > > of mentors and the Apache Way. After self-checking the EventMesh
> > > >> maturity
> > > >> > > model [2] and having a discussion [3], we started a vote [4] for
> > > >> > > graduation within the EventMesh community and got unanimous 
> > > >> > > positive
> > > >> > > feedback [5]. We believe Apache EventMesh (Incubating) is now 
> > > >> > > ready to
> > > >> > > graduate to be a Top Level Project. We'd like to have a discussion
> > > >> > > with the incubator community and get more feedback.
> > > >> > >
> > > >> > > Here is an overview of the Apache EventMesh(incubating) to help 
> > > >> > > with
> > > >> > > the discussion.
> > > >> > >
> > > >> > > *Community*
> > > >> > >
> > > >> > > ● 5 new PPMC members were added, bringing the total number of PPMC
> > > >> > > members to 14 from at least 9 different organizations.
> > > >> > > ● 20 new Committers were added, bringing the total number of
> > > >> > > committers to 42 from at least 23 different organizations.
> > > >> > > ● 210+ new contributors participate in the community. The number of
> > > >> > > contributors is now 240+ and growing.
> > > >> > > ● 20 Bi-weekly online meetings were held among the committers,
> > > >> > > contributors, and users. The meeting minutes are recorded on the
> > > >> > > mailing list[6] and wiki [7].
> > > >> > > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > > >> > > ● We've confirmed the VP, PMC, and Committers in the preparation
> > > >> > > discussion at private@eventmesh [8]. Eason
> > > >> > > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> > > >> > >
> > > >> > > *Project*
> > > >> > >
> > > >> > > ● Apache EventMesh(incubating) builds a fully serverless platform 
> > > >> > > used
> > > >> > > to build distributed event-driven applications.
> > > >> > > ● EventMesh community released a total of 7 Apache releases [9] by 
> > > >> > > 6
> > > >> > > different release managers from 5 different organizations.
> > > >> > > ● 1300+ issues created, and 1100+ issues closed [10].
> > > >> > > ● 1600+ pull requests created, and 1600+ pull requests closed [11],
> > > >> > > 2500+ commits added.
> > > >> > > ● The release cadence is about 3 months, with an average of 180+
> > > >> > > issues and 230+ pull requests per release.
> > > >> >

[DISCUSS] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Eason Chen]

Dear Apache Incubator Community,

Apache EventMesh has been incubating [1] since 2021-02-18 for over 23
months. The EventMesh community has grown rapidly under the guidance
of mentors and the Apache Way. After self-checking the EventMesh maturity
model [2] and having a discussion [3], we started a vote [4] for
graduation within the EventMesh community and got unanimous positive
feedback [5]. We believe Apache EventMesh (Incubating) is now ready to
graduate to be a Top Level Project. We'd like to have a discussion
with the incubator community and get more feedback.

Here is an overview of the Apache EventMesh(incubating) to help with
the discussion.

*Community*

● 5 new PPMC members were added, bringing the total number of PPMC
members to 14 from at least 9 different organizations.
● 20 new Committers were added, bringing the total number of
committers to 42 from at least 23 different organizations.
● 210+ new contributors participate in the community. The number of
contributors is now 240+ and growing.
● 20 Bi-weekly online meetings were held among the committers,
contributors, and users. The meeting minutes are recorded on the
mailing list[6] and wiki [7].
● The dev@eventmesh mailing list currently has 117 subscribers.
● We've confirmed the VP, PMC, and Committers in the preparation
discussion at private@eventmesh [8]. Eason
Chen(chenguangsh...@apache.org) was recommended as Vice President.

*Project*

● Apache EventMesh(incubating) builds a fully serverless platform used
to build distributed event-driven applications.
● EventMesh community released a total of 7 Apache releases [9] by 6
different release managers from 5 different organizations.
● 1300+ issues created, and 1100+ issues closed [10].
● 1600+ pull requests created, and 1600+ pull requests closed [11],
2500+ commits added.
● The release cadence is about 3 months, with an average of 180+
issues and 230+ pull requests per release.

*Brands, License, and Copyright*

● We submitted an application for the brand [12], which has been
reviewed and approved.
● EventMesh community maintains project code on GitHub and all modules
code is under Apache 2.0 license. We have reviewed all the
dependencies and ensured they do not bring any license issues [13].
All the status files, license headers, and copyright are up to date.
● EventMesh official website [14] is compliant with Apache Foundation
requirements.

-
BEGINNING OF DRAFT RESOLUTION
-

Establish the Apache EventMesh 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 EventMesh is a fully serverless platform used to build
distributed event-driven applications.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache EventMesh Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache EventMesh Project be and hereby is responsible
for the creation and maintenance of software related to EventMesh is a
fully serverless platform used to build distributed event-driven
applications; and be it further

RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache EventMesh
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 EventMesh
Project:

 * Alex Luo 
 * Du Heng      
 * Eason Chen   
 * Francois Papon   
 * Jean-Baptiste Onofré 
 * Junping Du   
 * Justin Mclean
 * ShannonDing  
 * Von Gosling  
 * Weiqiang Liang   
 * Wenjun Ruan  
 * XiaoShuang Li
 * Xue Weiming  
 * Yuwei Zhu

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eason Chen be appointed
to the office of Vice President, Apache EventMesh, 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 EventMesh Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator EventMesh
podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
EventMesh podling encumbered upon the Apache Incubator PMC are 

Re: [VOTE] Release Apache EventMesh (incubating) 1.8.0-rc2

[Eason Chen]

Hi,
This release still needs one more binding vote, welcome IPMC members
to help review it.

Best Regards,
Eason Chen

On Wed, Jan 18, 2023 at 8:23 PM walterzywei  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache EventMesh(Incubating)
> version 1.8.0-rc2
>
> The Apache EventMesh community has voted on and approved a
> proposal to release
> Apache EventMesh(Incubating) version 1.8.0-rc2
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> EventMesh community vote thread:
> • https://lists.apache.org/thread/z6p2kxw2l1zv641fsx4bhjgtmdh4xwyg
>
> Vote result thread:
> • https://lists.apache.org/thread/16js8nnlbypy203snxk2fqzt3vjz1yg5
>
> The release candidate:
> • https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.8.0-rc2
>
> Git tag for the release:
> • https://github.com/apache/incubator-eventmesh/tree/v1.8.0-rc2
> Release notes:
> • https://eventmesh.apache.org/events/release-notes/v1.8.0
>
> The artifacts signed with PGP key
> 16D5190EA34AC32AE3CE05A753FF44C181774D3F, corresponding to
> walterzy...@apache.org, that can be found in keys file:
> • https://downloads.apache.org/incubator/eventmesh/KEYS
>
> The vote will be open for at least 72 hours or until necessary
> number of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> On behalf of Apache EventMesh(Incubating) community
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@eventmesh.apache.org
> For additional commands, e-mail: dev-h...@eventmesh.apache.org
>

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

Re: [VOTE] Release Apache EventMesh (incubating) 1.7.0-rc1

[Eason Chen]

Thank you Junping.

On Thu, Dec 1, 2022 at 5:17 PM 俊平堵  wrote:
>
> +1 (binding).
>
> I have checked:
> - Download links are valid.
> - Checksums and PGP signatures looks good
> - ASF headers are present in source files
> - LICENSE, NOTICE and DISCLAIMER files are there and look good
> - No binaries found in the source distribution
>
> Thanks,
>
> Junping
>
> Alex Luo  于2022年11月25日周五 13:02写道：
>
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache EventMesh(Incubating)
> > version 1.7.0-rc1
> >
> > The Apache EventMesh community has voted on and approved a proposal to
> > release
> > Apache EventMesh(Incubating) version 1.7.0-rc1
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > EventMesh community vote thread:
> > • https://lists.apache.org/thread/0t8lz5d3ypbnd1094tkrc57ql12w6ckl
> >
> > Vote result thread:
> > • https://lists.apache.org/thread/p4zm61p636gjj7msmj8smyx8nsthn9kx
> >
> > The release candidate:
> > •https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.7.0-rc1
> >
> > Git tag for the release:
> > • https://github.com/apache/incubator-eventmesh/tree/v1.7.0-rc1
> > Release notes:
> > • https://eventmesh.apache.org/events/release-notes/v1.7.0
> >
> > The artifacts signed with PGP key
> > 235DBB05A82D0D8C1492D50079CD973EA1DBF237, corresponding to
> > alex...@apache.org, that can be found in keys file:
> > • https://downloads.apache.org/incubator/eventmesh/KEYS
> >
> > The vote will be open for at least 72 hours or until the necessary
> > number of votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > On behalf of Apache EventMesh(Incubating) community
> >

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

Re: [VOTE] Release Apache EventMesh (incubating) 1.7.0-rc1

[Eason Chen]

Thank you JB :)

On Wed, Nov 30, 2022 at 3:42 PM Jean-Baptiste Onofré  wrote:
>
> +1 (binding)
>
> I checked:
> - incubating is in the name
> - LICENSE, NOTICE and DISCLAIMER files are there and look good
> - Signatures and hashes are good
> - ASF headers are present in source files
> - No binaries found in the source distribution
>
> Regards
> JB
>
> On Fri, Nov 25, 2022 at 6:01 AM Alex Luo  wrote:
> >
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache EventMesh(Incubating)
> > version 1.7.0-rc1
> >
> > The Apache EventMesh community has voted on and approved a proposal to
> > release
> > Apache EventMesh(Incubating) version 1.7.0-rc1
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > EventMesh community vote thread:
> > • https://lists.apache.org/thread/0t8lz5d3ypbnd1094tkrc57ql12w6ckl
> >
> > Vote result thread:
> > • https://lists.apache.org/thread/p4zm61p636gjj7msmj8smyx8nsthn9kx
> >
> > The release candidate:
> > •https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.7.0-rc1
> >
> > Git tag for the release:
> > • https://github.com/apache/incubator-eventmesh/tree/v1.7.0-rc1
> > Release notes:
> > • https://eventmesh.apache.org/events/release-notes/v1.7.0
> >
> > The artifacts signed with PGP key
> > 235DBB05A82D0D8C1492D50079CD973EA1DBF237, corresponding to
> > alex...@apache.org, that can be found in keys file:
> > • https://downloads.apache.org/incubator/eventmesh/KEYS
> >
> > The vote will be open for at least 72 hours or until the necessary
> > number of votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > On behalf of Apache EventMesh(Incubating) community
>
> -
> 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] Release Apache EventMesh (incubating) 1.7.0-rc1

[Eason Chen]

+1, I have checked:
[√] Download links are valid.
[√] Checksums and PGP signatures are valid.
[√] DISCLAIMER is included.
[√] Source code artifacts have correct names matching the current release.
[√] LICENSE and NOTICE files are correct for each EventMesh repo.
[√] All files have license headers if necessary.
[√] No compiled archives bundled in source archive.

On Mon, Nov 28, 2022 at 10:33 AM Eason Chen  wrote:
>
> +1, thank you Alex.
>
> On Fri, Nov 25, 2022 at 1:01 PM Alex Luo  wrote:
> >
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache EventMesh(Incubating)
> > version 1.7.0-rc1
> >
> > The Apache EventMesh community has voted on and approved a proposal to
> > release
> > Apache EventMesh(Incubating) version 1.7.0-rc1
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > EventMesh community vote thread:
> > • https://lists.apache.org/thread/0t8lz5d3ypbnd1094tkrc57ql12w6ckl
> >
> > Vote result thread:
> > • https://lists.apache.org/thread/p4zm61p636gjj7msmj8smyx8nsthn9kx
> >
> > The release candidate:
> > •https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.7.0-rc1
> >
> > Git tag for the release:
> > • https://github.com/apache/incubator-eventmesh/tree/v1.7.0-rc1
> > Release notes:
> > • https://eventmesh.apache.org/events/release-notes/v1.7.0
> >
> > The artifacts signed with PGP key
> > 235DBB05A82D0D8C1492D50079CD973EA1DBF237, corresponding to
> > alex...@apache.org, that can be found in keys file:
> > • https://downloads.apache.org/incubator/eventmesh/KEYS
> >
> > The vote will be open for at least 72 hours or until the necessary
> > number of votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > On behalf of Apache EventMesh(Incubating) community

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

Re: [VOTE] Release Apache EventMesh (incubating) 1.7.0-rc1

[Eason Chen]

+1, thank you Alex.

On Fri, Nov 25, 2022 at 1:01 PM Alex Luo  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache EventMesh(Incubating)
> version 1.7.0-rc1
>
> The Apache EventMesh community has voted on and approved a proposal to
> release
> Apache EventMesh(Incubating) version 1.7.0-rc1
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> EventMesh community vote thread:
> • https://lists.apache.org/thread/0t8lz5d3ypbnd1094tkrc57ql12w6ckl
>
> Vote result thread:
> • https://lists.apache.org/thread/p4zm61p636gjj7msmj8smyx8nsthn9kx
>
> The release candidate:
> •https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.7.0-rc1
>
> Git tag for the release:
> • https://github.com/apache/incubator-eventmesh/tree/v1.7.0-rc1
> Release notes:
> • https://eventmesh.apache.org/events/release-notes/v1.7.0
>
> The artifacts signed with PGP key
> 235DBB05A82D0D8C1492D50079CD973EA1DBF237, corresponding to
> alex...@apache.org, that can be found in keys file:
> • https://downloads.apache.org/incubator/eventmesh/KEYS
>
> The vote will be open for at least 72 hours or until the necessary
> number of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> On behalf of Apache EventMesh(Incubating) community

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

Re: [VOTE] Graduate Apache Linkis(incubating) as an Apache Top Level Project

[Eason Chen]

+1(non-binding), Good Luck.

Warn Regards,

Eason Chen
Apache EventMesh(incubating) PPMC

On Mon, Nov 28, 2022 at 9:50 AM wangxiaogang  wrote:
>
> sorry, I am no-binding, not binding.
>
> +1(non-binding)
> We need Apache Linkis.
> Best Regards.
>
> wangxiaogang  于2022年11月28日周一 09:28写道：
> >
> > +1(binding)
> > We need Apache Linkis.
> > Best Regards.
> >
> > Jerry Tan  于2022年11月28日周一 08:52写道：
> > >
> > > +1 (binding)
> > >
> > >
> > > On 2022/11/27 10:17:58 Shuai Di wrote:
> > > > Dear Apache Incubator Community and IPMC members,
> > > >
> > > > After having the graduation discussion in the Linkis community [1], we
> > > > have passed the vote within Linkis community [2] and the vote result
> > > > was published[3].
> > > > We then discussed the graduation for Linkis in the Apache Incubator
> > > > Community [4], where no issues were raised and positive replies were
> > > > received.
> > > >
> > > > I would like to start this voting thread to request graduating Apache
> > > > Linkis(incubating) from Apache Incubator as a Top Level Project.
> > > >
> > > > Please provide your vote accordingly:
> > > > [ ] +1 Yes, I support Linkis project to graduate from the Apache 
> > > > Incubator.
> > > > [ ] +0 No opinion.
> > > > [ ] -1 No, the Linkis project is not ready to graduate, because...
> > > >
> > > > Thank you for participating in the vote. This vote will stay open for at
> > > > least 72 hours.
> > > >
> > > > Here is an overview of the Apache Linkis(incubating) to help with the
> > > > vote.
> > > >
> > > > *Community*
> > > >
> > > > ● 4 new PPMC members were added, bringing the total number of PPMC
> > > > members to 24 from 15 different organizations.
> > > > ● 13 new committers were added(including the new PPMC members),
> > > > bringing the total number of committers to 33 from 21 different
> > > > organizations.
> > > > ● 79 new contributors. The number of contributors is now 128 and 
> > > > growing.
> > > > ● 21 biweekly online meetings were held in the community among PPMC
> > > > members, committers, contributors, and users. The meeting minutes are
> > > > recorded on the cwiki and mailing list [5].
> > > > ● The dev@linkis mailing list currently has 113 subscribers [6].
> > > > ● We've confirmed the VP, PMC, and Committers in the preparation
> > > > discussion at private@linkis [7]. Shuai Di(shua...@apache.org) was
> > > > voted as Vice President.
> > > >
> > > > *Project*
> > > >
> > > > ● Apache Linkis(incubating) builds a computation middleware layer to
> > > > facilitate connection, governance and orchestration between the upper
> > > > applications and the underlying data engines.
> > > > ● Project maturity model is detailed in [8]
> > > > ● Linkis has been incubating [9] since 2021-08-02 for over 15
> > > > months.
> > > > ● Linkis community released a total of 7 Apache releases [10] by 7
> > > > different release managers from 6 different organizations.
> > > > ● 1935 pull requests created, and 1894 pull requests closed [11].
> > > > ● 1488 issues created, and 1271 issues closed [12].
> > > > ● The release cadence is about 2 months, with an average of 200+
> > > > issues and 270+ pull requests per release.
> > > > ● Please refer to the Linkis project incubation status [13][14] for more
> > > > information.
> > > >
> > > > *Brand, License, and Copyright*
> > > >
> > > > ● We submitted an application for the brand [15] and it has been
> > > > reviewed and approved.
> > > > ● Linkis community maintains project code on GitHub and all modules
> > > > code is under Apache 2.0 license. We have reviewed all the
> > > > dependencies and ensured they do not bring any license issues [16].
> > > > All the status files, license headers, and copyright are up to date.
> > > > ● Linkis official website [17] is compliant with Apache Foundation
> > > > requirements [18].
> > > >
> > > > -
> > > > BEGINNING OF DRAFT RESOLUTION
> > > > -
> &

Re: [VOTE] Accept Celeborn into the Apache Incubator

[Eason Chen]

+1(non-binding)
Good luck!

Best Regards,

Eason Chen
Apache EventMesh(incubating) PPMC

On Sun, Oct 16, 2022 at 10:44 PM david zollo 
wrote:

> +1 (binding)
> Good luck
>
>
>
> Best Regards
>
> ---
> Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> David
> Linkedin: https://www.linkedin.com/in/davidzollo
> Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy>
> ---
>
>
> On Thu, Oct 13, 2022 at 10:08 PM li gang  wrote:
>
> > +1(non-binding)
> > Good luck!
> >
> > Yu Li  于2022年10月12日周三 11:49写道：
> >
> > > Hi all,
> > >
> > > Following up on the [DISCUSS] thread on Celeborn [1] [2], I would like
> to
> > > call a VOTE to accept Celeborn into the Apache Incubator, please check
> > out
> > > the Celeborn Proposal from the incubator wiki [3].
> > >
> > > Please cast your vote:
> > >
> > > [ ] +1, bring Celeborn into the Incubator
> > > [ ] +0, I don't care either way
> > > [ ] -1, do not bring Celeborn 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.
> > >
> > > Best Regards,
> > > Yu
> > >
> > > [1] https://lists.apache.org/thread/rlkzg8m5923vngyon0bwcv97x3m68x4c
> > > [2] https://lists.apache.org/thread/hjy3gpvocjtls5vp9h1llcvmwkgz3lcy
> > > [3]
> > https://cwiki.apache.org/confluence/display/INCUBATOR/CelebornProposal
> > >
> >
> >
> > --
> >
> >
> > --
> > Best Regards
> >
> > DolphinScheduler PMC
> > Gang Li 李岗
> >
> > lgcar...@apache.org
> >
>

Re: [VOTE] Release Apache EventMesh (incubating) 1.6.0-rc1

[Eason Chen]

Thank you Justin, we will include the build instruction in the next
release, and fix the "WeChat Official Account”  in readme immediately.

On Wed, Aug 24, 2022 at 3:48 PM Justin Mclean 
wrote:

> HI,
>
> +1 (binding)
>
> Please include clear instruction on how to build in the release. The
> readme me also refers to an "WeChat Official Account” Apache doesn’t have
> offical WeChat accounts.
>
> I checked:
> - incubating in name
> - LICENSE need more work but WIP disclaimer
> - NOTICE is fine
> - WIP DISCLAIMER exists
> - signatures and hashes are fine
> - no unexpected binary files
> - ASF files have ASF headers
> - I was unable to compile from source but that likely my setup
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache ShenYu(Incubating) as a TLP [ROUND 2]

[Eason Chen]

+1 (non-binding)

On Wed, Jun 22, 2022 at 4:07 PM Kevin Ratnasekera 
wrote:

> +1 ( binding )
>
> On Wed, Jun 22, 2022 at 9:59 AM Willem Jiang 
> wrote:
>
> > +1 (binding).
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Wed, Jun 22, 2022 at 2:43 PM XiaoYu  wrote:
> > >
> > > Dear Apache Incubator Community,
> > >
> > > In the previous vote[1] thread,
> > >
> > > I only described the functionality of the project and not the scope of
> > > the project in the resolution template.It doesn't fit the standard
> > > template. so I initiate cancel the vote thread[2].
> > >
> > > Under the guidance of our mentors, I refactor the project description
> > > in this resolution template.
> > >
> > > The Apache ShenYu community has a discussion thread [3],
> > > passed the community vote[4], and the vote result is published [5].
> > > We have discussed the graduation for ShenYu in the Incubator Community
> > [6],
> > > where no issues were raised and lots of positive responses were
> received.
> > >
> > > I would like to start this voting thread to request graduating Apache
> > > ShenYu (incubating) from the incubator as a TLP. Please provide your
> vote
> > > as one of the following options:
> > >
> > > [ ] +1 Yes, I support ShenYu to graduate from the Apache incubator.
> > >
> > > [ ] +0 No opinion.
> > >
> > > [ ] -1 No, the ShenYu project is not ready to graduate, because ...
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > >
> > > ** Community **
> > >
> > > - 6 new PPMC members were added, bringing the total number of PPMC
> > > members to 30 from at least 15+ different organizations.
> > >
> > > - 7 new Committers were added, bringing the total number of
> > Committers 37.
> > >
> > > - 110+ new contributors participate in the community. The number
> > > of contributors is now 270+ and growing.
> > >
> > > - The dev@shenyu.a.o mailing list currently has 350+ subscribers,
> > > and all major project discussions are happening in the dev@shenyu.a.o.
> > >
> > > - 26 Bi-weekly online meetings were held between committers,
> > > contributors and users. The meeting minutes are recorded on the
> > > mailing list [7].
> > >
> > > - 1100+ pull requests merged [8], and 700+ issues closed [9] after
> > > into the apache incubator.
> > >
> > > ** Project **
> > >
> > > - 4 releases by 4 release managers.
> > >
> > > - ShenYu official website [10] is compliant with Apache Foundation
> > > requirements [11].
> > >
> > > - Project maturity model is detailed in [12].
> > >
> > > - See ShenYu Project Incubation Status [13] for more info.
> > >
> > > ** Brands ,License, and Copyright **
> > >
> > > - We submitted an application for the brand[14] and it has been
> > > reviewed and approved.
> > > - Apache ShenYu community maintains project code on GitHub, and all
> > modules
> > > code is under Apache 2.0 license. We have reviewed all the
> > > dependencies and ensured they do not bring any license issues [15]. All
> > > the status files, license headers, and copyright are up to date.
> > >
> > > ** PMC members **
> > >
> > >- 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
> > > [16].
> > >
> > > [1] https://lists.apache.org/thread/yk6kjx3j2mh9c5xzfojcln5dtrzt87yf
> > > [2] https://lists.apache.org/thread/53rj96r63sf2vxcdbfqbqbl27r4v9j0c
> > > [3] https://lists.apache.org/thread/lc1xr9gjf1t2lbk8070thf1bgt3sq1v3
> > > [4] https://lists.apache.org/thread/0fo3f3whl7bb5r7bhoh85czlgjdn7rog
> > > [5] https://lists.apache.org/thread/jdh2dcs4qd97t1mjjl8hp62sso470wc7
> > > [6] https://lists.apache.org/thread/cc2myvso0pbyl39yv26bdmzml8jjvpt2
> > > [7] https://lists.apache.org/list.html?d...@shenyu.apache.org
> > > [8]
> >
> https://github.com/apache/incubator-shenyu/pulls?q=is%3Apr+merged%3A%3E%3D2021-05-03+
> > > [9]
> >
> https://github.com/apache/incubator-shenyu/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-05-03
> > > [10] https://shenyu.incubator.apache.org/
> > > [11] https://whimsy.apache.org/pods/project/shenyu
> > > [12]
> https://github.com/apache/incubator-shenyu/blob/master/MATURITY.md
> > > [13] https://incubator.apache.org/projects/shenyu.html
> > > [14] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-197
> > > [15] https://github.com/apache/incubator-shenyu/blob/master/LICENSE
> > > [16] https://lists.apache.org/thread/gp1bnjflz7ysgopxk515l9clswgrvnko
> > >
> > >
> >
> --
> > >
> > > Establish the Apache ShenYu 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 

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

[Eason Chen]

+ 1 (non-binding)
Good luck~

Daming 于2022年6月18日 周六20:11写道：

> +1 non-binding
>
> haochao zhuang
>
> like...@apache.org 于2022年6月18日 周六18:50写道：
>
> >
> >
> > + 1 (non-binding)
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >  Replied Message 
> > | From | XiaoYu |
> > | Date | 06/18/2022 09:09 |
> > | To |  |
> > | Subject | [VOTE] Graduate Apache ShenYu(Incubating) as a TLP |
> > Dear Apache Incubator Community,
> >
> > The Apache ShenYu community has a discussion thread [1],
> > passed the community vote[2], and the vote result is published [3].
> > We have discussed the graduation for ShenYu in the Incubator Community
> [4],
> > where no issues were raised and lots of positive responses were received.
> >
> > I would like to start this voting thread to request graduating Apache
> > ShenYu (incubating) from the incubator as a TLP. Please provide your vote
> > as one of the following options:
> >
> > [ ] +1 Yes, I support ShenYu to graduate from the Apache incubator.
> >
> > [ ] +0 No opinion.
> >
> > [ ] -1 No, the ShenYu project is not ready to graduate, because ...
> >
> > The VOTE will remain open for at least 72 hours.
> >
> >
> > ** Community **
> >
> > - 6 new PPMC members were added, bringing the total number of PPMC
> > members to 30 from at least 15+ different organizations.
> >
> > - 7 new Committers were added, bringing the total number of Committers
> 37.
> >
> > - 110+ new contributors participate in the community. The number
> > of contributors is now 274 and growing.
> >
> > - The dev@shenyu.a.o mailing list currently has 357 subscribers,
> > and all major project discussions are happening in the dev@shenyu.a.o.
> >
> > - 26 Bi-weekly online meetings were held between committers,
> > contributors and users. The meeting minutes are recorded on the
> > mailing list [5].
> >
> > - 1100+ pull requests merged [6], and 700+ issues closed [7] after
> > into the apache incubator.
> >
> > ** Project **
> >
> > - 4 releases by 4 release managers.
> >
> > - ShenYu official website [8] is compliant with Apache Foundation
> > requirements [9].
> >
> > - Project maturity model is detailed in [10].
> >
> > - See ShenYu Project Incubation Status [11] for more info.
> >
> > ** Brands ,License, and Copyright **
> >
> > - We submitted an application for the brand[12] and it has been
> > reviewed and approved.
> > - Apache ShenYu community maintains project code on GitHub, and all
> modules
> > code is under Apache 2.0 license. We have reviewed all the
> > dependencies and ensured they do not bring any license issues [13]. All
> > the status files, license headers, and copyright are up to date.
> >
> > ** PMC members **
> >
> > - 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
> > [14].
> >
> > [1] https://lists.apache.org/thread/lc1xr9gjf1t2lbk8070thf1bgt3sq1v3
> > [2] https://lists.apache.org/thread/0fo3f3whl7bb5r7bhoh85czlgjdn7rog
> > [3] https://lists.apache.org/thread/jdh2dcs4qd97t1mjjl8hp62sso470wc7
> > [4] https://lists.apache.org/thread/cc2myvso0pbyl39yv26bdmzml8jjvpt2
> > [5] https://lists.apache.org/list.html?d...@shenyu.apache.org
> > [6]
> >
> https://github.com/apache/incubator-shenyu/pulls?q=is%3Apr+merged%3A%3E%3D2021-05-03+
> > [7]
> >
> https://github.com/apache/incubator-shenyu/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-05-03
> > [8] https://shenyu.incubator.apache.org/
> > [9] https://whimsy.apache.org/pods/project/shenyu
> > [10] https://github.com/apache/incubator-shenyu/blob/master/MATURITY.md
> > [11] https://incubator.apache.org/projects/shenyu.html
> > [12] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-197
> > [13] https://github.com/apache/incubator-shenyu/blob/master/LICENSE
> > [14] https://lists.apache.org/thread/gp1bnjflz7ysgopxk515l9clswgrvnko
> >
> >
> >
> --
> >
> > Establish the Apache ShenYu 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 ShenYu is a dynamic full lifecycle JAVA API gateway
> with
> > easy
> > scalability and hot-pluggable features.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache ShenYu Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache ShenYu is a dynamic full lifecycle JAVA API
> > gateway
> > with easy scalability and hot-pluggable features; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache ShenYu" be and
> > hereby is created, the person holding such office to serve at 

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

[Eason Chen]

+1
Good luck!

On Mon, Jun 13, 2022 at 3:16 PM Goson zhang  wrote:
>
> +1
> Good luck!
>
> Atri Sharma  于2022年6月13日周一 14:57写道：
>
> > It has been a pleasure as one of Shenyu's mentors to see the project
> > grow and take the mantle of a popular and active open source project.
> >
> > I wish it luck and look forward to continued association with the project.
> >
> > On Mon, Jun 13, 2022 at 11:05 AM XiaoYu  wrote:
> > >
> > > Dear Apache Incubator Community,
> > >
> > > Apache ShenYu has been incubating since 2021-05-03. For over a year, the
> > > Apache ShenYu community has made great progress and grown rapidly under
> > the
> > > guidance of our mentors. We believe the Apache ShenYu project has met the
> > > conditions for graduation. Summary statistics on the state of the
> > > community are listed below. Please feel free to participate in the
> > > discussion and give more feedback.
> > >
> > > The Apache ShenYu community has a discussion thread [1], passed the
> > > community vote
> > > [2], and the vote result is published [3]. Our assessment is that Apache
> > > ShenYu(Incubating) is ready to graduate as a Apache TLP. We would like
> > to raise
> > > the discussion to IPMC and collect more feedback towards graduation.
> > >
> > > ** Community **
> > >
> > > - 6 new PPMC members were added, bringing the total number of PPMC
> > > members to 30 from at least 15+ different organizations.
> > >
> > > - 7 new Committers were added, bringing the total number of
> > Committers 37.
> > >
> > > - 110+ new contributors participate in the community. The number
> > > of contributors is now 274 and growing.
> > >
> > > - The dev@shenyu.a.o mailing list currently has 357 subscribers,
> > > and all major project discussions are happening in the dev@shenyu.a.o.
> > >
> > > - 26 Bi-weekly online meetings were held between committers,
> > > contributors and users. The meeting minutes are recorded on the
> > > mailing list [4].
> > >
> > > - 1100+ pull requests merged [5], and 700+ issues closed [6] after
> > > into the apache incubator.
> > >
> > > ** Project **
> > >
> > > - 4 releases by 4 release managers.
> > >
> > > - ShenYu official website [7] is compliant with Apache Foundation
> > > requirements [8].
> > >
> > > - Project maturity model is detailed in [9].
> > >
> > > - See ShenYu Project Incubation Status [10] for more info.
> > >
> > > ** Brands ,License, and Copyright **
> > >
> > > - We submitted an application for the brand[11] and it has been
> > > reviewed and approved.
> > > - Apache ShenYu community maintains project code on GitHub, and all
> > modules
> > > code is under Apache 2.0 license. We have reviewed all the
> > > dependencies and ensured they do not bring any license issues [12]. All
> > > the status files, license headers, and copyright are up to date.
> > >
> > > ** PMC members **
> > >
> > >- 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].
> > >
> > > The discussion will remain open for at least 72 hours, looking forward to
> > > your feedback.
> > >
> > > [1] https://lists.apache.org/thread/lc1xr9gjf1t2lbk8070thf1bgt3sq1v3
> > > [2] https://lists.apache.org/thread/0fo3f3whl7bb5r7bhoh85czlgjdn7rog
> > > [3] https://lists.apache.org/thread/jdh2dcs4qd97t1mjjl8hp62sso470wc7
> > > [4] https://lists.apache.org/list.html?d...@shenyu.apache.org
> > > [5]
> > https://github.com/apache/incubator-shenyu/pulls?q=is%3Apr+merged%3A%3E%3D2021-05-03+
> > > [6]
> > https://github.com/apache/incubator-shenyu/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-05-03
> > > [7] https://shenyu.incubator.apache.org/
> > > [8] https://whimsy.apache.org/pods/project/shenyu
> > > [9] https://github.com/apache/incubator-shenyu/blob/master/MATURITY.md
> > > [10] https://incubator.apache.org/projects/shenyu.html
> > > [11] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-197
> > > [12] https://github.com/apache/incubator-shenyu/blob/master/LICENSE
> > > [13] https://lists.apache.org/thread/gp1bnjflz7ysgopxk515l9clswgrvnko
> > >
> > >
> > --
> > >
> > > Establish the Apache ShenYu 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 ShenYu is a high performance Microservices API gateway
> > > in Java ecosystem, compatible with a variety of mainstream framework
> > > systems, supports hot plug. Users can write their own plugin meet the
> > > current requirement and future needs in a variety of scenarios,
> > > especially in large-scale scenes.

Re: [VOTE] Accept Uniffle into the Apache Incubator

[Eason Chen]

+1 (non-binding)

On Tue, May 31, 2022 at 7:02 PM Zhang Yonglun  wrote:
>
> +1 (non-binding)
>
> --
>
> Zhang Yonglun
> Apache ShenYu (Incubating)
> Apache ShardingSphere
>
> Jerry Shao  于2022年5月31日周二 09:37写道：
> >
> > Hi all,
> >
> > Following up the [DISCUSS] thread on Uniffle[1] and Firestorm[2], I would
> > like to
> > call a VOTE to accept Uniffle into the Apache Incubator, please check out
> > the Uniffle Proposal from the incubator wiki[3].
> >
> > Please cast your vote:
> >
> > [ ] +1, bring Uniffle into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring Uniffle 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.
> >
> > [1] https://lists.apache.org/thread/fyyhkjvhzl4hpzr52hd64csh5lt2wm6h
> > [2] https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f
> > [3] 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
>

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

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

[Eason Chen]

Congrats！

On Tue, May 31, 2022 at 2:54 PM Shuai Di  wrote:
>
> Congratulations!
>
> 在 2022年5月31日星期二，Heal Chow  写道：
>
> > Congratulations! :-)
> >
> > On 2022/05/31 03:32:57 Aloys Zhang wrote:
> > > Congrats
> > >
> > > Zirui Peng  于2022年5月31日周二 11:30写道：
> > >
> > > > Congrats and excellent work !
> > > >
> > > > Best wishes,
> > > > Zirui
> > > >
> > > >
> > > > On 2022/05/31 03:16:11 Charles Zhang wrote:
> > > > > Dear Apache Incubator Community,
> > > > > The IPMC vote for graduating Apache InLong(Incubating) as a TLP has
> > > > passed.
> > > > > There are 29 (+1) and no 0 or -1 votes. The results are:
> > > > >
> > > > > Binding(14)
> > > > >
> > > > > *Junping Du
> > > > > *Jerry Shao
> > > > > *tison
> > > > > *Sheng Wu
> > > > > *Byung-Gon Chun
> > > > > *Jean-Baptiste Onofré
> > > > > *Lidong Dai
> > > > > *Liang Chen
> > > > > *Furkan KAMACI
> > > > > *Felix Cheung
> > > > > *Justin Mclean
> > > > > *Paul King
> > > > > *Kevin Ratnasekera
> > > > > *Ted Liu
> > > > >
> > > > > Non-binding (15)
> > > > >
> > > > > *Goson zhang
> > > > > *Eason Chen
> > > > > *Heal Chow
> > > > > *Kent Yao
> > > > > *Mingyu Chen
> > > > > *Cheng Pan
> > > > > *Mingshen Sun
> > > > > *XiaoYu
> > > > > *Jiwei Guo
> > > > > *Aloys Zhang
> > > > > *Guangxu Cheng
> > > > > *Sammi Chen
> > > > > *Zhang Yonglun
> > > > > *Gang Li
> > > > > *Zirui Peng
> > > > >
> > > > > The discussion thread:
> > > > > https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > > > >
> > > > > The voting thread:
> > > > > https://lists.apache.org/thread/f8fvq7p2r56nlm7ph7ywrm0kxcbl7010
> > > > >
> > > > > We will now submit the graduation proposal to the ASF board. Thank
> > you so
> > > > > much for all of your support.
> > > > >
> > > > > --
> > > > > Best wishes,
> > > > > Charles Zhang
> > > > >
> > > >
> > > > -
> > > > 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
> >
> >
>
> --
> Shuai Di
> Best Regards.

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

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Eason Chen]

+1 (non-binding)

Good luck!

On Wed, May 25, 2022 at 4:25 PM Sammi Chen  wrote:
>
> +1  (non-binding)
>
> Good luck to Uniffle.
>
> Bests,
> Sammi
>
> On Wed, 25 May 2022 at 00:05, 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

[Eason Chen]

+1 (no-binding)

Good luck!!

On Wed, May 25, 2022 at 4:27 PM Goson zhang  wrote:
>
> +1 (no-binding)
>
> Good luck!!
>
> tison  于2022年5月25日周三 16:18写道：
>
> > +1 (binding)
> >
> > Good luck!
> >
> > Best,
> > tison.
> >
> >
> > Jerry Shao  于2022年5月25日周三 16:12写道：
> >
> > > +1 (binding).
> > >
> > > Good luck to Inlong.
> > >
> > > Best
> > > Jerry
> > >
> > > 俊平堵  于2022年5月25日周三 14:50写道：
> > >
> > > > +1, good luck to InLong.:)
> > > >
> > > > Charles Zhang 于2022年5月25日 周三下午2:34写道：
> > > >
> > > > > Dear Apache Incubator Community,
> > > > >
> > > > >
> > > > > The InLong community has a discussion thread [1], passed the
> > community
> > > > vote
> > > > > [2], and the vote result is published [3]. We have discussed the
> > > > graduation
> > > > > for InLong in the Incubator Community [4], where no issues were
> > raised
> > > > and
> > > > > lots of positive responses were received.
> > > > >
> > > > >
> > > > > I would like to start this voting thread to request graduating Apache
> > > > > InLong (incubating) from the incubator as a TLP. Please provide your
> > > vote
> > > > > as one of the following options:
> > > > >
> > > > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> > > > >
> > > > > [ ] +0 No opinion.
> > > > >
> > > > > [ ] -1 No, the InLong project is not ready to graduate, because ...
> > > > >
> > > > >
> > > > > The VOTE will remain open for at least 72 hours.
> > > > >
> > > > >
> > > > > Since incubating in ASF, the project itself has become more mature
> > and
> > > > >
> > > > > stable. The following is a brief summary of the project and community
> > > > >
> > > > > during the incubation:
> > > > >
> > > > >
> > > > > - 11 versions were released by 6 different release managers, of
> > which 5
> > > > >
> > > > > versions are the original TubeMQ, and 6 versions are after the name
> > was
> > > > >
> > > > > changed to InLong. The release cadence is about 2 months [5].
> > > > >
> > > > >
> > > > > - 10 new Committers and 3 PPMCs were 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
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > --
> > > > >
> > > > > Establish the Apache InLong Project
> > > > >
> > > > > WHEREAS, the Board of Directors deems it to be in the best interests
> > of
> > > > >

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

[Eason Chen]

+ 1  （non-binding）

Good luck!

On Fri, May 20, 2022 at 3:43 PM XiaoYu  wrote:
>
> + 1  （non-binding）
>
> Good luck!
>
> Heal Chow  于2022年5月20日周五 15:16写道：
> >
> > +1.
> >
> > I've learned a lot about community collaboration and maintaining open 
> > source projects in the InLong project. Looking forward to InLong doing 
> > better in data integration.
> >
> > Good luck!
> > HealChow
> >
> > On 2022/05/19 10:47:52 Goson zhang wrote:
> > > +1
> > >
> > > Since the InLong project entered the incubation pool, the team has
> > > continued to grow, with the help of community contributors, the project 
> > > has
> > > developed from a single module to a mature data integration framework, and
> > > has implemented the application of the project in multiple environments.
> > >
> > > Looking forward to the continuous improvement of the InLong project to
> > > become a global community of contributors to better serve the big data
> > > business.
> > >
> > > Thanks!
> > >
> > > Kent Yao  于2022年5月19日周四 17:25写道：
> > >
> > > > +1, good luck to InLong community
> > > >
> > > > Charles Zhang  于2022年5月19日周四 17:09写道：
> > > > >
> > > > > Dear Apache Incubator Community,
> > > > >
> > > > >
> > > > > The InLong Project has been incubating since 2019-11-03. In the past 
> > > > > two
> > > > > and a half years, the project has been renamed from TubeMQ to InLong, 
> > > > > and
> > > > > expanded its scope from a message queue service to a one-stop 
> > > > > integration
> > > > > framework for massive data.
> > > > >
> > > > >
> > > > > The InLong community has a discussion thread [1], passed the community
> > > > vote
> > > > > [2], and the vote result is published [3]. Our assessment is that 
> > > > > Apache
> > > > > InLong(Incubating) is ready to graduate as a TLP. We would like to 
> > > > > raise
> > > > > the discussion to IPMC and collect more feedback towards graduation.
> > > > >
> > > > >
> > > > > Since incubating in ASF, the project itself has become more mature and
> > > > > stable. The following is a brief summary of the project and community
> > > > > during the incubation:
> > > > >
> > > > >
> > > > > - 11 versions were released by 6 different release managers, of which 
> > > > > 5
> > > > > versions are the original TubeMQ, and 6 versions are after the name 
> > > > > was
> > > > > changed to InLong. The release cadence is about 2 months [4].
> > > > >
> > > > >
> > > > > - 10 new Committers and 3 PPMCs were added during incubating, they are
> > > > from
> > > > > 4 different organizations. All PPMCs and Committers are spread across 
> > > > > 8
> > > > > different organizations [5].
> > > > >
> > > > >
> > > > > - 101 unique code developers [6].
> > > > >
> > > > >
> > > > > - Closed more than 2200 issues, with an average of 200 issues per 
> > > > > version
> > > > > [7].
> > > > >
> > > > >
> > > > > - All the dependencies were reviewed and ensured they do not bring any
> > > > > license issues [8].
> > > > >
> > > > >
> > > > > - Evaluated the InLong project and self-checked the InLong maturity 
> > > > > model
> > > > > [9] and the pre-graduation Check [10].
> > > > >
> > > > >
> > > > > - Well and Complete documentation for contributors and users [11].
> > > > >
> > > > >
> > > > > - 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
> > > > > [12].
> > > > >
> > > > >
> > > > > The discussion will remain open for at least 72 hours, looking 
> > > > > forward to
> > > > > your feedback.
> > > > >
> > > > >
> > > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > >
> > > > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > > >
> > > > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > > >
> > > > > [4] https://inlong.apache.org/download/main/
> > > > >
> > > > > [5] https://whimsy.apache.org/roster/ppmc/inlong
> > > > >
> > > > > [6] https://github.com/apache/incubator-inlong/graphs/contributors
> > > > >
> > > > > [7]
> > > > >
> > > > https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > > >
> > > > > [8] https://github.com/apache/incubator-inlong/tree/master/licenses
> > > > >
> > > > > [9]
> > > > >
> > > > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > > >
> > > > > [10]
> > > > > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > > > >
> > > > > [11] https://inlong.apache.org/docs/next/introduction
> > > > >
> > > > > [12] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
> 

Re: [VOTE] graduate Apache Doris (Incubating) as a Top Level Project

[Eason Chen]

+ 1 （non-binding）

On Sun, Apr 24, 2022 at 11:11 AM XiaoYu  wrote:
>
> + 1 （non-binding）
>
> Looking forward to it and wishing the community better the better!
>
> Calvin Kirs  于2022年4月24日周日 11:03写道：
> >
> > +1 (binding)
> > Good to see Doris graduation!
> >
> > 陈明雨  于2022年4月24日周日 10:26写道：
> > >
> > > Dear Incubator Community,
> > >
> > > After having the discussion in Doris community[1][2], we have passed the 
> > > community vote[3].
> > >
> > > And then made a discussion in general@incubator[4]. We got a lot of 
> > > positive responses.
> > >
> > > And have responded and addressed all suggestions and comments raised.
> > >
> > >
> > >
> > >
> > > I would like to start this voting thread to request graduating the Doris 
> > > project from the incubator as a TLP.
> > >
> > > Please provide your vote as one of the following options:
> > >
> > >
> > >
> > >
> > > [ ] +1 - Recommend graduation of Apache Doris as a TLP
> > >
> > > [ ] 0 - I don't feel strongly about it, but don't object
> > >
> > > [ ] -1 - Do not recommend the graduation of Apache Doris because…
> > >
> > >
> > >
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > >
> > >
> > >
> > > The following is a brief overview of the progress of the Doris project 
> > > and community since entering the incubator:
> > >
> > > 1. Community
> > >
> > > - 9 new PPMC members were added, from five different companies, bringing 
> > > the total number of PPMC members to 22.
> > >
> > > - 20 new Committers were added (including the new PPMC members), bringing 
> > > the total number of Committers to 33.
> > >
> > > - The number of Contributors is now 305 and growing[5].
> > >
> > > - The dev@doris mailing list currently has 328 subscribers, and all major 
> > > project discussions are happening in the dev@doris.
> > >
> > >
> > >
> > >
> > > 2. Project
> > >
> > > - 7 releases by 6 release managers. All compliance issues have been 
> > > resolved.
> > >
> > > - Doris official website[6] is compliant with Apache Foundation 
> > > requirements[7].
> > >
> > > - Project maturity model is detailed in [8].
> > >
> > > - See Doris Project Incubation Status[9] for more info.
> > >
> > >
> > >
> > >
> > > [1] https://lists.apache.org/thread/90fd2pd3r6wgn4hnfdo3rd0wqkv23cgr
> > >
> > > [2] https://lists.apache.org/thread/xc5qj7m2k1ph0mc97otj0nf8vskdfrzv
> > >
> > > [3] https://lists.apache.org/thread/9yklv4vbp39jhrzbcx3qgpcs1osk3lyf
> > >
> > > [4] https://lists.apache.org/thread/nbncjl8fdq0bcjop6l4747c8x9c06q00
> > >
> > > [5] https://github.com/apache/incubator-doris
> > >
> > > [6] http://doris.incubator.apache.org/
> > >
> > > [7] https://whimsy.apache.org/pods/project/doris
> > >
> > > [8] 
> > > https://cwiki.apache.org/confluence/display/DORIS/Maturity+Assessment+for+Doris
> > >
> > > [9] https://incubator.apache.org/projects/doris.html
> > >
> > >
> > >
> > >
> > > ==
> > >
> > > Establish the Apache Doris 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 MPP-based interactive SQL data warehousing for reporting
> > >
> > > and analysis.
> > >
> > >
> > >
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > >
> > > (PMC), to be known as the "Apache Doris Project", be and hereby is
> > >
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > >
> > >
> > >
> > > RESOLVED, that the Apache Doris Project be and hereby is responsible for
> > >
> > > the creation and maintenance of software related to a MPP-based
> > >
> > > interactive SQL data warehousing for reporting and analysis; and be it
> > >
> > > further
> > >
> > >
> > >
> > >
> > > RESOLVED, that the office of "Vice President, Apache Doris" 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 Doris
> > >
> > > Project, and to have primary responsibility for management of the
> > >
> > > projects within the scope of responsibility of the Apache Doris 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 Doris Project:
> > >
> > >
> > >
> > >
> > > * Bin Ling 
> > >
> > > * Bo Wang 
> > >
> > > * Chaoyong Li 
> > >
> > > * Chun Zhao 
> > >
> > > * Conghui Cai 
> > >
> > > * Dayue Gao 
> > >
> > > * De Li 
> > >
> > > * Hangyuan Liu 
> > >
> > > * Hao Chen 
> > >
> > > * HaoPeng Li 
> > >
> > > * Jiafeng Zhang 
> > >
> > > * Kaisen Kang 
> > >
> > > * 

Re: [VOTE] Accept Kvrocks into the Apache Incubator

[Eason Chen]

+1 (non-binding)

On Fri, Apr 22, 2022 at 11:38 AM Felix Cheung  wrote:
>
> +1
>
> On Thu, Apr 21, 2022 at 7:28 PM Sheng Wu  wrote:
>
> > +1 binding
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> > Liang Chen  于2022年4月22日周五 09:19写道：
> > >
> > > +1(binding)
> > >
> > > Regards
> > > Liang
> > >
> > > 在 2022年4月20日星期三，Furkan KAMACI  写道：
> > >
> > > > Hi,
> > > >
> > > > +1 (binding)
> > > >
> > > > Kind Regards,
> > > > Furkan KAMACI
> > > >
> > > > On 20 Apr 2022 Wed at 13:49 Calvin Kirs  wrote:
> > > >
> > > > > +1 (binding)
> > > > > Good luck.
> > > > >
> > > > > 张铎(Duo Zhang)  于2022年4月20日周三 18:29写道：
> > > > > >
> > > > > > +1(binding)
> > > > > >
> > > > > > Goson zhang  于2022年4月20日周三 18:27写道：
> > > > > >
> > > > > > > +1 (non-binding)
> > > > > > >
> > > > > > > Good luck!
> > > > > > >
> > > > > > > Willem Jiang  于2022年4月20日周三 14:38写道：
> > > > > > >
> > > > > > > > +1 (binding)
> > > > > > > >
> > > > > > > > Willem Jiang
> > > > > > > >
> > > > > > > > Twitter: willemjiang
> > > > > > > > Weibo: 姜宁willem
> > > > > > > >
> > > > > > > > On Wed, Apr 20, 2022 at 7:25 AM Liang Chen <
> > > > chenliang...@apache.org>
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > Following up the [DISCUSS] thread on Kvrocks[1], I would
> > like to
> > > > > > > > > call a VOTE to accept Kvrocks into the Apache Incubator,
> > please
> > > > > check
> > > > > > > out
> > > > > > > > > the Kvrocks Proposal from the incubator wiki[2].
> > > > > > > > >
> > > > > > > > > Please cast your vote:
> > > > > > > > >
> > > > > > > > > [ ] +1, bring Kvrocks into the Incubator
> > > > > > > > > [ ] +0, I don't care either way
> > > > > > > > > [ ] -1, do not bring Kvrocks 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.
> > > > > > > > >
> > > > > > > > > [1]
> > > > > https://lists.apache.org/thread/bdtmvbmvzrgjd1kj7mdrp9tkqrhg3d31
> > > > > > > > > [2]
> > > > > > > >
> > > > >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/KvrocksProposal
> > > > > > > > >
> > > > > > > > > Regards
> > > > > > > > > Liang
> > > > > > > >
> > > > > > > > 
> > > > -
> > > > > > > > To unsubscribe, e-mail:
> > general-unsubscr...@incubator.apache.org
> > > > > > > > For additional commands, e-mail:
> > general-h...@incubator.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best wishes！
> > > > > CalvinKirs
> > > > >
> > > > > -
> > > > > 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
> >
> >

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

Re: May 2022 Podling Reporting Timeline

[Eason Chen]

EventMesh also missed for not receiving reminder email, we will  add it later.

On Fri, Apr 22, 2022 at 8:38 AM tan zhongyi  wrote:
>
> brpc also missed the pod report of April.
>
> Maybe we are too used to wait for reminder email from Justin.
>
> Anyway,  I will provide pod report in May if needed.
>
> Thanks.
>
>
>
> 发件人: Mingshen Sun 
> 日期: 星期五, 2022年4月22日 上午2:00
> 收件人: general@incubator.apache.org , 
> d...@teaclave.apache.org 
> 主题: Re: May 2022 Podling Reporting Timeline
> Hi all,
>
> I'm from the Teaclave project. I just noticed that we missed April's
> report because of the reminder issue.
>
> Should we add it in May's report also? I see some discussions here but
> no conclusion yet.
>
> For Teaclave, we have no problem with adding an additional report in May.
>
> Mingshen
>
>
> On Thu, Apr 21, 2022 at 5:29 AM John D. Ament  wrote:
> >
> > Hi Christofer
> >
> > On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz 
> > wrote:
> >
> > > Hi John,
> > >
> > > guess I missed the second part of your email ;-)
> > >
> > > Well, I am a bit unsure if we really should skip the ones that for example
> > > missed to submit last month because nobody reminded them, but I think in
> > > such a case it would be half a year of information missing. Even if this
> > > might not be too useful for the board, I think it's useful to the IPMC.
> > >
> >
> > Basically, I can't (personally) fault a podling for not reporting when no
> > reminders were sent out.  We failed to hold up our side of the agreement in
> > my mind.  It's great that some podlings still did the work to get a report
> > put together.  Perhaps we review those in the past 3 months of missed
> > reports and also report them? I'm not sure.
> >
> >
> > >
> > > So, I think podlings that missed filling in their parts in the last 3
> > > months, should still report this time. But that's just my opinion.
> > >
> >
> > I agree with you, the problem is that every podling (other than new
> > podlings possibly) has missed a report (at least from the board's point of
> > view).  While there's the main review the IPMC takes on the podlings'
> > reports, the board also reviews them.  Since the IPMC lapsed on maintaining
> > this, it may end up over burdening the board to put out a report that has
> > every single podling reporting in it.
> >
> >
> > >
> > > Chris
> > >
> > > -Original Message-
> > > From: Christofer Dutz 
> > > Sent: Donnerstag, 21. April 2022 10:42
> > > To: general@incubator.apache.org
> > > Subject: RE: May 2022 Podling Reporting Timeline
> > >
> > > I should also add that some projects have failed to submit in the last 3
> > > months, so I would add to this list:
> > >
> > > - brpc
> > > - Annotator
> > > - Crail
> > > - EventMesh
> > > - Flagon
> > > - Hivemail
> > > - InLong
> > > - Liminal
> > > - Marvin-AI
> > > - Milagro
> > > - Nemo
> > > - Pony Mail
> > > - Spot
> > > - Teaclave
> > > - Wayang
> > >
> > > So, we're also expecting these projects to report this month.
> > >
> > > Chris
> > >
> > > -Original Message-
> > > From: John D. Ament 
> > > Sent: Mittwoch, 20. April 2022 18:24
> > > To: general 
> > > Subject: May 2022 Podling Reporting Timeline
> > >
> > > Note - I'm sending this a week early per procedure as we have some catch
> > > up to do.
> > >
> > > May 2022 Incubator report timeline:
> > >
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/May2022
> > >
> > > Wed May 04 -- Podling reports due by end of day
> > > Sun May 08 -- Shepherd reviews due by end of day
> > > Sun May 08 -- Summary due by end of day
> > > Tue May 10 -- Mentor signoff due by end of day
> > > Wed May 11 -- Report submitted to Board
> > > Wed May 18 -- Board meeting
> > >
> > > According to podlings.xml, the following podlings are expected to report:
> > > - Training
> > > - Heron
> > > - Tuweni
> > > - Pagespeed
> > > - Toree
> > > - Livy
> > > - NLPCraft
> > > - Sedona
> > > - Doris
> > > - SDAP
> > > - Linkis
> > >
> > > I'm suggesting that right now we keep the current reporting periods as we
> > > the Incubator PMC have failed to report to the Board, rather than it
> > > necessarily being a failing of podlings.  If your podling is on this list
> > > but isn't present on the confluence page, please add it with the necessary
> > > sections.  i'll take a look in the next few days and make sure 
> > > podlings.xml
> > > represents reality.
> > >
> > > - John, your friendly neighborhood Report Manager
> > >
>
> -
> 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] Release Apache EventMesh (incubating) 1.4.0-rc1

[Eason Chen]

Thank you JB for your kindly reply, very much appreciated.
We will confirm the concerns with you in the private mail list.

On Mon, Mar 28, 2022 at 5:20 PM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> I checked:
> - incubating is in the name
> - LICENSE file is there
> - NOTICE file is there but I would recommend to plan to check the
> content (it seems basically empty), especially regarding the third
> party license folder
> - DISCLAIMER is almost there (named DISCLAIMER-WIP), it's related to
> license and NOTICE file, I would recommend to rename in DISCLAIMER as
> soon as NOTICE file is clean
> - build doesn't work out of the box with gradlew (Error: Could not
> find or load main class org.gradle.wrapper.GradleWrapperMain Caused
> by: java.lang.ClassNotFoundException:
> org.gradle.wrapper.GradleWrapperMain)
> - ASF headers are present in almost all files, but some files (like
> the md ones) don't have it
> - sha512 and asc are good
>
> I would suggest focusing on fixing incomplete licensing conditions and
> the NOTICE file for the next release. I will take a look at why
> gradlew doesn't work out of the box.
>
> I hesitated to vote +0 for this release, but in order to move forward,
> let's focus on the next release.
>
> Regards
> JB
>
> On Thu, Mar 24, 2022 at 7:44 AM wqliang  wrote:
> >
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache EventMesh(Incubating)
> > version 1.4.0-rc1
> >
> > The Apache EventMesh community has voted on and approved a proposal
> to
> > release
> > Apache EventMesh(Incubating) version 1.4.0-rc1
> >
> > We now kindly request the Incubator PMC members review and vote on
> this
> > incubator release.
> >
> > EventMesh community vote thread:
> > • https://lists.apache.org/thread/bjps9o00h0d861df56pcqodsrx8qx4po
> >
> > Vote result thread:
> > • https://lists.apache.org/thread/qhlqy6hdwf6z0oq20k2ygk1w8wqh1jch
> >
> > The release candidate:
> > •
> https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.4.0-rc1
> >
> > Git tag for the release:
> > • https://github.com/apache/incubator-eventmesh/tree/v1.4.0-rc1
> >
> > Release notes:
> > • https://eventmesh.apache.org/events/release-notes/v1.4.0
> >
> > The artifacts signed with PGP key
> > *9B907F6A8A5A781D36D94B858B497E274D237979*, corresponding to
> > wqli...@apache.org, that can be found in keys file:
> > • https://downloads.apache.org/incubator/eventmesh/KEYS
> >
> > The vote will be open for at least 72 hours or until the necessary
> > number of votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > On behalf of Apache EventMesh(Incubating) community
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache YuniKorn (Incubating) as a Top Level Project

[Eason Chen]

+1 (non-binding)

Regards,
Eason

On Fri, Feb 18, 2022 at 2:04 PM Brahma Reddy Battula 
wrote:

> +1 (non-binding)
>
>
>
> On Fri, 18 Feb 2022 at 11:31 AM, Lionel Liu  wrote:
>
> > +1 (binding)
> >
> > Thanks,
> > Lionel Liu
> >
> > On Fri, Feb 18, 2022 at 9:59 AM Uma gangumalla 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > Regards,
> > > Uma
> > >
> > > On Tue, Feb 15, 2022 at 9:04 PM Weiwei Yang  wrote:
> > >
> > > > Hi Incubator Community
> > > >
> > > > After the discussion in the YuniKorn community [1], and passed the
> > > > community vote [2][3]. We have started the discussion in the
> > > > general@incubator list [4]. Based on all positive feedback received,
> > we
> > > > would like to start this voting thread to request graduating the
> > YuniKorn
> > > > project from the incubator as a TLP.
> > > >
> > > > Please provide your vote as one of the following options:
> > > >
> > > > [ ] +1 - Recommend graduation of Apache YuniKorn as a TLP
> > > > [ ]  0 -  I don't feel strongly about it, but don't object
> > > > [ ] -1 - Do not recommend the graduation of Apache YuniKorn because…
> > > >
> > > > The VOTE will remain open for at least 72 hours.
> > > >
> > > > To summarize what the YuniKorn community has achieved in the
> incubating
> > > > phase:
> > > >
> > > >- 6 releases were done by 6 different releases managers.
> > > >- 41 unique code contributors and over 1300+ commits.
> > > >- A growing community that added 2 new mentors, 10 new
> committers, 4
> > > new
> > > >PPMC from 6 different organizations
> > > >- A diverse community that has 6 mentors, 23 PPMC, and 29
> committers
> > > >from at least 14 different organizations [5]
> > > >- Well documented web site [6]
> > > >- The maturity self-assessment [7]
> > > >
> > > > [1] https://lists.apache.org/thread/dno411y59g2pcy1d3kd7s3kdjz9jw65n
> > > > [2] https://lists.apache.org/thread/gx5dmb4yqkw1dfvzf2l91gwhobx6g81m
> > > > [3] https://lists.apache.org/thread/dfvdk3dc82pvopxc28h6p4wdgp0xcfk2
> > > > [4] https://lists.apache.org/thread/o8y4b3mp21f608745ngqqdhc628qtwxf
> > > > [5] https://yunikorn.apache.org/community/people
> > > > [6] https://yunikorn.apache.org/
> > > > [7] https://yunikorn.apache.org/community/maturity
> > > >
> > > >
> > > >
> > >
> >
> --
> > > >
> > > > Establish the Apache YuniKorn 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 standalone resource scheduler responsible for scheduling
> > > > batch jobs and long-running services on large scale distributed
> systems
> > > > running in on-premises environments as well as different public
> clouds.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > (PMC), to be known as the "Apache YuniKorn Project", be and hereby is
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache YuniKorn Project be and hereby is
> responsible
> > > > for the creation and maintenance of software related to a standalone
> > > > resource scheduler responsible for scheduling batch jobs and
> > > > long-running services on large scale distributed systems running in
> > > > on-premises environments as well as different public clouds; and be
> it
> > > > further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache YuniKorn" 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
> YuniKorn
> > > > Project, and to have primary responsibility for management of the
> > > > projects within the scope of responsibility of the Apache YuniKorn
> > > > 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 YuniKorn
> > > > Project:
> > > >
> > > >  * Akhil PB
> > > >  * Arun Suresh 
> > > >  * Carlo Curino
> > > >  * Chaoran Yu  
> > > >  * Chenya Zhang
> > > >  * Craig Condit
> > > >  * DB Tsai 
> > > >  * Felix Cheung
> > > >  * Holden Karau
> > > >  * Jason Darrell Lowe  
> > > >  * Jonathan Hung   
> > > >  * Junping Du  
> > > >  * Kinga Marton
> > > >  * Konstantinos Karanasos  
> > > >  * Luciano Resende 
> > > >  * Subramaniam Krishnan
> > > >  * Sunil G 
> > > >  * Tao Yang
> > > >  * Vinod Kumar Vavilapalli 
> > > 

Re: [VOTE] Release Apache Linkis (Incubating) 1.0.3-RC2

[Eason Chen]

+1 ,

I have checked the following items:
[ok] Incubating in name
[ok] LICENSE and NOTICE are correct
[ok] DISCLAIMER-WIP exists
[ok] All links are valid
[ok] No compiled archives bundled in the source archive.

Best regards,
Eason Chen

On Wed, Jan 26, 2022 at 3:33 PM Qiang Yin  wrote:

> +1 (non-binding)
>
> I checked:
> [ok] Download links are valid.
> [ok] Checksums and PGP signatures are valid.
> [ok] Source code distributions have correct names matching the current
> release.
> [ok] LICENSE and NOTICE files are correct for each Linkis repo.
> [ok] All files have license headers if necessary.
> [ok] No compiled archives bundled in source archive.
> [yes] Can compile from source.
>
> On 2022/01/26 04:04:00 heng du wrote:
> > +1
> >
> > [ok] Download links are valid.
> > [ok] Source code distributions have correct names matching the current
> > release.
> > [ok] LICENSE and NOTICE files are correct for each Linkis repo.
> > [ok] All files have license headers if necessary.
> > [ok] No compiled archives bundled in the source archive.
> >
> >
> > Xun Liu  于2022年1月26日周三 09:44写道：
> >
> > > +1 (binding) from me,
> > >
> > > I have checked the following items:
> > > - Incubating in name
> > > - LICENSE and NOTICE are fine
> > > - DISCLAIMER-WIP exists
> > > - All links are valid
> > > - No unexpected binary files
> > > - All ASF files have ASF headers
> > > - Can compile from source in macOS
> > > - Checksums and PGP signatures are valid.
> > >
> > > Best regards,
> > > Xun Liu
> > >
> > > On Tue, Jan 25, 2022 at 8:22 PM peacewong 
> wrote:
> > >
> > > > +1   (non-binding)
> > > >
> > > > I checked:
> > > > [ok] Download links are valid.
> > > > [ok] Checksums and PGP signatures are valid.
> > > > [ok] Source code distributions have correct names matching the
> current
> > > > release.
> > > > [ok] LICENSE and NOTICE files are correct for each Linkis repo.
> > > > [ok] All files have license headers if necessary.
> > > > [ok] No compiled archives bundled in source archive.
> > > > [yes] Can compile from source.
> > > >
> > > > Jack™®☑™ <7956...@qq.com.invalid> 于2022年1月25日周二 15:46写道：
> > > >
> > > > > +1 (non-binding)
> > > > >
> > > > >
> > > > > I checked:
> > > > > [yes] Download links are valid.
> > > > > [yes] Checksums and PGP signatures are valid.
> > > > > [yes] Source code distributions have correct names matching the
> current
> > > > > release.
> > > > > [yes] LICENSE and NOTICE files are correct for each Linkis repo.
> > > > > [yes] All files have license headers if necessary.
> > > > > [yes] No compiled archives bundled in source archive.
> > > > > [yes] Can compile from source.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --原始邮件--
> > > > > 发件人:
> > > > >   "general"
> > > > >
>  <
> > > > > mengyoupans...@gmail.com;
> > > > > 发送时间:2022年1月25日(星期二) 下午3:18
> > > > > 收件人:"general" > > > >
> > > > > 主题:Re: [VOTE] Release Apache Linkis (Incubating) 1.0.3-RC2
> > > > >
> > > > >
> > > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > I checked:
> > > > > [yes] Download links are valid.
> > > > > [yes] Checksums and PGP signatures are valid.
> > > > > [yes] Source code distributions have correct names matching the
> current
> > > > > release.
> > > > > [yes] LICENSE and NOTICE files are correct for each Linkis repo.
> > > > > [yes] All files have license headers if necessary.
> > > > > [yes] No compiled archives bundled in source archive.
> > > > > [yes] Can compile from source.
> > > > > 在 2022年1月24日 +0800 PM11:07，Shuai Di  > > > >  Hello Incubator Community,
> > > > > 
> > > > >  The Apache Linkis community has voted and approved the
> release of
> > > > > Apache
> > > > >  Linkis(incubating) 1.0.3-RC2. We now kindly request IPMC
> mem

Re: [VOTE] Accept Hugegraph into the Apache Incubator

[Eason Chen]

+1 (non-binding)

good luck!


Goson zhang  于 2022年1月17日周一 上午9:54写道：

> +1 (non-binding)
>
> good luck!
>
> Calvin Kirs  于2022年1月17日周一 09:51写道：
>
> > +1 (non-binding)
> >
> > good luck!
> >
> > Xun Liu  于2022年1月17日周一 09:46写道：
> >
> > > +1 (binding) from me,
> > >
> > > good luck!
> > >
> > > Xun Liu
> > > Best regards,
> > >
> > > On Mon, Jan 17, 2022 at 8:51 AM tan zhongyi 
> > wrote:
> > >
> > > > +1, No binding.
> > > >
> > > >
> > > > 在 2022/1/16 上午7:22，“Willem Jiang” 写入:
> > > >
> > > > Hi all,
> > > >
> > > > Following up the [DISCUSS] thread on Hugegraph[1], I would like
> to
> > > > call a
> > > > VOTE to accept Hugegraph into the Apache Incubator.
> > > >
> > > > Please cast your vote:
> > > >
> > > >   [ ] +1, bring Hugegraph into the Incubator
> > > >   [ ] +0, I don't care either way
> > > >   [ ] -1, do not bring Hugegraph 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.
> > > >
> > > > Please check out the Hugegraph Proposal from the incubator
> wiki[2].
> > > >
> > > > [1]
> > https://lists.apache.org/thread/31k4jsgmmfhl3vggnbko1rjsmqjymh29
> > > > [2]
> > > >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/HugeGraphProposal
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > >
> >  -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail:
> general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
> >
> > --
> > Best wishes！
> > CalvinKirs
> >
>

Re: [ANNOUNCE] Apache EventMesh (incubating) 1.3.0 available

[Eason Chen]

Thanks Sebb, mikexue replied to this email with the correct link before, we
will re-announce if needed.

On Tue, Jan 4, 2022 at 8:37 PM sebb  wrote:

> It would be helpful to send a corrected announce.
>
> Also ideally set up a redirect for the incorrect link
>
> On Tue, 4 Jan 2022 at 02:15, Eason Chen  wrote:
> >
> > Thanks, Willem, we already updated it.
> >
> > On Tue, Jan 4, 2022 at 9:56 AM Willem Jiang 
> wrote:
> >
> > > The download link should be
> > >
> > > https://eventmesh.apache.org/download/
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Thu, Dec 30, 2021 at 6:49 PM sebb  wrote:
> > > >
> > > > On Thu, 30 Dec 2021 at 06:43, mikexue  wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > Apache EventMesh (incubating) Team is glad to announce the new
> release
> > > > > of Apache EventMesh (incubating) 1.3.0.
> > > > >
> > > > > Apache EventMesh (incubating) is a dynamic cloud-native eventing
> > > > > infrastructure used to decouple the application and backend
> middleware
> > > > > layer, which supports a wide range of use cases that encompass
> complex
> > > > > multi-cloud, widely distributed topologies using diverse technology
> > > > > stacks.
> > > > >
> > > > > Download Links:
> > > https://eventmesh.apache.org/projects/eventmesh/download/
> > > >
> > > > Link does not work.
> > > >
> > > > > Release Notes:
> > > https://eventmesh.apache.org/events/release-notes/v1.3.0/
> > > > >
> > > > > Website: https://eventmesh.apache.org/
> > > > >
> > > > > EventMesh Resources:
> > > > > - Issue: https://github.com/apache/incubator-eventmesh/issues
> > > > > - Mailing list: d...@eventmesh.apache.org
> > > > >
> > > > > Apache EventMesh (incubating) Team
> > > > >
> > > > >
> -
> > > > > 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
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@eventmesh.apache.org
> > > For additional commands, e-mail: dev-h...@eventmesh.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [ANNOUNCE] Apache EventMesh (incubating) 1.3.0 available

[Eason Chen]

Thanks, Willem, we already updated it.

On Tue, Jan 4, 2022 at 9:56 AM Willem Jiang  wrote:

> The download link should be
>
> https://eventmesh.apache.org/download/
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Dec 30, 2021 at 6:49 PM sebb  wrote:
> >
> > On Thu, 30 Dec 2021 at 06:43, mikexue  wrote:
> > >
> > > Hi all,
> > >
> > > Apache EventMesh (incubating) Team is glad to announce the new release
> > > of Apache EventMesh (incubating) 1.3.0.
> > >
> > > Apache EventMesh (incubating) is a dynamic cloud-native eventing
> > > infrastructure used to decouple the application and backend middleware
> > > layer, which supports a wide range of use cases that encompass complex
> > > multi-cloud, widely distributed topologies using diverse technology
> > > stacks.
> > >
> > > Download Links:
> https://eventmesh.apache.org/projects/eventmesh/download/
> >
> > Link does not work.
> >
> > > Release Notes:
> https://eventmesh.apache.org/events/release-notes/v1.3.0/
> > >
> > > Website: https://eventmesh.apache.org/
> > >
> > > EventMesh Resources:
> > > - Issue: https://github.com/apache/incubator-eventmesh/issues
> > > - Mailing list: d...@eventmesh.apache.org
> > >
> > > Apache EventMesh (incubating) Team
> > >
> > > -
> > > 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
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@eventmesh.apache.org
> For additional commands, e-mail: dev-h...@eventmesh.apache.org
>
>

Re: [ANNOUNCE] Apache EventMesh (incubating) 1.3.0 available

[Eason Chen]

Thanks Goson for your kindly support!


On Thu, Dec 30, 2021 at 4:18 PM Goson zhang  wrote:

> Congrats！
>
> mikexue  于2021年12月30日周四 14:43写道：
>
> > Hi all,
> >
> > Apache EventMesh (incubating) Team is glad to announce the new release
> > of Apache EventMesh (incubating) 1.3.0.
> >
> > Apache EventMesh (incubating) is a dynamic cloud-native eventing
> > infrastructure used to decouple the application and backend middleware
> > layer, which supports a wide range of use cases that encompass complex
> > multi-cloud, widely distributed topologies using diverse technology
> > stacks.
> >
> > Download Links:
> https://eventmesh.apache.org/projects/eventmesh/download/
> >
> > Release Notes: https://eventmesh.apache.org/events/release-notes/v1.3.0/
> >
> > Website: https://eventmesh.apache.org/
> >
> > EventMesh Resources:
> > - Issue: https://github.com/apache/incubator-eventmesh/issues
> > - Mailing list: d...@eventmesh.apache.org
> >
> > Apache EventMesh (incubating) Team
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [ANNOUNCE] Release Apache InLong(incubating) 0.12.0-incubating

[Eason Chen]

Congrats！

On Thu, Dec 30, 2021 at 10:45 AM heng du  wrote:

> Congrats！
>
> Goson zhang  于2021年12月30日周四 10:32写道：
>
> > Hi all,
> >
> > The Apache InLong(incubating) community is pleased to announce
> > that Apache InLong(incubating) 0.12.0-incubating has been released!
> >
> > Apache InLong is a one-stop data streaming platform that provides
> > automatic, secure,
> > distributed, and efficient data publishing and subscription capabilities.
> > This platform helps you easily build stream-based data applications.
> >
> > Download Links: https://inlong.apache.org/download/main
> >
> > Release Notes: https://inlong.apache.org/download/release-0.12.0
> >
> > Website: https://inlong.apache.org/
> >
> > InLong Resources:
> > - Issue: https://github.com/apache/incubator-inlong/issues
> > - Mailing-list: d...@inlong.apache.org
> >
> > Thanks
> > On behalf of Apache InLong(Incubating) community
> >
>

Re: [ANNOUNCE] Release Apache EventMesh(incubating) 1.2.0

[Eason Chen]

Hi, Mike

It may be misunderstood, You need to call a VOTE in the general mail list
too, not just PMC.

Thanks,
Eason

On Fri, Jul 9, 2021 at 9:56 AM mikexue  wrote:

> Hi Sheng Wu,
> The IPMC vote for the EventMesh release can find in below url, please
> take a look.
>
> https://lists.apache.org/list.html?d...@eventmesh.apache.org
>
> Thanks,
> mikexue
>
> Sheng Wu  于2021年7月9日周五 上午12:02写道：
> >
> > Hi EventMesh team
> >
> > I can NOT find the IPMC vote for the EventMesh release for the last 3
> > months, no matter which version.
> >
> >
> https://lists.apache.org/list.html?general@incubator.apache.org:lte=3M:EventMesh
> >
> > Is there a vote passed?
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> >
> > mikexue  于2021年7月8日周四 下午8:49写道：
> >
> > > Hi all,
> > >
> > > The Apache EventMesh team would like to announce the release of Apache
> > > Mesh(incubating) 1.2.0.
> > >
> > > Brief features of this release:
> > > 1.Support rocketmq as store
> > > 2.Support Spi for extended implementation to accommodate a variety of
> > > eventstore
> > > 3.Support http pub/sub ,heartbeat manage and subscribe manage
> > > 4.Support running eventmesh in docker
> > >
> > > More details regarding Apache EventMesh can be found at:
> > > https://eventmesh.apache.org/
> > >
> > > The release artifacts can be downloaded here:
> > > https://dist.apache.org/repos/dist/release/incubator/eventmesh/1.2.0
> > >
> > > The release notes can be found here:
> > > https://github.com/apache/incubator-eventmesh/releases/tag/v1.2.0
> > >
> > > Thanks,
> > > The Apache EventMesh Team
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@eventmesh.apache.org
> For additional commands, e-mail: dev-h...@eventmesh.apache.org
>
>

[RESULT][VOTE] Accept EventMesh into Apache Incubator

[Eason Chen]

Hi All,

The VOTE has PASSED and closed now.
The results are as follows:

[9] +1 Binding votes
- Junping Du
- Willem Jiang
- Von Gosling
- Francois Papon
- Jean-Baptiste Onofre
- Ted Liu
- Furkan KAMACI
- Dave Fisher
- Vinayakumar B

[ 0 ] +0  Votes
[ 0 ] -1  Votes

[10] +1 Non-binding votes
- Heng Du
- Jun Yang
- Goson Zhang
- Shannon Ding
- Tison
- Zhongyi Tan
- Jaskey Lam
- Juan Pan
- Alexander Alten
- Lidong Dai

[ 0 ] +0  Votes
[ 0 ] -1  Votes

Discuss thread:
https://lists.apache.org/thread.html/rcb4bc1e5b4994d377aba4191737ff7c1f7e375fb9044cfbebe236e95%40%3Cgeneral.incubator.apache.org%3E

Vote thread:
https://lists.apache.org/thread.html/r510badf68892968ca71b2639723c7279f6a097649243f0982c1c1143%40%3Cgeneral.incubator.apache.org%3E

Thanks for everyone to help checked and voted to EventMesh.

Thanks.

Best wishes！
Eason Chen

Re: [DISCUSS] EventMesh Proposal

[Eason Chen]

Hi,

"*On one hand we don’t have a policy that say you must have to have done a
name search before becoming a piddling, on the other changing a name does
incur a large community cost and Infra would prefer that podlings don’t
change names. Most podlings do the name search just before graduation. In a
lot of cases it fairly obvious there is not going to be an issue, with a
generic name like this it may be best to wait until the name is approved
before calling the results of the vote.*"
Thanks for Justin's clarification, i also want to add a few words:

I'm sorry, my words caused unnecessary confusion. I am still following up
on this issue[1]. I must admit that this name is a very serious problem. By
reading Apache’s regulations [2], I found that "*the original Podding
proposal established a working name for the new Podding. During the
election process, there are often discussions and filtering of suitable
names, but the proposed name is not final, just temporary*"
I am tring my best  to ensure that it is resolved before the formal
incubation.

[1]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-188? filter =
-4 = project%20%3D%20PODLINGNAMESEARCH%20order%20by%20created%20DESC
[2]: http://incubator.apache.org/guides/names.html


On Tue, Feb 2, 2021 at 5:14 PM Alexander Alten  wrote:

> Hi,
>
> Fully agree with Justin, we from Wayang had the same problem. We
> renamed the project before we submitted the proposal, and we
> documented everything.
> I’d encourage you to find a name which is TM ready in the US, India,
> CN and EU (if possible). You can’t graduate (or better it is unlikely)
> if a project name is not protectable by the ASF. And changing the
> whole INFRA after a podling is voted into the incubator is a huge
> effort.
>
> --alex
>
> On Tue, Feb 2, 2021 at 9:52 AM Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > On one hand we don’t have a policy that say you must have to have done a
> name search before becoming a piddling, on the other changing a name does
> incur a large community cost and Infra would prefer that podlings don’t
> change names. Most podlings do the name search just before graduation. In a
> lot of cases it fairly obvious there is not going to be an issue, with a
> generic name like this it may be best to wait until the name is approved
> before calling the results of the vote.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Accept EventMesh into Apache Incubator

[Eason Chen]

Hi,

After the discussion of EventMesh proposal (discussion thread is here[1]),
I would like to call a VOTE to accept it into the Apache Incubator.

Please cast your vote:

  [ ] +1, bring EventMesh into Incubator
  [ ] +0, I don't care either way
  [ ] -1, do not bring EventMesh into Incubator, because...

The vote will open at least for 72 hours and only votes from the Incubator
PMC are binding.

The project's proposal is available at [2].

[1]
https://lists.apache.org/thread.html/rcb4bc1e5b4994d377aba4191737ff7c1f7e375fb9044cfbebe236e95%40%3Cgeneral.incubator.apache.org%3E
[2]https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal

Re: [DISCUSS] EventMesh Proposal

[Eason Chen]

All problems and risks seem to be well clarified and resolved. Next, I will
initiate a vote, thank you for your attention and continued participation.

Regards,
Eason

On Thu, Jan 28, 2021 at 1:00 PM Dave Fisher  wrote:

> Exactly. Here’s a link -
> https://www.apache.org/foundation/marks/naming.html#namesearch
>
> It’s available from here -
> https://incubator.apache.org/guides/names.html#podling_suitable_name_search
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Jan 27, 2021, at 7:42 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > To help trademarks it would bee best if you provided them with some
> search results as described here. [1] Have a look at a couple of the other
> recent polling name search JIRAs to get a good idea of what is needed.
> >
> > Thanks,
> > Justin
> >
> > 1. http://incubator.apache.org/guides/names.html
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>

Re: [DISCUSS] EventMesh Proposal

[Eason Chen]

Thank you for your correction, a PODLINGNAMESEARCH issue has been created
and followed up.
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-188

On Thu, Jan 28, 2021 at 9:21 AM Dave Fisher  wrote:

>
>
> > On Jan 27, 2021, at 4:58 PM, vongosling  wrote:
> >
> > Agree to raise this issue, even before podling starts. Initial teams
> need
> > to follow up on this potential problem[1]. Let's see how things go :-)
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-21353
>
> No! Naming is not an INFRA issue. Please see my other note.
>
> >
> > Matt Sicker  于2021年1月28日周四 上午12:35写道：
> >
> >> It's typically a good idea to figure out your project name early on.
> >> If you have to change the name before graduation in order to get a
> >> trademark, then that wastes the momentum gathered under the old name.
> >> That can always happen after the podling boots up, though.
> >>
> >>> On Wed, 27 Jan 2021 at 07:44, Sheng Wu 
> wrote:
> >>>
> >>> This is just a reminder, not an instruction.
> >>> The naming search and approval will officially happen when you are
> >> powerful
> >>> enough to graduate.
> >>> Personally, I would like to see this as a potential risk, not just
> >>> regarding Solace.
> >>>
> >>> Of course, this is your option. you should know, if you can't get
> >> approval
> >>> in the future, you will have a much bigger branding hurt.
> >>> (You don't need to convince me)
> >>>
> >>> Sheng Wu 吴晟
> >>> Twitter, wusheng1108
> >>>
> >>>
> >>> ShannonDing  于2021年1月27日周三 下午9:23写道：
> >>>
> >>>>
> >>>>
> >>>> I would like to make a comments about this serious problem too,
> >>>> In order not to cause unnecessary trouble in the future, we also
> >> request
> >>>> the infra member from apache to help check whether this name is
> >>>> appropriate[1].
> >>>> For us, we have used the name EventMesh for a long time, and we want
> to
> >>>> keep it so that users can get better product positioning from this
> >> name.
> >>>> According to this document[2], we also searched in the US Patent
> >> Office[3]
> >>>> and found no non-compliance.
> >>>>
> >>>>
> >>>> [1] https://issues.apache.org/jira/browse/INFRA-21353
> >>>> [2] https://incubator.apache.org/guides/names.html
> >>>> [3] https://www.uspto.gov/trademark
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On 01/27/2021 21:11，Eason Chen wrote：
> >>>> @Sheng Wu
> >>>> thank you for your kindly reminder. I would like to clarify this
> >> concerns.
> >>>>
> >>>> As @Duane Pauls  clarified this before:
> >>>> “*I work for Solace and have consulted internally to confirm that we
> >> do not
> >>>> have any copyright or trademark on the term “Event Mesh”. It’s true it
> >> is
> >>>> something our products are closely aligned with。 Solace does not
> >> oppose the
> >>>> term being used in other applicable products or projects.*”
> >>>> Solace do not  have any copyright or trademark on the term “Event
> >> Mesh”.
> >>>>
> >>>> On Wed, Jan 27, 2021 at 5:17 PM Sheng Wu 
> >>>> wrote:
> >>>>
> >>>> Hi
> >>>>
> >>>> I want to send a reminder for your project name chosen.
> >>>> Event Mesh is widely used as a concept and term, you could find it
> >> through
> >>>> Google search,
> >> https://www.google.com/search?q=event+mesh=event+mesh
> >>>>
> >>>> Sheng Wu 吴晟
> >>>> Twitter, wusheng1108
> >>>>
> >>>>
> >>>>  于2021年1月27日周三 下午5:12写道：
> >>>>
> >>>> Hi,
> >>>>
> >>>> Yes, it looks very promising.
> >>>>
> >>>> I will be very happy to help in the incubation process and integrate
> >> the
> >>>> project into Karaf with JB ;)
> >>>>
> >>>> regards,
> >>>>
> >>>> François
> >>>> fpa...@apache.org
> >>>>
> >>>> Le 27/01/2021 à 10:07, vongosling a écrit :
> >>>> Hi,
>

Re: [DISCUSS] EventMesh Proposal

[Eason Chen]

Hi,
I am honored that JB and François are willing to help the eventmesh
project. I will soon initiate a discussion on evaluating Karaf 5 in the
community.

regards,
Eason Chen

On Wed, Jan 27, 2021 at 8:54 PM  wrote:

> +1 for me to be mentor on the project :)
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 27/01/2021 à 13:50, Jean-Baptiste Onofre a écrit :
> > If you are open to evaluate/PoC EventMesh with Karaf (especially, Karaf
> 5 would be a prefect candidate), you can count on me !
> >
> > I would be more than happy to be mentor on EventMesh if you think it
> would be helpful.
> >
> > Thanks !
> > Regards
> > JB
> >
> >> Le 27 janv. 2021 à 13:47, Eason Chen  a
> écrit :
> >>
> >> Thanks to the attention of @JB and @François,
> >> I have to admit that Karaf's lightweight operating environment, hot
> >> deployment, dynamic configuration, and safe and rich management
> functions
> >> are indeed very helpful to help developers and users deploy applications
> >> more flexibly. We will further investigate the feasibility of Karaf
> >> becoming EventMesh's runtime container and look forward to the
> integration
> >> of the two products. By the way, I would like to know if @JB and
> @François
> >> are interested in becoming EventMesh mentors to help the project develop
> >> better?
> >>
> >> On Wed, Jan 27, 2021 at 5:12 PM  wrote:
> >>
> >>> Hi,
> >>>
> >>> Yes, it looks very promising.
> >>>
> >>> I will be very happy to help in the incubation process and integrate
> the
> >>> project into Karaf with JB ;)
> >>>
> >>> regards,
> >>>
> >>> François
> >>> fpa...@apache.org
> >>>
> >>> Le 27/01/2021 à 10:07, vongosling a écrit :
> >>>> Hi,
> >>>>
> >>>> This is a very young but promising project. The team attached great
> >>>> importance to this project according to the feedback given by
> >>> communities.
> >>>> Through the efforts of the last five months, I am glad to see positive
> >>>> changes in the project and community.
> >>>>
> >>>> @Jean-Baptiste Onofré   EventMesh really need
> >>>> to improve its lighter plugin modules, karaf may be a good optional
> >>>>
> >>>> Best Regards,
> >>>> Von Gosling
> >>>>
> >>>> Jean-Baptiste Onofre  于2021年1月27日周三 下午4:43写道：
> >>>>
> >>>>> Hi Eason,
> >>>>>
> >>>>> That’s an interesting proposal, indeed.
> >>>>>
> >>>>> I would rewrite some part of the proposal, but overall good.
> >>>>>
> >>>>> I will check if the EventMesh architecture is "pluggable", meaning
> that
> >>> we
> >>>>> "could" replace RocketMQ with another messaging/async provider.
> >>>>>
> >>>>> Anyway, if you need some help on the project, please let me know,
> it’s
> >>>>> interesting and could be a good extend to Apache Karaf for instance.
> >>>>>
> >>>>> Regards
> >>>>> JB
> >>>>>
> >>>>>> Le 27 janv. 2021 à 09:32, Eason Chen  a
> >>>>> écrit :
> >>>>>> Good time of the time to all!
> >>>>>>
> >>>>>> I'd like to bring this new interesting project for the discussion,
> >>>>> comments
> >>>>>> and feedback with the aim of starting a formal [VOTE] of its
> acceptance
> >>>>>> into Incubator.
> >>>>>>
> >>>>>> People behind this project aren't new to Apache: some of them were
> >>> behind
> >>>>>> the Apache RocketMQ, which I consider a huge success(especially in
> >>> China)
> >>>>>> as the community is literally thriving almost 5 years after the
> >>>>> graduation.
> >>>>>> I have been involved a little bit with this project when it just
> >>> started
> >>>>> in
> >>>>>> WeBank a few years ago. And I'd like to emphasize that the community
> >>>>>> however small it might look so far, has been aligned with Apache
> ways
> >>> of
> >>>>>> doing things. Von Gosling is very instrume

Re: [DISCUSS] EventMesh Proposal

[Eason Chen]

@Sheng Wu
thank you for your kindly reminder. I would like to clarify this concerns.

As @Duane Pauls  clarified this before:
“*I work for Solace and have consulted internally to confirm that we do not
 have any copyright or trademark on the term “Event Mesh”. It’s true it is
something our products are closely aligned with。 Solace does not oppose the
term being used in other applicable products or projects.*”
>> Solace do not  have any copyright or trademark on the term “Event Mesh”.

On Wed, Jan 27, 2021 at 5:17 PM Sheng Wu  wrote:

> Hi
>
> I want to send a reminder for your project name chosen.
> Event Mesh is widely used as a concept and term, you could find it through
> Google search, https://www.google.com/search?q=event+mesh=event+mesh
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
>  于2021年1月27日周三 下午5:12写道：
>
> > Hi,
> >
> > Yes, it looks very promising.
> >
> > I will be very happy to help in the incubation process and integrate the
> > project into Karaf with JB ;)
> >
> > regards,
> >
> > François
> > fpa...@apache.org
> >
> > Le 27/01/2021 à 10:07, vongosling a écrit :
> > > Hi,
> > >
> > > This is a very young but promising project. The team attached great
> > > importance to this project according to the feedback given by
> > communities.
> > > Through the efforts of the last five months, I am glad to see positive
> > > changes in the project and community.
> > >
> > > @Jean-Baptiste Onofré   EventMesh really need
> > > to improve its lighter plugin modules, karaf may be a good optional
> > >
> > > Best Regards,
> > > Von Gosling
> > >
> > > Jean-Baptiste Onofre  于2021年1月27日周三 下午4:43写道：
> > >
> > >> Hi Eason,
> > >>
> > >> That’s an interesting proposal, indeed.
> > >>
> > >> I would rewrite some part of the proposal, but overall good.
> > >>
> > >> I will check if the EventMesh architecture is "pluggable", meaning
> that
> > we
> > >> "could" replace RocketMQ with another messaging/async provider.
> > >>
> > >> Anyway, if you need some help on the project, please let me know, it’s
> > >> interesting and could be a good extend to Apache Karaf for instance.
> > >>
> > >> Regards
> > >> JB
> > >>
> > >>> Le 27 janv. 2021 à 09:32, Eason Chen  a
> > >> écrit :
> > >>> Good time of the time to all!
> > >>>
> > >>> I'd like to bring this new interesting project for the discussion,
> > >> comments
> > >>> and feedback with the aim of starting a formal [VOTE] of its
> acceptance
> > >>> into Incubator.
> > >>>
> > >>> People behind this project aren't new to Apache: some of them were
> > behind
> > >>> the Apache RocketMQ, which I consider a huge success(especially in
> > China)
> > >>> as the community is literally thriving almost 5 years after the
> > >> graduation.
> > >>> I have been involved a little bit with this project when it just
> > started
> > >> in
> > >>> WeBank a few years ago. And I'd like to emphasize that the community
> > >>> however small it might look so far, has been aligned with Apache ways
> > of
> > >>> doing things. Von Gosling is very instrumental in tirelessly helping
> > this
> > >>> group to learn what it means to be a truly open source project.
> > >>>
> > >>> The code is already under ALv2 and is publicly available. As you will
> > see
> > >>> it has a lot of dependency connections with the rest of Apache
> > ecosystem
> > >>> and IMO will fit very well here and continue to grow the community.
> > >>>
> > >>> By the way, we still need 1 to 2 mentors, please let me know if you
> are
> > >>> interested.
> > >>>
> > >>> With best regards,
> > >>>
> > >>> The project's proposal is available at [1].
> > >>>
> > >>> Thank you very much for the feedback you're willing to provide!
> > >>>
> > >>> Eason Chen
> > >>>
> > >>> [1]
> > >>
> > >>
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] EventMesh Proposal

[Eason Chen]

Thanks to the attention of @JB and @François,
I have to admit that Karaf's lightweight operating environment, hot
deployment, dynamic configuration, and safe and rich management functions
are indeed very helpful to help developers and users deploy applications
more flexibly. We will further investigate the feasibility of Karaf
becoming EventMesh's runtime container and look forward to the integration
of the two products. By the way, I would like to know if @JB and @François
are interested in becoming EventMesh mentors to help the project develop
better?

On Wed, Jan 27, 2021 at 5:12 PM  wrote:

> Hi,
>
> Yes, it looks very promising.
>
> I will be very happy to help in the incubation process and integrate the
> project into Karaf with JB ;)
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 27/01/2021 à 10:07, vongosling a écrit :
> > Hi,
> >
> > This is a very young but promising project. The team attached great
> > importance to this project according to the feedback given by
> communities.
> > Through the efforts of the last five months, I am glad to see positive
> > changes in the project and community.
> >
> > @Jean-Baptiste Onofré   EventMesh really need
> > to improve its lighter plugin modules, karaf may be a good optional
> >
> > Best Regards,
> > Von Gosling
> >
> > Jean-Baptiste Onofre  于2021年1月27日周三 下午4:43写道：
> >
> >> Hi Eason,
> >>
> >> That’s an interesting proposal, indeed.
> >>
> >> I would rewrite some part of the proposal, but overall good.
> >>
> >> I will check if the EventMesh architecture is "pluggable", meaning that
> we
> >> "could" replace RocketMQ with another messaging/async provider.
> >>
> >> Anyway, if you need some help on the project, please let me know, it’s
> >> interesting and could be a good extend to Apache Karaf for instance.
> >>
> >> Regards
> >> JB
> >>
> >>> Le 27 janv. 2021 à 09:32, Eason Chen  a
> >> écrit :
> >>> Good time of the time to all!
> >>>
> >>> I'd like to bring this new interesting project for the discussion,
> >> comments
> >>> and feedback with the aim of starting a formal [VOTE] of its acceptance
> >>> into Incubator.
> >>>
> >>> People behind this project aren't new to Apache: some of them were
> behind
> >>> the Apache RocketMQ, which I consider a huge success(especially in
> China)
> >>> as the community is literally thriving almost 5 years after the
> >> graduation.
> >>> I have been involved a little bit with this project when it just
> started
> >> in
> >>> WeBank a few years ago. And I'd like to emphasize that the community
> >>> however small it might look so far, has been aligned with Apache ways
> of
> >>> doing things. Von Gosling is very instrumental in tirelessly helping
> this
> >>> group to learn what it means to be a truly open source project.
> >>>
> >>> The code is already under ALv2 and is publicly available. As you will
> see
> >>> it has a lot of dependency connections with the rest of Apache
> ecosystem
> >>> and IMO will fit very well here and continue to grow the community.
> >>>
> >>> By the way, we still need 1 to 2 mentors, please let me know if you are
> >>> interested.
> >>>
> >>> With best regards,
> >>>
> >>> The project's proposal is available at [1].
> >>>
> >>> Thank you very much for the feedback you're willing to provide!
> >>>
> >>> Eason Chen
> >>>
> >>> [1]
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[DISCUSS] EventMesh Proposal

[Eason Chen]

Good time of the time to all!

I'd like to bring this new interesting project for the discussion, comments
and feedback with the aim of starting a formal [VOTE] of its acceptance
into Incubator.

People behind this project aren't new to Apache: some of them were behind
the Apache RocketMQ, which I consider a huge success(especially in China)
as the community is literally thriving almost 5 years after the graduation.

I have been involved a little bit with this project when it just started in
WeBank a few years ago. And I'd like to emphasize that the community
however small it might look so far, has been aligned with Apache ways of
doing things. Von Gosling is very instrumental in tirelessly helping this
group to learn what it means to be a truly open source project.

The code is already under ALv2 and is publicly available. As you will see
it has a lot of dependency connections with the rest of Apache ecosystem
and IMO will fit very well here and continue to grow the community.

By the way, we still need 1 to 2 mentors, please let me know if you are
interested.

With best regards,

The project's proposal is available at [1].

Thank you very much for the feedback you're willing to provide!

Eason Chen

[1] https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Hi,
Many previous developments took place internally, but from the perspective of 
contributors, there have been more and more users, at least now oppo, alibaba, 
etc. users are participating in the contribution. I believe that with the help 
of the instructor, we have a better understanding of building the community. I 
think we are ready to enter apache instead of a temporary interest.


Thanks,
Eason




----
??: 
   "general"

https://github.com/WeBankFinTech/EventMesh

Willem Jiang

Twitter: willemjiang
Weibo: willem

On Sat, Aug 15, 2020 at 9:09 AM Eason Chen https://github.com/WeBankFinTech/EventMesh/issues
 [2]https://github.com/WeBankFinTech/EventMesh/issues/5

 Willem Jiang

 Twitter: willemjiang
 Weibo: willem


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

Re: [DISCUSS] EventMesh Proposal

[Eason Chen]

Hi,
All code of the project will be donated to ASF. There were some inconsistencies 
when the project was just open source, but now it is developed based on the 
github version.


Thanks,
Eason


-- Original --
From:   
 "general"  
  

?????? [CANCEL-VOTE] Accept EventMesh into Apache Incubator

[Eason Chen]

Hi,
Because there are some issues that have not been clarified, I cancel the voting 
first, and I will restart the process after all the issues are clarified.


Thanks,
Eason


----
??: 
   "general"

https://lists.apache.org/thread.html/r12b7357f2a9458e6d6719558f36c0bbf7f786771d1f727848d5170b4%40%3Cgeneral.incubator.apache.org%3E
 [2]https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Hi,


After the project was open sourced, we did not conduct evangelism, and the 
internal version iterations were not synchronized in time. Many of these issues 
and prs were raised by many of our partners, and many of them were not 
reflected on github. Some document changes were also requested by them, It is 
not very irregular at present, but we will run the standardized mechanism later.


Thanks,
Eason




----
??: 
   "general"

https://github.com/WeBankFinTech/EventMesh/issues
[2]https://github.com/WeBankFinTech/EventMesh/issues/5

Willem Jiang

Twitter: willemjiang
Weibo: willem

On Fri, Aug 14, 2020 at 7:42 PM Eason Chen 

[VOTE] Accept EventMesh into Apache Incubator

[Eason Chen]

Hi,


After the discussion of EventMesh proposal (discussion thread is here[1]),
I would like to call a VOTE to accept it into the Apache Incubator.


Please cast your vote:


 [ ] +1, bring EventMesh into Incubator
 [ ] +0, I don't care either way
 [ ] -1, do not bring EventMesh into Incubator, because...


The vote will open at least for 72 hours and only votes from the Incubator PMC 
are binding.



The project's proposal is available at [2].


[1]https://lists.apache.org/thread.html/r12b7357f2a9458e6d6719558f36c0bbf7f786771d1f727848d5170b4%40%3Cgeneral.incubator.apache.org%3E
[2]https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Thanks for your continued attention.
As i mentened before in my first discuss "And I'd like to emphasize that the 
community however small it might look so far",if there are seemingly 
inaccurate descriptions in the proposal, I can modify it as needed.




----
??: 
   "general"

https://incubator.apache.org/guides/names.html
 gt; amp;gt; amp;amp;gt; amp;amp;amp;gt; [2]
 https://www.uspto.gov/trademark
 gt <https://www.uspto.gov/trademarkgt;; amp;gt; 
amp;amp;gt;
 amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; amp;amp;amp;gt; Thanks
 gt; amp;gt; amp;amp;gt; amp;amp;amp;gt; Henry
 gt; amp;gt; amp;amp;gt; amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; amp;amp;amp;gt; Michael Andr?? 
Pearce <
 gt; michael.andre.pea...@me.com
 gt; amp;gt; .invalidamp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; ??2020??8??6??
 gt; amp;gt; amp;amp;gt; amp;amp;amp;gt; 3:33??
 gt; amp;gt; amp;amp;gt; amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; Hi
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; Im PMC member
 from ActiveMQ project.
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; I like the
 idea, nice. +1 on it as
 gt; a project idea.
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; I am though a
 little -1 on the name
 gt; of the project,
 gt; amp;gt; I would
 gt; amp;gt; amp;amp;gt; recommend
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; that an
 alternative name for the
 gt; project is found as
 gt; amp;gt; there maybe
 gt; amp;gt; amp;amp;gt; a conflict
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; in rights
 ability to copyright and
 gt; trademark to it.
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; I??m aware
 there is a commercial
 gt; vendor messaging
 gt; amp;gt; company called
 gt; amp;gt; amp;amp;gt; Solace,
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; where they use
 and market their
 gt; product with heavy
 gt; amp;gt; use of the
 gt; amp;gt; amp;amp;gt; name Event
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; Mesh, you can
 see this just
 gt; googling event mesh,
 gt; amp;gt; brings back many
 gt; amp;gt; amp;amp;gt; hits to
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; their
 products, marketing material
 gt; and other
 gt; amp;gt; records, so they may
 gt; amp;gt; amp;amp;gt; hold a
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; heavy claim to
 this name.
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; Best
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; Michael
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt; On 4 Aug 2020, at
 gt; 18:33, Kevin Ratnasekera <
 gt; amp;gt; amp;amp;gt; 
djkevincr1...@gmail.comamp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; wrote:
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt; Hi Easen,
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt; +1, Having worked in a
 gt; similar domain so
 gt; amp;gt; far, I have to say
 gt; amp;gt; amp;amp;gt; this is an
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt; interesting project.
 gt; If you are seeking new
 gt; amp;gt; mentors, please
 gt; amp;gt; amp;amp;gt; consider
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt; adding
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt; me as a mentor to the
 gt; project.
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt; Regards
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt; Kevin
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt; On Tue, Aug 4, 2020 at
 gt; 3:34 PM Eason Chen <
 gt; amp;gt; amp;amp;gt; 
daerduoc...@qq.comamp;amp;amp;gt; wrote:
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt;amp;amp;amp;gt; Good time
 gt; of the time to all!
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt;amp;amp;amp;gt;
 gt; amp;gt; amp;amp;gt; 
amp;amp;amp;gt;amp;amp;amp;gt;
 amp;amp;amp;gt;amp;

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Thanks Justin, and can not agree more.


Thanks everyone for your attention to this project and your valuable comments.


If everyone has no problems, i will initiate the voting processs later.


Thanks,
Eason


--  --
??: 
   "general"

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Hi,
Maybe a bit misunderstood, what I am trying to explain is that even if the 
project is really in its infancy, it does not prevent the building under apache 
way. In fact, many apache projects are built from 0. And mentors also don't 
think this is a big problem.


Thanks,
Eason


----
??: 
   "general"

https://incubator.apache.org/guides/names.html
 gt; amp;gt; amp;amp;gt; [2] https://www.uspto.gov/trademark
 gt; amp;gt; amp;amp;gt;
 gt; amp;gt; amp;amp;gt; Thanks
 gt; amp;gt; amp;amp;gt; Henry
 gt; amp;gt; amp;amp;gt;
 gt; amp;gt; amp;amp;gt; Michael Andr?? Pearce <
 michael.andre.pea...@me.com
 gt; .invalidamp;amp;gt;
 gt; amp;gt; ??2020??8??6??
 gt; amp;gt; amp;amp;gt; 3:33??
 gt; amp;gt; amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; Hi
 gt; amp;gt; amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; Im PMC member from 
ActiveMQ project.
 gt; amp;gt; amp;amp;gt;amp;amp;gt; I like the idea, 
nice. +1 on it as
 a project idea.
 gt; amp;gt; amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; I am though a 
little -1 on the name
 of the project,
 gt; I would
 gt; amp;gt; recommend
 gt; amp;gt; amp;amp;gt;amp;amp;gt; that an alternative 
name for the
 project is found as
 gt; there maybe
 gt; amp;gt; a conflict
 gt; amp;gt; amp;amp;gt;amp;amp;gt; in rights ability 
to copyright and
 trademark to it.
 gt; amp;gt; amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; I??m aware there is 
a commercial
 vendor messaging
 gt; company called
 gt; amp;gt; Solace,
 gt; amp;gt; amp;amp;gt;amp;amp;gt; where they use and 
market their
 product with heavy
 gt; use of the
 gt; amp;gt; name Event
 gt; amp;gt; amp;amp;gt;amp;amp;gt; Mesh, you can see 
this just
 googling event mesh,
 gt; brings back many
 gt; amp;gt; hits to
 gt; amp;gt; amp;amp;gt;amp;amp;gt; their products, 
marketing material
 and other
 gt; records, so they may
 gt; amp;gt; hold a
 gt; amp;gt; amp;amp;gt;amp;amp;gt; heavy claim to this 
name.
 gt; amp;gt; amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; Best
 gt; amp;gt; amp;amp;gt;amp;amp;gt; Michael
 gt; amp;gt; amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; On 
4 Aug 2020, at
 18:33, Kevin Ratnasekera <
 gt; amp;gt; djkevincr1...@gmail.comamp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; wrote:
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; Hi 
Easen,
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; 
+1, Having worked in a
 similar domain so
 gt; far, I have to say
 gt; amp;gt; this is an
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; 
interesting project.
 If you are seeking new
 gt; mentors, please
 gt; amp;gt; consider
 gt; amp;gt; amp;amp;gt;amp;amp;gt; adding
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; me 
as a mentor to the
 project.
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; 
Regards
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; 
Kevin
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; On 
Tue, Aug 4, 2020 at
 3:34 PM Eason Chen <
 gt; amp;gt; daerduoc...@qq.comamp;amp;gt; wrote:
 gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt; Good time
 of the time to all!
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt; I'd like
 to bring this new
 gt; interesting project for the
 gt; amp;gt; discussion,
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt; comments
 and feedback with the aim
 gt; of starting a formal
 gt; amp;gt; [VOTE] of its
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt; acceptance
 into Incubator.
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt; People
 behind this project aren't
 gt; new to Apache: some of
 gt; amp;gt; them were
 gt; amp;gt; amp;amp;gt;amp;amp;gt; behind
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt; the Apache
 RocketMQ, which I
 gt; consider a huge
 gt; amp;gt; success(especially in
 gt; amp;gt; amp;amp;gt;amp;amp;gt; China)as
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt; the
 community is literally thriving
 gt; almost 3 years after
 gt; amp;gt; the
 gt; amp;gt; amp;amp;gt;amp;amp;gt; graduation.
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt;
 gt; amp;gt; amp;amp;gt;amp;amp;gt; 
amp;amp;gt;amp;amp;gt; I 

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

1. Just open-sourced
3. Community development would be a challenge


As mentioned earlier, the project is still in its infancy. I also asked the 
mentors how to build the community. I believe that with the help of apache way 
and the mentors, we have reasons and confidence to make products more 
diversified and build a healthy internationalization community.


2. Have a risk of being an orphaned project



Event is a huge ecosystem, and especially eventmesh will be a very promising 
direction??currently such products are scarce, but the demand will be greater




--  --
??: 
   "general"

https://incubator.apache.org/guides/names.html
 gt; amp;gt; [2] https://www.uspto.gov/trademark
 gt; amp;gt;
 gt; amp;gt; Thanks
 gt; amp;gt; Henry
 gt; amp;gt;
 gt; amp;gt; Michael Andr?? Pearce https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
 gt
 

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Our product has actually received a lot of attention from people. We have 
conducted communication with many people and collected their opinions. We plan 
to abstract eventmesh more independently, make product positioning clearer, and 
make it easier for everyone to participate. We will invest more time and energy 
to build the community.




----
??: 
   "general"

https://incubator.apache.org/guides/names.html
 gt; [2] https://www.uspto.gov/trademark
 gt;
 gt; Thanks
 gt; Henry
 gt;
 gt; Michael Andr?? Pearce https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
 gt;gt
 

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Thanks for your help and answers @Duane, i will initiate the voting processs 
later if you have no other questions.




----
??: 
   "general"

https://incubator.apache.org/guides/names.html
 [2] https://www.uspto.gov/trademark

 Thanks
 Henry

 Michael Andr?? Pearce https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal


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

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Hi??
I want to modify the description of the proposal to make it more accurate, 
please help me add permissions??thanks


Here are the details of my account:
Usernamechenguangsheng
emailchenguangsh...@apache.org
Full NameChen Guangsheng






----
??: 
   "general"

https://incubator.apache.org/guides/names.html
 [2] https://www.uspto.gov/trademark

 Thanks
 Henry

 Michael Andr?? Pearce https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal


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

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Hi,
EventMesh will no longer rely strongly on RocketMQ in the future, it is only 
one choice of the storage layer, other MQs, redis, blockchain can be 
supported in the future plans.


EventMesh is very different from Camel i think, it positioned in event 
governance and mesh cloud nativeization.




----
??: 
   "general"

https://github.com/WeBankFinTech/EventMesh/graphs/contributors
   2. Only have 35 issues opened on the GitHub.
   https://github.com/WeBankFinTech/EventMesh/issues
   3. The issues(since issue #21) since 21 days ago have no comment 
any all.
  
   From my understanding, this project is only limited maintained 
by one and
   only one for now.
  
   To the project community, could you respond what is the real 
status now?
   And why there is a gap between your proposal and GitHub open 
statistics?
  
   Personally, I have concerns about the activity and support of the
   community, or a little more, whether the basic community has been
   established.
   I think the incubator should notice the status, in case, it will 
be hard to
   make consensus and release soon in the incubating stage.
  
   Sheng Wu 
   Twitter, wusheng1108
  
  
   Ming Wen https://github.com/WeBankFinTech/EventMesh/graphs/contributors
   gt 
<https://github.com/WeBankFinTech/EventMesh/graphs/contributorsgt;;
   gt; Thanks,
   gt; Ming Wen, Apache APISIX amp; Apache SkyWalking
   gt; Twitter: _WenMing
   gt;
   gt;
   gt; Eason Chen https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
   gt
   
<https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposalgt;
   ;



 --
 Clebert Suconic



-- 
Clebert Suconic

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

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Hi,


We do not deny that the community is not really big and active, we share our 
best practices and look forward to getting more people's attention and help, at 
the same time can help our colleagues.we believe that as long as we find 
the right method and organization such as the apache way, the community will 
become stronger and stronger.


In addition, I want to clarify that these codes are submitted by the entire 
team within our company, but I open sourced them, as you see some components 
are not yet open source, we are reviewing and reforming internally, and will 
open source soon.




----
??: 
   "general"

https://github.com/WeBankFinTech/EventMesh/graphs/contributors
2. Only have 35 issues opened on the GitHub.
https://github.com/WeBankFinTech/EventMesh/issues
3. The issues(since issue #21) since 21 days ago have no comment any all.

From my understanding, this project is only limited maintained by one and
only one for now.

To the project community, could you respond what is the real status now?
And why there is a gap between your proposal and GitHub open statistics?

Personally, I have concerns about the activity and support of the
community, or a little more, whether the basic community has been
established.
I think the incubator should notice the status, in case, it will be hard to
make consensus and release soon in the incubating stage.

Sheng Wu 
Twitter, wusheng1108


Ming Wen https://github.com/WeBankFinTech/EventMesh/graphs/contributors

 Thanks,
 Ming Wen, Apache APISIX  Apache SkyWalking
 Twitter: _WenMing


 Eason Chen https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal

?????? [DISCUSS] EventMesh Proposal

[Eason Chen]

Hi, wenming
1. I believe more people will join in the future ;)
2. Sure




----
??: 
   "general"

https://github.com/WeBankFinTech/EventMesh/graphs/contributors

Thanks,
Ming Wen, Apache APISIX  Apache SkyWalking
Twitter: _WenMing


Eason Chen https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal

[DISCUSS] EventMesh Proposal

[Eason Chen]

Good time of the time to all!


I'd like to bring this new interesting project for the discussion, comments and 
feedback with the aim of starting a formal [VOTE] of its acceptance into 
Incubator.


People behind this project aren't new to Apache: some of them were behind the 
Apache RocketMQ, which I consider a huge success(especially in China)as the 
community is literally thriving almost 3 years after the graduation.


I have been involved a little bit with this project when it just started in 
WeBank a few years ago. And I'd like to emphasize that the community however 
small it might look so far, has been aligned with Apache ways of doing things. 
Heng Du (from RocketMQ PMC) is very instrumental in tirelessly helping this 
group to learn what it means to be a truly open source project.


The code is already under ALv2 and is publicly available. As you will see it 
has a lot of dependency connections with the rest of Apache ecosystem and IMO 
will fit very well here and continue to grow the community.


The project's proposal is available at [1].


Thank you very much for the feedback you're willing to provide!


With best regards,

Eason Chen



[1] https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal