Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[Justin Mclean]

Hi,

> It can be a case of The Ship of Theseus. When you take a look at the issued
> files[1][2], you may find a commit history touching them and modifying
> them. Anyway, it's not an identical copy or one-shot translation.

This has been discussed many times on various lists, translating an algorithm 
from one language to another does not change its license.

> And we keep the origin comments.

Which is also an IP issue.

Kinds Regards,
Justin


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

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

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, Feb 10, 2023 at 3:31 AM Eason Chen  wrote:
>
> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
>
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
>
> *Community*
>
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
>
> *Project*
>
> ● Apache EventMesh(incubating) builds a fully serverless platform for
> distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
>
> *Brands, License, and Copyright*
>
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache EventMesh Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a fully serverless platform used to build distributed
> event-driven applications.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to a fully
> serverless platform used to build distributed event-driven applications;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache EventMesh
> Project:
>
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   
>  * Wenjun Ruan  
>  * XiaoShuang Li
>  * Xue Weiming  
>  * Yuwei Zhu
>
> NOW, THEREFORE, BE IT FURTHER RESOLV

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

[Shuai Di]

+1 (non-binding)
EventMesh has a group of very passionate and hard working guys. Good luck!

在 2023年2月14日星期二，梁荣华  写道：

> +1. Feel happy for this great moment
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> At 2023-02-14 10:23:17, "Jialin Sun"  wrote:
> >+1. Feel happy for this great moment
> >
> >On 2023/02/10 02:31:56 Eason Chen wrote:
> >> Dear Apache Incubator Community and IPMC members,
> >>
> >> After having the graduation discussion in the EventMesh community [1],
> >> we passed the vote within the EventMesh community [2] and the vote
> >> result was published[3].
> >> We then discussed the graduation for EventMesh in the Apache Incubator
> >> Community [4], where no issues were raised and positive replies were
> >> received.
> >>
> >> I would like to start this voting thread to request graduating Apache
> >> EventMesh(incubating) from Apache Incubator as a Top Level Project.
> >>
> >> Please provide your vote accordingly:
> >> [ ] +1 Yes, I support the EventMesh project to graduate from the
> >> Apache Incubator.
> >> [ ] +0 No opinion.
> >> [ ] -1 No, the EventMesh project is not ready to graduate, because...
> >>
> >> Thank you for participating in the vote. This vote will stay open for
> >> at least 72 hours.
> >>
> >> Here is an overview of the Apache EventMesh(incubating) to help with
> the vote.
> >>
> >> *Community*
> >>
> >> ● 5 new PPMC members were added, bringing the total number of PPMC
> >> members to 14 from at least 9 different organizations.
> >> ● 20 new Committers were added, bringing the total number of
> >> committers to 42 from at least 30 different organizations.
> >> ● 220+ new contributors participate in the community. The number of
> >> contributors is now 250+ and growing.
> >> ● 20 Bi-weekly online meetings were held among the committers,
> >> contributors, and users. The meeting minutes are recorded on the
> >> mailing list[5] and cwiki [6].
> >> ● The dev@eventmesh mailing list currently has 117 subscribers.
> >> ● We've confirmed the VP, PMC, and Committers in the preparation
> >> discussion at private@eventmesh [7]. Eason
> >> Chen(chenguangsh...@apache.org) was recommended as Vice President.
> >>
> >> *Project*
> >>
> >> ● Apache EventMesh(incubating) 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 imme

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

[Shuai Di]

+1 (non-binding)
EventMesh has a group of very passionate and hard working guys. Good luck!

在 2023年2月14日星期二，Jianbo Mai  写道：

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

[CANCEL][VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[Pengbo Cai]

Hello Incubator PMC,

I'm cancelling this vote due to license issues:
https://lists.apache.org/thread/q11wxgg3hdw694w5csf43trgv7yvj2jt

I will start a new vote after we have resolved those issues.

Best,
Pengbo Cai

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[Pengbo Cai]

Due to doubts, I will cancel this release vote. I will start a new vote after 
we have resolved @kezhenxu94's issue.

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

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[tison]

I submit a patch: https://github.com/apache/incubator-kvrocks/pull/1259

@zhenxu you're welcome to help verify if it fixes your concerns.

... and -1 (binding)

@Myth I think we need a new release candidate :)

Best,
tison.


tison  于2023年2月14日周二 10:47写道：

> Thanks for your confirmation. Then I agree the content should be updated
> to avoid risk.
>
> kezhenxu94 于2023年2月14日 周二10:43写道：
>
>> But at the same time, the file header has `/* from valgrind tests */`,
>> I assumed you ported the variation of Valgrind.
>>
>> A good practice is not to add more license information than you
>> actually do, i.e., don't declare it's from valgrind tests if you
>> believe you are using the original Public Domain sha1.c file,
>> confusions arise like this.
>>
>> > On Feb 14, 2023, at 10:22, tison  wrote:
>> >
>> > Hi zhenxu,
>> >
>> > When you look at the header, it writes:
>> >
>> > SHA-1 in C
>> > By Steve Reid 
>> > 100% Public Domain
>> >
>> > Zhenxu Ke 于2023年2月14日 周二10:00写道：
>> >
>> >> Hi, sorry the mailer-dae...@apache.org just says it can't deliver my
>> >> email, which should be sent out last night (2023/02/13 22:49), here is
>> my
>> >> reply:
>> >>
>> >> Hi, now I would continue to vote -1 and I believe this should be fixed
>> >> ASAP, because you might copy the file[1] from Redis, but the file is
>> not
>> >> originated from Redis either, it’s copied from yet another project
>> >> valgrind[2], which is GPL licensed[3].
>> >>
>> >> [1] incubator-kvrocks/src/common/sha1.cc
>> >> [2]
>> https://github.com/danos/valgrind/blob/master/none/tests/sha1_test.c
>> >> [3] https://github.com/danos/valgrind/blob/master/COPYING
>> >>
>> >> On 2023/02/14 00:43:19 tison wrote:
>> >>> Hi Justin,
>> >>>
>> >>> It can be a case of The Ship of Theseus. When you take a look at the
>> >> issued
>> >>> files[1][2], you may find a commit history touching them and modifying
>> >>> them. Anyway, it's not an identical copy or one-shot translation. And
>> we
>> >>> keep the origin comments.
>> >>>
>> >>> Even a one-shot translation, if it's done by humans, generally
>> >> modification
>> >>> will be applied.
>> >>>
>> >>> But if you insist on "keep the original license header and don't add
>> the
>> >>> ASF header" with an existing documented guideline, the Kvrocks
>> >> contributors
>> >>> would be glad to change it.
>> >>>
>> >>> Best,
>> >>> tison.
>> >>>
>> >>> [1]
>> >>>
>> >>
>> https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc
>> >>> [2]
>> >>>
>> >>
>> https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc
>> >>>
>> >>>
>> >>> Justin Mclean  于2023年2月14日周二 05:39写道：
>> >>>
>>  Hi,
>> 
>>  In general porting a file from one language to another would not
>> change
>>  the original license.
>> 
>>  Kind Regards,
>>  Justin
>>  -
>>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>  For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
>> >>>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>
>> >> --
>> > Best,
>> > tison.
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>> --
> Best,
> tison.
>

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

[梁荣华]

+1. Feel happy for this great moment















At 2023-02-14 10:23:17, "Jialin Sun"  wrote:
>+1. Feel happy for this great moment
>
>On 2023/02/10 02:31:56 Eason Chen wrote:
>> Dear Apache Incubator Community and IPMC members,
>> 
>> After having the graduation discussion in the EventMesh community [1],
>> we passed the vote within the EventMesh community [2] and the vote
>> result was published[3].
>> We then discussed the graduation for EventMesh in the Apache Incubator
>> Community [4], where no issues were raised and positive replies were
>> received.
>> 
>> I would like to start this voting thread to request graduating Apache
>> EventMesh(incubating) from Apache Incubator as a Top Level Project.
>> 
>> Please provide your vote accordingly:
>> [ ] +1 Yes, I support the EventMesh project to graduate from the
>> Apache Incubator.
>> [ ] +0 No opinion.
>> [ ] -1 No, the EventMesh project is not ready to graduate, because...
>> 
>> Thank you for participating in the vote. This vote will stay open for
>> at least 72 hours.
>> 
>> Here is an overview of the Apache EventMesh(incubating) to help with the 
>> vote.
>> 
>> *Community*
>> 
>> ● 5 new PPMC members were added, bringing the total number of PPMC
>> members to 14 from at least 9 different organizations.
>> ● 20 new Committers were added, bringing the total number of
>> committers to 42 from at least 30 different organizations.
>> ● 220+ new contributors participate in the community. The number of
>> contributors is now 250+ and growing.
>> ● 20 Bi-weekly online meetings were held among the committers,
>> contributors, and users. The meeting minutes are recorded on the
>> mailing list[5] and cwiki [6].
>> ● The dev@eventmesh mailing list currently has 117 subscribers.
>> ● We've confirmed the VP, PMC, and Committers in the preparation
>> discussion at private@eventmesh [7]. Eason
>> Chen(chenguangsh...@apache.org) was recommended as Vice President.
>> 
>> *Project*
>> 
>> ● Apache EventMesh(incubating) 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] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[tison]

Thanks for your confirmation. Then I agree the content should be updated to
avoid risk.

kezhenxu94 于2023年2月14日 周二10:43写道：

> But at the same time, the file header has `/* from valgrind tests */`,
> I assumed you ported the variation of Valgrind.
>
> A good practice is not to add more license information than you
> actually do, i.e., don't declare it's from valgrind tests if you
> believe you are using the original Public Domain sha1.c file,
> confusions arise like this.
>
> > On Feb 14, 2023, at 10:22, tison  wrote:
> >
> > Hi zhenxu,
> >
> > When you look at the header, it writes:
> >
> > SHA-1 in C
> > By Steve Reid 
> > 100% Public Domain
> >
> > Zhenxu Ke 于2023年2月14日 周二10:00写道：
> >
> >> Hi, sorry the mailer-dae...@apache.org just says it can't deliver my
> >> email, which should be sent out last night (2023/02/13 22:49), here is
> my
> >> reply:
> >>
> >> Hi, now I would continue to vote -1 and I believe this should be fixed
> >> ASAP, because you might copy the file[1] from Redis, but the file is not
> >> originated from Redis either, it’s copied from yet another project
> >> valgrind[2], which is GPL licensed[3].
> >>
> >> [1] incubator-kvrocks/src/common/sha1.cc
> >> [2]
> https://github.com/danos/valgrind/blob/master/none/tests/sha1_test.c
> >> [3] https://github.com/danos/valgrind/blob/master/COPYING
> >>
> >> On 2023/02/14 00:43:19 tison wrote:
> >>> Hi Justin,
> >>>
> >>> It can be a case of The Ship of Theseus. When you take a look at the
> >> issued
> >>> files[1][2], you may find a commit history touching them and modifying
> >>> them. Anyway, it's not an identical copy or one-shot translation. And
> we
> >>> keep the origin comments.
> >>>
> >>> Even a one-shot translation, if it's done by humans, generally
> >> modification
> >>> will be applied.
> >>>
> >>> But if you insist on "keep the original license header and don't add
> the
> >>> ASF header" with an existing documented guideline, the Kvrocks
> >> contributors
> >>> would be glad to change it.
> >>>
> >>> Best,
> >>> tison.
> >>>
> >>> [1]
> >>>
> >>
> https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc
> >>> [2]
> >>>
> >>
> https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc
> >>>
> >>>
> >>> Justin Mclean  于2023年2月14日周二 05:39写道：
> >>>
>  Hi,
> 
>  In general porting a file from one language to another would not
> change
>  the original license.
> 
>  Kind Regards,
>  Justin
>  -
>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>  For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >> --
> > Best,
> > tison.
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
Best,
tison.

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[kezhenxu94]

But at the same time, the file header has `/* from valgrind tests */`,
I assumed you ported the variation of Valgrind.

A good practice is not to add more license information than you
actually do, i.e., don't declare it's from valgrind tests if you
believe you are using the original Public Domain sha1.c file,
confusions arise like this.

> On Feb 14, 2023, at 10:22, tison  wrote:
> 
> Hi zhenxu,
> 
> When you look at the header, it writes:
> 
> SHA-1 in C
> By Steve Reid 
> 100% Public Domain
> 
> Zhenxu Ke 于2023年2月14日 周二10:00写道：
> 
>> Hi, sorry the mailer-dae...@apache.org just says it can't deliver my
>> email, which should be sent out last night (2023/02/13 22:49), here is my
>> reply:
>> 
>> Hi, now I would continue to vote -1 and I believe this should be fixed
>> ASAP, because you might copy the file[1] from Redis, but the file is not
>> originated from Redis either, it’s copied from yet another project
>> valgrind[2], which is GPL licensed[3].
>> 
>> [1] incubator-kvrocks/src/common/sha1.cc
>> [2] https://github.com/danos/valgrind/blob/master/none/tests/sha1_test.c
>> [3] https://github.com/danos/valgrind/blob/master/COPYING
>> 
>> On 2023/02/14 00:43:19 tison wrote:
>>> Hi Justin,
>>> 
>>> It can be a case of The Ship of Theseus. When you take a look at the
>> issued
>>> files[1][2], you may find a commit history touching them and modifying
>>> them. Anyway, it's not an identical copy or one-shot translation. And we
>>> keep the origin comments.
>>> 
>>> Even a one-shot translation, if it's done by humans, generally
>> modification
>>> will be applied.
>>> 
>>> But if you insist on "keep the original license header and don't add the
>>> ASF header" with an existing documented guideline, the Kvrocks
>> contributors
>>> would be glad to change it.
>>> 
>>> Best,
>>> tison.
>>> 
>>> [1]
>>> 
>> https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc
>>> [2]
>>> 
>> https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc
>>> 
>>> 
>>> Justin Mclean  于2023年2月14日周二 05:39写道：
>>> 
 Hi,
 
 In general porting a file from one language to another would not change
 the original license.
 
 Kind Regards,
 Justin
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> --
> Best,
> tison.


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

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[tison]

Hi zhenxu,

When you look at the header, it writes:

SHA-1 in C
By Steve Reid 
100% Public Domain

Zhenxu Ke 于2023年2月14日 周二10:00写道：

> Hi, sorry the mailer-dae...@apache.org just says it can't deliver my
> email, which should be sent out last night (2023/02/13 22:49), here is my
> reply:
>
> Hi, now I would continue to vote -1 and I believe this should be fixed
> ASAP, because you might copy the file[1] from Redis, but the file is not
> originated from Redis either, it’s copied from yet another project
> valgrind[2], which is GPL licensed[3].
>
> [1] incubator-kvrocks/src/common/sha1.cc
> [2] https://github.com/danos/valgrind/blob/master/none/tests/sha1_test.c
> [3] https://github.com/danos/valgrind/blob/master/COPYING
>
> On 2023/02/14 00:43:19 tison wrote:
> > Hi Justin,
> >
> > It can be a case of The Ship of Theseus. When you take a look at the
> issued
> > files[1][2], you may find a commit history touching them and modifying
> > them. Anyway, it's not an identical copy or one-shot translation. And we
> > keep the origin comments.
> >
> > Even a one-shot translation, if it's done by humans, generally
> modification
> > will be applied.
> >
> > But if you insist on "keep the original license header and don't add the
> > ASF header" with an existing documented guideline, the Kvrocks
> contributors
> > would be glad to change it.
> >
> > Best,
> > tison.
> >
> > [1]
> >
> https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc
> > [2]
> >
> https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc
> >
> >
> > Justin Mclean  于2023年2月14日周二 05:39写道：
> >
> > > Hi,
> > >
> > > In general porting a file from one language to another would not change
> > > the original license.
> > >
> > > Kind Regards,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
Best,
tison.

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

[Jialin Sun]

+1. Feel happy for this great moment

On 2023/02/10 02:31:56 Eason Chen wrote:
> Dear Apache Incubator Community and IPMC members,
> 
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
> 
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
> 
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
> 
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
> 
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
> 
> *Community*
> 
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
> 
> *Project*
> 
> ● Apache EventMesh(incubating) builds a fully serverless platform for
> distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
> 
> *Brands, License, and Copyright*
> 
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
> 
> -
> BEGINNING OF DRAFT RESOLUTION
> -
> 
> Establish the Apache EventMesh Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a fully serverless platform used to build distributed
> event-driven applications.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to a fully
> serverless platform used to build distributed event-driven applications;
> and be it further
> 
> RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache EventMesh
> Project:
> 
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   
>  * Wenjun Ruan  
>  * XiaoShuang Li
>  * Xue Weiming  
>  * Yuwei Zhu
> 
> NOW, THEREFORE, 

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[Zhenxu Ke]

Hi, sorry the mailer-dae...@apache.org just says it can't deliver my email, 
which should be sent out last night (2023/02/13 22:49), here is my reply:

Hi, now I would continue to vote -1 and I believe this should be fixed ASAP, 
because you might copy the file[1] from Redis, but the file is not originated 
from Redis either, it’s copied from yet another project valgrind[2], which is 
GPL licensed[3]. 

[1] incubator-kvrocks/src/common/sha1.cc
[2] https://github.com/danos/valgrind/blob/master/none/tests/sha1_test.c
[3] https://github.com/danos/valgrind/blob/master/COPYING

On 2023/02/14 00:43:19 tison wrote:
> Hi Justin,
> 
> It can be a case of The Ship of Theseus. When you take a look at the issued
> files[1][2], you may find a commit history touching them and modifying
> them. Anyway, it's not an identical copy or one-shot translation. And we
> keep the origin comments.
> 
> Even a one-shot translation, if it's done by humans, generally modification
> will be applied.
> 
> But if you insist on "keep the original license header and don't add the
> ASF header" with an existing documented guideline, the Kvrocks contributors
> would be glad to change it.
> 
> Best,
> tison.
> 
> [1]
> https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc
> [2]
> https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc
> 
> 
> Justin Mclean  于2023年2月14日周二 05:39写道：
> 
> > Hi,
> >
> > In general porting a file from one language to another would not change
> > the original license.
> >
> > Kind Regards,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> 

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

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

[Mark Li]

+1. Good luck!

On 2023/02/14 01:57:27 李晓双 wrote:
> +1
> 
> Alex Luo  于2023年2月13日周一 23:00写道：
> 
> > +1
> >
> > Alex Luo
> >
> > On 2023/02/13 10:44:48 vongosling wrote:
> > > +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
> > 

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

[Jianbo Mai]

+1

On 2023/02/09 12:19:14 Eason Chen wrote:
> Dear Apache Incubator Community and IPMC members,
> 
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
> 
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
> 
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
> 
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
> 
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
> 
> *Community*
> 
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
> 
> *Project*
> 
> ● Apache EventMesh(incubating) is a fully serverless platform used to
> build distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
> 
> *Brands, License, and Copyright*
> 
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
> 
> -
> BEGINNING OF DRAFT RESOLUTION
> -
> 
> Establish the Apache EventMesh Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a fully serverless platform used to build distributed
> event-driven applications.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to EventMesh is a
> fully serverless platform used to build distributed event-driven
> applications; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache EventMesh
> Project:
> 
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   
>  * Wenjun Ruan  
>  * XiaoShuang Li
>  * Xue Weiming  
>  * Yuwei Zhu
> 
> NOW, THEREFORE, BE IT FURTHER R

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

[李晓双]

+1

Alex Luo  于2023年2月13日周一 23:00写道：

> +1
>
> Alex Luo
>
> On 2023/02/13 10:44:48 vongosling wrote:
> > +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

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[tison]

Hi Justin,

It can be a case of The Ship of Theseus. When you take a look at the issued
files[1][2], you may find a commit history touching them and modifying
them. Anyway, it's not an identical copy or one-shot translation. And we
keep the origin comments.

Even a one-shot translation, if it's done by humans, generally modification
will be applied.

But if you insist on "keep the original license header and don't add the
ASF header" with an existing documented guideline, the Kvrocks contributors
would be glad to change it.

Best,
tison.

[1]
https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc
[2]
https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc


Justin Mclean  于2023年2月14日周二 05:39写道：

> Hi,
>
> In general porting a file from one language to another would not change
> the original license.
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[Justin Mclean]

Hi,

In general porting a file from one language to another would not change the 
original license.

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

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

[Alex Luo]

+1

Alex Luo

On 2023/02/13 10:44:48 vongosling wrote:
> +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
> > appoin

[VOTE] Release Apache HugeGraph (Incubating) 1.0.0-rc2

[Imba Jin]

Hello Incubator Community,

This is a call for a vote to release Apache HugeGraph(Incubating)
version 1.0.0-rc2

The Apache HugeGraph community has voted on and approved a proposal
to release Apache HugeGraph(Incubating) version 1.0.0-rc2

In this release, we fixed a string of license problems mentioned by
Willem Jiang & Justin Mclean:
1. check and fix all license-headers in source files
2. remove copyright in ASF header & refer it in NOTICE file & correct
the information
3. remove all the unnecessary binary files in source release package
4. remove swagger-ui's static files & use a download way to handle it
5. choose one proper license instead of list them all in the LICENSE
file for easy review (remove extra *GPL/CC-BY license)

Now we kindly request the Incubator PMC members review and vote on
this incubator release.

HugeGraph community vote thread:
• https://lists.apache.org/thread/zt5pw0s5njwy75c49v45ch3hswyq9bd8

Vote result thread:
• https://lists.apache.org/thread/y4yx1qovsmp3nyc7rgdlrv6298wsoyzr

The release candidate:
• https://dist.apache.org/repos/dist/dev/incubator/hugegraph/1.0.0

Git tag & Commit hash for the release:
• https://github.com/apache/incubator-hugegraph/tree/1.0.0-rc2 (c8e0f0c)
• https://github.com/apache/incubator-hugegraph-toolchain/tree/1.0.0-rc2
(e2b4eb2)
• https://github.com/apache/incubator-hugegraph-computer/tree/1.0.0-rc2
(d2b9526)
• https://github.com/apache/incubator-hugegraph-commons/tree/1.0.0-rc2 (82f2a65)

Release notes:
• https://hugegraph.apache.org/docs/changelog/hugegraph-1.0.0-release-notes/

Keys to verify the Release Candidate:
• https://downloads.apache.org/incubator/hugegraph/KEYS

The release GPG user ID: imbajin (j...@apache.org)

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

More detail checklist  please refer:
• 
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist

Steps to validate the release, could refer to:
English Version:
• https://hugegraph.apache.org/docs/contribution-guidelines/validate-release/
Chinese Version:
• https://hugegraph.apache.org/cn/docs/contribution-guidelines/validate-release/


Thanks,
On behalf of Apache HugeGraph(Incubating) community

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

Re: [VOTE] Graduate Apache 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 EventMesh(incubating) as an Apache Top Level Project

[fpapon]

+1 (binding)

regards,

François

On 10/02/2023 03:31, Eason Chen wrote:

Dear Apache Incubator Community and IPMC members,

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

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

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

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

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

*Community*

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

*Project*

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

*Brands, License, and Copyright*

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

-
BEGINNING OF DRAFT RESOLUTION
-

Establish the Apache EventMesh Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a fully serverless platform used to build distributed
event-driven applications.

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

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

RESOLVED, that the office of "Vice President, Apache EventMesh" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache EventMesh
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache EventMesh
Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache EventMesh
Project:

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

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

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[tison]

> you believe the original authors agree that the modifications
> are significant and can be relicensed, then I'm totally OK
> to add ASF license headers there

Hi zhenxu,

This is the case for Kvrocks. Kvrocks contributors port the file to cpp and
the original license is BSD 3-Clause which allows the recipient to
relicense.

Best,
tison.


kezhenxu94  于2023年2月13日周一 17:15写道：

> Hi,
>
> When it comes to human feelings there is no quantifiable standard,
> if the original authors granted you to relicense the file, or,
> you believe the original authors agree that the modifications
> are significant and can be relicensed, then I'm totally OK
> to add ASF license headers there.
>
> If that's neither the case, I'd be conservative to keep the original
> license header.
>
> I also remember there was a discussion already in this mailing list,
> but can't recall the link at the moment, anyone else can find
> and share would be appreciated.
>
> > On Feb 13, 2023, at 16:51, Twice  wrote:
> >
> > Hi @kezhenxu94,
> >
> > Thank you for taking the time to vote and for your valuable input.
> >
> > However, I would like to point out that
> > - You can see the changes we have made to these files in the commit log,
> >  and I have included some links [1-2] for your convenience.
> > - I cannot find an official description of the inclusion of the ASF
> header
> > to the modified third-party code: i.e.
> >  how many changes can be described as not being "mostly the same"? Is
> > there a quantifiable standard for this?
> >
> > [1]
> >
> https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc
> > [2]
> >
> https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc
> >
> > Best,
> > Twice
> >
> >
> > On Mon, Feb 13, 2023 at 4:07 PM kezhenxu94 
> wrote:
> >
> >> Hi sorry -1 (binding) due to license issue, the following files [1] have
> >> ASF license headers along with the original license header,
> >> I saw you mentioned it's a conversion from C to C++ from Redis project,
> >> but from my comparison they look to
> >> be mostly the same so you might want to remove the ASF license header
> from
> >> those files.
> >>
> >> Other files [2] might be controversial whether we should have dual
> license
> >> headers, but I won't vote -1 on those files if [1] are resolved.
> >>
> >> [1]  - apache/incubator-kvrocks/src/types/geohash.cc <
> http://geohash.cc/>
> >> - apache/incubator-kvrocks/src/common/sha1.cc 
> >>
> >> [2] - src/common/rand.cc src/common/rand.h
> >>- src/storage/scripting.*
> >>
> >>> On Feb 11, 2023, at 22:43, Myth  wrote:
> >>>
> >>> Hello Incubator PMC,
> >>>
> >>> The Apache Kvrocks community has voted and approved the release of
> Apache
> >>> Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members
> review
> >>> and vote for this release.
> >>>
> >>> This is  the second call for a vote. The first call for a vote, which
> is
> >>> cancelled:
> >>> *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt
> >>> *
> >>>
> >>> 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, many improvements and fixes many bugs.
> >>>
> >>> Kvrocks community vote thread:
> >>> https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2
> >>>
> >>> Vote result thread:
> >>> https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw
> >>>
> >>> The release candidate:
> >>> https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/
> >>>
> >>> This release has been signed with a PGP available here:
> >>> https://downloads.apache.org/incubator/kvrocks/KEYS
> >>>
> >>> Git tag for the release:
> >>> https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0
> >>>
> >>> Docker image:
> >>>
> >>
> https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807
> >>>
> >>> 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.3.0
> >>> [ ] +0
> >>> [ ] -1 Do not approve (please specify the reason)
> >>>
> >>> Thanks
> >>
> >>
> >> -
> >> 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
>
>

[CANCEL][VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

[Huajie Wang]

Hello Incubator Community,

I'm cancelling this vote:
https://lists.apache.org/thread/zz7h1tmkrnbx06lnzodtbdpwflpvw9mr


due to licenses issues. I'll fix them and start a new vote process.


Thanks a lot for all your help.



Best,
Huajie Wang

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[kezhenxu94]

Hi, 

When it comes to human feelings there is no quantifiable standard,
if the original authors granted you to relicense the file, or,
you believe the original authors agree that the modifications
are significant and can be relicensed, then I'm totally OK
to add ASF license headers there.

If that's neither the case, I'd be conservative to keep the original
license header.

I also remember there was a discussion already in this mailing list,
but can't recall the link at the moment, anyone else can find
and share would be appreciated.

> On Feb 13, 2023, at 16:51, Twice  wrote:
> 
> Hi @kezhenxu94,
> 
> Thank you for taking the time to vote and for your valuable input.
> 
> However, I would like to point out that
> - You can see the changes we have made to these files in the commit log,
>  and I have included some links [1-2] for your convenience.
> - I cannot find an official description of the inclusion of the ASF header
> to the modified third-party code: i.e.
>  how many changes can be described as not being "mostly the same"? Is
> there a quantifiable standard for this?
> 
> [1]
> https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc
> [2]
> https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc
> 
> Best,
> Twice
> 
> 
> On Mon, Feb 13, 2023 at 4:07 PM kezhenxu94  wrote:
> 
>> Hi sorry -1 (binding) due to license issue, the following files [1] have
>> ASF license headers along with the original license header,
>> I saw you mentioned it's a conversion from C to C++ from Redis project,
>> but from my comparison they look to
>> be mostly the same so you might want to remove the ASF license header from
>> those files.
>> 
>> Other files [2] might be controversial whether we should have dual license
>> headers, but I won't vote -1 on those files if [1] are resolved.
>> 
>> [1]  - apache/incubator-kvrocks/src/types/geohash.cc 
>> - apache/incubator-kvrocks/src/common/sha1.cc 
>> 
>> [2] - src/common/rand.cc src/common/rand.h
>>- src/storage/scripting.*
>> 
>>> On Feb 11, 2023, at 22:43, Myth  wrote:
>>> 
>>> Hello Incubator PMC,
>>> 
>>> The Apache Kvrocks community has voted and approved the release of Apache
>>> Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members review
>>> and vote for this release.
>>> 
>>> This is  the second call for a vote. The first call for a vote, which is
>>> cancelled:
>>> *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt
>>> *
>>> 
>>> 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, many improvements and fixes many bugs.
>>> 
>>> Kvrocks community vote thread:
>>> https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2
>>> 
>>> Vote result thread:
>>> https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw
>>> 
>>> The release candidate:
>>> https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/
>>> 
>>> This release has been signed with a PGP available here:
>>> https://downloads.apache.org/incubator/kvrocks/KEYS
>>> 
>>> Git tag for the release:
>>> https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0
>>> 
>>> Docker image:
>>> 
>> https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807
>>> 
>>> 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.3.0
>>> [ ] +0
>>> [ ] -1 Do not approve (please specify the reason)
>>> 
>>> Thanks
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


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

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

[Huajie Wang]

thanks for your clarification, this vote is closed, We will fix these
issues and start a new vote process.



Best,
Huajie Wang



kezhenxu94  于2023年2月13日周一 15:52写道：

> It depends, if you wrote the codes of `AssertUtils.scala` from scratch
> without referencing
> the Spring's Assert class, you can definitely said it's your own work and
> your own IP,
> but if you copied the content from Spring's, and converted it into Scala,
> even with some modifications,
> I still consider it's originated from Spring project.
>
> And the most important thing is that, you listed it in the LICENSE file
> and admit that it's copied from Spring project.
>
> If you don't agree it's copied from the Spring project,
> you should remove it from the LICENSE file, but I don't think that's the
> case.
>
> P.S. Sorry, I know it's me who raised this issue in the previous RC vote,
> if you think
> that file is not copied from Spring project, you could clarify it
> and I'd be happy to turn my vote into +1 when convinced.
>
> > On Feb 13, 2023, at 15:28, Huajie Wang  wrote:
> >
> > Thanks for your review and feedback, we will fix this issue, but I
> > have a question:
> >
> > As we all know, spring is developed in java language, while
> > Streampark's AssertUtils.scala[1] is developed in scala. As you can
> > see, the methods and logic in it are very simple. Even if the logic
> > and method names in AssertUtils.scala are the same as in spring, it
> > cannot be said that AssertUtils.scala is copied from spring's code. In
> > other words, I implemented it in another language, like .net. Can you
> > tell me that I copied the code? I don't know how this part is defined
> > in ASF?
> >
> > [1]
> streampark-common/src/main/scala/org/apache/streampark/common/util/AssertUtils.scala
> >
> >
> > Best,
> > Huajie Wang
> >
> >
> >
> > kezhenxu94  于2023年2月13日周一 14:48写道：
> >
> >> Hi, -1 (binding), you cannot change the license header of a
> third-party's
> >> file[1] as you mentioned in LICENSE it's from Spring team[2].
> >>
> >> [1]
> >>
> streampark-common/src/main/scala/org/apache/streampark/common/util/AssertUtils.scala
> >> [2] https://github.com/spring-projects/spring-framework
> >>
> >>> On Feb 10, 2023, at 17:44, Huajie Wang  wrote:
> >>>
> >>> Hello Incubator Community:
> >>>
> >>> This is a call for a vote to release Apache StreamPark(Incubating)
> >>> version 2.0.0-RC6
> >>>
> >>> The Apache StreamPark community has voted on and approved a proposal to
> >>> release
> >>> Apache StreamPark(Incubating) version 2.0.0-RC6
> >>>
> >>> We now kindly request the Incubator PMC members review and vote on this
> >>> incubator release.
> >>>
> >>> Apache StreamPark, Make stream processing easier! easy-to-use streaming
> >>> application development framework and operation platform.
> >>>
> >>>
> >>> StreamPark community vote thread:
> >>> https://lists.apache.org/thread/lvpc2hywbkdlvkpmjm0knchyk6vhvmnl
> >>>
> >>> Vote result thread:
> >>> https://lists.apache.org/thread/y77vc8c3d5x7wtslm99jydgwmp10ypxv
> >>>
> >>>
> >>> The release candidate:
> >>> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC6/
> >>>
> >>> Git tag for the release:
> >>> https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc6
> >>>
> >>> Release notes:
> >>> https://streampark.apache.org/download/release-note/2.0.0/
> >>>
> >>> Maven artifacts are available in a staging repository at:
> >>>
> >>
> https://repository.apache.org/content/repositories/orgapachestreampark-1009/
> >>>
> >>> The artifacts signed with PGP key [5AE01B8E], corresponding to [
> >>> benj...@apache.org], that can be found in keys file:
> >>> https://downloads.apache.org/incubator/streampark/KEYS
> >>>
> >>>
> >>> Last commit hash:
> >>> •apache-streampark-2.0.0-incubating-src.tar.gz:
> >>>
> >>
> 91083d97727e302997ae35e54e583340101d2e88968495b78fae16c32a0bd47dc0b87aa285f2a6279758906b811ca6665fb2b0120ebbb6d8d41a4da1263bca23
> >>>
> >>>
> >>> • apache-streampark_2.11-2.0.0-incubating-bin.tar.gz:
> >>>
> >>
> e055643a1657cd4f4dd1352d22bdafd9b3dd2cece5698f503e2a46bd8c1ad6d1a559e2c1041b528b65701f268ba0ae2aefc9072c9a1b0c783fc45c91ec2e88f9
> >>>
> >>>
> >>> • apache-streampark_2.12-2.0.0-incubating-bin.tar.gz:
> >>>
> >>
> 0fbccc5f3fec8c997fea61d60a399f69ab60abfa21e00a07d7bfce92773ef1a19780c3d639e8411b0ac8891f388ed62ff9b437bfec6c7bfcea3f5debbc98be88
> >>>
> >>> In this vote we fixed RC4,RC5 vote process issue, and some licenses
> >> issues
> >>> mentioned in RC3 vote process:
> >>> https://github.com/apache/incubator-streampark/pull/2277
> >>>
> >>>
> >>> 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
> >>>
> >>> More detailed checklist please refer:
> >>> •
> >>>
> >>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >>>
> >>> Steps to validate the release， Please refer t

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[Twice]

Hi @kezhenxu94,

Thank you for taking the time to vote and for your valuable input.

However, I would like to point out that
- You can see the changes we have made to these files in the commit log,
  and I have included some links [1-2] for your convenience.
- I cannot find an official description of the inclusion of the ASF header
to the modified third-party code: i.e.
  how many changes can be described as not being "mostly the same"? Is
there a quantifiable standard for this?

[1]
https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc
[2]
https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc

Best,
Twice


On Mon, Feb 13, 2023 at 4:07 PM kezhenxu94  wrote:

> Hi sorry -1 (binding) due to license issue, the following files [1] have
> ASF license headers along with the original license header,
> I saw you mentioned it's a conversion from C to C++ from Redis project,
> but from my comparison they look to
> be mostly the same so you might want to remove the ASF license header from
> those files.
>
> Other files [2] might be controversial whether we should have dual license
> headers, but I won't vote -1 on those files if [1] are resolved.
>
> [1]  - apache/incubator-kvrocks/src/types/geohash.cc 
>  - apache/incubator-kvrocks/src/common/sha1.cc 
>
> [2] - src/common/rand.cc src/common/rand.h
> - src/storage/scripting.*
>
> > On Feb 11, 2023, at 22:43, Myth  wrote:
> >
> > Hello Incubator PMC,
> >
> > The Apache Kvrocks community has voted and approved the release of Apache
> > Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members review
> > and vote for this release.
> >
> > This is  the second call for a vote. The first call for a vote, which is
> > cancelled:
> > *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt
> > *
> >
> > 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, many improvements and fixes many bugs.
> >
> > Kvrocks community vote thread:
> > https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2
> >
> > Vote result thread:
> > https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/
> >
> > This release has been signed with a PGP available here:
> > https://downloads.apache.org/incubator/kvrocks/KEYS
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0
> >
> > Docker image:
> >
> https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807
> >
> > 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.3.0
> > [ ] +0
> > [ ] -1 Do not approve (please specify the reason)
> >
> > Thanks
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Celeborn(Incubating) 0.2.0-incubating-rc4

[Ethan Feng]

Thanks Yu Li and anyone who participated in this thread.

Due to critical issue, this vote is closed.

Ethan Feng

在 2023年2月13日 15:58:45 上，Yu Li  写道：

> Sorry guys, but I found a critical issue thus another -1 (binding)
>
> * The source package contains a licenses-binary directory, which has
> un-included dependency licenses (for source). Please check the packaging
> script and confirm whether there is any error in it (the name of "licenses-
> *binary*" indicates something wrong, which causes my attention)
>
> Best Regards,
> Yu
>
>
> On Thu, 9 Feb 2023 at 18:43, angers zhu  wrote:
>
> +1 (no-binding)
>
>
> Checked:
>
>
> [1] ./build/make-distribution.sh -Pspark-3.1 (macOs Catalina 10.15.7)
>
> [2] RELEASE file are correct
>
> [3] jar soft link looks good
>
> [4] "incubating" in celeborn jar name
>
> [5] checksums are good
>
> [6] signatures are good.
>
>
> Kent Yao  于2023年2月8日周三 15:07写道：
>
>
> > +1 nonbinding
>
> >
>
> > - downloads ok
>
> > - All source files have license headers
>
> > - no binary files in the source release
>
> > - sig/checksums are ok
>
> > - notice/disclaimer/license files are good
>
> > - build from source successfully
>
> >
>
> > Kent Yao
>
> >
>
> > On 2023/02/08 02:40:34 Cheng Pan wrote:
>
> > >  +1 (no-binding)
>
> > >
>
> > > I checked
>
> > >
>
> > > - links are valid.
>
> > > - "incubating" is in the name.
>
> > > - LICENSE looks good.
>
> > > - NOTICE looks good.
>
> > > - DISCLAIMER exists.
>
> > >
>
> > > - signatures are good.
>
> > > ```
>
> > > gpg --verify apache-celeborn-0.2.0-incubating-source.tgz.asc
>
> > > gpg --verify apache-celeborn-0.2.0-incubating-bin.tgz.asc
>
> > > ```
>
> > >
>
> > > - checksums are good.
>
> > > ```
>
> > > sha512sum --check apache-celeborn-0.2.0-incubating-bin.tgz.sha512
>
> > > sha512sum --check apache-celeborn-0.2.0-incubating-source.tgz.sha512
>
> > > ```
>
> > >
>
> > > - build success from source code (openjdk-8, ubuntu 22.04 x86).
>
> > > ```
>
> > > build/make-distribution.sh --release
>
> > > ```
>
> > >
>
> > > Thanks,
>
> > > Cheng Pan
>
> > >
>
> > >
>
> > > On Feb 8, 2023 at 10:37:32, Ethan Feng  wrote:
>
> > >
>
> > > > Hello Incubator Community,
>
> > > >
>
> > > > This is a call for a vote to release Apache Celeborn(Incubating)
>
> > > > version 0.2.0-incubating-rc4
>
> > > >
>
> > > > The Apache Celeborn community has voted on and approved a proposal to
>
> > > > release
>
> > > > Apache Celeborn(Incubating) version 0.2.0-incubating-rc4
>
> > > >
>
> > > > We now kindly request the Incubator PMC members review and vote on
>
> this
>
> > > > incubator release.
>
> > > >
>
> > > > Celeborn community vote thread:
>
> > > > • https://lists.apache.org/thread/3qv3byyy1rqv7l9qsx02gbto1n9ymd1h
>
> > > >
>
> > > > Vote result thread:
>
> > > > • https://lists.apache.org/thread/k4jvqdd0dwk9dc7t6n80tgqv99fmwok7
>
> > > >
>
> > > > The release candidate:
>
> > > > •
>
> > > >
>
> >
>
>
> https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.2.0-incubating-rc4
>
> > > >
>
> > > > Git tag for the release:
>
> > > > •
>
> > > >
>
> >
>
>
> https://github.com/apache/incubator-celeborn/releases/tag/v0.2.0-incubating-rc4
>
> > > >
>
> > > > Public keys file:
>
> > > > • https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS
>
> > > >
>
> > > > The change log is available in:
>
> > > > •
>
> > > >
>
> >
>
>
> https://github.com/apache/incubator-celeborn/compare/v0.1.4...v0.2.0-incubating-rc4
>
> > > >
>
> > > > 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
>
> > > >
>
> > > > More detailed checklist please refer:
>
> > > > •
>
> > > >
>
> >
>
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> > > >
>
> > > > Steps to validate the release， Please refer to:
>
> > > > • https://www.apache.org/info/verification.html
>
> > > >
>
> > > > Thanks,
>
> > > > On behalf of Apache Celeborn(Incubating) community
>
> > > >
>
> > >
>
> >
>
> > -
>
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
> >
>
> >
>
>
>

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

[kezhenxu94]

Hi sorry -1 (binding) due to license issue, the following files [1] have ASF 
license headers along with the original license header,
I saw you mentioned it's a conversion from C to C++ from Redis project, but 
from my comparison they look to
be mostly the same so you might want to remove the ASF license header from 
those files.

Other files [2] might be controversial whether we should have dual license 
headers, but I won't vote -1 on those files if [1] are resolved.

[1]  - apache/incubator-kvrocks/src/types/geohash.cc 
 - apache/incubator-kvrocks/src/common/sha1.cc 

[2] - src/common/rand.cc src/common/rand.h
- src/storage/scripting.*

> On Feb 11, 2023, at 22:43, Myth  wrote:
> 
> Hello Incubator PMC,
> 
> The Apache Kvrocks community has voted and approved the release of Apache
> Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members review
> and vote for this release.
> 
> This is  the second call for a vote. The first call for a vote, which is
> cancelled:
> *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt
> *
> 
> 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, many improvements and fixes many bugs.
> 
> Kvrocks community vote thread:
> https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2
> 
> Vote result thread:
> https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw
> 
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/
> 
> This release has been signed with a PGP available here:
> https://downloads.apache.org/incubator/kvrocks/KEYS
> 
> Git tag for the release:
> https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0
> 
> Docker image:
> https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807
> 
> 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.3.0
> [ ] +0
> [ ] -1 Do not approve (please specify the reason)
> 
> Thanks


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