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

[Goson zhang]

I've known about echart for a long time, and I think it's actually graduated

Ovilia  于2020年11月23日周一 下午2:26写道：

> Thank you all for the discussion. I will start the recommendation vote soon
> since we
> have reached the consensus.
> Thanks
>
> *Ovilia*
>
>
> On Mon, Nov 16, 2020 at 9:28 PM Xiangdong Huang 
> wrote:
>
> > Nice achievement, ECharts community!
> > Congrats.
> >
> > Best,
> > ---
> > Xiangdong Huang
> >
> >
> >
> > Sheng Wu  于2020年11月14日周六 下午10:36写道：
> >
> > > My support for the ECharts.
> > >
> > > I joined the mentor team a little late, and super excited that you have
> > > gotten all things resolved. Congrats!!
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > >
> > > Dave Fisher  于2020年11月14日周六 上午6:49写道：
> > >
> > > > Well done ECharts community!
> > > >
> > > > It has my pleasure to be one of your Mentors and to remain as a PMC
> > > member.
> > > >
> > > > Regards,
> > > > Dave
> > > >
> > > > > On Nov 12, 2020, at 9:05 PM, Ovilia  wrote:
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > After discussion with the community [1], and a positive vote result
> > > [2],
> > > > we
> > > > > believe
> > > > > ECharts is ready for graduation to a TLP, and we'd like to bring up
> > in
> > > > > discussion with
> > > > > the IPMC.
> > > > >
> > > > > Please see the proposed board resolution below and let us know what
> > you
> > > > > think.
> > > > >
> > > > > A few points to assist in the discussion:
> > > > >
> > > > > - Released 9 official Apache releases by 3 release managers [3]
> > > > > - Voted in 9 committers including 3 PPMC members
> > > > > - Achieved 43556 stars (and counting) on GitHub
> > > > > - Apache suitable name search has been approved [4]
> > > > > - Completed the Podling Maturity Assessment, all items are passed
> [5]
> > > > > - Our PPMC is diverse and consists of members from 9 organizations
> > > > > - There have been 143 contributors to the codebase, 82 of whom
> > > > contributed
> > > > > during incubation
> > > > > - Closed 11033+ issues
> > > > > - Merged 603+ pull requests
> > > > >
> > > > > We've resolved all branding issues which include Logo, GitHub repo,
> > > > > documentation, website, and others.
> > > > >
> > > > > Thank you!
> > > > >
> > > > > *Ovilia*
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/rf05e9dfa1aec1ac072c71c9cba882a59c9c57f4f89723da68e96de01%40%3Cdev.echarts.apache.org%3E
> > > > > [2]
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r1179386814f4f99ccb3809527bc9436fe702e0e7573fb5de2c99151f%40%3Cdev.echarts.apache.org%3E
> > > > > [3] https://dist.apache.org/repos/dist/release/incubator/echarts/
> > > > > [4] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153
> > > > > [5]
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -
> > > > >
> > > > > X. Establish the Apache ECharts Project
> > > > >
> > > > > WHEREAS, the Board of Directors deems it to be in the best
> > > > > interests of the Foundation and consistent with the
> > > > > Foundation's purpose to establish a Project Management
> > > > > Committee charged with the creation and maintenance of
> > > > > open-source software, for distribution at no charge to
> > > > > the public, related to a charting and data visualization
> > > > > library written in JavaScript.
> > > > >
> > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > > > > Committee (PMC), to be known as the "Apache ECharts Project",
> > > > > be and hereby is established pursuant to Bylaws of the
> > > > > Foundation; and be it further
> > > > >
> > > > > RESOLVED, that the Apache ECharts Project be and hereby is
> > > > > responsible for the creation and maintenance of software
> > > > > related to a charting and data visualization
> > > > > library written in JavaScript; and be it further
> > > > >
> > > > > RESOLVED, that the office of "Vice President, Apache ECharts" be
> > > > > and hereby is created, the person holding such office to
> > > > > serve at the direction of the Board of Directors as the chair
> > > > > of the Apache ECharts Project, and to have primary responsibility
> > > > > for management of the projects within the scope of
> > > > > responsibility of the Apache ECharts Project; and be it further
> > > > >
> > > > > RESOLVED, that the persons listed immediately below be and
> > > > > hereby are appointed to serve as the initial members of the
> > > > > Apache ECharts Project:
> > > > >
> > > > >* Houjin Huang  
> > > > >* Deqing Li 
> > > > >* Dong Rui  
> > > > >* Kener Linfeng 
> > > > >* Kevin A. McGrail  
> > > > >* Wenli Zhang   
> > > > >* Shen Yi   
> > > > >* Shuang Su 
> > > > >* Siwen Su  
> > > > >* 

Re: [VOTE] Apache Tuweni 1.3.0 release

[Antoine Toulme]

Dave, I appreciate and thank you for your change of vote.

I already have changed how we generate the NOTICE in our binary distribution - 
next time, I might run it by the list here before the vote starts to discuss 
its format.

> On Nov 22, 2020, at 11:32 AM, Dave Fisher  wrote:
> 
> Hi Antoine,
> 
> With your explanations I’m changing my VOTE:
> 
> +1 (binding)
> 
> Regards,
> Dave
> 
>> On Nov 21, 2020, at 3:42 PM, Antoine Toulme  wrote:
>> 
>> 
>> 
>>> On Nov 21, 2020, at 2:50 PM, Dave Fisher  wrote:
>>> 
>>> 
>>> 
 On Nov 21, 2020, at 2:25 PM, Antoine Toulme  wrote:
 
 The binaries are generated by the build.
>>> 
>>> I ran a build the jars were generated, but the scripts in the bin are not 
>>> anywhere in the source tree. Those aren’t built I have no idea where the 
>>> binary convenience got those scripts.
>> The scripts are generated by the application plugin of Gradle:
>> https://docs.gradle.org/current/userguide/application_plugin.html 
>> 
>> 
>>> 
 
 I thought the build was a vote on the sources and their distribution, 
 while binaries are convenience.
>>> 
>>> They are a convenience, but if you are using ASF resources then the 
>>> licensing needs to properly follow policy.
>> OK.
>>> 
 
 Do you have an example of (3)?
>>> 
>>> leveldbjni-all-1.8.jar is BSD 3-Clause
>>> Jetty is dual licensed - you should declare that you are choosing AL2.
>>> Jersey is quad licensed - …
>>> Jaxb is CDDL 1.1, but used to be GPL
>>> Javax is CDDL and GPL2 so you definitely need to declare.
>>> Javasist is triple licensed - AL2, LGPL2, and MPL 1.1 so ...
>>> Jakarta are EPL2 and GPL2.
>>> 
>>> I found this information quickly using mvnrepository.com
>>> 
>>> It’s all about easily assuring users of the binary package what the terms 
>>> are.
>>> 
>>> These classes can be used for Binaries
>>> Class A licenses: https://www.apache.org/legal/resolved.html#category-a
>>> Class B licenses: https://www.apache.org/legal/resolved.html#category-b
>>> Sources must not contain Class B.
>>> 
>>> Class X cannot be used: 
>>> https://www.apache.org/legal/resolved.html#category-x 
>>> 
>> 
>> Ah, we generate a license report but don’t include it. We can fix that in 
>> the next release.
>>> 
>>> Regards,
>>> Dave
>>> 
 
> On Nov 21, 2020, at 2:20 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> Incubator in name, Signatures, Hashes, NOTICE, DISCLAIMER are in place.
> 
> Source package LICENSEs are fine.
> 
> Binaries -
> (1) bin directory - where are the sources for the scripts and bat files 
> in the Source Release?
> (2) bin directory - what is the license for these files?
> (3) LICENSE is identical to source release. The binary LICENSE and NOTICE 
> need to reflect everything included in the lib directory.
> 
> I’m -0 (binding) on this release, I think these 3 issues do need to be 
> addressed.
> 
> If other IPMC members are willing to VOTE +1 that’s ok with me.
> 
> Regards,
> Dave
> 
>> On Nov 19, 2020, at 11:16 AM, Antoine Toulme  wrote:
>> 
>> Hi all,
>> 
>> We're voting on the source distributions available here:
>> https://dist.apache.org/repos/dist/dev/incubator/tuweni/1.3.0-incubating/
>> The release tag is present here:
>> https://github.com/apache/incubator-tuweni/releases/tag/v1.3.0-incubating-rc
>> 
>> Please review and vote as appropriate.
>> 
>> The following changes were made since 1.2.0:
>> 
>> * Update to support Sodium 1.0.18 
>> (https://github.com/apache/incubator-tuweni/pull/164 
>> )
>> * Base58 encoding support 
>> (https://github.com/apache/incubator-tuweni/pull/150 
>> )
>> * eth65 support (https://github.com/apache/incubator-tuweni/pull/152 
>> )
>> * Add a helper to transform a SECP256K1 public key into an Ethereum 
>> address (https://github.com/apache/incubator-tuweni/pull/154 
>> )
>> * Add a discv5 scraper 
>> (https://github.com/apache/incubator-tuweni/pull/157 
>> )
>> * Upgrade Bouncy Castle 
>> (https://github.com/apache/incubator-tuweni/pull/160 
>> )
>> * Upgrade Error Prone 
>> (https://github.com/apache/incubator-tuweni/pull/165 
>> )
>> * Add Windows CI test build 
>> (https://github.com/apache/incubator-tuweni/pull/167 
>> )
>> * Add binary snapshots 
>> 

[VOTE] Graduate Apache ECharts as TLP

[Ovilia]

Hi everyone,

After discussion with the community [1], and a positive vote result [2] and
the
discussion under general mailing list [6], we believe
ECharts is ready for graduation to a TLP, and we'd like to call on the vote
to
graduate Apache ECharts as TPL.

This is a formal voting thread about Apache TVM's graduation, please Vote:
[ ] +1 - Recommend graduation of Apache TVM as a TLP
[ ]  0 - I don't feel strongly about it, but don't object
[ ] -1 - Do not recommend graduation of Apache TVM because...

The VOTE will open for at least 72 hours.
https://www.timeanddate.com/countdown/vote?iso=20201126T1435=237=%5BVOTE%5D+Graduate+Apache+ECharts+as+TLP=serif=1

-

X. Establish the Apache ECharts Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to a charting and data visualization
library written in JavaScript.

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

RESOLVED, that the Apache ECharts Project be and hereby is
responsible for the creation and maintenance of software
related to a charting and data visualization
library written in JavaScript; and be it further

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

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

* Houjin Huang  
* Deqing Li 
* Dong Rui  
* Kener Linfeng 
* Kevin A. McGrail  
* Wenli Zhang   
* Shen Yi   
* Shuang Su 
* Siwen Su  
* Junting Wang  
* Zhongxiang Wang   
* Dave Fisher   
* Sheng Wu  
* Zak Wu

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
be appointed to the office of Vice President, Apache ECharts, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

RESOLVED, that the initial Apache ECharts PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache ECharts Project; and be it further

RESOLVED, that the Apache ECharts Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator ECharts podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator ECharts podling encumbered upon the Apache Incubator
Project are hereafter discharged.

--

A few points to assist in the discussion:

- Released 9 official Apache releases by 3 release managers [3]
- Voted in 9 committers including 3 PPMC members
- Achieved 43556 stars (and counting) on GitHub
- Apache suitable name search has been approved [4]
- Completed the Podling Maturity Assessment, all items are passed [5]
- Our PPMC is diverse and consists of members from 9 organizations
- There have been 143 contributors to the codebase, 82 of whom contributed
during incubation
- Closed 11033+ issues
- Merged 603+ pull requests

We've resolved all branding issues which include Logo, GitHub repo,
documentation, website, and others.

Thank you!

*Ovilia*

[1]
https://lists.apache.org/thread.html/rf05e9dfa1aec1ac072c71c9cba882a59c9c57f4f89723da68e96de01%40%3Cdev.echarts.apache.org%3E
[2]
https://lists.apache.org/thread.html/r1179386814f4f99ccb3809527bc9436fe702e0e7573fb5de2c99151f%40%3Cdev.echarts.apache.org%3E
[3] https://dist.apache.org/repos/dist/release/incubator/echarts/
[4] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153
[5]
https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts
[6]
https://lists.apache.org/thread.html/r8dfeabf8c51be0233a27444bbb2fe420d0d6e998dcc55c47b958d3e9%40%3Cgeneral.incubator.apache.org%3E

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

[Ovilia]

Thank you all for the discussion. I will start the recommendation vote soon
since we
have reached the consensus.
Thanks

*Ovilia*


On Mon, Nov 16, 2020 at 9:28 PM Xiangdong Huang  wrote:

> Nice achievement, ECharts community!
> Congrats.
>
> Best,
> ---
> Xiangdong Huang
>
>
>
> Sheng Wu  于2020年11月14日周六 下午10:36写道：
>
> > My support for the ECharts.
> >
> > I joined the mentor team a little late, and super excited that you have
> > gotten all things resolved. Congrats!!
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> >
> > Dave Fisher  于2020年11月14日周六 上午6:49写道：
> >
> > > Well done ECharts community!
> > >
> > > It has my pleasure to be one of your Mentors and to remain as a PMC
> > member.
> > >
> > > Regards,
> > > Dave
> > >
> > > > On Nov 12, 2020, at 9:05 PM, Ovilia  wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > After discussion with the community [1], and a positive vote result
> > [2],
> > > we
> > > > believe
> > > > ECharts is ready for graduation to a TLP, and we'd like to bring up
> in
> > > > discussion with
> > > > the IPMC.
> > > >
> > > > Please see the proposed board resolution below and let us know what
> you
> > > > think.
> > > >
> > > > A few points to assist in the discussion:
> > > >
> > > > - Released 9 official Apache releases by 3 release managers [3]
> > > > - Voted in 9 committers including 3 PPMC members
> > > > - Achieved 43556 stars (and counting) on GitHub
> > > > - Apache suitable name search has been approved [4]
> > > > - Completed the Podling Maturity Assessment, all items are passed [5]
> > > > - Our PPMC is diverse and consists of members from 9 organizations
> > > > - There have been 143 contributors to the codebase, 82 of whom
> > > contributed
> > > > during incubation
> > > > - Closed 11033+ issues
> > > > - Merged 603+ pull requests
> > > >
> > > > We've resolved all branding issues which include Logo, GitHub repo,
> > > > documentation, website, and others.
> > > >
> > > > Thank you!
> > > >
> > > > *Ovilia*
> > > >
> > > > [1]
> > > >
> > >
> >
> https://lists.apache.org/thread.html/rf05e9dfa1aec1ac072c71c9cba882a59c9c57f4f89723da68e96de01%40%3Cdev.echarts.apache.org%3E
> > > > [2]
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r1179386814f4f99ccb3809527bc9436fe702e0e7573fb5de2c99151f%40%3Cdev.echarts.apache.org%3E
> > > > [3] https://dist.apache.org/repos/dist/release/incubator/echarts/
> > > > [4] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153
> > > > [5]
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts
> > > >
> > > >
> > > >
> > > >
> > > > -
> > > >
> > > > X. Establish the Apache ECharts Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best
> > > > interests of the Foundation and consistent with the
> > > > Foundation's purpose to establish a Project Management
> > > > Committee charged with the creation and maintenance of
> > > > open-source software, for distribution at no charge to
> > > > the public, related to a charting and data visualization
> > > > library written in JavaScript.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > > > Committee (PMC), to be known as the "Apache ECharts Project",
> > > > be and hereby is established pursuant to Bylaws of the
> > > > Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache ECharts Project be and hereby is
> > > > responsible for the creation and maintenance of software
> > > > related to a charting and data visualization
> > > > library written in JavaScript; and be it further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache ECharts" be
> > > > and hereby is created, the person holding such office to
> > > > serve at the direction of the Board of Directors as the chair
> > > > of the Apache ECharts Project, and to have primary responsibility
> > > > for management of the projects within the scope of
> > > > responsibility of the Apache ECharts Project; and be it further
> > > >
> > > > RESOLVED, that the persons listed immediately below be and
> > > > hereby are appointed to serve as the initial members of the
> > > > Apache ECharts Project:
> > > >
> > > >* Houjin Huang  
> > > >* Deqing Li 
> > > >* Dong Rui  
> > > >* Kener Linfeng 
> > > >* Kevin A. McGrail  
> > > >* Wenli Zhang   
> > > >* Shen Yi   
> > > >* Shuang Su 
> > > >* Siwen Su  
> > > >* Junting Wang  
> > > >* Zhongxiang Wang   
> > > >* Dave Fisher   
> > > >* Sheng Wu  
> > > >* Zak Wu
> > > >
> > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
> > > > be appointed to the office of Vice President, Apache ECharts, to
> > > > serve in accordance with and subject to the direction of the
> > > > Board of Directors and the Bylaws 

[IP CLEARANCE] Apache APISIX ingress controller

[Ming Wen]

Apache APISIX is receiving a donation of ingress controller [1].

Please vote to approve this contribution.

This is a lazy consensus majority vote, per the IP clearance process [2],
open for at least 72 hours.

[1] https://incubator.apache.org/ip-clearance/apisix-ingress-controller.html
[2] https://incubator.apache.org/ip-clearance/

Thanks,
Ming Wen, Apache APISIX PMC Chair
Twitter: _WenMing

Re: Process to rename the project

[Saisai Shao]

The podling project is Apache TubeMQ. Currently the project is planning to
change the name, but haven't yet figured out a new name, neither did a
podling name search. Just want to understand what is the process.

CC @general@incubator.apache.org 

Thanks
Jerry

Dave Fisher  于2020年11月23日周一 上午10:26写道：

> Has the podling done a podling name search?
>
> What podling?
>
> What is the new name?
>
> Changing names is work for infrastructure so we want to be careful not to
> be spurious!
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Nov 22, 2020, at 6:19 PM, Jerry Shao  wrote:
> >
> > 
> > Hi Team,
> >
> > We have a podling project which wants to change its current name, the
> main reason of changing is to expand the scope of the project. I would like
> to know if it is possible to change the project name? If so, what is the
> process, do we have any document about this?
> >
> > Thanks
> > Jerry
>
>
> -
> To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org
> For additional commands, e-mail: private-h...@incubator.apache.org
>
>

Re: Request SVN permission for ip-clearance

[Ming Wen]

Hi, John,
HTTPS is works. thanks for your help.

Thanks,
Ming Wen, Apache APISIX PMC Chair
Twitter: _WenMing


John D. Ament  于2020年11月22日周日 下午11:53写道：

> Please make sure you are using https. HTTP is read only. Try again.
>
> John
>
>
> On Sun, Nov 22, 2020 at 10:37 Ming Wen  wrote:
>
> > hello, incubator,
> >  I want to submit a new ip clearance to svn[1], but I found that I did
> not
> > have the permission to write.
> > How should I apply? thank you.
> > my svn user name: wenming
> >
> > [1]
> >
> >
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/
> >
> > Thanks,
> > Ming Wen, Apache APISIX PMC Chair
> > Twitter: _WenMing
> >
>

Re: [VOTE] Apache Tuweni 1.3.0 release

[Dave Fisher]

Hi Antoine,

With your explanations I’m changing my VOTE:

+1 (binding)

Regards,
Dave

> On Nov 21, 2020, at 3:42 PM, Antoine Toulme  wrote:
> 
> 
> 
>> On Nov 21, 2020, at 2:50 PM, Dave Fisher  wrote:
>> 
>> 
>> 
>>> On Nov 21, 2020, at 2:25 PM, Antoine Toulme  wrote:
>>> 
>>> The binaries are generated by the build.
>> 
>> I ran a build the jars were generated, but the scripts in the bin are not 
>> anywhere in the source tree. Those aren’t built I have no idea where the 
>> binary convenience got those scripts.
> The scripts are generated by the application plugin of Gradle:
> https://docs.gradle.org/current/userguide/application_plugin.html 
> 
> 
>> 
>>> 
>>> I thought the build was a vote on the sources and their distribution, while 
>>> binaries are convenience.
>> 
>> They are a convenience, but if you are using ASF resources then the 
>> licensing needs to properly follow policy.
> OK.
>> 
>>> 
>>> Do you have an example of (3)?
>> 
>> leveldbjni-all-1.8.jar is BSD 3-Clause
>> Jetty is dual licensed - you should declare that you are choosing AL2.
>> Jersey is quad licensed - …
>> Jaxb is CDDL 1.1, but used to be GPL
>> Javax is CDDL and GPL2 so you definitely need to declare.
>> Javasist is triple licensed - AL2, LGPL2, and MPL 1.1 so ...
>> Jakarta are EPL2 and GPL2.
>> 
>> I found this information quickly using mvnrepository.com
>> 
>> It’s all about easily assuring users of the binary package what the terms 
>> are.
>> 
>> These classes can be used for Binaries
>> Class A licenses: https://www.apache.org/legal/resolved.html#category-a
>> Class B licenses: https://www.apache.org/legal/resolved.html#category-b
>> Sources must not contain Class B.
>> 
>> Class X cannot be used: 
>> https://www.apache.org/legal/resolved.html#category-x 
>> 
> 
> Ah, we generate a license report but don’t include it. We can fix that in the 
> next release.
>> 
>> Regards,
>> Dave
>> 
>>> 
 On Nov 21, 2020, at 2:20 PM, Dave Fisher  wrote:
 
 Hi -
 
 Incubator in name, Signatures, Hashes, NOTICE, DISCLAIMER are in place.
 
 Source package LICENSEs are fine.
 
 Binaries -
 (1) bin directory - where are the sources for the scripts and bat files in 
 the Source Release?
 (2) bin directory - what is the license for these files?
 (3) LICENSE is identical to source release. The binary LICENSE and NOTICE 
 need to reflect everything included in the lib directory.
 
 I’m -0 (binding) on this release, I think these 3 issues do need to be 
 addressed.
 
 If other IPMC members are willing to VOTE +1 that’s ok with me.
 
 Regards,
 Dave
 
> On Nov 19, 2020, at 11:16 AM, Antoine Toulme  wrote:
> 
> Hi all,
> 
> We're voting on the source distributions available here:
> https://dist.apache.org/repos/dist/dev/incubator/tuweni/1.3.0-incubating/
> The release tag is present here:
> https://github.com/apache/incubator-tuweni/releases/tag/v1.3.0-incubating-rc
> 
> Please review and vote as appropriate.
> 
> The following changes were made since 1.2.0:
> 
> * Update to support Sodium 1.0.18 
> (https://github.com/apache/incubator-tuweni/pull/164 
> )
> * Base58 encoding support 
> (https://github.com/apache/incubator-tuweni/pull/150 
> )
> * eth65 support (https://github.com/apache/incubator-tuweni/pull/152 
> )
> * Add a helper to transform a SECP256K1 public key into an Ethereum 
> address (https://github.com/apache/incubator-tuweni/pull/154 
> )
> * Add a discv5 scraper 
> (https://github.com/apache/incubator-tuweni/pull/157 
> )
> * Upgrade Bouncy Castle 
> (https://github.com/apache/incubator-tuweni/pull/160 
> )
> * Upgrade Error Prone 
> (https://github.com/apache/incubator-tuweni/pull/165 
> )
> * Add Windows CI test build 
> (https://github.com/apache/incubator-tuweni/pull/167 
> )
> * Add binary snapshots 
> (https://github.com/apache/incubator-tuweni/issues/161 
> )
> * Misc fixes and clean ups to docs
> 
> Here is the release thread on the d...@tuweni.apache.org 
>  list:
> https://lists.apache.org/thread.html/r6ed976ff5519ea7227b5676e6a0af382afbb075a1bff1def384737b1%40%3Cdev.tuweni.apache.org%3E
> 
> The release vote has passed with 

Re: Request SVN permission for ip-clearance

[John D. Ament]

Please make sure you are using https. HTTP is read only. Try again.

John


On Sun, Nov 22, 2020 at 10:37 Ming Wen  wrote:

> hello, incubator,
>  I want to submit a new ip clearance to svn[1], but I found that I did not
> have the permission to write.
> How should I apply? thank you.
> my svn user name: wenming
>
> [1]
>
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/
>
> Thanks,
> Ming Wen, Apache APISIX PMC Chair
> Twitter: _WenMing
>

Re: Request SVN permission for ip-clearance

[Sheng Wu]

Hi Ming

I am not sure, whether this requires the IPMC authority, if really so, I
could help.

Sheng Wu 吴晟
Twitter, wusheng1108


Ming Wen  于2020年11月22日周日 下午11:37写道：

> hello, incubator,
>  I want to submit a new ip clearance to svn[1], but I found that I did not
> have the permission to write.
> How should I apply? thank you.
> my svn user name: wenming
>
> [1]
>
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/
>
> Thanks,
> Ming Wen, Apache APISIX PMC Chair
> Twitter: _WenMing
>

Request SVN permission for ip-clearance

[Ming Wen]

hello, incubator,
 I want to submit a new ip clearance to svn[1], but I found that I did not
have the permission to write.
How should I apply? thank you.
my svn user name: wenming

[1]
http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/

Thanks,
Ming Wen, Apache APISIX PMC Chair
Twitter: _WenMing

Re: [VOTE] Apache Tuweni 1.3.0 release

[Furkan KAMACI]

Hi,

+1 from me.

I checked:

- Incubating in name
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- No unexpected binary files
- Checked PGP signatures
- Checked checksums
- Code compiles and tests successfully run
- Apache rat checks are OK

Kind Regards,
Furkan KAMACI

On Sun, Nov 22, 2020 at 2:42 AM Antoine Toulme  wrote:

>
>
> > On Nov 21, 2020, at 2:50 PM, Dave Fisher  wrote:
> >
> >
> >
> >> On Nov 21, 2020, at 2:25 PM, Antoine Toulme 
> wrote:
> >>
> >> The binaries are generated by the build.
> >
> > I ran a build the jars were generated, but the scripts in the bin are
> not anywhere in the source tree. Those aren’t built I have no idea where
> the binary convenience got those scripts.
> The scripts are generated by the application plugin of Gradle:
> https://docs.gradle.org/current/userguide/application_plugin.html <
> https://docs.gradle.org/current/userguide/application_plugin.html>
>
> >
> >>
> >> I thought the build was a vote on the sources and their distribution,
> while binaries are convenience.
> >
> > They are a convenience, but if you are using ASF resources then the
> licensing needs to properly follow policy.
> OK.
> >
> >>
> >> Do you have an example of (3)?
> >
> > leveldbjni-all-1.8.jar is BSD 3-Clause
> > Jetty is dual licensed - you should declare that you are choosing AL2.
> > Jersey is quad licensed - …
> > Jaxb is CDDL 1.1, but used to be GPL
> > Javax is CDDL and GPL2 so you definitely need to declare.
> > Javasist is triple licensed - AL2, LGPL2, and MPL 1.1 so ...
> > Jakarta are EPL2 and GPL2.
> >
> > I found this information quickly using mvnrepository.com
> >
> > It’s all about easily assuring users of the binary package what the
> terms are.
> >
> > These classes can be used for Binaries
> > Class A licenses: https://www.apache.org/legal/resolved.html#category-a
> > Class B licenses: https://www.apache.org/legal/resolved.html#category-b
> > Sources must not contain Class B.
> >
> > Class X cannot be used:
> https://www.apache.org/legal/resolved.html#category-x <
> https://www.apache.org/legal/resolved.html#category-x>
>
> Ah, we generate a license report but don’t include it. We can fix that in
> the next release.
> >
> > Regards,
> > Dave
> >
> >>
> >>> On Nov 21, 2020, at 2:20 PM, Dave Fisher  wrote:
> >>>
> >>> Hi -
> >>>
> >>> Incubator in name, Signatures, Hashes, NOTICE, DISCLAIMER are in place.
> >>>
> >>> Source package LICENSEs are fine.
> >>>
> >>> Binaries -
> >>> (1) bin directory - where are the sources for the scripts and bat
> files in the Source Release?
> >>> (2) bin directory - what is the license for these files?
> >>> (3) LICENSE is identical to source release. The binary LICENSE and
> NOTICE need to reflect everything included in the lib directory.
> >>>
> >>> I’m -0 (binding) on this release, I think these 3 issues do need to be
> addressed.
> >>>
> >>> If other IPMC members are willing to VOTE +1 that’s ok with me.
> >>>
> >>> Regards,
> >>> Dave
> >>>
>  On Nov 19, 2020, at 11:16 AM, Antoine Toulme 
> wrote:
> 
>  Hi all,
> 
>  We're voting on the source distributions available here:
> 
> https://dist.apache.org/repos/dist/dev/incubator/tuweni/1.3.0-incubating/
>  The release tag is present here:
> 
> https://github.com/apache/incubator-tuweni/releases/tag/v1.3.0-incubating-rc
> 
>  Please review and vote as appropriate.
> 
>  The following changes were made since 1.2.0:
> 
>  * Update to support Sodium 1.0.18 (
> https://github.com/apache/incubator-tuweni/pull/164 <
> https://github.com/apache/incubator-tuweni/pull/164>)
>  * Base58 encoding support (
> https://github.com/apache/incubator-tuweni/pull/150 <
> https://github.com/apache/incubator-tuweni/pull/150>)
>  * eth65 support (https://github.com/apache/incubator-tuweni/pull/152
> )
>  * Add a helper to transform a SECP256K1 public key into an Ethereum
> address (https://github.com/apache/incubator-tuweni/pull/154 <
> https://github.com/apache/incubator-tuweni/pull/154>)
>  * Add a discv5 scraper (
> https://github.com/apache/incubator-tuweni/pull/157 <
> https://github.com/apache/incubator-tuweni/pull/157>)
>  * Upgrade Bouncy Castle (
> https://github.com/apache/incubator-tuweni/pull/160 <
> https://github.com/apache/incubator-tuweni/pull/160>)
>  * Upgrade Error Prone (
> https://github.com/apache/incubator-tuweni/pull/165 <
> https://github.com/apache/incubator-tuweni/pull/165>)
>  * Add Windows CI test build (
> https://github.com/apache/incubator-tuweni/pull/167 <
> https://github.com/apache/incubator-tuweni/pull/167>)
>  * Add binary snapshots (
> https://github.com/apache/incubator-tuweni/issues/161 <
> https://github.com/apache/incubator-tuweni/issues/161>)
>  * Misc fixes and clean ups to docs
> 
>  Here is the release thread on the d...@tuweni.apache.org  d...@tuweni.apache.org> list:
> 
>