Re: [VOTE] Accept HoraeDB Into the ASF Incubator

[vongosling]

+1, binding

ShaoFeng Shi  于2023年12月5日周二 11:04写道：
>
> +1 (binding)
>
> Best regards,
>
> Shaofeng Shi 史少锋
> Apache Kylin PMC,
> Apache Incubator PMC,
> Email: shaofeng...@apache.org
>
> Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> Join Kylin user mail group: user-subscr...@kylin.apache.org
> Join Kylin dev mail group: dev-subscr...@kylin.apache.org
>
>
>
>
> PJ Fanning  于2023年12月4日周一 23:25写道：
>
> > +1 (binding)
> >
> > On Mon, 4 Dec 2023 at 14:17, li gang  wrote:
> > >
> > > +1 (binding)
> > >
> > > tison  于2023年12月4日周一 21:01写道：
> > >
> > > > Hi Incubator
> > > >
> > > > Following the discussion [DISCUSS] HoraeDB proposal[1],
> > > > I am starting this official vote for the HoraeDB project.
> > > >
> > > > Here is their proposal:
> > > > https://cwiki.apache.org/confluence/display/INCUBATOR/HoraeDB+Proposal
> > > >
> > > > Please cast your vote:
> > > >
> > > > [ ] +1, bring into the Incubator
> > > > [ ] +0, I don't care either way
> > > > [ ] -1, do not bring HoraeDB into the Incubator, because...
> > > >
> > > > The vote will open for one week from today, Dec. 4th, 2023
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > > [1] https://lists.apache.org/thread/6vbhv4soxw45yf2w9l495ofdqr3029ll
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> > > --
> > >
> > >
> > > --
> > > Best Regards
> > > Gang Li 李岗
> > >
> > > lgcar...@apache.org
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >



-- 
Best Regards :-)

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

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

[vongosling]

+1, binding

Very happy to see the healthy growth of the community, Let's know more
about the new choice of NoSQL @ASF.  Good luck to move on :-)

Xiaoqiao He  于2023年5月14日周日 19:03写道：

> +1(binding).
>
> Good luck on the next journey!
>
> Best Regards,
> - He Xiaoqiao
>
>
> On Sat, May 13, 2023 at 9:13 PM tison  wrote:
>
> > +1 (binding)
> >
> > Kvrocks has a strong community with diversity in users, developers, and
> > release managers. I'm confident in its sustainability.
> >
> > Best,
> > tison.
> >
> >
> > PJ Fanning  于2023年5月13日周六 17:32写道：
> >
> > > +1 (binding)
> > >
> > > Kvrocks project seems to be in a very healthy position to move forward
> as
> > > a TLP.
> > >
> > > On Sat, 13 May 2023 at 09:43, Yuan Wang  wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > We already used it for several years in production environment, very
> > glad
> > > > to see this happen, good luck!
> > > >
> > > > Best Regards
> > > > Yuan Wang
> > > >
> > > > peacewong  于2023年5月13日周六 13:55写道：
> > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > Good Luck!
> > > > >
> > > > > Best regards,
> > > > > Peace Wong
> > > > > Liang Chen  于2023年5月13日周六 13:50写道：
> > > > >
> > > > > > +1(binding)
> > > > > >
> > > > > > Regards
> > > > > > Liang
> > > > > >
> > > > > > hulk  于2023年5月12日周五 05:55写道：
> > > > > >
> > > > > > > Hello all,
> > > > > > >
> > > > > > > We've got positive feedback on the DISCUSS thread[1], I'd like
> to
> > > start
> > > > > > an
> > > > > > > official VOTE thread now.
> > > > > > >
> > > > > > > Please vote on the resolution pasted below to graduate Apache
> > > Kvrocks
> > > > > > from
> > > > > > > the incubator to the Top Level Project.
> > > > > > >
> > > > > > > [ ] +1 Graduate Apache Kvrocks from the Incubator.
> > > > > > > [ ] +0 No opinion.
> > > > > > > [ ] -1 Don't graduate Apache Kvrocks from the Incubator because
> > ...
> > > > > > >
> > > > > > > This vote will open for at least 72 hours.
> > > > > > >
> > > > > > > Many thanks to our mentors and everyone else for their support.
> > > > > > >
> > > > > > > [1]
> > > https://lists.apache.org/thread/ld8x1wvh1n745j96ksy0pmy92gwn2t06
> > > > > > >
> > > > > > >
> > ---
> > > > > > >
> > > > > > > Establish the Apache Kvrocks 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 distributed key-value NoSQL database, supporting
> the
> > > rich
> > > > > > > data structure.
> > > > > > >
> > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee
> > > > > > > (PMC), to be known as the "Apache Kvrocks Project", be and
> hereby
> > > is
> > > > > > > established pursuant to Bylaws of the Foundation; and be it
> > further
> > > > > > >
> > > > > > > RESOLVED, that the Apache Kvrocks Project be and hereby is
> > > responsible
> > > > > > > for the creation and maintenance of software related to a
> > > distributed
> > > > > > > key-value NoSQL database, supporting the rich data structure;
> and
> > > be it
> > > > > > > further
> > > > > > >
> > > > > > > RESOLVED, that the office of "Vice President, Apache Kvrocks"
> 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
> > > Kvrocks
> > > > > > > Project, and to have primary responsibility for management of
> the
> > > > > > > projects within the scope of responsibility of the Apache
> Kvrocks
> > > > > > > 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 Kvrocks
> > > > > Project:
> > > > > > >
> > > > > > >  * Alfejik Liu  
> > > > > > >  * Hulk Lin 
> > > > > > >  * Jean-Baptiste Onofré 
> > > > > > >  * Liang Chen   
> > > > > > >  * Mingyang Liu 
> > > > > > >  * Von Gosling  
> > > > > > >  * Xiaoqiao He  
> > > > > > >  * Yaroslav Stepanchuk  
> > > > > > >  * Yuan Wang
> > > > > > >  * Zili Chen
> > > > > > >
> > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hulk Lin be
> > appointed
> > > to
> > > > > > > the office of Vice President, Apache Kvrocks, 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
> > > > > > >
> > > > > > 

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

[vongosling]

+1, binding

Nice to see we have good practice for Apache Way. When we bring this
project here, we are all looking forward to a promising road for the Event
First Platform. Apache EventMesh seems to be ready to open the door for us.
Good luck to the community ：-）

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

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

[vongosling]

+1, binding

Shuai Di  于2022年11月27日周日 18:17写道：

> 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
> -
>
> Establish the Apache Linkis 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 distributed and computation middleware to
> facilitate connection, governance, and orchestration between the upper
> applications and the underlying data engines.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Linkis Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Linkis Project be and hereby is responsible
> for the creation and maintenance of software related to a computation
> middleware to facilitate connection, governance and orchestration
> between the upper applications and the underlying data engines; and be
> it further
>
> RESOLVED, that the office of "Vice President, Apache Linkis" 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 Linkis
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Linkis
> 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 Linkis
> Project:
>
>  ●  Alex Young 
>  ●  Deyi Hua 
>  ●  Duo Zhang 
>  ●  HuaJin Zhang 
>  ●  Hui Zhu 
>  ●  Jacky Xie 
>  ●  Jerry Shao 
>  ●  Junping Du 
>  ●  Ke Zhou 
>  ●  Kelu Tao 
>  ●  Le Bai 
>  ●  Lidong Dai 
>  ●  Ling Xu 
>  ●  Longping Jie 
>  ●  Peacewong 
>  ●  Qiang Yin 
>  ●  Rong Zhang 
>  ●  

Re: [VOTE] Release Apache Sedona 1.3.0-incubating-rc2

[vongosling]

+1, binding

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files


Jia Yu  于2022年11月22日周二 12:36写道：

> Hi all,
>
> This is a call for vote on Apache Sedona 1.3.0-incubating-rc2. Please refer
> to the changes listed at the bottom of this email.
>
> Sedona Community vote thread (Permalink from
> https://lists.apache.org/list.html):
> https://lists.apache.org/thread/f7vnm6pchltjco686dsqfc8ntrhbwto2
>
> Sedona community vote result thread (Permalink from
> https://lists.apache.org/list.html):
> https://lists.apache.org/thread/4098nf7rl8byl8pkcyyj8z62qt3l9rkh
>
> Release notes:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.3.0-incubating-rc2/docs/setup/release-notes.md
>
> Build instructions:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.3.0-incubating-rc2/docs/setup/compile.md
>
> GitHub tag:
>
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.3.0-incubating-rc2
>
> GPG public key to verify the Release:
> https://downloads.apache.org/incubator/sedona/KEYS
>
> Source code and binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.3.0-incubating-rc2/
>
> The vote will be open for at least 72 hours or until at least 3 "+1" PMC
> votes are cast
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> For a detailed checklist  please refer to:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Thanks,
> Jia
>


-- 
Best Regards :-)

Re: [VOTE] Release Apache Kvrocks (incubating) 2.2.0

[vongosling]

+1 (binding)

I checked:
- incubating in name
- signatures and hashes are fine
- LICENSE/NOTICE looks OK
- no unexpected binary files


Twice  于2022年11月14日周一 21:21写道：

> Hello IPMC,
>
> The Apache Kvrocks (incubating) community has voted and approved the
> release of Apache
> Kvrocks(incubating) 2.2.0. We now kindly request the IPMC members
> review and vote for this release.
>
> Kvrocks is a distributed key value NoSQL database that uses RocksDB as the
> storage engine
> and is compatible with Redis protocol. The current release provides many
> new features,
> improvements to existing features and bug fixes.
>
> Kvrocks community vote thread:
>
> https://lists.apache.org/thread/10bxhgdd4nlk6dt039b4zxh2k4c3xncb
>
> Vote result thread:
>
> https://lists.apache.org/thread/djtoc1lgy56wtchtsl0r4jy6r8lhbv3l
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.2.0
>
> This release has been signed with a PGP available here:
>
> https://dist.apache.org/repos/dist/dev/incubator/kvrocks/KEYS
>
> Git tag for the release:
>
> https://github.com/apache/incubator-kvrocks/tree/v2.2.0
>
> Build guide can be found at:
>
> https://github.com/apache/incubator-kvrocks#build
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.2.0
> [ ] +0
> [ ] -1 Do not approve (please specify the reason)
>
> Thanks!
>
> Best wishes,
> Twice
>


-- 
Best Regards :-)

Re: [VOTE] Graduate Apache bRPC to a TLP

[vongosling]

+1, binding

Great to have been part of this journey over the last years.

Jerry Tan  于2022年11月11日周五 22:48写道：

> Hello, dear IPMC members,
>
> following the [DISCUSS] thread at [1],
>
> I'd like to call a vote to graduate bRPC to a TLP.
>
>
> Please vote accordingly:
>
> [ ] +1 Apache bRPC (incubating) is ready to graduate to a TLP
>
> [ ] +0 No opinion.
>
> [ ] -1 Apache bRPC (Incubating) is not ready to graduate (please state
> reasons)
>
>
> Thank you for participating in the vote!
>
>
> Best regards
>
> Jerry Tan
>
>
> ---
>
> Project Updates since 2018-11-13:
>
> ---
>
>
> 1. We release 1.0.0,1.1.0, 1.2.0, 1.3.0, 4 apache releases, and
> 0.9.6,0.9.7, 2 disclaim releases; by different release managers (including
> Jerry Tan, Jiashun Zhu, Lorin Lee, Wang Weibing, Shuai Liu, Xiguo Hu) (see
> it at [2])
>
>
> 2. We add 5 new PPMC members including Jiashun Zhu, Wang Weibing, Cai
> Daojin, He Lei, and Lorin Lee. see it at [2]. Now we have 10 PPMC members
> altogether, they are from different companies, including ByteDance (James
> Ge,
> He Lei), Baidu (Yao Wang, Wang Weibing), Google (Jiashun Zhu), 4Paradigm
> (Jerry
> Tan), Shopee (Cai Daojin), Momenta.AI (Zhangyi Chen), Ant Group (Bear Jiang
> ), Freelancer (Lorin Lee).
>
>
> 3. We add 9 new committers, including Cai Daojin, He Lei, Mou Gaidong,
> Lorin
> Lee, Wang Wei, Shuai Liu, Wang Xiaofeng, Xiguo Hu, and Guangming Chen. see
> it at [2].
>
>
> 4. There are 17 members subscribed to the private email list and 60
> engineers subscribed to the dev mail list. The discussion on the dev mail
> list is active, including release, roadmap, committer related topics. see
> it at [3]
>
>
> 5. Branding issues have been solved and name searching has been completed.
> See it at [4]
>
>
> 6. Assessment of the maturity model is available at [5]. All answers to
> these check items are 'Yes'.
>
>
> 7. The bRPC website has passed the Apache Podling Website Checks [6].
>
>
> 8. 1000+ issues resolved[7], and 600+ pull requests merged and closed[8].
>
>
> 9. bRPC has been widely adopted outside Baidu since incubating, including
> iQiyi， Bytedance， Bilibili， Bigo， Didi， Weibo， Vivo，4padradigm， X
> iaohongshu， Ishumei， Doris， Amap， etc.
>
>
> And we plan to move on with new features and new scenarios, such as RDMA
> support has been integrated into the trunk and will be included in the next
> release, and extend bRPC with service mesh features.
>
> ---
>
> Draft resolution
>
> ---
>
> Establish the Apache bRPC 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 an industrial-grade RPC framework for building reliable and
>
> high-performance services.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache bRPC Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache bRPC Project be and hereby is responsible for
>
> the creation and maintenance of software related to an industrial-grade
>
> RPC framework for building reliable and high-performance services; and
>
> be it further
>
> RESOLVED, that the office of "Vice President, Apache bRPC" 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 bRPC Project, and to
>
> have primary responsibility for management of the projects within the
>
> scope of responsibility of the Apache bRPC 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 bRPC Project:
>
> * Bear Jiang 
>
> * Cai Daojin 
>
> * He Lei 
>
> * James Ge 
>
> * Jean-Baptiste Onofré 
>
> * Jerry Tan 
>
> * Jiashun Zhu 
>
> * Juan Pan 
>
> * Lorin Lee 
>
> * Von Gosling 
>
> * Wang Weibing 
>
> * Yao Wang 
>
> * Zhangyi Chen 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that James Ge be appointed to
>
> the office of Vice President, Apache bRPC, 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 bRPC Project be and hereby is tasked with the
>
> migration and rationalization of the Apache Incubator bRPC podling; and
>
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>
> bRPC podling encumbered upon the Apache Incubator PMC are hereafter
>
> discharged.
>
>
> [1]  https://lists.apache.org/thread/nb3sw03skm2j80rxnv0xxwyl4lnbwky1
>
> [2] https://incubator.apache.org/projects/brpc.html
>
> [3] 

Re: [VOTE] Release Apache Sedona 1.2.1-incubating-rc1

[vongosling]

Hi,

+1, binding. Sorry for getting back to you:-)

I checked:
- incubating in name
- signatures and hashes are fine
- disclaimer exists
- LICENSE looks OK
- NOTICE needs fixing (see above)
- No unexpected binary files in the source release
- All source files have ASF headers


Jia Yu  于2022年8月27日周六 02:00写道：

> Dear all,
>
> Two of our mentors didn't respond to our emails probably because they have
> too much on their plate. We just need 1 more binding vote. Can someone help
> us? We really appreciate it.
>
> Thanks,
> Jia
>
> On Wed, Aug 24, 2022 at 2:58 PM Felix Cheung 
> wrote:
>
> > Source code and binaries:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.2.1-incubating-rc1/
> >
> > On Sat, Aug 13, 2022 at 9:22 PM Jean-Baptiste Onofré 
> > wrote:
> >
> > > Hi,
> > >
> > > Can you please include the link to dist source package ? That's the
> > > most important thing to check.
> > >
> > > Thanks,
> > > Regards
> > > JB
> > >
> > > On Wed, Aug 10, 2022 at 4:55 AM Kanchan Chowdhury <
> kanchan...@apache.org
> > >
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > This is a call for vote on Apache Sedona 1.2.1-incubating-rc1. Please
> > > refer
> > > > to the changes listed at the bottom of this email.
> > > >
> > > > Sedona Community vote thread:
> > > > https://lists.apache.org/thread/511gjndxmdxh4g2rzwyxppjc00orz3s3
> > > >
> > > > Sedona community vote result thread:
> > > > https://lists.apache.org/thread/jyb3yp2wpnhp8kx7t8dnls8xljwqflxr
> > > >
> > > > Release notes:
> > > >
> > >
> >
> https://github.com/apache/incubator-sedona/blob/bcb1803c24dc9decfb113a31db8fc14433be025b/docs/setup/release-notes.md
> > > >
> > > > Build instructions:
> > > >
> > >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.2.1-incubating-rc1/docs/setup/compile.md
> > > >
> > > > GitHub tag:
> > > >
> > >
> >
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.2.1-incubating-rc1
> > > >
> > > > GPG public key to verify the Release:
> > > > https://downloads.apache.org/incubator/sedona/KEYS
> > > >
> > > > Source code and binaries:
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.2.1-incubating-rc1/
> > > >
> > > > The vote will be open for at least 72 hours or until at least 3 "+1"
> > PMC
> > > > votes are cast
> > > >
> > > > Please vote accordingly:
> > > >
> > > > [ ] +1 approve
> > > >
> > > > [ ] +0 no opinion
> > > >
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > Checklist for reference (because of DISCLAIMER-WIP, other checklist
> > items
> > > > are not blockers):
> > > >
> > > > [ ] Download links are valid.
> > > >
> > > > [ ] Checksums and PGP signatures are valid.
> > > >
> > > > [ ] DISCLAIMER is included.
> > > >
> > > > [ ] Source code artifacts have correct names matching the current
> > > release.
> > > >
> > > > For a detailed checklist  please refer to:
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>


-- 
Best Regards :-)

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

[vongosling]

HI,

+1, binding

I checked:
- incubating in name
- LICENSE is ok, also has a WIP disclaimer
- NOTICE is fine
- WIP DISCLAIMER exists
- signatures and hashes are fine
- no unexpected binary files
- ASF files have ASF headers

Please remove "WeChat Official Account” description :-)


李晓双  于2022年8月17日周三 14:21写道：

> Hello Incubator Community,
>
>   This is a call for a vote to release Apache EventMesh(Incubating) version
> 1.6.0 rc1
>
>   The Apache EventMesh community has voted on and approved a proposal to
> release
> Apache EventMesh(Incubating) version 1.6.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/bs6hg19ttldx6ztop85osjwf0kdmtdx8
>
> Vote result thread:
> • https://lists.apache.org/thread/hs36127ynjnf7vqcb9cl62qj9dcnfrr5
>
> The release candidate:
> •https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.6.0-rc1/
>
>   Git tag for the release:
>   • https://github.com/apache/incubator-eventmesh/tree/v1.6.0-rc1
>   Release notes:
>   •
>
> https://github.com/apache/incubator-eventmesh/blob/v1.6.0-rc1/release-node.md
>
>   The artifacts signed with PGP key
> EB0B0EE0AA11B1A437B5DB9E59632DD43B216CE5, corresponding to
> lixiaoshu...@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
>


-- 
Best Regards :-)

Re: [VOTE] Release Apache Sedona 1.2.0-incubating-rc2

[vongosling]

+1, binding,
I checked:
- incubating is in the name
- changes since the last vote
- LICENSE, DISCLAIMER-WIP are there and look good
- hash and signature are good
- no binary in the source archive

Paweł Kociński  于2022年4月10日周日 16:55写道：

> Hi all,
>
> This is a call for vote on Apache Sedona 1.2.0-incubating-rc2. Please refer
> to the changes listed at the bottom of this email.
>
> Sedona Community vote thread (
> https://lists.apache.org/thread/fpfz5jmr5vomoyh4tkopxq1nzymn74gj):
>
> Sedona community vote result thread (
> https://lists.apache.org/thread/xozcc7p7896d0v7t9oyt643kkofpcfrs):
>
>
> Release notes:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.2.0-incubating-rc2/docs/setup/release-notes.md
>
> Build instructions:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.2.0-incubating-rc2/docs/setup/compile.md
>
> GitHub tag:
>
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.2.0-incubating-rc2
>
> GPG public key to verify the Release:
> https://downloads.apache.org/incubator/sedona/KEYS
>
>
> Source code and binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.2.0-incubating-rc2/
>
> The vote will be open for at least 72 hours or until a majority of at least
> 3 "approve" PMC votes are cast
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference (because of DISCLAIMER-WIP, other checklist items
> are not blockers):
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> For a detailed checklist  please refer to:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> 
>
> Changes according to the comments on the previous release candidate
> - NOTICE file has been fix in the PR (
> https://github.com/apache/incubator-sedona/pull/594/files) and it's
> included in this release (1.2.0-incubating-rc2)
>
> Regards,
> Paweł
>


-- 
Best Regards :-)

Re: [VOTE] Release Apache brpc (Incubating) 1.1.0

[vongosling]

+1, binding

I checked:
- incubating is in the name
- LICENSE, NOTICE, DISCLAIMER are there and look good
- hash and signature are good
- no binary in the source archive

Wang,Weibing  于2022年4月6日周三 13:49写道：

> Hello IPMC,
>
> The Apache brpc community has voted and approved the release of Apache
> brpc (Incubating) 1.1.0. We now kindly request the IPMC members
> review and vote for this release.
>
> brpc is an industrial-grade RPC framework with extremely high performance,
> and it supports multiple protocols, full rpc features, and has many
> convenient tools. The current release provides some new features
> such as ipv6 and uds support, and fixes many bugs.
>
> brpc community vote thread:
> https://lists.apache.org/thread/6p7lqprok26r3ko456mpwb77vq4lx0qf
>
> Vote result thread:
> https://lists.apache.org/thread/o9k0prhdrpg975mr8prnrf3ghnmzvl3d
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/1.1.0/
>
> This release has been signed with a PGP available here:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS
>
> Git tag for the release:
> https://github.com/apache/incubator-brpc/releases/tag/1.1.0
>
> Build guide and get started instructions can be found at:
>
> https://github.com/apache/incubator-brpc/blob/master/docs/en/getting_started.md
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 Approve the release of Apache brpc (Incubating) 1.1.0
> [ ] +0
> [ ] -1 Do not approve (please specify the reason)
>
> Regards,
> Weibing Wang
> Apache brpc (Incubating)
>


-- 
Best Regards :-)

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

[vongosling]

Carrying over my binding +1 in the PPMC channel:-)

wqliang  于2022年3月24日周四 14:45写道：

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


-- 
Best Regards :-)

Re: [VOTE] Release Apache InLong 0.12.0-incubating RC0

[vongosling]

Hi,

+1 (binding)

I checked:

- Signatures and hashes are fine
- DISCLAIMER (WIP) exists
- LICENSE and NOTICE ok
- No unexpected binary files

Goson zhang  于2021年12月26日周日 14:02写道：

> Hello Incubator Community,
>
> This is a call for a vote to release Apache InLong(Incubating) version
> 0.12.0-incubating RC0
>
> The Apache InLong community has voted on and approved a proposal to
> release
> Apache InLong(Incubating) version 0.12.0-incubating RC0
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> InLong community vote thread:
> • https://lists.apache.org/thread/yrvt1mso9khk44wjjornjqrbv25bngjj
>
> Vote result thread:
> • https://lists.apache.org/thread/9qvtq0szkh2k6gyr2f5fvvkcfcxkmnh0
>
> The release candidate:
> •
>
> https://dist.apache.org/repos/dist/dev/incubator/inlong/0.12.0-incubating-RC0/
>
> Git tag for the release:
> •
>
> https://github.com/apache/incubator-inlong/releases/tag/0.12.0-incubating-RC0
>
> Release notes:
> •
>
> https://github.com/apache/incubator-inlong/blob/0.12.0-incubating-RC0/CHANGES.md
>
> The artifacts signed with PGP key A4D4D578, corresponding to
> dockerzh...@apache.org, that can be found in keys file:
> • https://downloads.apache.org/incubator/inlong/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 InLong(Incubating) community
>


-- 
Best Regards :-)

Re: [VOTE] Release Apache EventMesh (incubating) 1.3.0 rc0

[vongosling]

Hi,

+1 (binding)

I checked:

- Signatures and hashes are fine
- DISCLAIMER (WIP) exists
- LICENSE and NOTICE ok
- No unexpected binary files

mikexue  于2021年12月23日周四 16:45写道：

> Hello Incubator Community,
>
> This is a call for a vote to release Apache EventMesh(Incubating)
> version 1.3.0 rc0
>
> The Apache EventMesh community has voted on and approved a proposal to
> release Apache EventMesh(Incubating) version 1.3.0 rc0
>
> We now kindly request the Incubator PMC members review and vote on
> this incubator release.
>
> EventMesh community vote thread:
> • https://lists.apache.org/thread/wolw8dvoxw1z53jc7cj52fj5vn8lt1m0
>
> Vote result thread:
> • https://lists.apache.org/thread/xkkq19onk7lrrlboqybjsvxhgtdvn11c
>
> The release candidate:
> •
> https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.3.0-rc0/
>
> Git tag for the release:
> • https://github.com/apache/incubator-eventmesh/tree/v1.3.0-rc0
>
> Release notes:
> • https://eventmesh.apache.org/events/release-notes/v1.3.0
>
> The artifacts signed with PGP key
> F84A0041D70B37AF9C7BF0B339F429D7579C25F5, corresponding to
> mike...@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: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Best Regards :-)

Re: [VOTE] Accept EventMesh into Apache Incubator

[vongosling]

+1, binding
Good luck ~

Eason Chen  于2021年2月1日周一 下午2:44写道：

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


-- 
Nothing is impossible

Re: [DISCUSS] EventMesh Proposal

[vongosling]

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

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,
> > >
> > > 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 kn

Re: [DISCUSS] EventMesh Proposal

[vongosling]

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

-- 
Nothing is impossible

Re: [VOTE] Release the Apache Pegasus 2.1.0

[vongosling]

+1, binding(forward my vote from ppmc)

p.s. There are still some minor issues that could be addressed in the
following release, such as a newbie-friendly build and quick start
documentation. I'm sure more guys will try this interesting project :-)

Best Regards,
Von Gosling

Tao Wu  于2020年11月25日周三 下午4:26写道：

> Hi, all
>
> This is a call for a vote to release Apache Pegasus (Incubating) version
> 2.1.0. Pegasus is a distributed key-value storage system that is designed
> to be simple, horizontally scalable, strongly consistent, and
> high-performance.
>
> The Apache Pegasus community has voted on and approved a proposal to
> release Apache Pegasus 2.1.0.
>
> Apache Pegasus community vote thread:
> <
> https://lists.apache.org/thread.html/r04796d87a3f4465ce1d6478c1d804e4a2ef9f885a71b5bc3cdbf605c%40%3Cdev.pegasus.apache.org%3E
> >
>
> https://lists.apache.org/thread.html/rcb5dc577fa790827c4455902317c7a322db51db28d1844d2257b7a32%40%3Cdev.pegasus.apache.org%3E
>
> Vote result thread:
>
> https://lists.apache.org/thread.html/r615af7064a766e4c00b33e2894a294eb13b229005c0af703232d671e%40%3Cdev.pegasus.apache.org%3E
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/pegasus/2.1.0-RC5/
>
> It is tagged in Git as 2.1.0-RC5 and the corresponding hash is the
> following:
>
> https://gitbox.apache.org/repos/asf?p=incubator-pegasus.git;a=commit;h=7686ecef697795a1333028b14072472d920d8d19
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/pegasus/KEYS
>
> For information about the contents of this release, see:
> <
> https://docs.google.com/document/d/1Ul5W0ViA6HK0h4blu3PD2JKnUR_8SSViHXQmmzHyew8/edit?usp=sharing
> >
> https://cwiki.apache.org/confluence/x/cxbZCQ
>
> It'd be appreciated if you could help validate this release candidate.
> Please follow this doc to learn the validation process:
> https://cwiki.apache.org/confluence/x/qhnZCQ
>
> The compilation doc is here:
> http://pegasus.apache.org/en/docs/build/compile-by-docker/
>
> The vote will be open for 72 hours.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Best regards
> Tao Wu
>


-- 
Nothing is impossible

Re: Finding a champion and mentors

[vongosling]

Hi,

It's an interesting project around OpenBCI. I really understand your
concern about how to reach your rational mentors. It's not a bad way to go
straight in the general mail, at least more professional mentors could see
your project. I'm not a veteran in this direction, but it's interesting to
read the project introduction. I'd like to be your mentor, you could count
me in :-)

Best Regards,
Von Gosling

Andrey Parfenov  于2020年11月25日周三 上午7:35写道：

> Hello,
>
> I am an author of open source project BrainFlow, and currently I am
> thinking about moving this project to Apache Incubator.
> I've read all the documents about the application process and seems like
> finding mentors/champions is the first step.
>
> But it's unclear how to find them and get feedback about the project and
> it's perspectives at Apache Incubator.
>
> More info about project:
>
> BrainFlow is a library to read, parse and analyze data from biosensors with
> primary focus on BCI devices, the goal of this library is to provide
> uniform SDK to different devices and allow programmers to write device
> agnostic code.
> As of right now it supports 7 programming languages. First commit was
> around ~2.5 years ago
>
> Docs https://brainflow.readthedocs.io/en/stable/
> Github https://github.com/brainflow-dev/brainflow
> Website https://brainflow.org/
> Slack Workspace was created around 6 months ago and currently there are 137
> members
>
>
> Best Regards,
> Andrey
>


-- 
Nothing is impossible

Re: [VOTE] Graduate Apache ECharts as TLP (round 2)

[vongosling]

+1, binding


Best Regards,
Von Gosling

lidong dai  于2020年11月23日周一 下午7:38写道：

> +1 non-binding
> looking forward to ECharts graduation as TLP
>
>
> Best Regards
> ---
> DolphinScheduler(Incubator) PPMC
> Lidong Dai 代立冬
> dailidon...@gmail.com
> ---
>
>
> On Mon, Nov 23, 2020 at 7:33 PM tison  wrote:
>
> > +1 non-binding
> >
> > Good luck!
> >
> > Best,
> > tison.
> >
> >
> > Willem Jiang  于2020年11月23日周一 下午7:28写道：
> >
> > > +1 （binding）
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Mon, Nov 23, 2020 at 4:31 PM Ovilia  wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > After discussion with the community [1], and a positive vote result
> [2]
> > > and
> > > > the
> > > > discussion under general mailing list [6], we believe
> > > > ECharts is ready for graduation to a TLP, and we'd like to call on
> the
> > > vote
> > > > to
> > > > graduate Apache ECharts as TPL.
> > > >
> > > > This is a formal voting thread about Apache ECharts's graduation,
> > please
> > > > Vote:
> > > > [ ] +1 - Recommend graduation of Apache ECharts as a TLP
> > > > [ ]  0 - I don't feel strongly about it, but don't object
> > > > [ ] -1 - Do not recommend graduation of Apache ECharts because...
> > > >
> > > > The VOTE will open for at least 72 hours.
> > > > <
> > >
> >
> https://www.timeanddate.com/countdown/vote?iso=20201126T1435=237=%5BVOTE%5D+Graduate+Apache+ECharts+as+TLP=serif=1
> > > >
> > > >
> > >
> >
> https://www.timeanddate.com/countdown/vote?iso=20201126T1635=237=Graduate+Apache+ECharts+as+TLP=serif=1
> > > >
> > > > -
> > > >
> > > > X. Establish the Apache ECharts Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best
> > > > interests of the Foundation and consistent with the
> > > > Foundation's purpose to establish a Project Management
> > > > Committee charged with the creation and maintenance of
> > > > open-source software, for distribution at no charge to
> > > > the public, related to a charting and data visualization
> > > > library written in JavaScript.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > > > Committee (PMC), to be known as the "Apache ECharts Project",
> > > > be and hereby is established pursuant to Bylaws of the
> > > > Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache ECharts Project be and hereby is
> > > > responsible for the creation and maintenance of software
> > > > related to a charting and data visualization
> > > > library written in JavaScript; and be it further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache ECharts" be
> > > > and hereby is created, the person holding such office to
> > > > serve at the direction of the Board of Directors as the chair
> > > > of the Apache ECharts Project, and to have primary responsibility
> > > > for management of the projects within the scope of
> > > > responsibility of the Apache ECharts Project; and be it further
> > > >
> > > > RESOLVED, that the persons listed immediately below be and
> > > > hereby are appointed to serve as the initial members of the
> > > > Apache ECharts Project:
> > > >
> > > > * Houjin Huang  
> > > > * Deqing Li 
> > > > * Dong Rui  
> > > > * Kener Linfeng 
> > > > * Kevin A. McGrail  
> > > > * Wenli Zhang   
> > > > * Shen Yi   
> > > > * Shuang Su 
> > > > * Siwen Su  
> > > > * Junting Wang  
> > > > * Zhongxiang Wang   
> > > > * Dave Fisher   
> > > > * Sheng Wu  
> > > > * Zak Wu
> > > >
> > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
> > > > be appointed to the office of Vice President, Apache ECharts, to
> > > > serve in accordance with and subject to the direction of the
> > > > Board of Directors and the Bylaws of the Foundation until
> > > > death, resignation, retirement, removal or disqualification,
> > > > or until a successor is appointed; and be it further
> > > >
> > > > RESOLVED, that the initial Apache ECharts PMC be and hereby is
> > > > tasked with the creation of a set of bylaws intended to
> > > > encourage open development and increased participation in the
> > > > Apache ECharts Project; and be it further
> > > >
> > > > RESOLVED, that the Apache ECharts Project be and hereby
> > > > is tasked with the migration and rationalization of the Apache
> > > > Incubator ECharts podling; and be it further
> > > >
> > > > RESOLVED, that all responsibilities pertaining to the Apache
> > > > Incubator ECharts podling encumbered upon the Apache Incubator
> > > > Project are hereafter discharged.
> > > >
> > > > --
> > > >
> > > > A few points to assist in the discussion:
> > > >
> > > > - Released 9 official Apache releases by 3 release managers [3]
> > > > - Voted in 9 committers including 3 PPMC members
> > > > - Achieved 

Re: [VOTE] Release the Apache Pegasus 2.1.0

[vongosling]

Hi,

-1, binding

1. There are many files without a license header.
2. License file has not listed the dependencies statement. AFAIK, there are
many MIT and other licenses in pegasus.
3. It would be nice to list the release note when voting for release. I
usually encourage peoples to do it. Someone may be interested in your new
version. and quickie help to vote for release :-)
4. I also recommend to add release-manual to your website. The community
could vote as your guide, thereby avoiding unnecessary rc1, rc2, rc3...


p.s
I really understand the license difficulties in some of the  c++ projects
when the first release in podling. Here are two references[1][2] for you.
In addition, I hope you could check this link carefully[3]:-)

[1] https://github.com/apache/rocketmq-client-cpp/blob/master/LICENSE
[2] https://github.com/apache/incubator-brpc/blob/master/LICENSE
[3] https://www.apache.org/legal/resolved.html

张铎(Duo Zhang)  于2020年10月23日周五 上午10:30写道：

> Just carry my +1 (binding) here from the previous vote thread.
>
> I suggest that we provide a dockerfile for building and verifying so others
> will be more easy to verify your release.
>
> Thanks.
>
> Tao Wu  于2020年10月21日周三 下午12:12写道：
>
> > Yes. We always have the targets to use English as our primary language.
> > But since most of the resources were initiated in Chinese, it's a huge
> > translation work for the community. To not badly affect the reading
> > experience,
> > we choose to display Chinese docs by default. You can switch to English
> > using the top-right "En" button.
> >
> > When there are enough English resources, we will change the default
> > to English then. Hopefully, the translation won't take a very long time.
> >
> > Tao Wu.
> >
> > Henry Saputra  于2020年10月21日周三 上午2:50写道：
> >
> > > Question to Apache Pegasus community. Looks like the website for the
> > > project is in Chinese only, or at least the default is in Chinese:
> > >
> > > http://pegasus.incubator.apache.org
> > >
> > > Also including the Docs of the project, like this one:
> > > https://pegasus.apache.org/2020/02/18/bulk-load-design.html
> > >
> > > Would the community consider changing the default to be in English with
> > the
> > > option to display in Chinese?
> > >
> > > - Henry
> > >
> > > On Tue, Oct 20, 2020 at 5:09 AM Tao Wu  >
> > > wrote:
> > >
> > > > Hi, all
> > > >
> > > > This is a call for a vote to release Apache Pegasus (Incubating)
> > version
> > > > 2.1.0. Pegasus is a distributed key-value storage system that is
> > designed
> > > > to be simple, horizontally scalable, strongly consistent, and
> > > > high-performance.
> > > >
> > > > The Apache Pegasus community has voted on and approved a proposal to
> > > > release Apache Pegasus 2.1.0.
> > > >
> > > > Apache Pegasus community vote thread:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r04796d87a3f4465ce1d6478c1d804e4a2ef9f885a71b5bc3cdbf605c%40%3Cdev.pegasus.apache.org%3E
> > > >
> > > > Vote result thread:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r0d300672a3e139b43acfca627fe1013d696f5d2545a45ec96c9bd12e%40%3Cdev.pegasus.apache.org%3E
> > > >
> > > > The source tarball, including signatures, digests, etc. can be found
> > at:
> > > > https://dist.apache.org/repos/dist/dev/incubator/pegasus/2.1.0-RC4/
> > > >
> > > > It is tagged in Git as 2.1.0-RC4 and the corresponding hash is the
> > > > following:
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-pegasus.git;a=commit;h=b40ab43ea37128afef0838c33e3a38c11d5dbebf
> > > >
> > > > KEYS file available:
> > > > https://dist.apache.org/repos/dist/dev/incubator/pegasus/KEYS
> > > >
> > > > For information about the contents of this release, see:
> > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1Ul5W0ViA6HK0h4blu3PD2JKnUR_8SSViHXQmmzHyew8/edit?usp=sharing
> > > >
> > > > The vote will be open for 72 hours.
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > Best regards
> > > > Tao Wu
> > > >
> > >
> >
>


-- 
Nothing is impossible

Re: [VOTE] Project proposal - Apache AgensGraph Extension

[vongosling]

+1, binding

Very happy to see we have a new graph-database project in apache, hope
folks have a  wonderful podling trip.

Best Regards,
Von Gosling

Jim Jagielski  于2020年4月15日周三 下午11:12写道：

> We would like to propose AgensGraph Extension as an Apache incubator
> project. As such, I am calling a VOTE.
>
> The AgensGraph Extension provides an extension for PostgreSQL to give the
> users the ability to leverage graph database on top of the existing
> relational database with minimal effort. The basic principle of the project
> is to create single storage that can handle both relational and graph model
> data so that the users can use the standard ANSI SQL along with openCypher (
> http://www.opencypher.org), the Graph query language.
>
> The proposal can be found here:
>
>o
> https://cwiki.apache.org/confluence/display/INCUBATOR/AgensGraphExtension
>
> Please cast your vote. I will leave the polls open for at least 72 hours.
>
> PS: Please note that before the podling enters the Incubator, assuming a
> positive vote response, the actual project name will be changed to
> something acceptable as determined by VP Brand.
>
> PPS: If you are interested in mentoring, please let us know. We are
> looking for additional mentors...
>
> Cheers!
> Jim
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Nothing is impossible

Re: [VOTE] Release Apache brpc(incubating) 0.9.7-rc03

[vongosling]

Hi,

+1 (binding)

I checked:
- signatures and hashes fine
- LICENSE and NOTICE is basically ok(there is still a category b dependency
in the source code)
- All necessary files have license headers

To Willem Jiang, the problem I listed last time was the main license
issue(category X should be removed and may keep the category b dependency
in binary ) :-)

Best Regards,
Von Gosling

tan zhongyi  于2020年2月21日周五 下午5:21写道：

> Yes, we will fix these issues later,
> so we add WIP disclaimer as Justin suggested.
> Thanks
>
>
>
> 在 2020/2/19 下午7:36，“Justin Mclean” 写入:
>
> Hi,
>
> > From my understanding, for the CDDL license and LGPL license
> > dependencies, if we don't modify the code, it should be fine.
>
> You can’t have a category X dependancy unless it’s optional. So GPL or
> LGPL dependancies are in general not allowed. See [1]
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/licenses/GPL-compatibility.html
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>

-- 
Nothing is impossible

Re: [DISCUSS] APISIX incubator proposal

[vongosling]

Hi,

It seems to be a very interesting project, which is very close to kong's
positioning. I personally feel that future support for asynchrony may be a
direction that this project may need to consider.
In addition, I am willing to be a mentor for APISIX.



Best Regards,
Von Gosling

Ming  于2019年9月27日周五 上午8:37写道：

> Hi Incubator
>
> I am Ming Wen, we have open-sourced a microservices API gateway called
> APISIX (https://github.com/iresty/apisix), which delivering the ultimate
> performance, security, open source and scalable platform for APIs and
> microservices.
>
> To better build up the whole ecosystem, we decide to donate APISIX project
> to Apache Software Foundation. Therefore, we’d like to propose our project
> to go through the incubation process.
>
> we have already invited Willem Ning Jiang as Champion, Justin Mclean as
> mentor, and welcome other experienced IPMC members to mentor this project.
>
> Attached is our incubation proposal for open discussion, and I added this
> proposal to list (
> https://cwiki.apache.org/confluence/display/INCUBATOR/APISIXProposal).
> Thank you.
>
> Best,
> Ming Wen
>
> --
> = APISIX Proposal =
>
> == Abstract ==
>
> APISIX is a cloud-native microservices API gateway, delivering the ultimate
> performance, security,
> open source and scalable platform for all your APIs and microservices.
>
> APISIX is based on OpenResty and etcd, and has dynamic routing and plug-in
> hot loading,
>  which is especially suitable for API management under micro-service
> system.
>
> == Proposal ==
>
> The goal of this proposal is to bring the existing APISIX
>  codebase and existing developers and
> community
> into the Apache Software Foundation (ASF) in order to build a global,
> diverse and self-governed open source community in API gateway field.
>
> Zhiliu is submitting this proposal to donate the APISIX sources code and
> associated artifacts
> (documentation, web site content, wiki, etc.) to the Apache Software
> Foundation Incubator under the Apache License, Version 2.0.
>
> These artifacts are currently available on GitHub at
> https://github.com/iresty/apisix and include:
> - APISIX: The Cloud-Native Microservices API gateway.
> - APISIX-dashboard: The dashboard for APISIX API gateway.
>
> == Background ==
>
> Mircro-service and Cloud Native architecture are becoming more and more
> popular,
> traditional monolithic applications are being replaced by microservices.
> This also brings more challenges for API gateways, not only handling
> north-south traffic,
> but also handling east-west traffic between microservices,
> and need to ensure high concurrency and very low latency at the same time.
>
> APISIX was open sourced on Github in in June 2019.
> At first, APISIX needs to interact directly with etcd to modify the
> configuration of routes and plugins.
> After we opened on the GitHub, the community gives the feedbacks about high
> level API and built-in dashboard.
> So in 0.6 version, APISIX provided REST admin API and dashboard to control
> the API gateway.
> Since then more and more contributors have joined in, and more plugins and
> features provided.
>
> == Rationale ==
>
> APISIX acts as an entry point for business traffic and plays an important
> role in the current system.
>  Making traffic more secure and faster to process is the ultimate goal of
> APISIX.
>
> APISIX includes these primary parts:
> - Provide the core of the API gateway, including various processing of
> requests and responses, dynamic upstream and dynamic SSL certificates,
> upstream active and passive health checks, etc. The core does not bind
> APISIX, other projects can be used directly.
> - Provide the plug-in hot plugging mechanism based on the core, to
> support gRPC transcoding,
>  identity authentication, rate limiting, OpenTracing etc. And provide a
> plugin development library,
>   users can easily write their own plugins.
> - Provide the admin API and dashboard to operate the API gateway,
> and also support updating with the yaml configuration file, which is
> friendly for Kubernetes.
>
> There is a strong need for an open, easy-to-use microservice API gateway to
> help developers
>  reduce duplication of code development and better manage APIs.
> We believe that by moving to Apache it will help us work in a more global
> and open way.
> Under Apache’s strong governance and existing processes, hope is also to
> make APISIX more reliable and encourage more developers to participate,
>  as is crucial for API gateway.
>
> == Current Status ==
>
> === Meritocracy ===
>
> APISIX was created in April 2019 and opened on github on June 6, 2019.
> The project now has contributors and users from a dozen companies;
> we have set up the PMC Team and Committer Team. New contributors are guided
> and reviewed by existed PMC members.
> When they are ready, PMC will start a vote to promote him/her to become a
> member of PMC or 

Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top Level Project' resolution to board

[vongosling]

+1, binding

Great work!


Mick Semb Wever  于2019年3月19日周二 下午1:21写道：

>
>
> After the latest discussion amongst this dev community on this dev mailing
> list[1],  presenting Sheng Wu as the PMC Chair and the maturity model[2],
> and then the discussion again on the incubator list[3],  a vote for Apache
> SkyWalking graduating to a top level project was called and has passed[4].
> From the past incubator discussions the PPMC altered the draft graduation
> proposal, specifically the proposed PMC list: removing some inactive people
> and adding all the podling Committers.
>
>
> Apache SkyWalking entered the incubator on December of 2017.  SkyWalking
> has delivered 8 releases so far in total, and now shows a good cadence of
> successful releases.
>
> During the podling's time in the Apache Incubator there has been
>  3200+ commits on development of the project,
>   378 Issues tagged as question in GitHub created, 373 resolved,
>   850+ Pull request created and resolved,
>   97 different contributors,
> 9 elected new committers, and
> 3 elected new PPMC members.
>
> And the dev ML has had 72 participants:
> https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019
>
> Attached is the draft Resolution for the PPMC and IPMC to vote upon.
>
> Please take a minute to vote on whether or not Apache SkyWalking should
> graduate to a Top Level Project by responding with one of the following:
>
> [ ] +1 Apache SkyWalking should graduate.
> [ ] +0 No opinion
> [ ] -1 Apache SkyWalking should not graduate (please provide the reason)
>
> The VOTE is open for a minimum of 72 hours. As there has been previous
> discussions on past versions of this proposal, I have not preluded the vote
> with a DISCUSS email. If feedback arises the vote period will be extended
> in good faith.
>
> regards,
> Mick
>
>
> [1]
> https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E
> [2]
> https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking
> [3]
> https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E
> [4]
> https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E
>
> 
>
>
> Establish the Apache SkyWalking 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 application performance management and monitoring (APM).
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache SkyWalking Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache SkyWalking Project be and hereby is
> responsible for the creation and maintenance of software related to
> application performance management and monitoring (APM); and
> be it further
>
> RESOLVED, that the office of "Vice President, Apache SkyWalking" 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
> SkyWalking Project, and to have primary responsibility for management of
> the projects within the scope of responsibility of the Apache SkyWalking
> 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 SkyWalking
> Project:
>
>   * Haoyang Liu  (刘浩杨)  
>   * Hongtao Gao  (高洪涛)  
>   * Ignasi Barrera  
>   * Mick Semb Wever 
>   * Sheng Wu  (吴晟)  
>   * Shinn Zhang  (张鑫)   
>   * Willem Ning Jiang  (姜宁)
>   * Yongsheng Peng  (彭勇升)   
>   * DongXue Si (司冬雪)
>   * Jian Tan (谭建)   
>   * Kai Wang (王凯)   
>   * Yang Bai (柏杨)   
>   * Yao Wang (王垚)   
>   * Zhang Kewei (张科伟)  
>  * Can Li (李璨)  
>  * Jiaqi Lin (林嘉绮)  
>  * Jinlin Fu (付金林)  
>  * Lang Li (李浪)   
>  * Wenbin Wang (王文斌)
>  * Yixiong Cao (曹奕雄)
>
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Wu (吴晟) be
> appointed to the office of Vice President, Apache SkyWalking, 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
>
> 

Re: [VOTE]: Release Apache Dubbo Spring Boot Project (Incubating) 0.2.1 and 0.1.2

[vongosling]

Hi,

+1 binding.

I checked:
- incubating in name
- DISCLAIMER exits
- LICENSE and NOTICE are fine
- Al source file have ASF headers
- No unexpected binary files
- Can compile from source

BTW, some minor problems of the dependency coordinate have been clarified,
hope to update in the next version :-)

Thanks,
Von Gosling


Huxing Zhang  于2019年1月24日周四 下午3:55写道：

> Hi community,
>
> It is already 72 hours, we are still waiting for binding votes to get
> the release passed.
> Would you please take some time to vote for the release candidate?
>
> On Mon, Jan 21, 2019 at 11:53 AM Mercy  wrote:
> >
> > Hello all,
> >
> > This is a call for vote to release Apache Dubbo Spring Boot Project
> (Incubating) 0.2.1 and 0.1.2.
> >
> > The Apache Dubbo community has voted on and approved a proposal to
> release
> > Apache Dubbo Spring Boot Project (Incubating) 0.2.1 and 0.1.2.
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Apache Dubbo™ (incubating) is a high-performance, java based, open source
> > RPC framework. Dubbo offers three key functionalities, which include
> > interface based remote call, fault tolerance & load balancing, and
> > automatic service registration & discovery.
> >
> > Dubbo community vote and result thread:
> >
> https://lists.apache.org/thread.html/e86b324bf3c8c606cb609560a1c4693669a734197e8e4ea95efbd194@%3Cdev.dubbo.apache.org%3E
> >
> >
> > The release candidates (RC2):
> > 0.2.1:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/spring-boot-project/0.2.1/
> > 0.1.2:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/spring-boot-project/0.1.2/
> >
> > Git tag for the release (RC2):
> > 0.2.1:
> https://github.com/apache/incubator-dubbo-spring-boot-project/tree/0.2.1-release
> > 0.1.2:
> https://github.com/apache/incubator-dubbo-spring-boot-project/tree/0.1.2-release
> >
> > Hash for the release tag:
> > 0.2.1: 79e9fa899b74324a8e83d00aac10e3d899b8c3f8
> > 0.1.2: cb66ba32400986609f9e00b0d160173e7b2f55d2
> >
> > Release Notes:
> > 0.2.1:
> https://github.com/apache/incubator-dubbo-spring-boot-project/releases/tag/0.2.1
> > 0.1.2:
> https://github.com/apache/incubator-dubbo-spring-boot-project/releases/tag/0.1.2
> >
> > The artifacts have been signed with Key: A7F508EFDA68B4F5, which can be
> found in the keys file:
> > https://dist.apache.org/repos/dist/dev/incubator/dubbo/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,
> > The Apache Dubbo (Incubating) Team
> >
> > -
> > 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
>
>

-- 
Nothing is impossible

Re: Mentors wanted for Apache Dubbo (incubating)

[vongosling]

Thanks dave, It's our honor to be your mentor for Dubbo, welcome :)

Huxing Zhang  于2018年10月1日周一 下午3:26写道：

> Hi Dave,
>
> Thanks for being a Dubbo mentor! Welcome!
>
> On Wed, Sep 26, 2018 at 9:27 PM Dave Fisher  wrote:
> >
> > Hi -
> >
> > Great talking to community members last night at Apachecon. I appreciate
> being asked to mentor. I’m willing to join Justin and Mark in helping the
> Dubbo community as a mentor.
> >
> > Regards,
> > Dave
> >
> > > On Sep 20, 2018, at 10:33 PM, Huxing Zhang  wrote:
> > >
> > > Hi community,
> > >
> > > The Apache Dubbo project now has two active mentors, and is looking
> > > for new mentors.
> > >
> > > We will be very appreciated if anyone would like to volunteer.
> > >
> > > Below is the brief information:
> > >
> > > Apache Dubbo™ (incubating) is a high-performance, java based open
> > > source RPC framework.
> > > Website: http://dubbo.incubator.apache.org/
> > > Github: https://github.com/apache/incubator-dubbo
> > > Latest Incubator report:
> https://wiki.apache.org/incubator/September2018
> > >
> > > --
> > > 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
> >
>
>
> --
> Best Regards！
> Huxing
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Nothing is impossible

Re: [VOTE] Accept Dubbo into the Apache Incubator

[vongosling]

> > easymockApache License 2.0  true
> > cglib-nodep Apache License 2.0  true
> > resteasyApache License 2.0  true
> > fst Apache License 2.0  true
> > slf4j-api   MIT true
> > jmockit MIT     true
> > jedis   MIT true
> > grizzly CDDL 1.1true
> > servlet-api CDDL 1.1true
> > javax.elCDDL 1.1true
> > logback-classic EPL 1.0 true
> > junit   EPL 1.0 true
> > kryoBSD 3-clausetrue
> >
> >
> > == Required Resources ==
> >
> > === Mailing lists ===
> >
> >  * dubbo-private (PMC discussion)
> >  * dubbo-dev (developer discussion)
> >  * dubbo-commits (SCM commits)
> >  * dubbo-issues (JIRA issue feed)
> >
> > === Subversion Directory ===
> >
> > Instead of subversion, Dubbo prefers to git as source control
> > management system: git://git.apache.org/dubbo
> >
> > === Issue Tracking ===
> >
> > JIRA Dubbo (Dubbo)
> >
> > === Other Resources ===
> >
> > The existing source code already has unit tests so we will make use of
> > existing Apache continuous testing infrastructure. The resulting load
> > should not be very large.
> >
> > == Initial Committers ==
> >
> > (In alphabetical order)
> >
> >  * Ding Li (oldratlee at gmail dot com)
> >  * Huxing Zhang (huxing at apache dot org)
> >  * Ian Luo (ian.luo at gmail dot com)
> >  * Jean-Frederic Clere (jfclere at apache dot org)
> >  * Jun Liu (ken.lj.hz at gmail dot com)
> >  * John D. Ament (johndament at apache dot org)
> >  * Justin McLean  (jmclean at apache dot org)
> >  * Liang Zhang (terrymanu at 163 dot com)
> >  * Liujie Qin (qinliujieyangliu at gmail dot com)
> >  * Mark Thomas (markt at apache dot org)
> >  * Mercy Ma (mercyblitz at gmail dot com)
> >  * Von Gosling (vongosling at apache dot org)
> >  * William Liang (liangfei0201 at gmail dot com)
> >  * Xin Wang (ovepoem at hotmail dot com)
> >  * Zhaohui Yu (yuyijq at gmail dot com)
> >
> > == Affiliations ==
> >
> > (In alphabetical order)
> >
> >  * Alibaba: Ding Li, Huxing Zhang, Ian Luo, Jun Liu, Liujie Qin, Mercy
> > Ma, Von Gosling, William Liang
> >  * Class Software: Justin McLean
> >  * DangDang: Liang Zhang
> >  * Pivotal: Mark Thomas
> >  * Qunar: Zhaohui Yu
> >  * Redhat: Jean-Frederic Clere
> >  * Sparta Systems: John D. Ament
> >  * WeiDian: Xin Wang
> >
> > == Additional Interested Contributors ==
> >
> > (In alphabetical order)
> >
> >  * Hanson Huang (hanson19921129 at gmail dot com)
> >  * Jerrick Zhu (diecui1202 at gmail dot com)
> >  * Peng Wei (weipeng2k at gmail dot com)
> >  * Yuneng Xie (xieyuneng at gmail dot com)
> >  * Zhixuan Cheng (hengyunabc at gmail dot com)
> >
> > == Sponsors ==
> >
> > === Champion ===
> >
> >  * Justin McLean  (jmclean at apache dot org)
> >
> > === Nominated Mentors ===
> >
> >  * Justin McLean  (jmclean at apache dot org)
> >  * John D. Ament (johndament at apache dot org)
> >  * Jean-Frederic Clere (jfclere at apache dot org)
> >  * Mark Thomas (markt at apache dot org)
> >
> >  Informal Mentors 
> >
> >  * Huxing Zhang (huxing at apache dot org)
> >  * Von Gosling (vongosling at apache dot org)
> >
> >
> > === Sponsoring Entity ===
> >
> > We are requesting the Incubator to sponsor this project.
> >
> > --
> > Best Regards！
> > Huxing
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
Nothing is impossible

Re: [DISCUSS] China Contribution. (was: RocketMQ Incubation Proposal)

[vongosling]

Hi,Gunnar Tapper, Willem Jiang:

It's a good idea that we can address the questions or issues through email
list.Thanks for your advice. :)

I am chinese hah~ Through the active participation of the community(Google
Group, Apache Jira, Github Issue, even Gitter )these years, I also found
that if we could make the best use of these tools,  it will be helpful to
the standardization of  software feedback and improvement of the efficiency
:)

As for RocketMQ community, although we also have QQ group previously, at
least two years ago.  In the last two years, we start G
oogle Group, Gitter. But as Willem Jiang said. It is not easy thing to
participating for most chinese developer. For this reason, recently,  we
standard our community. All issues must be discuss and post in issues part.
Question ? oh, no ~ you must post your question on StackOverFlow. In there,
your problem may be able to help a friend who has the same problem as you :)


I believe, with more and more chinese developer come here.  they also hope
to seek a simple and efficient way of communication. As for QQ, may be it
is our last resort, it is an effective complement to local group :)





2016-11-11 9:33 GMT+08:00 Willem Jiang :

> Hi,
>
> As we can see more and more Chinese developer wants to contribute to
>  Apache Software Foundation, but they still need to overcome the language
> barrier even some technical barriers to really join the community.
>
> I'm prefer to use email instead of IM or forums because all the
> discussion can be accessed from public.  But for lot of average Chinese
> users , they may not use English as their working language, it could be
> hard for them to write English email. With the help of Google Translator,
> it could be easy for us to be in the same page if every one use the mailing
> list to discuss the issues.
>
> We tried to setup a cxf-zh google group(there were about 2 hundred people)
> to encourage the CXF users to discuss question in Chinese during the CXF
> incubation, but few people uses it after the Great Fire Wall  started to
> block the Services of Google.   It's convenient for the people to talk to
> each other within the QQ group in China, but it's hard for people to catch
> up the previous talk which happened before he joined the group.  So I think
>  we need to encourage Chinese developer to use the mailing list as the
> major channel to discussion questions and it could be great if email is
> written in English.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Nov 11, 2016 at 3:00 AM, Gunnar Tapper 
> wrote:
>
> > Hi,
> >
> > Using the RocketMQ proposal to start a larger discussion.
> >
> > Apache Trafodion is another project that has a lot of contribution from
> > China.
> >
> > One of the struggles I've seen is that the contributors aren't that
> active
> > on email. Rather, they prefer to use a forum on QQ communicating in
> > Chinese.
> >
> > I'm currently the release manager and I must admit that it's hard not to
> > see all discussions. Several of us are trying to encourage questions etc
> > via the email lists but users just prefer Chinese forums.
> >
> > I suspect that Apache will see more of this behavior moving forward,
> > especially as other proposals come in. So, I'm hoping that members in
> China
> > can help advise on what can be done to address communication issues like
> > this.
> >
> > Thanks,
> >
> > Gunnar
> >
> > On Nov 5, 2016 12:21 PM, "Ross Gardler" 
> > wrote:
> >
> > Some folks may remember my state of the feather session a couple of years
> > ago when I called for more awareness of the ASFs role in open source
> beyond
> > English speaking countries. This was prompted by a fact finding trip to
> > China.
> >
> > RocketMQ and the team behind it was one of the projects I talked to. We
> > discussed the Apache way at length, however I have not been involved with
> > this proposal.
> >
> > I'm excited to see this proposal. I hope we can bring this project and
> > welcome the excellent team I met in China into the foundation. We will
> need
> > to work hard to ensure the project is a success. Like other China born
> > projects we will find that there are cultural differences that we need to
> > understand, but this would not be the first time we, as a foundation and
> as
> > individuals, accept an opportunity to grow in this way. Having met some
> of
> > the proposing team I am confident that with the right mentors the project
> > can succeed.
> >
> > Bruce, thanks for stepping up to help.
> >
> > Ross
> >
> > ---
> > Twitter: @rgardler
> >
> > 
> > From: Bruce Snyder 
> > Sent: Saturday, November 5, 2016 9:21:47 AM
> > To: general@incubator.apache.org
> > Subject: Re: [DISCUSS] RocketMQ Incubation Proposal
> >
> > Hi John,
> >

Re: [DISCUSS] RocketMQ Incubation Proposal

[vongosling]

Justin:

welcome you join our mentor list ~

Best Regards,

Von Gosling

2016-11-08 10:53 GMT+08:00 Justin Mclean :

> Hi,
>
> I’d like my name be added to be a Mentor to the project. Assuming the
> project is willing to have me that is :-)
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Nothing is impossible

Re: [DISCUSS] RocketMQ Incubation Proposal

[vongosling]

Hi, Guys:

I have revised a little about RocketMQ proposal, adding some text to focus
our design attention about RocketMQ. Also, we have removed some mistakenly
imported dependency.

IMO, we are ready to accept contributions from other Apache projects 

Thanks every apacher's advice and help, We have reason to believe RocketMQ
is walking towards a more healthy and more active direction~


Best regards~

from Von Gosling

2016-11-07 18:55 GMT+08:00 John D. Ament :

> On Mon, Nov 7, 2016 at 3:08 AM Bertrand Delacretaz  >
> wrote:
>
> > Hi,
> >
> > On Fri, Nov 4, 2016 at 10:26 PM, John D. Ament 
> > wrote:
> > > ...- How can RocketMQ work with the existing Kafka or ActiveMQ
> > communities to
> > > build cross platform clients?
> > > - How can RocketMQ look to leverage Cassandra, Geode, Derby as backend
> > > persistence stores?...
> >
> > It would be wrong to require a podling to create specific modules so
> > that it plays better with other Apache projects. I'm not saying you
> > are suggesting this John, but the above questions could be interpreted
> > like that.
> >
> >
> This question has already been clarified a second time for the proposal.
> Luke seems to have a handle on it and has made notions to update the
> proposal to sound less competitive and focus on what we typically see in
> this area.
>
> John
>
>
> > The ASF doesn't have a technical roadmap and doesn't influence our
> > project's technical direction - besides requirements for being serious
> > about security and quality as per
> > http://community.apache.org/apache-way/apache-project-
> maturity-model.html
> >
> > What's important IMO is whether the new podling is ready to accept
> > contributions from other Apache projects that enable things like
> > mentioned in the above questions.
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
Nothing is impossible

Re: [DISCUSS] RocketMQ Incubation Proposal

[vongosling]

Hi, john:

Thank you providing AsterixDB proposal, so as to help our complement our
proposal. Or to say, give us some advice for RocketMQ community development
roadmap~

Next, let me clarify some question we have talked about.


1. About ONS and RocketMQ relationship~

ONS is our Cloud Messaging Service, you also think it as our internal
messaging name. But it is built base on RocketMQ, adding some extra
features mainly associated with security, audit, web console, etc...  Have
I made everything clear to you. If not, I can depict it using some
pictures~


2. How can RocketMQ work with the existing Kafka or ActiveMQ communities to
build cross platform clients?

IMO, excellent products, They must have a common feature. That is its
pluggable mechanism. We can use it, just like i have said in the latest
reply(we are developing kafka-proxy this product, in the near future, we
hope to invite kafka guys to make a technical exchange). We can use this
idea to integrate RocketMQ with Kafka and ActiveMQ ecosystem seamlessly.

In addition, we are planning to draft some messaging specification.we want
it absorb the advantage of the existing Corbar‘s Notification Service
Specification, JMS, AMQP, MQTT and other text protocol.It not include API
layer standard, but also possess wireless protocol advantage. May be it
will experience a long time to discuss. But If an agreement is reached, may
be, no matter Kafka, ActiveMQ, RocketMQ or other MQ products, there was no
doubting that cross platform client is not a difficult thing because our
common cross-platform protocol.

3. How can RocketMQ look to leverage Cassandra, Geode, Derby as backend
persistence stores?

As I have said, nowadays, RocketMQ storage is custom-built for low-latency
purpose. It just use JDK primitive FIle API and some JNI tech..
In the next step, if we hope to leverage Cassandra, Geode, Derby or other
full-blown product, we must research them intensively, knowing about and
make sure they are suitable for our low latency design goal. At the same
time, we also abstract our storage layer(you can think it as SPI), let it
meet adaptor design pattern(We will also make use of JDK's service locator
pattern to support our storage SPI ). All these are in ready, many concrete
implementation adapter can be created, may be by RocketMQ project guys, may
be contributed by community enthusiast. if latter way, we must give some
guidance and help for them. The guidance seems like this
https://github.com/alibaba/RocketMQ/wiki/multi-language-sdk.


Last, Thanks again every apache guys(Especially Bruce, Brian, Ross, John,
Roman, Greg, Jim etc... )magnanimous diverse culture. We have reasons to
believe that Apache is the most suitable home as an open source project
following an established development model. We are always willing to lend
an ear to the apache and communities, making our product ecosystem towards
a more healthy and more active direction~


Best Regards ~

Von Gosling


2016-11-06 17:20 GMT+08:00 Greg Stein :

> On Fri, Nov 4, 2016 at 4:26 PM, John D. Ament 
> wrote:
> >...
>
> > I'm still a bit leary about the "relationship with other apache products"
> > section still.  I'm not interested in seeing how a podling competes with
> > other projects
>
>
> Apache projects don't "compete" with anybody. The source code is *offered*
> to the public.
>
> As a 501(c)(3), we're specifically disallowed from competing with
> commercial organizations. But even within the ASF and other open source
> projects, the ASF is simply providing a home for communities to organize,
> to grow, to construct software for the public. At its most base level, the
> Foundation doesn't care what the project does, how "successful" it is (by
> whatever metric), or if ten of its communities all produce software to do
> the same thing. Each community might have a different thought, a different
> approach, or even something as minor as a different view on release cycles.
>
> All communities are welcome.
>
> Cheers,
> -g
>



-- 
Nothing is impossible

Re: [DISCUSS] RocketMQ Incubation Proposal

[vongosling]

Hi，John，Roman:

I am vongosling. The creator of RocketMQ. Please let me, on behalf of the
RocketMQ project, to talk about a period of history. May be it can explain
why we wrote "RocketMQ has open source since 2012". Actually, RocketMQ is
the third generation Distributed MOM product within alibaba. The other 2
generation products, we call it "MetaQ". So you can think it  we created
the MetaQ 1.0 and MetaQ 2.0.
The biggest luminescent spot of MetaQ1 is its scalable text protocol and
JTA support. In MetaQ 2, we let one broker support more partitions and less
IO resources. MetaQ1 has open source since 2012. About this product , we
can see from this link here https://github.com/killme2008/Metamorphosis.
Maybe the follwing chinese texts will give us some clue.

"MetaQ的淘宝版本已经发展到2.0乃至3.0版本，设计原则发生了变更，有兴趣的可以上它的官方网站看。”

The text above definitely showing that MetaQ has developed to 2.0 and 3.0.
No problem. In 3.0 version, we can not follow the previous name convention.
We renamed it RocketMQ. hoping it will be as fast as Rocket, low latency in
our high frequency trading scenario.Haha, yeah.Even now, MetaQ is still
maintained by some alibaba‘s tech. enthusiast in Github.

Like Roman said, "commit early, commit often" mentality, is always our open
source belief. According to what I said before, we really hope to find a
way to keep the same deploy, especially commit pace between Git
repositories. Thanks Roman’s advice 


 "there wasn't a ton of open source development on the product ". Thank's
john question. Please believe our open source mentality. In past 7 years,
With the alibaba business dramatical growth, our team faced a lot of
system architecture
and design challenges, we want to share our experience with every people.
But, We also hope more people to join us, to help us to perfect messaging
engine, which can bearing Trillion message  communication in the double
eleven Shopping Festival every year. For this purpose, we open a survey for
our customer as the link(https://github.com/alibaba/RocketMQ/issues/1 and
https://github.com/alibaba/RocketMQ/issues/353)  shows.Knowing your
customers, assembleing them together and making our community more health,
more active~

  "relationship with other apache products".There is no doubting, apache is
the most famous open source organization. Many companies, especially those
tech. companies, having benefited from apache's a ton of excellent open
source projects. Alibaba is also One of the beneficiaries, RocketMQ used a
lot of Apache Commons tools  in its every component.Also, this reason drive
us to donate our product. As an old Chinese saying goes  “What is taken
from the people is used in the interests of the people”. Here, we can
replace people with apache hah~

Also, IMHO, ActiveMQ, Kafka, RocektMQ and other apache MQ products. The
relationship, like apache’s many
streaming solutions(spark,flink,samza,storm etc.), they are
not competitors, They both have their own designs and do well in their
dedicated directions. BTW, within alibaba, in some bigdata departments,
Kafka is still their first choice. Also this reason, in my team, we have
some kafka tech. staffs to service them passionately.

 Last. Nowadays, RocketMQ storage is custom-built for low-latency purpose,
using JDK primitive FIle API and some JNI tech.. Different with activeMQ.
we are not support many storage strategies now. but we are planning to
extract storage layer. May be a  thin abstract layer, many concrete
implementation adapter (leverage Cassandra, Derby  or some off heap storage
engine). would occur. As another question, "cross platform
clients cooperativity". as I said above, some staffs in my team, are
dedicated to support service for kafka. they are developing anther product
kafka-proxy, make use of kafka existence client. The full data streaming
process is like this "kafka producer -> kafka proxy-> kafka consumer or
rocketmq consumer " Moreover, we are absorbing community proactive guys, to
assist us to complete cross language sdk like our design showing(
https://github.com/alibaba/RocketMQ/wiki/multi-language-sdk).

As proposal said, the ASF is the natural choice to host the RocketMQ
project as its goal of encouraging community-driven open source projects
fits with our vision for RocketMQ.

That's all, Thanks for everyone‘s advice and questions.



Best regards ~

from vongosling

2016-11-05 5:26 GMT+08:00 John D. Ament <john.d.am...@gmail.com>:

> On Fri, Nov 4, 2016 at 4:43 PM Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
> > The proposal looks fine in general, but I'm slightly concerned about:
> >https://github.com/alibaba/RocketMQ/graphs/contributors
> >
> > It seems that the model so far has been -- through huge blobs of
> > code over the wall. Given that the composition of initial committers
> > is all from Alibaba I hope their mentors will spend 

Re: [DISCUSS] RocketMQ Incubation Proposal

[vongosling]

Hi，John:
  1. Our mentor Luke and Willem will rectify IPMC membership
later. Thank you for reminding~

  2. About another mentioned product ONS( is the abbreviation for Open
Notification Service)，which is maintained by Alibaba. Custom-built product for
enterprise and cloud application.It based on RocketMQ(RocketMQ not depend
ONS),adding some value added service, such as security, audit, web console
etc. We asked about RocketMQ brand thing with ASF chairman Ross when he
came to china previously，so we make another name ONS since then~

  3. Sparse revision. hah~~~ It can be talked about from la long time
ago, our one core committer commit some sensitive data in Github because
of oversight. Some one day, our Security department supervisor found me,
“Why do you commit some company related secret data to Github, Why ?” The
end of the story is the same as you think. Because revision history, we
must erase it. So we reset our commit history using git command. BTW,
RocketMQ has open source since 2012. For simplicity in local community, we
also push our code to our local famous Git repository except for Github(But
it's unlucky, we also erase it in last scavenging activity). We want to
develop borderless open source and make the same release
pace within company. So, we comply with apache way, also hope some advice
from community to help us improve our product.

 4. It was a slight overlook on my part. Derby and Apache Commons-IO
dependency can be removed(Its' useless in our latest version ). RocketMQ
uses JNA to solve the latency issue in storage, and we found that JNA also
is under the Apache Software License(
https://github.com/java-native-access/jna#license). If JNA is incompatible
with Apache License, we can replace it with JNI, actually we are planning
to do this.


Last but not important, we hope to more and more people join us, we are
always very happy to have contributions, whether for trivial cleanups, big
new features or other material rewards. For this purpose, we started one
issue thread(https://github.com/alibaba/RocketMQ/issues/353) to assemble
some enthusiast to join us. to make our community more active, to make our
service more attractive~

2016-11-04 6:42 GMT+08:00 John D. Ament :

> Bruce,
>
> While Willem and Luke are both foundation members, neither is on the IPMC.
> That's easy enough to rectify if you can get them to send appropriate
> emails out requesting membership.
>
> I'm assuming the mailing lists will all be in the new format of
> list@rocketmq.i.a.o
>
> The RocketMQ github site mentions "Alibaba's MQ, also aliyun ONS.
> http://www.aliyun.com/product/ons; Can you explain the relationship to
> Aliyun ONS? (the link is dead)
>
> I notice that the revision history is pretty sparse.  I'm assuming that it
> was mostly maintained internal and not fully open sourced until recently?
>
> I notice in the proposal that its mentioned RocketMQ doesn't integration
> with existing Apache projects - but it currently declares dependencies on
> Commons IO, CLI, Derby to name a few.  The only license that sticks out is
> JNA, which itself has a weird licensing scheme.  Not a blocker for
> incubation, but may require some trickery at release time.
>
> John
>
> On Thu, Nov 3, 2016 at 6:10 PM Bruce Snyder 
> wrote:
>
> > Please find below a proposal for a new Incubator podling named Apache
> > RocketMQ, a fast, low latency, reliable, scalable, distributed, easy to
> use
> > message-oriented middleware, especially for processing large amounts of
> > streaming data.
> >
> > The draft proposal can be found in the wiki at the following URL:
> >
> > https://wiki.apache.org/incubator/RocketMQProposal
> >
> > Below, please find the text for the proposal below.
> >
> > Thanks,
> >
> > Bruce
> >
> >
> >
> > = RocketMQ Proposal =
> >
> > == Abstract ==
> >
> > RocketMQ is a fast, low latency, reliable, scalable, distributed, easy to
> > use message-oriented middleware, especially for processing large amounts
> of
> > streaming data.
> >
> > == Proposal ==
> >
> > RocketMQ provides a message model including both pub/sub and P2P and it
> > supports both reliable FIFO and strict sequential message queues. It also
> > has the ability to accumulate a billion messages in a single queue,
> > provides mobile, internet-friendly protocols such as MQTT and HTTP.
> > RocketMQ also supports the ability to load data into Apache Hadoop for
> > offline storage or to handle stream processing for Apache Storm.
> >
> > == Background ==
> >
> > RocketMQ was developed at Alibaba in 2011 and has been used in production
> > there since that time. It can process the large amounts of events
> generated
> > by various systems and provides a common repository for many types of
> > consumers to access and process those events. RocketMQ also handles
> dozens
> > of types of events including trade order process, search, social network
> > activity stream and data pipeline. Every day 

Re: [VOTE] Accept NetBeans into the Apache Incubator

[vongosling]

+1 (enthusiastic, non-binding) :-)

2016-09-29 8:29 GMT+08:00 David Lyle :

> +1 (non-binding) Welcome!
>
> On Wed, Sep 28, 2016 at 7:53 PM, Bruno Flávio 
> wrote:
>
> > +1 (enthusiastic)
> >
> > On Tuesday, 27 September 2016 22:30:36 WEST Ate Douma wrote:
> > > Hi everyone,
> > >
> > > Now that the discussion thread on the NetBeans Proposal has ended,
> > > please vote on accepting NetBeans into the Apache Incubator.
> > >
> > > The ASF voting rules are described at:
> > > http://www.apache.org/foundation/voting.html
> > >
> > > A vote for accepting a new Apache Incubator podling is a majority vote
> > > for which only Incubator PMC member votes are binding.
> > >
> > > Votes from other people are also welcome as an indication of peoples
> > > enthusiasm (or lack thereof).
> > >
> > > Please do not use this VOTE thread for discussions.
> > > If needed, start a new thread instead.
> > >
> > > This vote will run for at least 72 hours. Please VOTE as follows
> > > [] +1 Accept NetBeans into the Apache Incubator
> > > [] +0 Abstain.
> > > [] -1 Do not accept NetBeans into the Apache Incubator because ...
> > >
> > >
> > > The proposal is listed below, but you can also access it on the wiki:
> > > https://wiki.apache.org/incubator/NetBeansProposal
> > >
> > >
> > > Thanks,
> > > Ate.
> > >
> > > == Abstract ==
> > >
> > > NetBeans is an open source development environment, tooling platform,
> and
> > > application framework, used by 1.5 million individuals each month.
> > >
> > > == Proposal ==
> > > Apache NetBeans will continue to focus on the areas it has focused on
> > while
> > > sponsored by Sun Microsystems and Oracle. It will continue to primarily
> > > focus on providing tools for the Java ecosystem, while also being
> focused
> > > on tools for other ecosystems, languages and technologies, such as
> > > JavaScript, PHP, and C/C++. It will continue to actively support its
> > > community by means of mailing lists, tutorials, and documentation.
> > >
> > > == Background ==
> > > NetBeans started in 1995/96 in Prague, in the Czech Republic, as a
> > student
> > > project. Sun Microsystems acquired and open sourced it in 2000 and,
> with
> > the
> > > acquisition of Sun Microsystems by Oracle in 2010, became part of
> Oracle.
> > > Throughout its history in Sun Microsystems and Oracle, NetBeans has
> been
> > > free and open source and has been leveraged by its sponsor as a
> mechanism
> > > for driving the Java ecosystem forward.
> > >
> > > == Rationale ==
> > > Although NetBeans is already open source, moving it to a neutral place
> > like
> > > Apache, with its strong governance model, is expected to help get more
> > > contributions from various organizations. For example, large companies
> > are
> > > using NetBeans as an application framework to build internal or
> > commercial
> > > applications and are much more likely to contribute to it once it moves
> > to
> > > neutral Apache ground. At the same time, though Oracle will relinquish
> > its
> > > control over NetBeans, individual contributors from Oracle are expected
> > to
> > > continue contributing to NetBeans after it has been contributed to
> > Apache,
> > > together with individual contributors from other organizations, as well
> > as
> > > self-employed individual contributors.
> > >
> > > == Initial Goals ==
> > > The initial goals of the NetBeans contribution under the Apache
> umbrella
> > are
> > > to establish a new home for an already fully functioning project and to
> > > open up the governance model so as to simplify and streamline
> > contributions
> > > from the community.
> > >
> > > == Current Status ==
> > >  Meritocracy: NetBeans has been run by Oracle, with the majority of
> > code
> > > contributions coming from Oracle. The specific reason for moving to
> > Apache
> > > is to expand the diversity of contributors and to increase the level of
> > > meritocracy in NetBeans. Apache NetBeans will be actively seeking new
> > > contributors and will welcome them warmly and provide a friendly and
> > > productive environment for purposes of providing a development
> > environment,
> > > tooling environment, and application framework.
> > >
> > >  Community: NetBeans has approximately 1.5 million active users
> > around
> > > the world, in extremely diverse structures and organizations. NetBeans
> is
> > > used by teachers and instructors at schools and universities to teach
> > Java
> > > and other languages. It is used by students as an educational tool. It
> is
> > > used by large organizations who base their software on the application
> > > framework beneath NetBeans. It is used by web developers for creating
> web
> > > sites and by developers using a range of tools, languages, and
> > technologies
> > > to be productive and efficient software developers.
> > >
> > >  Core Developers: The core developers will come from a range of
> > > organizations,