Re: [VOTE] Release Apache Superset (incubating) version 0.37.1

2020-09-15 Thread Willem Jiang
+1 (binding)
I checked
1. Incubating in name
2. Download links are valid.
3. Checksums and PGP signatures are valid.
4. DISCLAIMER included.
5. LICENSE and NOTICE are fine
6. License headers
7. No unexpected binary files

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Wed, Sep 9, 2020 at 11:37 PM Ville Brofeldt
 wrote:
>
> Hello IPMC,
>
> The Apache Superset (incubating) community has voted on and approved a 
> proposal to
> release Apache Superset (incubating) version 0.37.1.
> The voting thread can be found here: 
> https://lists.apache.org/thread.html/r4462440505c3eea8fbfdbad76575d29a6ce23e7fb575d45a66a1e946%40%3Cdev.superset.apache.org%3E
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Superset (incubating) is a modern, enterprise-ready business 
> intelligence web application
>
> The release candidate: 
> https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.1rc1/
>
> Git tag for the release: 
> https://github.com/apache/incubator-superset/tree/0.37.1rc1
>
> The Change Log for the release: 
> https://github.com/apache/incubator-superset/blob/0.37.1rc1/CHANGELOG.md
>
> public keys are available at: 
> https://www.apache.org/dist/incubator/superset/KEYS
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Superset (Incubating) Team

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



Re: [VOTE] Graduate Apache IoTDB as TLP

2020-09-11 Thread Willem Jiang
+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Sep 10, 2020 at 3:42 PM Xiangdong Huang  wrote:
>
> Dear all IPMCs:
>
> Following discussions with great support from our mentors,
> committers and community members.
> I would like to call for a formal VOTE for graduating Apache IoTDB
> (Incubating),
> as a Top Level Project.
>
> This is a formal voting thread about Apache IoTDB's graduation, please Vote:
> [ ] +1 - Recommend graduation of Apache IoTDB as a TLP
> [ ]  0
> [ ] -1 - Do not recommend the graduation of Apache IoTDB because...
>
> The VOTE will open for at least 72 hours.
>
> Apache IoTDB (Incubating) entered the incubator in Nov 2018, the community
> has grown vibrantly since, with all the design, development happening on
> the Apache infrastructure, the "Apache Way".
>
> To list a few of the community's achievements,
>
> - Apache IoTDB name search has been approved
> - Accepted > 1300 PRs from 75 contributors
> - Migrated developer conversations to the list at d...@iotdb.apache.org
>   (more than 3000 mails, without JIRA notifications, and gitbox, are sent
> by more than 160 persons)
> - There are 9 versions (3 major versions) released successfully conformant
> to Apache release policy by 5 release managers;
> - Invited 12 new committers (all of them accepted)
> - invited 4 of those new committers to join the PMC (all of them accepted)
> - Our proposed PMC is diverse and consists of members from more than 10
> organizations
>
> Preparations and discussions history about the graduation:
>
> - The maturity assessment is done [2],
> - The community agreed on starting the graduation process in a formal vote
> [3] (result see [4]).
> And, I'd like to note that all our mentors also participated in the vote
> with a positive vote!
> - The community also decided about a suggestion for the initial VP, a
> charter [5, 6] and the initial PMC list [7].
> - We also received positive feedback from the incubator general mailing
> list [8].
>
>
> The draft of the resolution:
>
> Establish the Apache IoTDB Project
>
>WHEREAS, the Board of Directors deems it to be in the best
>interests of the Foundation and consistent with the
>Foundation's purpose to establish a Project Management
>Committee charged with the creation and maintenance of
>open-source software, for distribution at no charge to
>the public, related to an IoT native database with high performance
>for data management and analysis, on the edge and the cloud.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache IoTDB Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache IoTDB Project be and hereby is
>responsible for the creation and maintenance of software
>related to an IoT native database with high performance
>for data management and analysis, on the edge and the cloud.
>and be it further
>
>RESOLVED, that the office of "Vice President, Apache IoTDB 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 IoTDB Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache IoTDB 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 IoTDB Project:
>
>  * Chen Wang  
>  * Christofer Dutz 
>  * Dawei Liu 
>  * Gaofei Cao 
>  * Haonan Hou 
>  * Jialin Qiao 
>  * Jianmin Wang 
>  * Jincheng Sun 
>  * Jinrui Zhang 
>  * Julian Feinauer 
>  * Jun Yuan 
>  * Justin Mclean 
>  * Kevin A. McGrail 
>  * Kun Liu 
>  * Lei Rui 
>  * Rong Kang 
>  * Rui Liu 
>  * Shuo Zhang 
>  * Stefanie Zhao 
>  * Tian Jiang 
>  * Tianan Li 
>  * Willem Ning Jiang 
>  * Xiangdong Huang 
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Xiangdong Huang
>be appointed to the office of Vice President, Apache IoTDB, 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,
>   

Re: [DISCUSS] Apache IoTDB Graduation

2020-09-07 Thread Willem Jiang
IoTDB made a great progress in community building and software
developing and releasing.
Congratulations!  I'm sure that IoTDB can go even better and faster
after graduation :)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Sep 7, 2020 at 7:55 PM Xiangdong Huang  wrote:
>
> Hi,
>
> To make it easy to touch all the important information, I'd like to
> organize  the content
> from the reference URLs, especially  the whole draft of the resolution, to
> this thread:
>
>
> Apache IoTDB (Incubating) entered the incubator in Nov 2018, the community
> has grown vibrantly since, with all the design, development happening on
> the Apache infrastructure, the "Apache Way".
>
> To list a few of the community's achievements,
>
> - Apache IoTDB name search has been approved
> - Accepted > 1300 PRs from 75 contributors
> - Migrated developer conversations to the list at d...@iotdb.apache.org
>   (more than 3000 mails, without JIRA notifications, and gitbox, are sent
> by more than 160 persons)
> - There are 9 versions (3 major versions) released successfully conformant
> to Apache release policy by 5 release managers;
> - Invited 12 new committers (all of them accepted)
> - invited 4 of those new committers to join the PMC (all of them accepted)
> - Our proposed PMC is diverse and consists of members from more than 10
> organizations
>
>
> The maturity assessment is done [2], and the community agreed on starting
> the graduation process in a formal vote [3] (result see [4]).
> And, I'd like to note that all our mentors also participated in the vote
> with a positive vote!
> The community also decided about a suggestion for the initial VP and a
> charter [5, 6].
>
> The draft of the resolution is:
>
> Establish the Apache IoTDB Project
>
>WHEREAS, the Board of Directors deems it to be in the best
>interests of the Foundation and consistent with the
>Foundation's purpose to establish a Project Management
>Committee charged with the creation and maintenance of
>open-source software, for distribution at no charge to
>the public, related to an IoT native database with high performance
>for data management and analysis, on the edge and the cloud.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache IoTDB Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache IoTDB Project be and hereby is
>responsible for the creation and maintenance of software
>related to an IoT native database with high performance
>for data management and analysis, on the edge and the cloud.
>and be it further
>
>RESOLVED, that the office of "Vice President, Apache IoTDB 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 IoTDB Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache IoTDB 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 IoTDB Project:
>
>  * Chen Wang  
>  * Christofer Dutz 
>  * Dawei Liu 
>  * Gaofei Cao 
>  * Haonan Hou 
>  * Jialin Qiao 
>  * Jianmin Wang 
>  * Jincheng Sun 
>  * Jinrui Zhang 
>  * Julian Feinauer 
>  * Jun Yuan 
>  * Justin Mclean 
>  * Kevin A. McGrail 
>  * Kun Liu 
>  * Lei Rui 
>  * Rong Kang 
>  * Rui Liu 
>  * Shuo Zhang 
>  * Tian Jiang 
>  * Tianan Li 
>  * Willem Ning Jiang 
>  * Xiangdong Huang 
>  * Stefanie Zhao 
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Xiangdong Huang
>be appointed to the office of Vice President, Apache IoTDB, 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 IoTDB 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 IoTDB Project; and be it further
>
>RESO

Re: [VOTE] Release Apache IoTDB 0.10.1

2020-08-18 Thread Willem Jiang
+1 (binding)

I just have a quick question about the README files. Why do we put
them into the release directory?

I checked:
Verified the signed the key and hash code.
 Incubating in the release kit name.
License and Notice files  are good to me.
The maven staging repo looks good.
Git repo release tag.
There is no binary in the source kit.
I can build the kit from source.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Aug 14, 2020 at 9:59 AM Xiangdong Huang  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version
> 0.10.1, which is a bug-fix version of 0.10.0.
>
> The Apache IoTDB community has voted on and approved a proposal to
> release Apache
> IoTDB (Incubating) version 0.10.1 (with 12 +1 votes).
>
> We now kindly request the Incubator PMC members review and vote on
> this incubator
> release.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an
> integrated data management engine designed for timeseries data.
>
> IoTDB community vote and result thread:
>
> Result:
>
> https://lists.apache.org/thread.html/r3d2081bac4aed5217820a4587383150dc7b6471828675d9b6eeacf5e%40%3Cdev.iotdb.apache.org%3E
>
>
> Vote:
>
> https://lists.apache.org/thread.html/r94e5dcac19d5f2ba9990a95cc1fb5232074702de9f1c326d27eebfe3%40%3Cdev.iotdb.apache.org%3E
>
>
> The release candidates (RC3):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/
>
> Git tag for the release (RC3):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.10.1
>
> Hash for the release tag:
> 023fb84e0b76c0ac64b7a9ac098c640f26795a25
>
>
> Release Notes:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/RELEASE_NOTES.md
>
>
> The artifacts have been signed with Key: 2206EF8F64C35889, which can be found
> in the keys file:
>
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
>
> The vote will be passed if there are at least 3 IPMC +1 votes and there is
> no -1 vote.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Xiangdong Huang
> Apache IoTDB (incubating)

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



Re: [DISCUSS] EventMesh Proposal

2020-08-14 Thread Willem Jiang
We need to build the community around the project once we open source
the code.  It's quite important for the health of the project.
Even the project is accepted as a podling of incubator,  you still
need to keep building the community.
>From the information we got through the Github project, I cannot get
the conclusion that you are building the community here[1].
I don't know you plan of the internal version and the open source
version, if there are two different version projects why are you so
urge to contribute the project which is not in active development to
Apache?

I think Sheng Wu already expressed the same concern as I did.  Please
think about it carefully, and make process to address our concerns.

[1]https://github.com/WeBankFinTech/EventMesh

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Aug 15, 2020 at 9:09 AM Eason Chen  wrote:
>
> Hi,
>
>
> After the project was open sourced, we did not conduct evangelism, and the 
> internal version iterations were not synchronized in time. Many of these 
> issues and prs were raised by many of our partners, and many of them were not 
> reflected on github. Some document changes were also requested by them, It is 
> not very irregular at present, but we will run the standardized mechanism 
> later.
>
>
> Thanks,
> Eason
>
>
>
>
> --原始邮件--
> 发件人:  
>   "general"   
>  
>  发送时间:2020年8月14日(星期五) 晚上9:37
> 收件人:"Incubator General"
> 主题:Re: [DISCUSS] EventMesh Proposal
>
>
>
> Hi,
>
> I just spent some time on the issues of EventMesh[1], it looks like
> there are a bunch of people interested about this project, but
> unfortunately the recent replied issue is about three weeks ago.
> It's quite strange for me that the project maintainers are not keen to
> answer the issues if they want to build the community from the
> scratch.
>
> I also checked the commit logs, I can only find some small
> documentation fixes which were done through the Github web interface.
> I cannot find any new feature development commits after went through
> the commits.
> I'm not sure if WeBankFinTech guys do regular development on this repo.
>
> BTW, There is still an open issue asking if all the features are open
> sourced[2].
>
> [1]https://github.com/WeBankFinTech/EventMesh/issues
> [2]https://github.com/WeBankFinTech/EventMesh/issues/5
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>

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



Re: [DISCUSS] EventMesh Proposal

2020-08-14 Thread Willem Jiang
Hi,

I just spent some time on the issues of EventMesh[1], it looks like
there are a bunch of people interested about this project, but
unfortunately the recent replied issue is about three weeks ago.
It's quite strange for me that the project maintainers are not keen to
answer the issues if they want to build the community from the
scratch.

I also checked the commit logs, I can only find some small
documentation fixes which were done through the Github web interface.
I cannot find any new feature development commits after went through
the commits.
I'm not sure if WeBankFinTech guys do regular development on this repo.

BTW, There is still an open issue asking if all the features are open
sourced[2].

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

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Aug 14, 2020 at 7:42 PM Eason Chen  wrote:
>
> Thanks Justin, and can not agree more.
>
>
> Thanks everyone for your attention to this project and your valuable comments.
>
>
> If everyone has no problems, i will initiate the voting processs later.
>
>
> Thanks,
> Eason
>
>
> -- 原始邮件 --
> 发件人:  
>   "general"   
>  
>  发送时间:2020年8月14日(星期五) 下午4:57
> 收件人:"general"
> 主题:Re: [DISCUSS] EventMesh Proposal
>
>
>
> Hi,
>
> The incubator prefers that a project comes with a community around it but 
> it’s not essential. Not having one may possibly make graduation harder, as 
> long as the project is aware of that I don’t see any issues.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

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



Re: [MENTORS] Podling reports due today

2020-08-06 Thread Willem Jiang
Sorry for that, I will ping Doris PPMC for sending a report next month.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Aug 6, 2020 at 3:43 PM Justin Mclean  wrote:
>
> HI,
>
> > Looks like Doris will reimport next moth.
>
> Report next month even :-)
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: [VOTE] Release Apache brpc(incubating) 0.9.8-rc01

2020-08-02 Thread Willem Jiang
+1. (binding)

Here are my checks,
1. Signature and Hashed are good.
2. Release commit and Tag are good.
3. LICENSE and NOTICE files are good for me.
4. I can build the binary from the Source release kit by going through
the build readme.
5. DISCLAIMER-WIP is included.

BTW, We need to remove the file of incubator-brpc-0.9.8-rc01.tar.gz
from the release staging directory.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Wed, Jul 15, 2020 at 7:02 PM tan zhongyi  wrote:
>
> Hi, guys,
>
>
>
> I am pleased to be calling this vote for the release of Apache brpc 
> (incubating) 0.9.8-rc01
>
>  BTW: there is still some license issues to be fixed, so we keep  
> DISCLAIMER-WIP there, we will fix them in later releases.
>
>
>
> Apache brpc community has voted and approved the release.
>
>
>
> Vote thread: 
> https://lists.apache.org/thread.html/r5b76897ad047c326d4b580a6c110e17ec26f7cb1db95425248827df8%40%3Cdev.brpc.apache.org%3E
>
>  Results thread: 
> https://lists.apache.org/thread.html/rd6667c2aad6a94238234e07461831cadf08e7ae7e66170dd4b25a694%40%3Cdev.brpc.apache.org%3E
>
>
>
> The release candidate to be voted over is available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.8-rc01/incubator-brpc-0.9.8-rc01.tar.gz
>
>
>
>
>
> The SHA-512 checksum is:
>
> 972744e0915b2bf881ad04bae393761170bf91003b44c82dff8ba5306e8081abb5c4108c469a58ac4e4162838a04191fcf681594d89a7d97bbbfa0943cc2f41d
>
> which can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.8-rc01/incubator-brpc-0.9.8-rc01.tar.gz.sha512
>
> The signature can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.8-rc01/incubator-brpc-0.9.8-rc01.tar.gz.asc
>
> KEYS file is available here:
>
> https://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS
>
>
>
>
>
> [Release Note]
>
> * Fix bug that time unit is not listed in grpc timeout options.
>
> https://github.com/apache/incubator-brpc/pull/1036
>
> * Fix heap overflow in simple_data_pool
>
> https://github.com/apache/incubator-brpc/pull/1056
>
> * Make args of redis protocol be StringPiece
>
> https://github.com/apache/incubator-brpc/pull/1128
>
> * Support the length of redis args could be zero
>
> https://github.com/apache/incubator-brpc/pull/1128
>
> * Optimize code in timer_thread
>
> https://github.com/apache/incubator-brpc/pull/1137/files
>
> * Fix a narrowing warning on aarch64
>
> https://github.com/apache/incubator-brpc/commit/87f149c464ea0322a5b59d040bb80e7847f365be
>
> * Make pthread_atfork not registered in child process
>
> https://github.com/apache/incubator-brpc/commit/2f8fc37d52c2a02ee6f348aaa52c7ded4a4844c3
>
> * Rename LOG_NONE which conflicts with a name in mysql
>
> https://github.com/apache/incubator-brpc/commit/e3840c18cdd9e1ff81f8280b96ac14869007a122
>
> * Fix several warnings under MAC
>
> https://github.com/apache/incubator-brpc/commit/f8c188a7a5186c2d43a20735ad175a32b39788a3
>
> * Ignore ELIMIT for circuit breaker
>
> https://github.com/apache/incubator-brpc/pull/1005
>
> * limit minimum value of max_concurrency for auto_cl
>
> https://github.com/apache/incubator-brpc/pull/1003
>
>
>
>
>
> Please vote on releasing this package as:
>
> Apache brpc(incubating) 0.9.8-rc01
>
>
>
> This vote will be open until “Monday July 20 2020 00:00:00 GMT+0800 (CST)" and
>
> passes if a majority of at least three +1 Apache Incubator IPMC votes are
>
> cast.
>
>
>
> [ ] +1 Release this package
>
> [ ] 0  I don't feel strongly about it, but don't object
>
> [ ] -1 Do not release this package because...
>
>
>
> Anyone can participate in testing and voting, not just committers, please
>
> feel free to try out the release candidate and provide your votes.
>
>
>
> A checklist for reference:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>

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



Re: [VOTE] Accept Sedona into the Apache Incubator

2020-07-18 Thread Willem Jiang
+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Jul 16, 2020 at 11:49 AM Felix Cheung  wrote:
>
> Hi,
>
> As we discussed the Sedona proposal [1], I would like to call for a vote to
> accept Sedona into the Apache Incubator.
>
> Sedona is a big geospatial data processing engine. The system provides an
> easy to use Scala, SQL, and Python APIs for spatial data scientists to
> manage, wrangle, and process geospatial data. The system extends and builds
> upon a popular cluster computing framework (Apache Spark) to provide
> scalability.
>
> The final proposal can be found at
> https://cwiki.apache.org/confluence/display/INCUBATOR/Sedona+Proposal
>
> Please cast your vote:
>
>   [ ] +1, yes, bring Sedona into Incubator
>   [ ] 0, I don't care either way
>   [ ] -1, no, do not bring Sedona into Incubator, because...
>
> The vote will open for at least 72 hours and only votes from the IPMC
> members are considered binding, but other votes are welcome!
>
> Thanks,
> Felix
>
>
> -
> [1]
> https://lists.apache.org/thread.html/r72f0b7ddd3143179045653050de9b7de8508d8f8b8194bd73a53e704%40%3Cgeneral.incubator.apache.org%3E

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



Re: [VOTE] Release Apache IoTDB 0.10.0

2020-06-28 Thread Willem Jiang
+1 (binding)

Here are my checks,
1. Signature and Hashed are good.
2. Release commit and Tag are good.
3. LICENSE and NOTICE files are good for me.
4. I can build the binary from the Source release kit.
5. DISCLAIMER is included.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Jun 24, 2020 at 9:39 AM Xiangdong Huang  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version
> 0.10.0, which is the 3rd major version (and the  8th minor version) of
> Apache IoTDB Project.
>
> The Apache IoTDB community has voted on and approved a proposal to release
> Apache IoTDB (Incubating) version 0.10.0.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache IoTDB (incubating) (Database for the Internet of Things) is an
> integrated data management engine designed for timeseries data. It provides
> users with services for data collection, storage and analysis.
>
> IoTDB community vote and result thread:
>
>
> Result (17 +1 votes from mentors, IPMCs, PPMCs, committers and other
> contributors):
>
> -
> https://lists.apache.org/thread.html/rf40abefda97a0675cb44ae985e3a3b7741dcac90ac5b01408c6331f6%40%3Cdev.iotdb.apache.org%3E
>
>
> Vote:
>
> -
> https://lists.apache.org/thread.html/r67d045df992a3d5d400dbe396e926ed847e4e102559c9c6508544009%40%3Cdev.iotdb.apache.org%3E
>
> -
> https://lists.apache.org/thread.html/r89794d3741f9f63757b09ec440fcd5d557346540d40e74c0dd27%40%3Cdev.iotdb.apache.org%3E
>
> The release candidates (RC4):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.0/rc4
>
> Git tag for the release (RC4):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.10.0
>
> Hash for the release tag:
> f506d9c731231f97d8813528cbf062760d40
>
> Release Notes:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.0/rc4/RELEASE_NOTES.md
>
> The artifacts have been signed with Key : 2206EF8F64C35889, which can be
>
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
> From the PPMC Vote we carry over 3 binding IPMC Votes:
>
> +1 from Justin Mclean,
> +1 from Julian Feinauer,
> +1 from Christofer Dutz
>
> The vote will be passed if there is no -1 vote ( as there are 3 IPMC +1
> votes already), but we still hope all other IPMCs vote for it.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Xiangdong Huang
> Apache IoTDB (incubating)

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



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

2020-06-17 Thread Willem Jiang
+1 (binding).

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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

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



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

2020-06-12 Thread Willem Jiang
+1 (binding).
It's great to see that APISIX made a big step during the incubation process.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Jun 12, 2020 at 4:53 PM Ming Wen  wrote:
>
> Hello,
>
> After discussion with the community[1], finally positive vote result[2].
> We'd like to bring this to a discussing at the IPMC.
>
> Please see the proposed resolution below and let us know what do you think.
>
> A few status to help with the discussion:
>
> - Released 6 Apache releases, through 6 different release managers
> - Invited 9 new committers (all accepted)
> - Invited 5 new PPMC members (all accepted)
> - Apache APISIX name search has been approved [3]
> - finished the Podling Maturity Assessment for APISIX, all items are passed[4]
> - Our PPMC is diverse and consists of members from 10+ organizations
> - 1156 emails sent by 81 people in dev mailing-list excepted GitBox
> forwarded
> - There are 82 contributors for now
> - Resolved 360+ issues and 820+ pull requestsduring ASF incubating
>
> We've resolved all branding issues which include Logo, GitHub repo,
> document, website, luarocks and DockerHub.
>
> [1]
> https://lists.apache.org/thread.html/r3cd791660b7a8aeb06a116a3802c8e154cde392dc90797d66a9267e9%40%3Cdev.apisix.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/ree04577ad2ebb2959f401b0848400f3b2876457f510f375797b6fbf8%40%3Cdev.apisix.apache.org%3E
> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-180
> [4]
> https://cwiki.apache.org/confluence/display/APISIX/Podling+Maturity+Assessment+for+APISIX
>
> ---
>
> Establish the Apache APISIX Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to Apache APISIX is a cloud-native microservices API gateway,
> delivering the ultimate performance, security and scalable platform
> for APIs and microservices...
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache APISIX Project", be and hereby
> is established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache APISIX Project be and hereby is
> responsible for the creation and maintenance of software related to
>  Apache APISIX is a cloud-native microservices API gateway,
> delivering the ultimate performance, security and scalable platform
> for APIs and microservices; and be it further
>
> RESOLVED, that the office of "Vice President, Apache APISIX" be
> and hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache
> APISIX Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of the
> Apache APISIX Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache APISIX Project:
> * agile6v 
> * Ayeshmantha Perera  
> * Jarvis.Qiu 
> * jinwei 
> * junxu chen 
> * Justin Mclean 
> * Kevin Ratnasekera 
> * Lang Wang 
> * liling 
> * linsir 
> * Ming Wen 
> * Nirojan Selvanathan 
> * sheng wu 
> * spacewander 
> * Von Gosling  
> * Willem Ning Jiang 
> * yousa 
> * YuanSheng Wang 
> * Zhiyuan Ju  
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ming Wen be appointed to
> the office of Vice President, Apache APISIX, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache APISIX Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> APISIX podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> APISIX podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
> ---
>
> Thanks,
> Ming Wen, Apache APISIX & Apache SkyWalking
> Twitter: _WenMing

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



Re: [Proposal] Pegasus - proposal for Apache Incubation

2020-06-08 Thread Willem Jiang
Hi,

I just went through the proposal and found there are two source code
repos[1][2] which are forked.

Are you planning to donate these two repos into Apache as a part of
Pegasus project?
It makes the donation of the Pegasus complicated as we need to address
this two code repo belonging issue first.
Normally we just contribute the patch to the upstream as it consume
lots of resources if we maintain the forked repo.

[1] https://github.com/XiaoMi/rdsn
[2] https://github.com/XiaoMi/pegasus-rocksdb


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jun 2, 2020 at 3:49 PM 吴涛  wrote:
>
> Dear Apache Incubator Community,
>
> I'd like to open up a discussion about incubating Pegasus at Apache. Our 
> proposal can be found at https://pegasus-kv.github.io/community/proposal and 
> is also included below.
>
> We are looking for possible Champion if anyone would like to volunteer. 
> Thanks a lot!
>
> Best regards
>   Tao Wu
>
> Pegasus Proposal
>
> == Abstract ==
>
> Pegasus is a distributed key-value storage system that is designed to be 
> horizontally scalable, strongly consistent and high-performance.
>
> - Pegasus codebase: https://github.com/XiaoMi/pegasus
> - Website: https://pegasus-kv.github.io
>
> == Proposal ==
>
> Pegasus is a key-value database that delivers low-latency data access 
> together with horizontal scalability, using hash-based partitioning. Pegasus 
> uses PacificA protocol for strong consistency and RocksDB as the underlying 
> storage engine.
>
> We propose to contribute the Pegasus codebase and associated artifacts (e.g., 
> documentation, website content, etc.) to the Apache Software Foundation, and 
> aim to build an open community around Pegasus’s continued development in the 
> ‘Apache Way’.
>
> == Background ==
>
> Apache HBase was recognized as mostly the only large-scale KV store solution 
> in XiaoMi Corp until Pegasus came out in 2015. The original purpose of 
> Pegasus was to solve the problems caused by HBase’s two-level architecture 
> and implementation, including high latency because of Java GC and RPC 
> overhead of the underlying distributed filesystem, and long failover time 
> because of single point of RegionServer and recovery overhead of splitting 
> and replaying the HLog files.
>
> Pegasus aims to fill the gap between Redis and HBase. As the former is 
> in-memory, low latency, but does not provide a strong-consistency guarantee. 
> And unlike the latter, Pegasus server is entirely written in C++ and its 
> read-write path relies merely on the local filesystem.
>
> Apart from performance requirements, we also need a storage system to ensure 
> multiple-level data safety and support fast data migration among data 
> centers, automatic load balancing, and online partition splitting.
>
> After investigating lots of existing storage systems in the open source 
> world, we could hardly find a suitable solution to satisfy all the 
> requirements. So the journey of Pegasus begins.
>
> === Rationale ===
>
> Pegasus is a mature and active project which has been widely adopted in 
> XiaoMi. After the initial release of open source project in 2017, we have 
> seen a great amount of interest across a diverse set of users and companies.
>
> Our experiences at committers and PMC members on other Apache projects have 
> convinced us that having a long-term home at Apache foundation would be a 
> great fit for the project, to ensure that processes and procedures are in 
> place to keep project and community ‘healthy’ and free of any commercial, 
> political or legal faults.
>
> === Initial Goal ===
>
> Move the existing codebase, website, documentation, and mailing lists to 
> Apache-hosted infrastructure.
> Work with the infrastructure team to implement and approve our code review, 
> build, and testing workflows in the context of the ASF.
> Incremental development and releases along with Apache guidelines.
>
> == Current Status ==
>
> Pegasus has been an open-source project on GitHub 
> https://github.com/XiaoMi/pegasus since October 2017.
>
> === Meritocracy ===
>
> The intent of this proposal is to start building a diverse developer and user 
> community around Pegasus following the ASF meritocracy model. We plan to 
> invite more people as committers if they contribute to this project.
>
> === Releases ===
>
> Pegasus has undergone multiple public releases, listed here: 
> https://github.com/XiaoMi/pegasus/releases.
>
> These old releases were not performed in the typical ASF fashion. We will 
> adopt the ASF source release process upon joining the incubator.
>
> === Code Reviews ===
>
> Pegasus’s code reviews are currently public on Github 
> https://github.com/Xia

Re: [VOTE] Accept Apache BlueMarlin in the incubator

2020-06-02 Thread Willem Jiang
+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, May 25, 2020 at 2:27 PM Jean-Baptiste Onofre  wrote:
>
> Hi everyone,
>
> Following the discussion about BlueMarlin, I would like to start a formal 
> vote to accept BlueMarlin into the incubator.
>
> As reminder, here’s the proposal: 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Apache+BlueMarlin 
> <https://cwiki.apache.org/confluence/display/INCUBATOR/Apache+BlueMarlin>
>
> Please vote to accept BlueMarlin in the incubator:
>
>   [ ] +1, accept BlueMarlin into Incubator
>   [ ] -1, don’t accept BlueMarlin into Incubator (please provide a reason)
>
> The vote is open for 72 hours.
>
> Thanks,
> Regards
> JB

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



Re: [VOTE] Release Apache ECharts (incubating) 4.8.0 (release candidate 1)

2020-05-22 Thread Willem Jiang
+1 (binding)

I checked:
1. Signature and Hashed are good.
2. Release commit and Tag are good.
3. LICENSE and NOTICE file are good for me.
4. DISCLAIMER is included.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 13, 2020 at 4:24 PM SHUANG SU  wrote:
>
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.8.0 (release candidate 1).
>
> Apache ECharts community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/rebb8453baeeb21eaaa27a4dfc278413b6be0b1cf6850e50a0c3fc61e%40%3Cdev.echarts.apache.org%3E
>
> Results thread:
> https://lists.apache.org/thread.html/r2556f5ff658f5d0c9d74416d7c8be010e9d678f9e3454c3cdb092bef%40%3Cdev.echarts.apache.org%3E
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.8.0-rc.1/
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> The Git commit for this release is:
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=3b61add
>
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.8.0-rc.1/RELEASE_NOTE.txt
>
> Build Guide:
> https://github.com/apache/incubator-echarts/blob/4.8.0-rc.1/README.md#build
>
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.8.0 (release candidate 1)
> by "2020-05-16T09:21:46.851Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
>
>
> From the votes on the dev mailing list we carry over 1 binding IPMC vote
> +1 from Sheng Wu.
>
>
>
> Thanks,
> --
>  Su Shuang (100pah)
> --

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



Re: [VOTE] Recommend Apache Iceberg graduation to top-level project resolution to the board

2020-05-18 Thread Willem Jiang
+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, May 16, 2020 at 8:40 AM Ryan Blue  wrote:
>
> Hi everyone,
>
> With the support of our mentors (as well as helpful ASF members), the
> Apache Iceberg community has voted to graduate to a top-level project.
>
> I propose a vote to recommend graduation for the Iceberg community to the
> board. Here is the proposed resolution:
>
> ```
> Establish the Apache Iceberg 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 managing huge analytic datasets using a standard at-rest
> table format that is designed for high performance and ease of use..
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Iceberg Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Iceberg Project be and hereby is responsible
> for the creation and maintenance of software related to managing huge
> analytic datasets using a standard at-rest table format that is designed
> for high performance and ease of use; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Iceberg" 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 Iceberg
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Iceberg
> 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 Iceberg Project:
>
>  * Anton Okolnychyi 
>  * Carl Steinbach   
>  * Daniel C. Weeks  
>  * James R. Taylor  
>  * Julien Le Dem
>  * Owen O'Malley
>  * Parth Brahmbhatt 
>  * Ratandeep Ratti  
>  * Ryan Blue
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ryan Blue be appointed to
> the office of Vice President, Apache Iceberg, to serve in accordance
> with and subject to the direction of the Board of Directors and the
> Bylaws of the Foundation until death, resignation, retirement, removal
> or disqualification, or until a successor is appointed; and be it
> further
>
> RESOLVED, that the Apache Iceberg Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Iceberg
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Iceberg podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
> ```
>
> The community vote passed with 19 +1 votes:
> https://lists.apache.org/thread.html/r9081df0181768f26490f5a85aed7b5a111a82a741764eb3a0e99621d%40%3Cdev.iceberg.apache.org%3E
>
> We also addressed concerns on the IPMC thread, which you can read here:
> https://lists.apache.org/thread.html/r3e5795d959feb0a19b233aeaf1121a1d97fd473f5e9b14227de41c54%40%3Cgeneral.incubator.apache.org%3E
>
> Please vote on whether to recommend graduation for the Apache Iceberg
> community to the board.
>
> [ ] +1 Apache Iceberg should graduate
> [ ] +0
> [ ] -1 Apache Iceberg should not graduate because . . .
>
> The vote will be open for at least 72 hours.
>
> --
> Ryan Blue

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



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

2020-05-16 Thread Willem Jiang
+1 (binding)


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, May 16, 2020 at 9:50 AM Vinoth Chandar  wrote:
>
> Hello all,
>
> I would like to call for a VOTE for graduating Apache Hudi (Incubating), as
> a top level project.
>
> Please vote on the resolution pasted below to graduate Apache Hudi from the
> incubator to a Top Level Project.
>
> [ ] +1 Graduate Apache Hudi from the Incubator.
> [ ] +0
> [ ] -1 Don't graduate Apache Hudi from the Incubator because ...
>
> This vote will open for at least 72 hours.
>
> Apache Hudi (Incubating) entered the incubator in Jan 2019, the community
> has grown vibrantly since, with all the design, development happening on
> the Apache infrastructure, the "Apache way".
>
> To list a few of the community's achievements,
>
> - Accepted > 500 patches from 90 contributors, including 15+ new  design
> proposals
> - Performed 3 releases with 3 different release managers [5]
> - Invited 5 new committers (all of them accepted)
> - invited 3 of those new committers to join the PMC (all of them accepted)
> - Migrated our web site to ASF infrastructure [1]
> - Migrated developer conversations to the list at d...@hudi.apache.org
> - Migrated all issue tracking to JIRA [2]
> - Apache Hudi name search has been approved [3]
> - Assessed ourselves against the Apache Project maturity matrix [4]
> - We have built a meritocratic, open collaborative process, the Apache way
> - Our proposed PMC is diverse and consists of members from ~10 organizations
>
> We discussed our readiness for graduation as a community [6] and voted
> unanimously in favor [7] (results summarized in [8]).  We have collaborated
> on a resolution for graduation, including PMC membership and PMC chair. We
> have also addressed the issues raised on the general@incubator DISCUSS
> thread [9].
>
>
> [1] https://hudi.apache.org
>
> [2] https://issues.apache.org/jira/projects/HUDI/
>
> [3] https://jira.apache.org/jira/browse/PODLINGNAMESEARCH-162
>
> [4]
> https://cwiki.apache.org/confluence/display/HUDI/Apache+Hudi+Maturity+Matrix
>
>
> [5] https://hudi.apache.org/releases.html
> [6]
> https://lists.apache.org/thread.html/rc98303d9f09665af90ab517ea0baeb7c374e9a5478d8424311e285cd%40%3Cdev.hudi.apache.org%3E
> [7]
> https://lists.apache.org/thread.html/rc19cedf6bb423cfc24efea27d8952a2224370a7679bab74d05de19b2%40%3Cdev.hudi.apache.org%3E
> [8]
> https://lists.apache.org/thread.html/r7b5c169c1bc3a1acaa35f43ff5388f5fc8b60746d423043464fcf5df%40%3Cdev.hudi.apache.org%3E
> [9]
> https://lists.apache.org/thread.html/r10d8c2038f1131c4da3e0cc2759da3554fab846bd623830251327b27%40%3Cgeneral.incubator.apache.org%3E
>
> Establish the Apache Hudi 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 providing atomic upserts and incremental data streams on Big Data.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Hudi Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Hudi Project be and hereby is responsible for the
> creation and maintenance of software related to providing atomic upserts
> and incremental data streams on Big Data; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Hudi" 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 Hudi Project, and to have
> primary responsibility for management of the projects within the scope of
> responsibility of the Apache Hudi 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 Hudi Project:
>
>  * Anbu Cheeralan   
>
>  * Balaji Varadarajan
>
>  * Bhavani Sudha Saktheeswaran   
>
>  * Luciano Resende 
>
>  * Nishith Agarwal
>
>  * Prasanna Rajaperumal
>
>  * Shaofeng Li   
>
>  * Steve Blackmon  
>
>  * Suneel Marthi  
>
>  * Thomas Weise
>
>  * Vino Yang   
>
>  * Vinoth Chandar
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Vinoth Chandar be appointed to
> the 

Re: [VOTE] Release Apache IoTDB 0.9.3

2020-05-12 Thread Willem Jiang
My +1 (binding)

I checked:

Download links are valid.
Checksums and PGP signatures are valid.
DISCLAIMER is included.
Checked the git tag.
No binary file in the source file.
I can build the source from scratch without any error.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Sun, May 10, 2020 at 3:21 PM 孙泽嵩  wrote:
>
> Hello all,
>
>
> This is a call for vote to release Apache IoTDB (Incubating) version 0.9.3.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an integrated 
> data management engine designed for timeseries data. It provides users with 
> services for data collection, storage and analysis.
> The Apache IoTDB community has voted on and approved a proposal to release
> Apache IoTDB (incubating) version 0.9.3.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> IoTDB community vote and result thread:
> Result: 
> https://lists.apache.org/thread.html/r1b1c8058fe2dcf7602b3d987b613cd0807abb53f86ad24f358f991a5%40%3Cdev.iotdb.apache.org%3E
> Vote: 
> https://lists.apache.org/thread.html/rfef4652594af3e3ba0561ebdd9e6fa8eaa549abbb2c7bf1d0c584da9%40%3Cdev.iotdb.apache.org%3E
>
> The release candidates (RC1):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.3/rc1/
>
> Git tag for the release (RC1):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.9.3
>
> Hash for the release tag:
> a704aa2cd6a61db57c5495f8b43849be876a1980
>
> Release Notes:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.3/rc1/RELEASE_NOTES.md
>
> The artifacts have been signed with Key : C336E0143A553B89, which can be
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
> From the PPMC Vote we carry over 1 binding IPMC Votes:
>
> +1 from Christofer Dutz
>
>
> The vote will be passed if there are at least 2 more IPMC +1 votes and no -1 
> vote.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> Best,
> ---
> Zesong Sun
> Apache IoTDB

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



Re: [VOTE] Release Apache IoTDB 0.9.2

2020-04-21 Thread Willem Jiang
+1.(Binding)
Download links are valid.
Checksums and PGP signatures are valid.
DISCLAIMER is included.
Checked the git tag.
No binary file in the source file.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Mon, Apr 20, 2020 at 10:37 PM Dawei Liu  wrote:
>
> Hello all,
>
>
> This is a call for vote to release Apache IoTDB (Incubating) version 0.9.2, 
> which is the first Apache Release for the IoTDB Project.
>
>
> The Apache IoTDB community has voted on and approved a proposal to release
> Apache IoTDB (Incubating) version 0.9.2.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an integrated 
> data management engine designed for timeseries data. It provides users with 
> services for data collection, storage and analysis.
>
>
> IoTDB community vote and result thread:
> Result: 
> https://lists.apache.org/thread.html/ra9efae1ec1ee6c89d58f86b16bb195b3e19f925183b4838379896e83%40%3Cdev.iotdb.apache.org%3E
> Vote: 
> https://lists.apache.org/thread.html/r9789da87ec813bcb8d0cb6e93451275f2d276685f7f059c457898fe3%40%3Cdev.iotdb.apache.org%3E
>
>
> The release candidates (RC2):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.2/rc2
>
>
> Git tag for the release (RC2):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.9.2
>
>
> Hash for the release tag:
> cf1bfb329bb6ac7c2dff0fe3de28404bacfac4aa
>
>
> Release Notes:
> https://github.com/apache/incubator-iotdb/blob/cf1bfb329bb6ac7c2dff0fe3de28404bacfac4aa/RELEASE_NOTES.md
>
>
> The artifacts have been signed with Key : EC80A08B232C50B2, which can be
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
>
> The vote will be open for at least 72 hours.
>
>
> From the PPMC Vote we carry over 3 binding IPMC Votes:
>
>
> +1 from Justin Mclean,
> +1 from Jialin Qiao,
> +1 from Xiangdong Huang
>
>
> The vote will be passed if there is no -1 vote ( as there are 3 IPMC +1 votes 
> already), but we still hope all other IPMCs vote for it.
>
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> Dawei Liu
> Apache IoTDB

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



Re: [VOTE] Release Apache Doris 0.12.0-incubating-rc03

2020-04-20 Thread Willem Jiang
+1.
I checked:
signatures and hash file are fine.
The git tag is OK.
License and Note are OK for me.
As Justin mentioned, there are some compiled files in webroot, it's
better to provide a script to download these js and css file
somewhere.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Apr 17, 2020 at 4:49 PM Li,Chaoyong  wrote:
>
> Hi all,
>
> Please review and vote on Apache Doris 0.12.0-incubating-rc03 release.
>
> Apache Doris is an MPP-based interactive SQL data warehousing for reporting 
> and analysis.
>
> The Apache Doris community has voted on and approved this release:
> https://lists.apache.org/thread.html/r7e87245e8e9af643e9cd5ba13a58b100b88043e7ba6a93f3e7a2abc2%40%3Cdev.doris.apache.org%3E
>
> The vote result email thread:
> https://lists.apache.org/thread.html/rc4852baaba81243c010f1626fe59997237ddbd528587553aca0b42a6%40%3Cdev.doris.apache.org%3E
>
> The release candidate has been tagged in GitHub as 0.12.0-rc03, available 
> here:
> https://github.com/apache/incubator-doris/releases/tag/0.12.0-rc03
>
> Thanks to everyone who has contributed to this release, and there is a simple 
> release notes can be found here:
> https://github.com/apache/incubator-doris/issues/2872
>
> The artifacts (source, signature and checksum) corresponding to this release 
> candidate can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.12.0-rc03/
>
>
> This has been signed with PGP key 9BDFF97E, corresponding to 
> lichaoy...@apache.org<mailto:lichaoy...@apache.org>.
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
>
> The vote will be open for at least 72 hours.
> [ ] +1 Approve the release
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> To verify and build, you can refer to following instruction:
>
> Firstly, you must be install and start docker service, and then you could 
> build Doris as following steps:
>
> Step1: Pull the docker image with Doris building environment
> $ docker pull apachedoris/doris-env:build-env-1.2
> You can check it by listing images, its size is about 3.28GB.
>
> Step2: Run the Docker image
> You can run image directly:
> $ docker run -it apachedoris/doris-dev:build-env-1.2
>
> Step3: Download Doris source
> Now you should in docker environment, and you can download Doris source 
> package.
> (If you have downloaded source and it is not in image, you can map its path 
> to image in Step2.)
> $ wget 
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.12.0-rc03/apache-doris-0.12.0-incubating-src.tar.gz
>
> Step4: Build Doris
> Now you can decompress and enter Doris source path and build Doris.
> $ tar zxvf apache-doris-0.12.0-incubating-src.tar.gz
> $ cd apache-doris-0.12.0-incubating-src
> $ sh build.sh
>
> Best Regards,
> Li Chaoyong
>
> 
> DISCLAIMER-WIP:
> Apache Doris is an effort undergoing incubation at The Apache Software 
> Foundation (ASF),
> sponsored by the Apache Incubator. Incubation is required of all newly 
> accepted projects
> until a further review indicates that the infrastructure, communications, and 
> decision
> making process have stabilized in a manner consistent with other successful 
> ASF projects.
> While incubation status is not necessarily a reflection of the completeness 
> or stability
> of the code, it does indicate that the project has yet to be fully endorsed 
> by the ASF.
>
> Some of the incubating project’s releases may not be fully compliant with ASF 
> policy. For
> example, releases may have incomplete or un-reviewed licensing conditions. 
> What follows is
> a list of known issues the project is currently aware of (note that this 
> list, by definition,
> is likely to be incomplete):
>
> * Releases may have incomplete licensing conditions
>
> If you are planning to incorporate this work into your product/project, 
> please be aware that
> you will need to conduct a thorough licensing review to determine the overall 
> implications of
> including this work. For the current status of this project through the 
> Apache Incubator
> visit: https://incubator.apache.org/projects/doris.html
>
>

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



Re: [VOTE] Release Apache ECharts (incubating) 4.7.0 (release candidate 1)

2020-03-17 Thread Willem Jiang
+1 (binding)
I checked:
- Download links are valid.
- Checksums and PGP signature are valid.
- DISCLAIMER file is included.
- Both LICENSE and NOTICE files are just fine.
- No binary file in the source.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Mar 6, 2020 at 5:12 AM SHUANG SU  wrote:
>
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.7.0 (release candidate 1).
>
> Apache ECharts community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/rba533eb56dea8181f3ce713487b715539d95bca6c96587797780b7ac%40%3Cdev.echarts.apache.org%3E
>
> Results thread:
> https://lists.apache.org/thread.html/r4f0cd4b49f4f7be86cf7f867b66762ae4584a859739c27401890f039%40%3Cdev.echarts.apache.org%3E
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.7.0-rc.1/
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> The Git commit for this release is:
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=4f3748d
>
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.7.0-rc.1/RELEASE_NOTE.txt
>
> Build Guide:
> https://github.com/apache/incubator-echarts/blob/4.7.0-rc.1/README.md#build
>
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.7.0 (release candidate 1)
> by "2020-03-08T22:09:56.629Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
>
> Thanks,
> --
>  Su Shuang (100pah)
> --

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



Re: [VOTE] Graduate Apache ShardingSphere (incubating)

2020-03-14 Thread Willem Jiang
+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Mar 14, 2020 at 1:30 AM zhangli...@apache.org
 wrote:
>
> Hi!
>
> We've got positive feedback on the DISCUSS thread, I'd like to start an
> official VOTE thread now.
>
> Please vote on the resolution pasted below to graduate Apache
> ShardingSphere from the incubator to the Top Level Project.
>
> [ ] +1 Graduate Apache ShardingSphere from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache ShardingSphere from the Incubator because ...
>
> This vote will open for at least 72 hours.
>
> Many thanks to our mentors and everyone else for their support.
>
> ---
>
> Establish the Apache ShardingSphere Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to Apache ShardingSphere is an ecosystem consisted of a set of
> distributed database middleware solutions, including 2 independent
> products, Sharding-JDBC, Sharding-Proxy. They all provide functions of
> data sharding, distributed transaction, database and data governance,
> applicable in a variety of situations such as Java isomorphism and
> heterogeneous language..
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache ShardingSphere Project", be and hereby
> is established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache ShardingSphere Project be and hereby is
> responsible for the creation and maintenance of software related to
> Apache ShardingSphere is an ecosystem consisted of a set of distributed
> database middleware solutions, including 2 independent products,
> Sharding-JDBC, Sharding-Proxy. They all provide functions of data
> sharding, distributed transaction, database and data governance,
> applicable in a variety of situations such as Java isomorphism and
> heterogeneous language.; and be it further
>
> RESOLVED, that the office of "Vice President, Apache ShardingSphere" 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
> ShardingSphere Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of the
> Apache ShardingSphere 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 ShardingSphere
> Project:
>
>  * Craig L Russell   
>  * Hao Cao   
>  * Hongjun Du
>  * Hongtao Gao   
>  * Juan Pan  
>  * Jun Zhao  
>  * Liang Zhang   
>  * QingYang Chen 
>  * Sheng Wu  
>  * Von Gosling   
>  * Willem Ning Jiang 
>  * Xiaoguang Ma  
>  * Yang Yi   
>  * Yonglun Zhang 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Liang Zhang be appointed to
> the office of Vice President, Apache ShardingSphere, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache ShardingSphere Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> ShardingSphere podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> ShardingSphere podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
> --
>
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo

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



Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP

2020-03-12 Thread Willem Jiang
It good to see ShardingSphere is ready to graduate.
My +1 for this proposal.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Mar 9, 2020 at 10:14 PM zhangli...@apache.org
 wrote:
>
> Hi!
>
> After an enthusiastic discussion with the community[1], finally positive
> vote result[2].
>
> We'd like to bring this to a discussing at the IPMC.
>
> Please see the proposed resolution below and let us know what do you think.
>
> A few status to help with the discussion:
>
> - There are 1301 emails sent by 159 people in dev mailing-list excepted
> GitBox forwarded;
> - 2539 Issues created during ASF incubating, 2468 Issues resolved during
> ASF incubating;
> - 1073 PRs created during ASF incubating, 918 PRs merged during ASF
> incubating;
> - There are 89 contributors for now;
> - There are 4 versions released successfully conformant to Apache release
> policy by 3 release managers;
> - There are 2 new PPMCs and 8 new committers were invited to join the
> community.
>
> We had already finished the Podling Maturity Assessment for
> ShardingSphere[3], the 34 items are all passed.
>
> We had resolved all branding issues which include Logo, GitHub repo,
> document, website and DockerHub image.
>
> [1]
> https://lists.apache.org/thread.html/rf6a2cec7143395ac0126dcb13f331fbc87b680eaca015d50d7793172%40%3Cdev.shardingsphere.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/rc46c2869cd87f4d92c1322f0e008fc294980e1470443265d98529e66%40%3Cdev.shardingsphere.apache.org%3E
> [3] https://github.com/apache/incubator-shardingsphere/blob/dev/MATURITY.md
>
>
> 
>
> Establish the Apache ShardingSphere Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to Apache ShardingSphere is an ecosystem consisted of a set of
> distributed database middleware solutions, including 2 independent
> products, Sharding-JDBC, Sharding-Proxy. They all provide functions of
> data sharding, distributed transaction, database and data governance,
> applicable in a variety of situations such as Java isomorphism and
> heterogeneous language..
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache ShardingSphere Project", be and hereby
> is established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache ShardingSphere Project be and hereby is
> responsible for the creation and maintenance of software related to
> Apache ShardingSphere is an ecosystem consisted of a set of distributed
> database middleware solutions, including 2 independent products,
> Sharding-JDBC, Sharding-Proxy. They all provide functions of data
> sharding, distributed transaction, database and data governance,
> applicable in a variety of situations such as Java isomorphism and
> heterogeneous language.; and be it further
>
> RESOLVED, that the office of "Vice President, Apache ShardingSphere" 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
> ShardingSphere Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of the
> Apache ShardingSphere 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 ShardingSphere
> Project:
>
>  * Craig L Russell   
>  * Hao Cao   
>  * Hongjun Du
>  * Hongtao Gao   
>  * Juan Pan  
>  * Jun Zhao  
>  * Liang Zhang   
>  * QingYang Chen 
>  * Sheng Wu  
>  * Von Gosling   
>  * Willem Ning Jiang 
>  * Xiaoguang Ma  
>  * Yang Yi   
>  * Yonglun Zhang 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Liang Zhang be appointed to
> the office of Vice President, Apache ShardingSphere, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache ShardingSphere Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> ShardingSphere podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> ShardingSphere p

Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.1

2020-03-08 Thread Willem Jiang
Carry my vote +1 to IPMC.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Mar 5, 2020 at 1:07 PM zhaojun  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache ShardingSphere (Incubating) version 
> 4.0.1.
>
> The Apache ShardingSphere community has voted on and approved a proposal to 
> release
> Apache ShardingSphere (Incubating) version 4.0.1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> ShardingSphere is an open-source ecosystem consisted of a set of distributed 
> database middleware solutions, including 2 independent products, 
> Sharding-JDBC & Sharding-Proxy.
> They both provide functions of data sharding, distributed transaction and 
> database orchestration, applicable in a variety of situations such as Java 
> isomorphism, heterogeneous language.
> Aiming at reasonably making full use of the computation and storage capacity 
> of the database in a distributed system, ShardingSphere defines itself as a 
> middleware, rather than a totally new type of database.
> As the cornerstone of many enterprises, relational database still takes a 
> huge market share.
> Therefore, at the current stage, we prefer to focus on its increment instead 
> of a total overturn.
>
> Sharding-JDBC defines itself as a lightweight Java framework that provides 
> extra service at Java JDBC layer.
> With the client end connecting directly to the database, it provides service 
> in the form of jar and requires no extra deployment and dependence.
> It can be considered as an enhanced JDBC driver, which is fully compatible 
> with JDBC and all kinds of ORM frameworks.
>
> * Applicable in any ORM framework based on Java, such as JPA, Hibernate, 
> Mybatis, Spring JDBC Template or direct use of JDBC.
> * Based on any third-party database connection pool, such as DBCP, C3P0, 
> BoneCP, Druid, HikariCP.
> * Support any kind of database that conforms to JDBC standard: MySQL, Oracle, 
> SQLServer and PostgreSQL for now.
>
> Sharding-Proxy defines itself as a transparent database proxy, providing a 
> database server that encapsulates database binary protocol to support 
> heterogeneous languages.
> Friendlier to DBA, the MySQL/PostgreSQL version provided now can use any kind 
> of terminal (such as MySQL Command Client, MySQL Workbench, Navicat etc.) 
> that is compatible of MySQL/PostgreSQL protocol to operate data.
>
> * Totally transparent to applications, it can be used directly as MySQL and 
> PostgreSQL.
>
> * Applicable to any kind of terminal that is compatible with MySQL and 
> PostgreSQL protocol.
>
> ShardingSphere community vote and result thread:
> https://lists.apache.org/thread.html/r7f19ccb6a01ad39d75481ee8eebaccb7a90b9414f0cc078ddca6adea%40%3Cdev.shardingsphere.apache.org%3E
>
> Release notes:
> https://github.com/apache/incubator-shardingsphere/blob/dev-4.x/RELEASE-NOTES.md
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.1/
>
> Maven 2 staging repository:
> https://repository.apache.org/content/repositories/orgapacheshardingsphere-1047/org/apache/shardingsphere/
>
> Git tag for the release:
> https://github.com/apache/incubator-shardingsphere/tree/4.0.1/
>
> Release Commit ID:
> https://github.com/apache/incubator-shardingsphere/commit/b67d320209b4d4585231b356f2c575cfa383a98b
>
> Keys to verify the Release Candidate, public key is ED4872D5B97BBB65
> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS
>
> Look at here for how to verify this release candidate:
> https://shardingsphere.apache.org/community/en/contribute/release/
>
> 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
>
> Checklist for reference:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code distributions have correct names matching the current release.
>
> [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo.
>
> [ ] All files have license headers if necessary.
>
> [ ] No compiled archives bundled in source archive.
>
> The following votes are carried over from ShardingSphere dev mailing list,
>
> +1 binding, Craig Russell
> +1 binding, Willem Jiang
>
> +1 non-binding, Yi Yang
> +1 non-binding, Liang Zhang
> +1 non-binding, Juan Pan
> +1 non-binding, kimmking
> +1 non-binding, Guangyuan Wang
> +1 non-binding, Zonglei Dong
>
> --
> Zhao Jun (cherrylzhao)
> Apache ShardingSphere

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

2020-02-27 Thread Willem Jiang
+1.

I checked
- Download links are valid.
- Checksums and PGP signature are valid.
- DISCLAIMER file is included.
- Both LICENSE and NOTICE files are just fine, there is an known issue(#1045).
- No binary file.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Feb 12, 2020 at 9:19 PM tan zhongyi  wrote:
>
> Hi, guys,
>
> I am pleased to be calling this vote for the release of Apache brpc 
> (incubating) 0.9.7-rc03
> (it goes to vote in incubator mail list at last.)
>
> BTW: there is still some license issues to be fixed, so we add  
> DISCLAIMER-WIP there, we will fix them in later releases.
>
> Apache brpc community has voted and approved the release.
>
> Vote thread: 
> https://lists.apache.org/thread.html/r383eb48e113c1da48505bf983a11c4bb0b5faaf6a9293e25237734a6%40%3Cdev.brpc.apache.org%3E
>
> Results thread: 
> https://lists.apache.org/thread.html/r13103b44566f3c39e0a935681a9035435c466a0b9cb344edf407c168%40%3Cdev.brpc.apache.org%3E
>
> The release candidate to be voted over is available at:
>
>  
> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc03/apache-brpc-0.9.7.rc03-incubating-src.tar.gz
>
>
> The SHA-512 checksum is:
> 3852185929f8b242aacef5601acb85ab4b397584c515813f740effb1a9eabdba43eaccbe4b5eb1e6763f672fbb4a7937fe71a0dc4a240ef8891d413f30e9b257
>
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc03/apache-brpc-0.9.7.rc03-incubating-src.tar.gz.sha512
>
> The signature can be found via:
>  
> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc03/apache-brpc-0.9.7.rc03-incubating-src.tar.gz.asc
>
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS
>
> Please vote on releasing this package as:
> Apache brpc (incubating) 0.9.7-rc03
> by "2020-02-17 T23:59:00.00Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
>
>
>

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



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

2020-02-22 Thread Willem Jiang
Please create an issue to check this problem.
We need to address it in the next release.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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

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



Re: [VOTE] Release Apache APISIX (Incubating) 1.1-RC1

2020-02-22 Thread Willem Jiang
+1 (binding)
I checked
- Download links are valid.
- Checksums and PGP signature are valid.
- DISCLAIMER file is included.
- Both LICENSE and NOTICE files are good.
- No binary file.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Fri, Feb 21, 2020 at 11:15 AM junxu chen  wrote:
>
> Hello, Community,
>
> This is a call for the vote to release Apache APISIX (Incubating) version
> 1.1-RC1.
>
> The Apache APISIX community has voted on and approved a proposal to release
> Apache APISIX (Incubating) based on 1.1-RC1.
>
> Here is the Apache APISIX community vote result:
>
>
> 6 PPMC +1 votes:
> - Yuansheng Wang
> - agile6v
> - Ming Wen
> - Lang Wang
> - Linsir Wu
> - Li Ling
>
>
> 1 mentor +1 vote:
> - Justin Mclean
>
>
> 1  community +1 vote:
> - doggieと杨
>
>
> We now kindly request the other Incubator IPMC members to review and vote
> for this incubator release.
>
>
> Apache APISIX community vote and result threads:
>
> https://lists.apache.org/thread.html/r97d9450c5ec695bb292d1d8119d639494d24ed57c93b63ca6a1b5d24%40%3Cdev.apisix.apache.org%3E
>
>
>
> Release notes:
>
> https://github.com/apache/incubator-apisix/blob/v1.1/CHANGELOG.md#110
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.1-rc1/
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-apisix/tree/v1.1
>
>
> Release Commit ID:
>
> https://github.com/apache/incubator-apisix/commit/3c57401d76ee32bc84c1ceb568e6c7ae1cef41a0
>
>
> Keys to verify the Release Candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
>
>
> Steps to validating the release:
>
> 1. Download the release
>
> ```
>
> wget
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.1-rc1/apache-apisix-1.1-rc1-incubating-src.tar.gz
>
> ```
>
>
> 2. Checksums and signatures
>
> ```
>
> wget https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
>
> wget
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.1-rc1/apache-apisix-1.1-rc1-incubating-src.tar.gz.asc
>
> wget
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.1-rc1/apache-apisix-1.1-rc1-incubating-src.tar.gz.sha512
>
>
> shasum -c apache-apisix-1.1-rc1-incubating-src.tar.gz.sha512
>
>
> gpg --import KEYS
>
> # input `trust`, `5`, then `save`
>
> gpg --edit-key "Junxu Chen"
>
> gpg --verify apache-apisix-1.1-rc1-incubating-src.tar.gz.asc
> apache-apisix-1.1-rc1-incubating-src.tar.gz
>
> ```
>
>
> 3. Unzip and Check files
>
> ```
>
> tar zxvf apache-apisix-1.1-rc1-incubating-src.tar.gz
>
> ```
>
>
> 4. Build Apache APISIX:
>
> https://github.com/apache/incubator-apisix/blob/v1.1/doc/how-to-build.md
>
>
> 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
>
>
> Checklist for reference:
>
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] LICENSE and NOTICE files are good.
>
> [ ] No binary file.
>
> [ ] All files have license headers if necessary.
>
>
>
> And below is a more detailed checklist:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
>
>
> Thanks!

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



Re: [VOTE] Release Apache APISIX Dashboard (Incubating) 1.0-RC2

2020-02-22 Thread Willem Jiang
Carry my +1 from dev@apisix here.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Feb 20, 2020 at 11:35 PM Zhiyuan Ju  wrote:
>
> Hi everyone,
>
> This is a call for the vote to release Apache APISIX Dashboard (Incubating)
> based on 1.0-RC2.
>
> The Apache APISIX community has voted on and approved a proposal to release
> Apache APISIX Dashboard (Incubating) based on 1.0-RC2, 6 votes from PPMC,
> and 2 votes from IPMC already.
>
> PPMC:
> - Ming Wen
> - Li Ling
> - Yuansheng Wang
> - agile6v
> - Lang Wang
> - Linsir Wu
>
> IPMC:
> - Justin
> - Willem Jiang
>
> We now kindly request the other Incubator IPMC members to review and vote
> for this incubator release.
>
> Apache APISIX community vote and result threads:
>
> https://lists.apache.org/thread.html/r8c37b3a99bc3819c92b838ca90a4cd3b0b4ce1c87feaf91aa1c1e751%40%3Cdev.apisix.apache.org%3E
>
> Release notes:
>
> https://github.com/apache/incubator-apisix-dashboard
> /blob/v1.0/CHANGELOG.md#100
>
> Release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/apisix/dashboard-1.0-rc2/
>
> Git tree for the release:
>
> https://github.com/apache/incubator-apisix-dashboard/tree/v1.0
>
> Release commit id:
>
> https://github.com/apache/incubator-apisix-dashboard
> /commit/813142e202d5f90135c9aa16b7fa60be83e8d5e6
>
> Keys to verify the release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
>
> Steps to validate the release:
>
> 1. Download the release:
>
> $ wget https://dist.apache.org/repos/dist/dev/incubator/apisix/dashboard
> -1.0-rc2/apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz
>
> 2. Checksum and verify signature:
>
> $ wget https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
>
> $ wget https://dist.apache.org/repos/dist/dev/incubator/apisix/dashboard
> -1.0-rc2/apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz.asc
>
> $ wget https://dist.apache.org/repos/dist/dev/incubator/apisix/dashboard
> -1.0-rc2/apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz.sha512
>
> $ shasum -c apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz.sha512
>
> $ gpg --import KEYS
>
> $ gpg --edit-key juzhiyuan
>
> $ Input *trust* and press return button
>
> $ Input *5* and press return button
>
> $ Input *y* and press return button
>
> $ gpg --verify apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz.asc
> apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz
>
> 3. Unzip and check files
>
> $ tar zxvf apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz
>
> $ cd apache-apisix-dashboard-1.0-incubating
>
> 4. Build the Apache APISIX Dashboard
> 4.1 Make sure both Node.js 8.12.0+ and yarn are installed on your machine.
> 4.2 $ yarn
> 4.3 $ yarn build:prod
> 4.4 copy all files under /dist directory to your APISIX's /dashboard
>  directory.
> 4.5 Open browser and visit http://127.0.0.1:9080/apisix/dashboard/
> 4.6 More detailed documentation: https://github.com/apache/incubator-apisix#
> dashboard
>
> This vote will last for at least 72 hours or necessary number of votes are
> reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with your reason
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and PGP signature are valid.
> [ ] DISCLAIMER file is included.
> [ ] Both LICENSE and NOTICE files are good.
> [ ] No binary file.
> [ ] All files have valid License header if necessary.
>
> The following link is a more detailed checklist for reference:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Best Regards!
> @ Zhiyuan Ju <https://www.shaoyaoju.org/>

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



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

2020-02-19 Thread Willem Jiang
Hi Gosling,

Could you share more detail for the third party dependencies license issue?
We need to look into the library for the license issue.
>From my understanding, for the CDDL license and LGPL license
dependencies, if we don't modify the code, it should be fine.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Feb 18, 2020 at 2:09 PM Gosling Von  wrote:
>
> Hi
>
> Some reasonable feedback from the Justin since last 0.9.7-rc2 version:
> - the artefact names must include "incubating “ but this can be easily fixed 
> and the voting doesn’t need to restarted (if this was the only issue)
> - but it also contains category B code [2] under the CDDL license.
> - and it also contains category X code [9] under the GPL license.
>
> AFAIK, for many c++ projects, license issues are usual a blocker for their 
> first release in Apache Podling, I've seen a lot of efforts from brpc 
> community to fix the problem as the mentor's suggestions. This is a public, 
> inclusive and impressive process. In addition to category B license 
> problem(committers are making their best effort to evaluate and remove it), 
> other problems have been solved accordingly.
>
> So, kindly request more voice from the incubator community and help brpc to 
> boost its release.
>
>
> Best Regards,
> Von Gosling
>
> > On Feb 12, 2020, at 9:18 PM, tan zhongyi  wrote:
> >
> > Hi, guys,
> >
> > I am pleased to be calling this vote for the release of Apache brpc 
> > (incubating) 0.9.7-rc03
> > (it goes to vote in incubator mail list at last.)
> >
> > BTW: there is still some license issues to be fixed, so we add  
> > DISCLAIMER-WIP there, we will fix them in later releases.
> >
> > Apache brpc community has voted and approved the release.
> >
> > Vote thread: 
> > https://lists.apache.org/thread.html/r383eb48e113c1da48505bf983a11c4bb0b5faaf6a9293e25237734a6%40%3Cdev.brpc.apache.org%3E
> >
> > Results thread: 
> > https://lists.apache.org/thread.html/r13103b44566f3c39e0a935681a9035435c466a0b9cb344edf407c168%40%3Cdev.brpc.apache.org%3E
> >
> > The release candidate to be voted over is available at:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc03/apache-brpc-0.9.7.rc03-incubating-src.tar.gz
> >
> >
> > The SHA-512 checksum is:
> > 3852185929f8b242aacef5601acb85ab4b397584c515813f740effb1a9eabdba43eaccbe4b5eb1e6763f672fbb4a7937fe71a0dc4a240ef8891d413f30e9b257
> >
> > which can be found via:
> > https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc03/apache-brpc-0.9.7.rc03-incubating-src.tar.gz.sha512
> >
> > The signature can be found via:
> > https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc03/apache-brpc-0.9.7.rc03-incubating-src.tar.gz.asc
> >
> > KEYS file is available here:
> > https://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS
> >
> > Please vote on releasing this package as:
> > Apache brpc (incubating) 0.9.7-rc03
> > by "2020-02-17 T23:59:00.00Z".
> >
> > [ ] +1 Release this package
> > [ ] 0 I don't feel strongly about it, but don't object
> > [ ] -1 Do not release this package because...
> >
> > Anyone can participate in testing and voting, not just committers, please
> > feel free to try out the release candidate and provide your votes.
> >
> > A checklist for reference:
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> >
> >
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: [VOTE] Release Apache IoTDB 0.9.1

2020-01-06 Thread Willem Jiang
+1(binding)

I checked
Download links are valid, git tag is OK.
The kits have incubating in the name.
Checksums and PGP signatures are valid.
DISCLAIMER is included.
LICENSE and NOTICE files are good.
There is a incubating in the kits name.
No binary file in the source kit.
I can build the kits from source kit.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Fri, Jan 3, 2020 at 1:09 PM Lei Rui  wrote:
>
> Hi all,
>
>
> This is a call for vote to release Apache IoTDB (Incubating) version 0.9.1.
>
>
> The Apache IoTDB community has voted on and approved a proposal to release
> Apache IoTDB (Incubating) version 0.9.1.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an integrated 
> data management engine designed for timeseries data. It provides users with 
> services for data collection, storage and analysis.
>
>
> IoTDB community vote and result thread:
> Result: 
> https://lists.apache.org/thread.html/2b8ffe042d340001f0f5d7aeb16cb068ddc7b9141a8dd1401283e7cd%40%3Cdev.iotdb.apache.org%3E
> Vote: 
> https://lists.apache.org/thread.html/ee976b92c2a425a3172b840980a59eb2c4dd4361be7c198489010b49%40%3Cdev.iotdb.apache.org%3E
>
>
> The release candidates (RC1):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.1/rc1
>
>
> Git tag for the release (RC1):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.9.1
>
>
> Hash for the release tag:
> d665690607933db9fdac057ebe250c19c9f63974
>
>
> Release Notes:
> https://github.com/apache/incubator-iotdb/blob/release/0.9.1/RELEASE_NOTES.md
>
>
> The artifacts have been signed with Key: 28662AC6, which can be found in the 
> keys file:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
>
> The vote will be open for at least 72 hours.
>
>
> From the PPMC vote, we carry over 1 binding IPMC vote:
> +1 from Justin Mclean
>
>
> A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
> required to pass.
>
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> Lei Rui
> Apache IoTDB
>

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



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

2020-01-01 Thread Willem Jiang
+1 (binding)

I checked
Download links are valid, git tag is OK.
Checksums and PGP signatures are valid.
DISCLAIMER is included.
LICENSE and NOTICE files are good.
No binary file in the source kit.
I can build the kit from source kit.

It take me some time to find out how to build the source here[1].
Please add the build section in the README.md file.

[1]https://github.com/apache/incubator-brpc/blob/master/docs/cn/getting_started.md#macos

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Dec 25, 2019 at 10:23 PM tan zhongyi  wrote:
>
> Hi, guys,
>
> I am pleased to be calling this vote for the release of Apache brpc 
> (incubating) 0.9.7-rc02
> (it goes to vote in incubator mail list at last.)
>
> Apache brpc community has voted and approved the release.
>
> Vote thread: 
> https://lists.apache.org/thread.html/0d1c8ea0d057033c05a6198920fa03e8a0bda8329682754dc969e025%40%3Cdev.brpc.apache.org%3E
>
> Results thread: 
> https://lists.apache.org/thread.html/8c39a192ffb2efeaee9cc3ba38ab9a8222705391b3d9bfabc92c22e8%40%3Cdev.brpc.apache.org%3E
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc02/incubator-brpc-0.9.7-rc02.tar.gz
>
> The SHA-512 checksum is:
> ec57b40641734dad8f2ab9629b75a658ef35da5248b1bef8af17298f2722f18106f48d1a4bf2a4f98b2a23d9fa0c727f95863ae762ddb4c67cb02a8848ee0851
>
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc02/incubator-brpc-0.9.7-rc02.tar.gz.sha512
>
> The signature can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc02/incubator-brpc-0.9.7-rc02.tar.gz.asc
>
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS
>
> Please vote on releasing this package as:
> Apache brpc (incubating) 0.9.7-rc02
> by "2019-12-31 T23:59:00.00Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
>
> From the votes on the dev mailing list we carry over 1 binding IPMC vote
> +1 from Gosling Von(binding)
>
>
> Thanks.
>

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



Re: [VOTE] Release Apache ECharts (incubating) 4.6.0 (release candidate 1)

2019-12-24 Thread Willem Jiang
+1 (binding)

I checked below items:
Download links are valid, git tag is OK.
There are incubating in the release kit.
Checksums and PGP signatures are valid.
DISCLAIMER is included.
LICENSE and NOTICE files are good.
No binary file in the source kit.
I can build the kit from source kit.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Fri, Dec 20, 2019 at 1:52 PM SHUANG SU  wrote:
>
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.6.0 (release candidate 1).
>
> Apache ECharts community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/8007897bcd0e1bb6832dc8ac41a5e5a2271ec62e63dc079d1cd52e1d%40%3Cdev.echarts.apache.org%3E
>
> Results thread:
> https://lists.apache.org/thread.html/4e90092b68ff74abf513f1da6832439e663584dd0f7f4c9d8e0615ac%40%3Cdev.echarts.apache.org%3E
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.6.0-rc.1/
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> The Git commit for this release is:
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=f4fc1b0
>
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.6.0-rc.1/RELEASE_NOTE.txt
>
> Build Guide:
> https://github.com/apache/incubator-echarts/blob/4.6.0-rc.1/README.md#build
>
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.6.0 (release candidate 1)
> by "2019-12-23T06:47:52.393Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
>
> From the votes on the dev mailing list we carry over 1 binding IPMC vote
> +1 from Wu Sheng (binding)
>
>
>
> Thanks,
> --
>  Su Shuang (100pah)
> --

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



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

2019-12-11 Thread Willem Jiang
+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Dec 8, 2019 at 5:55 AM Gian Merlino  wrote:
>
> Earlier this year, Druid voted to graduate to a top level project. The vote
> passed in the Druid community and the Incubator, and a resolution was
> submitted to the Board, but needed to be shelved at the last minute. We are
> now ready to proceed to graduation once again, and so I would like to call
> another vote. The Druid project has re-voted and has notified the Board of
> these developments. We now seek consent from the Incubator community to
> propose a graduation resolution for the Dec 18 board meeting.
>
> The proposed graduation resolution is nearly the same as last time; the
> only changes are the addition of four new initial members (fokko, furkan,
> qmm, and vogievetsky).
>
> For reference,
>
> 1) The Druid vote that was just held:
> https://lists.apache.org/thread.html/3b1432780b8d841fffce3033cd5cc39fe1fe0f46feccb96f036dbf01%40%3Cdev.druid.apache.org%3E
>
> 2) Our prior Incubator graduation vote, which passed earlier this year:
> https://lists.apache.org/thread.html/19b703fdf192ddf8e31bda57264e03113c7e44b5954a56886e05@%3Cgeneral.incubator.apache.org%3E
>
> Please take a minute to vote on whether or not Apache Druid should graduate
> to a Top Level Project by responding with one of the following:
>
> [ ] +1 Apache Druid should graduate
> [ ]  0 No opinion
> [ ] -1 Apache Druid should not graduate because...
>
> The VOTE is open for a minimum of 72 hours.
>
> ---
>
> Establish Apache Druid 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 analytical database
> software, for distribution at no charge to the public.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "The Apache Druid Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that The Apache Druid Project be and hereby is
> responsible for the creation and maintenance of an analytical
> database software project; and be it further
>
> RESOLVED, that the office of "Vice President, Druid" 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
> Druid Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of
> The Apache Druid 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 Druid Project:
>
>   * Benedict Jin (asdf2...@apache.org)
>   * Charles Allen(cral...@apache.org)
>   * Clint Wylie  (cwy...@apache.org)
>   * David Lim(david...@apache.org)
>   * Dylan Wylie  (dylanwy...@apache.org)
>   * Eric Tschetter   (ched...@apache.org)
>   * Fangjin Yang (f...@apache.org)
>   * Fokko Driesprong (fo...@apache.org)
>   * Furkan Kamaci(kam...@apache.org)
>   * Gian Merlino (g...@apache.org)
>   * Himanshu Gupta   (himans...@apache.org)
>   * Jihoon Son   (jihoon...@apache.org)
>   * Jonathan Wei (jon...@apache.org)
>   * Julian Hyde  (jh...@apache.org)
>   * Kurt Young   (k...@apache.org)
>   * Lijin Bin(binli...@apache.org)
>   * Maxime Beauchemin(maximebeauche...@apache.org)
>   * Mingming Qiu (q...@apache.org)
>   * Niketh Sabbineni (nik...@apache.org)
>   * Nishant Bangarwa (nish...@apache.org)
>   * P. Taylor Goetz  (ptgo...@apache.org)
>   * Parag Jain   (pja...@apache.org)
>   * Roman Leventov   (leven...@apache.org)
>   * Slim Bouguerra   (bs...@apache.org)
>   * Surekha Saharan  (sure...@apache.org)
>   * Xavier Léauté(x...@apache.org)
>   * Vadim Ogievetsky (vogievet...@apache.org)
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gian Merlino
> be and hereby is appointed to the office of Vice President,
> Druid, 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 Druid Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Druid podling; and be it further
>
> RESOLVED, th

Re: [Vote] Release Apache IoTDB 0.8.2

2019-12-11 Thread Willem Jiang
+1 (binding)

I checked
- Incubating in the name of source and binary kit
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- No unexpected binary files
- Checked PGP signatures
- Checked Checksums
- Build the source without any issue

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Dec 8, 2019 at 10:10 PM Xiangdong Huang  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version 0.8.2,
> which is a bug fix version of 0.8.1.
>
> The Apache IoTDB community has voted on and approved a proposal to release
> Apache IoTDB (Incubating) version 0.8.2.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an
> integrated data management engine designed for timeseries data. It provides
> users with services for data collection, storage and analysis.
>
> IoTDB community vote and result thread:
> Result:
> https://lists.apache.org/thread.html/918d52d0fd306aa92b9ad3f0510611e73dc843d65c6747bd28c6a143%40%3Cdev.iotdb.apache.org%3E
> Vote:
> https://lists.apache.org/thread.html/dadba801d3e72b97d997d17470bcf98bdfd217cde14434c8db847ca4%40%3Cdev.iotdb.apache.org%3E
>
> The release candidates (RC2):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.2/rc2
>
> Git tag for the release (RC2):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.2
>
> Hash for the release tag:
> 09a94f2c02dec27f483a2ccb41a8265331be193d
>
> Release Notes:
> https://github.com/apache/incubator-iotdb/blob/release/0.8.2/RELEASE_NOTES.md
>
> The artifacts have been signed with Key : 2206EF8F64C35889, which can be
>
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
>
> From the PPMC Vote we carry over 1 binding IPMC Votes:
>
> +1 from Justin Mclean
>
> The vote will be passed if there is more than 2 +1 votes (except for Justin
> Mclean)  and no -1 votes.
>
> Look forward to all IPMCs' vote for it.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Yours Sincerely,
> Xiangdong Huang
> Apache IoTDB (incubating)

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



Re: [VOTE] Release Apache IoTDB 0.9.0

2019-11-27 Thread Willem Jiang
+1 (binding)

I checked below items:
Download links are valid.
There are incubating in the release kit.
Checksums and PGP signatures are valid.
DISCLAIMER is included.
LICENSE and NOTICE files are good.
No binary file in the source kit.
All files have license headers if necessary.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Wed, Nov 27, 2019 at 3:48 PM Jialin Qiao  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version 0.9.0, a
> major version with many exciting features.
>
> The Apache IoTDB community has voted on and approved a proposal to
> release Apache
> IoTDB (Incubating) version 0.9.0.
>
> We now kindly request the Incubator PMC members review and vote on
> this incubator
> release.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an
> integrated data management engine designed for time series data. It
> provides users with services for data collection, storage and analysis.
>
> IoTDB community vote and result thread:
> Result:
> https://lists.apache.org/thread.html/ebf6b2b4f435868a14e89fa3a767f99a0db71f4e22a7acc9a7b5b22b@%3Cdev.iotdb.apache.org%3E
> Vote:
> https://lists.apache.org/thread.html/ddcdc40e74e7592dd9efe190ef96cc62cf0b07d9e0aa4e7f0d6e7577@%3Cdev.iotdb.apache.org%3E
>
> The release candidates (RC5):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.0/rc5
>
> Git tag for the release (RC5):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.9.0
> <https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.0>
>
> Hash for the release tag:
> 257df94d57c29c628b1ab0d6a2fdd20ba7df9ca4
>
> Release Notes:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.0/rc5/RELEASE_NOTES.md
>
> The artifacts have been signed with Key: 0FC7F131CAA00430, which can
> be found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
> A minimum of 3 IPMC +1 votes and more binding +1 than binding -1 are
> required to pass the vote.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Jialin Qiao
> Apache IoTDB

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



Re: [VOTE] Accept StreamPipes into the Apache Incubator

2019-11-08 Thread Willem Jiang
+1 (binding), good luck!

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Nov 8, 2019 at 3:00 AM Dominik Riemer  wrote:
>
> Hi all,
>
> following up the [DISCUSS] thread on StreamPipes 
> (https://lists.apache.org/thread.html/1cf79ef65888f695b4b925fd67ef8a2b845f6b0931c251a0ff1115e1@%3Cgeneral.incubator.apache.org%3E),
>  I would like to call a VOTE to accept StreamPipes into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring StreamPipes into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring StreamPipes into the Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator 
> PMC are binding, but votes from everyone are welcome.
>
> Dominik
>
> 
> StreamPipes Proposal 
> (https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPipesProposal)
>
> == Abstract ==
> StreamPipes is a self-service (Industrial) IoT toolbox to enable 
> non-technical users to connect, analyze and explore (Industrial) IoT data 
> streams.
>
> = Proposal =
>
> The goal of StreamPipes (www.streampipes.org) is to provide an easy-to-use 
> toolbox for non-technical users, e.g., domain experts, to exploit data 
> streams coming from (Industrial) IoT devices. Such users are provided with an 
> intuitive graphical user interface with the Pipeline Editor at its core. 
> Users are able to graphically model processing pipelines based on data 
> sources (streams), data processors and data sinks. Data processors and sinks 
> are self-contained microservices, which implement either stateful or 
> stateless processing logic (e.g., a trend detection or image classifier). 
> Their processing logic is implemented using one of several provided wrappers 
> (we currently have wrappers for standalone/Edge-based processing, Apache 
> Flink, Siddhi and working wrapper prototypes for Apache Kafka Streams and 
> Spark, in the future we also plan to integrate with Apache Beam). An SDK 
> allows to easily create new pipeline elements. Pipeline elements can be 
> installed at runtime. To support users in creating pipelines, an underlying 
> semantics-based data model enables pipeline elements to express requirements 
> on incoming data streams that need to be fulfilled, thus reducing modeling 
> errors.
> Data streams are integrated by using StreamPipes Connect, which allows to 
> connect data sources (based on standard protocols, such as MQTT, Kafka, 
> Pulsar, OPC-UA and further PLC4X-supported protocols) without further 
> programming using a graphical wizard. Additional user-faced modules of 
> StreamPipes are a Live dashboard to quickly explore IoT data streams and a 
> wizard that generates code templates for new pipeline elements, a Pipeline 
> Element Installer used to extend the algorithm feature set at runtime.
>
> === Background ===
> StreamPipes was started in 2014 by researchers from FZI Research Center for 
> Information Technology in Karlsruhe, Germany. The original prototype was 
> funded by an EU project centered around predictive analytics for the 
> manufacturing domain. Since then, StreamPipes was constantly improved and 
> extended by public funding mainly from federal German ministries. In early 
> 2018, the source code was officially released under the Apache License 2.0. 
> At the same time, while we focused on bringing the research prototype to a 
> production-grade tool, the first companies started to use StreamPipes. 
> Currently, the primary goal is to widen the user and developer base. At 
> ApacheCon NA 2019, after having talked to many people from the Apache 
> Community, we finally decided that we would like to bring StreamPipes to the 
> Apache Incubator.
>
> === Rationale ===
> The (Industrial) IoT domain is a highly relevant and emerging sector. 
> Currently, IoT platforms are offered by many vendors ranging from SMEs up to 
> large enterprises. We believe that open source alternatives are an important 
> cornerstone for manufacturing companies to easily adopt data-driven decision 
> making. From our point of view, StreamPipes fits very well into the existing 
> (I)IoT ecosystem within the ASF, with projects such as Apache PLC4X focusing 
> on connecting machine data from PLCs, or other tools we are also using either 
> in the core of StreamPipes or with integrations (Apache Kafka, Apache IoTDB, 
> Apache Pulsar). StreamPipes itself focuses on enabling self-service IoT data 
> analytics for non-technical users.
> The whole StreamPipes code is currently on Github. To get a rough estimate of 
> the project size:
> * streampipes: Backend and core modules, ~3300 commits
> * streampipes-ui: User Interface, ~1300 commits
> * streampipes-pipeline-elements: ~100 Pipeline Elements (da

Re: [VOTE] Accept TubeMQ into the Apache Incubator

2019-10-31 Thread Willem Jiang
+1 (binding).

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Oct 30, 2019 at 9:48 AM David Nalley  wrote:
>
> Hi folks,
>
> The [DISCUSS] thread on TubeMQ has died down.
>
> Accordingly, I would like to call a VOTE to accept TubeMQ into the
> Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring TubeMQ into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring TubeMQ into the Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the
> Incubator PMC are binding, but votes from everyone are welcome.
>
> =Abstract=
>
> TubeMQ is a distributed messaging queue (MQ) system developed by
> Tencent Big Data since 2013. It focuses on high-performance storage
> and transmission of massive data in big data scenarios.After nearly
> seven years of massive data precipitation, TubeMQ has certain
> advantages in production practice (stability + performance) and low
> cost compared to many open source MQ projects.
>
> =Proposal=
>
> TubeMQ is suitable for high concurrency, massive data and tolerates a
> small amount of data loss scenarios under abnormal conditions, such as
> massive log collection, indicator statistics and monitoring, etc.
> TubeMQ does not support highly reliable data transmission services
> yet. It could be on a future project roadmap, as many other MQs. but
> not today.
>
> =Rationale=
>
> Just like other message queue systems, TubeMQ is built on the
> publish-subscribe pattern, aka pub-sub.
> In this pattern, producers publish messages to topics while consumers
> subscribe to those topics. After incoming messages get proceeded,
> consumers send an acknowledgement back to producer. Once a
> subscription has been created, all messages will be tracked and
> retained by TubeMQ, even if the consumer go offline for some reasons.
> Retained messages will be discarded only when a consumer acknowledges
> that they've been successfully processed.
>
> Portal is responsible for interact with user and admin system which
> include two parts: API and web portal.
>
> Master is controller of the cluster, which include one or multiple
> master node(s) which is responsible for managing state of cluster,
> resource scheduling, authentication check and maintaining of metadata.
> As a reliable system, TubeMQ provides HA solution for master node.
>
> Broker is responsible for data store which include a cluster of broker
> nodes. Every broker node is managing a set of topics, include: append,
> delete, update, query of topic information. In TubeMQ, these brokers
> can be horizontal scaled and can be very large size for massive data
> case.
>
> Client is responsible for producing and consuming messages. When a
> pub-sub topic get setup, we can support two ways (push and pull) for
> delivering message from producers to consumers.
>
> Zookeeper is for storing offset of messages which is used to recover
> topic during some components get failed.
>
>
> =Initial Goals=
>
> The initial goal will be to move the current codebase in github’s
> repository under Tencent account to Apache and integrate with the
> Apache development process and infrastructure.
> A primary goal of incubation will be to grow and diversify the TubeMQ
> community. We are well aware that the project community is largely
> comprised of individuals from a single company. We aim to change that
> during incubation.
>
> =Current Status=
>
> As previously mentioned, TubeMQ is under active development at
> Tencent, and is being used in processing large volumes of data for
> most services and products.
>
> =Meritocracy=
>
> We value meritocracy and we understand that it is the basis for an
> open community that encourages multiple companies and individuals to
> contribute and be invested in the project’s future. We will encourage
> and monitor participation and make sure to extend privileges and
> responsibilities to all contributors.
>
> =Community=
>
> TubeMQ is currently being used by developers at Tencent and a growing
> number of users are actively using it in production environments.
> TubeMQ has received contributions from developers working outside of
> Tencent since it was open sourced on github in September 2019 By
> bringing TubeMQ to Apache we aim to assure current and future
> contributors that the TubeMQ community is neutral, meritocratic, and
> open, in order to broaden and diversity the user and developer
> community.
>
> =Core Developers=
>
> TubeMQ was initially developed at Tencent and is under active
> development. We believe Tencent will be of interest to a broad range
> of users and developers and that incubating the project at the ASF
> will he

[jira] [Updated] (INCUBATOR-247) IP clearance for ServiceComb osa-validator

2019-10-29 Thread Willem Jiang (Jira)


 [ 
https://issues.apache.org/jira/browse/INCUBATOR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated INCUBATOR-247:
---
Description: 
 
[chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
  is contributing the oas-validator to Apache ServiceComb.

The clearance tasks are in progress and recorded at: 
[https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html]

This issue is partly to track that and primarily to provide an official record 
of the code drop contribution. The contributed code is attached to this issue 
as oas-validator-apache.zip.

MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851

Github repo [https://github.com/NewCapec-Institute/oas-validator]

Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199

 

 

  was:
 
[chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
  is contributing the oas-validator to Apache ServiceComb.

The clearance tasks are in progress and recorded at: 
[https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html]

This issue is partly to track that and primarily to provide an official record 
of the code drop contribution. The contributed code is attached to this issue 
as oas-validator-apache.zip.

MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851

Github repo [https://github.com/NewCapec-Institute/oas-validator]

Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199

 

 


> IP clearance for ServiceComb osa-validator
> --
>
> Key: INCUBATOR-247
> URL: https://issues.apache.org/jira/browse/INCUBATOR-247
> Project: Incubator
>  Issue Type: Task
>    Reporter: Willem Jiang
>Priority: Major
> Attachments: oas-validator-apache.zip
>
>
>  
> [chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
>   is contributing the oas-validator to Apache ServiceComb.
> The clearance tasks are in progress and recorded at: 
> [https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html]
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as oas-validator-apache.zip.
> MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851
> Github repo [https://github.com/NewCapec-Institute/oas-validator]
> Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



[jira] [Updated] (INCUBATOR-247) IP clearance for ServiceComb osa-validator

2019-10-29 Thread Willem Jiang (Jira)


 [ 
https://issues.apache.org/jira/browse/INCUBATOR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated INCUBATOR-247:
---
Description: 
 
[chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
  is contributing the oas-validator to Apache ServiceComb.

The clearance tasks are in progress and recorded at: 
[https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html]

This issue is partly to track that and primarily to provide an official record 
of the code drop contribution. The contributed code is attached to this issue 
as oas-validator-apache.zip.

MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851

Github repo [https://github.com/NewCapec-Institute/oas-validator]

Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199

 

 

  was:
 
[chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
  is contributing the oas-validator to Apache ServiceComb.

The clearance tasks are in progress and recorded at: 
[https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html]

This issue is partly to track that and primarily to provide an official record 
of the code drop contribution. The contributed code is attached to this issue 
as oas-validator-apache.zip.

MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851

Github repo [https://github.com/NewCapec-Institute/oas-validator]

Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199

 

 


> IP clearance for ServiceComb osa-validator
> --
>
> Key: INCUBATOR-247
> URL: https://issues.apache.org/jira/browse/INCUBATOR-247
> Project: Incubator
>  Issue Type: Task
>    Reporter: Willem Jiang
>Priority: Major
> Attachments: oas-validator-apache.zip
>
>
>  
> [chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
>   is contributing the oas-validator to Apache ServiceComb.
> The clearance tasks are in progress and recorded at: 
> [https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html]
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as oas-validator-apache.zip.
> MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851
> Github repo [https://github.com/NewCapec-Institute/oas-validator]
> Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



Re: [VOTE] Graudate Apache Weex (Incubating) as a Top Level Project

2019-10-28 Thread Willem Jiang
Hi Justin,

Thanks for pointing out these issues.  Weex has spent lot of time on
the release kit part during the incubation, but they also need to work
on growing a health community.
I will work with the Weex PPMC to figure out the solution of the
issues by filling the project maturity model.
For the branding protection, I think Weex PPMC also need to figure out
a solution at the meantime.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Oct 29, 2019 at 2:23 AM Justin Mclean  wrote:
>
> HI,
>
> While optional, and not a requirement for graduation, has the project 
> considered filling out the ASF maturity model?
>
> https://community.apache.org/apache-way/apache-project-maturity-model.html
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: [IP CLEARANCE] ServiceComb toolkit contribution

2019-10-27 Thread Willem Jiang
72 hours passed. We got none -1 vote.

Based on lazy consensus, this vote passed. I will update the
ip-clearance page for the vote information.

Willem Jiang

On behalf of ServiceComb PMC.

On Thu, Oct 24, 2019 at 9:58 AM Willem Jiang  wrote:
>
> Hi Incubator PMC,
>
> The TLP Apache ServiceComb toolkit[1] has been donated code for
> OpenAPI Specific Validator being referred to as
> `servicecomb-oas-validator`, old hostsd at [2].
>
> This is the formal request for IP clearance to be checked as per [3].
> The donated code can be found at [4] .
>
> Please check the ip-clearance filed here[5] for more information.
> The PMC has voted and passed to accept this donation[6].
> The ICLA of major contributors,  Daniel Qian has been filed.
> The SGA from NewCapec Institute has been filed.
>
> Please vote to approve this contribution.
>
> This majority vote is open for at least 72 hours and as usual lazy
> consensus applies.
>
> [1]https://github.com/apache/servicecomb-toolkit
> [2]https://github.com/NewCapec-Institute/oas-validator
> [3]https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling
> [4]https://issues.apache.org/jira/browse/INCUBATOR-247
> [5]https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html
> [6]https://lists.apache.org/thread.html/704967302e2f3c093441bf197bfe83b7aee34c210e0c3bb3898d4170@%3Cdev.servicecomb.apache.org%3E
>
> Willem Jiang
>
> On behalf of ServiceComb PMC.

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



[IP CLEARANCE] ServiceComb toolkit contribution

2019-10-23 Thread Willem Jiang
Hi Incubator PMC,

The TLP Apache ServiceComb toolkit[1] has been donated code for
OpenAPI Specific Validator being referred to as
`servicecomb-oas-validator`, old hostsd at [2].

This is the formal request for IP clearance to be checked as per [3].
The donated code can be found at [4] .

Please check the ip-clearance filed here[5] for more information.
The PMC has voted and passed to accept this donation[6].
The ICLA of major contributors,  Daniel Qian has been filed.
The SGA from NewCapec Institute has been filed.

Please vote to approve this contribution.

This majority vote is open for at least 72 hours and as usual lazy
consensus applies.

[1]https://github.com/apache/servicecomb-toolkit
[2]https://github.com/NewCapec-Institute/oas-validator
[3]https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling
[4]https://issues.apache.org/jira/browse/INCUBATOR-247
[5]https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html
[6]https://lists.apache.org/thread.html/704967302e2f3c093441bf197bfe83b7aee34c210e0c3bb3898d4170@%3Cdev.servicecomb.apache.org%3E

Willem Jiang

On behalf of ServiceComb PMC.

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



[jira] [Updated] (INCUBATOR-247) IP clearance for ServiceComb osa-validator

2019-10-22 Thread Willem Jiang (Jira)


 [ 
https://issues.apache.org/jira/browse/INCUBATOR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated INCUBATOR-247:
---
Description: 
 
[chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
  is contributing the oas-validator to Apache ServiceComb.

The clearance tasks are in progress and recorded at: 
[https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html]

This issue is partly to track that and primarily to provide an official record 
of the code drop contribution. The contributed code is attached to this issue 
as oas-validator-apache.zip.

MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851

Github repo [https://github.com/NewCapec-Institute/oas-validator]

Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199

 

 

  was:
 
[chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
  is contributing the oas-validator to Apache ServiceComb.

The clearance tasks are in progress and recorded at: 
[https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html]

This issue is partly to track that and primarily to provide an official record 
of the code drop contribution. The contributed code is attached to this issue 
as 

Github repo [https://github.com/NewCapec-Institute/oas-validator]

Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199

 

 


> IP clearance for ServiceComb osa-validator
> --
>
> Key: INCUBATOR-247
> URL: https://issues.apache.org/jira/browse/INCUBATOR-247
> Project: Incubator
>  Issue Type: Task
>    Reporter: Willem Jiang
>Priority: Major
> Attachments: oas-validator-apache.zip
>
>
>  
> [chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
>   is contributing the oas-validator to Apache ServiceComb.
> The clearance tasks are in progress and recorded at: 
> [https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html]
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as oas-validator-apache.zip.
> MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851
> Github repo [https://github.com/NewCapec-Institute/oas-validator]
> Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



[jira] [Created] (INCUBATOR-247) IP clearance for ServiceComb osa-validator

2019-10-22 Thread Willem Jiang (Jira)
Willem Jiang created INCUBATOR-247:
--

 Summary: IP clearance for ServiceComb osa-validator
 Key: INCUBATOR-247
 URL: https://issues.apache.org/jira/browse/INCUBATOR-247
 Project: Incubator
  Issue Type: Task
Reporter: Willem Jiang
 Attachments: oas-validator-apache.zip

 
[chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
  is contributing the oas-validator to Apache ServiceComb.

The clearance tasks are in progress and recorded at: 
[https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html]

This issue is partly to track that and primarily to provide an official record 
of the code drop contribution. The contributed code is attached to this issue 
as 

Github repo [https://github.com/NewCapec-Institute/oas-validator]

Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



[jira] [Updated] (INCUBATOR-247) IP clearance for ServiceComb osa-validator

2019-10-22 Thread Willem Jiang (Jira)


 [ 
https://issues.apache.org/jira/browse/INCUBATOR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated INCUBATOR-247:
---
Attachment: oas-validator-apache.zip

> IP clearance for ServiceComb osa-validator
> --
>
> Key: INCUBATOR-247
> URL: https://issues.apache.org/jira/browse/INCUBATOR-247
> Project: Incubator
>  Issue Type: Task
>    Reporter: Willem Jiang
>Priority: Major
> Attachments: oas-validator-apache.zip
>
>
>  
> [chanjarster|https://github.com/NewCapec-Institute/oas-validator/commits?author=chanjarster]
>   is contributing the oas-validator to Apache ServiceComb.
> The clearance tasks are in progress and recorded at: 
> [https://incubator.apache.org/ip-clearance/servicecomb-osa-validator.html|https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html]
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as 
> Github repo [https://github.com/NewCapec-Institute/oas-validator]
> Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7d2182d7199
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



Re: [DISCUSS] TubeMQ Proposal

2019-10-22 Thread Willem Jiang
Yeah, you made a very good point. We bring project to Apache Incubator
is for growing the community.
It take some time to let the team learn about the Apache Way. It could
be a growing pain because we need to change the mind set when doing
the project development.
Good luck for your project incubating journey, please let me know if
you need any help from my side.

Regards,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Oct 23, 2019 at 9:36 AM 俊平堵  wrote:
>
> Agree. My understanding is that it is magic of Apache incubation that help
> the project to build a diversity community.
> TubeMQ is working towards this direction although just get open sourced
> last month ACNA 2019.
>
> Thanks,
>
> Junping
>
> Tan,Zhongyi 于2019年10月23日 周三上午8:54写道:
>
> > It is a challenge but it is normal,
> > Many projects start from one company, then expand into community.
> >
> >
> > 在 2019/10/22 下午10:49,“Willem Jiang” 写入:
> >
> > I have the same concern as WenMing does.
> > It could be a challenge to build a diversity community for a project
> > which is just open sourced for few month.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> >
> > On Tue, Oct 22, 2019 at 11:29 AM Ming Wen 
> > wrote:
> > >
> > > Hi, this is an interesting proposal.
> > >
> > > I think the competition among different MQ is not an issue for
> > incubator
> > > stage. Users and developers will have their own choices.
> > >
> > > I guess that your challenges during the incubation:
> > > expanding diversity (now committers come from one company),
> > > and dealing with the relationship between the tencent internal
> > version and
> > > the open source version (I guess the two are not consistent, if I am
> > wrong,
> > > please correct me) .
> > >
> > > Thanks,
> > > Ming Wen
> > > Twitter: _WenMing
> > >
> > >
> > > Dave Fisher  于2019年10月22日周二 上午10:38写道:
> > >
> > > > Hi -
> > > >
> > > > > On Oct 21, 2019, at 7:26 PM, 俊平堵  wrote:
> > > > >
> > > > > bq. You might be right about that the project currently I
> > believe there's
> > > > > only one mentor with recent mentoring experience, and while all
> > proposed
> > > > are
> > > > > ASF members, not all of them are active on the IPMC general
> > list. It
> > > > might
> > > > > be better for the project to have at least one other mentor with
> > > > executive
> > > > > and is more active in the IPMC. What do others think?
> > > > > +1. Justin, do you have candidate to join the mentor team here?
> > > >
> > > > I’m on the Pulsar PMC with Sijie and know that he was also
> > involved with
> > > > DistributedLog which graduated into Bookkeeper. He will certainly
> > be good
> > > > help as a mentor.
> > > >
> > > > If Justin is good with this initial mix. I’m fine. If not then JBO
> > has
> > > > offered.
> > > >
> > > > Best wishes.
> > > >
> > > > Regards,
> > > > Dave
> > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Junping
> > > > >
> > > > > Justin Mclean  于2019年10月21日周一
> > 下午10:31写道:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >>> The first one is if we are able to mentor the project well
> > enough (old
> > > > >> discussion).
> > > > >>
> > > > >> You might be right about that the project currently I believe
> > there's
> > > > only
> > > > >> one mentor with recent mentoring experience, and while all
> > proposed are
> > > > ASF
> > > > >> members, not all of them are active on the IPMC general list.
> > It might
> > > > be
> > > > >> better for the project to have at least one other mentor with
> > executive
> > > > and
> > > > >> is more active in the IPMC. What do others think?
> > > 

Re: [DISCUSS] TubeMQ Proposal

2019-10-22 Thread Willem Jiang
I have the same concern as WenMing does.
It could be a challenge to build a diversity community for a project
which is just open sourced for few month.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Tue, Oct 22, 2019 at 11:29 AM Ming Wen  wrote:
>
> Hi, this is an interesting proposal.
>
> I think the competition among different MQ is not an issue for incubator
> stage. Users and developers will have their own choices.
>
> I guess that your challenges during the incubation:
> expanding diversity (now committers come from one company),
> and dealing with the relationship between the tencent internal version and
> the open source version (I guess the two are not consistent, if I am wrong,
> please correct me) .
>
> Thanks,
> Ming Wen
> Twitter: _WenMing
>
>
> Dave Fisher  于2019年10月22日周二 上午10:38写道:
>
> > Hi -
> >
> > > On Oct 21, 2019, at 7:26 PM, 俊平堵  wrote:
> > >
> > > bq. You might be right about that the project currently I believe there's
> > > only one mentor with recent mentoring experience, and while all proposed
> > are
> > > ASF members, not all of them are active on the IPMC general list. It
> > might
> > > be better for the project to have at least one other mentor with
> > executive
> > > and is more active in the IPMC. What do others think?
> > > +1. Justin, do you have candidate to join the mentor team here?
> >
> > I’m on the Pulsar PMC with Sijie and know that he was also involved with
> > DistributedLog which graduated into Bookkeeper. He will certainly be good
> > help as a mentor.
> >
> > If Justin is good with this initial mix. I’m fine. If not then JBO has
> > offered.
> >
> > Best wishes.
> >
> > Regards,
> > Dave
> >
> > >
> > > Thanks,
> > >
> > > Junping
> > >
> > > Justin Mclean  于2019年10月21日周一 下午10:31写道:
> > >
> > >> Hi,
> > >>
> > >>> The first one is if we are able to mentor the project well enough (old
> > >> discussion).
> > >>
> > >> You might be right about that the project currently I believe there's
> > only
> > >> one mentor with recent mentoring experience, and while all proposed are
> > ASF
> > >> members, not all of them are active on the IPMC general list. It might
> > be
> > >> better for the project to have at least one other mentor with executive
> > and
> > >> is more active in the IPMC. What do others think?
> > >>
> > >>> As the project comes from Tencent I assume that the community is mostly
> > >> Chinese and due to the language barrier (and probably a different
> > culture)
> > >> we have seen that these projects tend to be "more challenging" (this
> > does
> > >> not describe it accurate enough but I hope that readers understand what
> > I
> > >> mean).
> > >>
> > >> While projects in this group do have some challenges, I don’t believe
> > it’s
> > >> anymore than other projects from different background. In some ways the
> > ASF
> > >> model is a good cultural fit - see Sharan’s thesis on that.
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> > >>
> > >> -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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



Re: [Vote] Release Apache Weex (Incubating) 0.28.0-RC1

2019-10-21 Thread Willem Jiang
+1 (binding)

I checked the staged source and binary bundles.
- Hashes file and signature files are OK
- DISCLAIMER file is there
- LICENSE and NOTICE files are fine

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Thu, Oct 17, 2019 at 8:34 PM 申远  wrote:
>
> Hi, folks
>
> The Apache Weex community has voted and approved the proposal to release
> Apache Weex (Incubating) version 0.28.0-RC1, we now kindly request the
> Incubator PMC members to review and vote on this incubator release.
>
>- Vote thread:
>
> https://lists.apache.org/thread.html/3b56f8ceb75981487de107c90995de27ebfa9ff9acfb0e16ca07cc55@%3Cdev.weex.apache.org%3E
>- Vote result thread:
>
> https://lists.apache.org/thread.html/7df08b9020fc11c0cb01b15faea16207cb791314ef993ab73a9b2721@%3Cdev.weex.apache.org%3
>
> <https://lists.apache.org/thread.html/7df08b9020fc11c0cb01b15faea16207cb791314ef993ab73a9b2721@%3Cdev.weex.apache.org%3E>
>- Git tag for this Release:
>https://github.com/apache/incubator-weex/releases/tag/0.28.0-RC1
>- The source tarball could be found at :
>
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz
>- The signature of the source tarball could be found at :
>
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.asc
>- The SHA-512 checksum of the source tarball could be found at :
>
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.sha512
>- The source tarball is signed with
>Key:D7E6B58FFA293FB1AC9E7B624FD8BC09C7E9DB81, which could be found in the
>key file: https://dist.apache.org/repos/dist/release/incubator/weex/KEYS
>- ChangeLog about this version:
>https://github.com/apache/incubator-weex/blob/release/0.28/CHANGELOG.md
>
>
> One can build the binary from source according to
> https://github.com/apache/incubator-weex/blob/release/0.28/HOW-TO-BUILD.md
> with build environment installed.
>
> *FYI: I only test the build scripts on Mac environment, it should also work
> in Linux/Unit platform according to my understanding. But you may get
> problems if you try to build Weex from source on a windows platform.*
>
> This vote will remain open for at least 72 hours, until we get enough
> votes. Please vote on releasing this RC.
>
>-  +1 approve
>-  +0 no opinion
>-  -1 disapprove (and reason why)
>
>
> Best Regards,
> YorkShen
>
> 申远

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



Re: [LAZY][VOTE] Release Apache IoTDB 0.8.1 (a bug-fix version of 0.8.0)

2019-10-21 Thread Willem Jiang
+1 (binding).
Carrying my vote here.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Oct 21, 2019 at 1:47 PM Xiangdong Huang  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version 0.8.1,
> which is a bug-fix Release of 0.8.0 for the IoTDB Project.
>
> The Apache IoTDB community has voted on and approved a proposal to release
> Apache IoTDB (Incubating) version 0.8.1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an
> integrated data management engine designed for timeseries data. It provides
> users with services for data collection, storage and analysis.
>
> IoTDB community vote and result thread:
> Result:
> https://lists.apache.org/thread.html/3773662919c65fb997322f7c1a5fd54560da079b912846ccb1a56b2e@%3Cdev.iotdb.apache.org%3E
>
> Vote:
> https://lists.apache.org/thread.html/0b2153f07af8f2a0f7ac13b8005c67f2d511bc30a9a2e20a461d60f4@%3Cdev.iotdb.apache.org%3E
> (and one vote is at
> https://lists.apache.org/thread.html/741fc778f75607d58f8e814c9f7297bcdc7098b96f65d4abd299da7e@%3Cdev.iotdb.apache.org%3E
> )
>
> The release candidates (RC3):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.1/rc3
>
> Git tag for the release (RC3):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.1
>
> Hash for the release tag:
> 4b8d46f9861e12bbe4a1d952bede7c9293b90b46
>
> Release Notes:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.1/rc3/RELEASE_NOTES.md
>
> The artifacts have been signed with Key : 2206EF8F64C35889, which can be
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB
> /Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
> From the PPMC Vote we cary over 3 binding IPMC Votes:
>
> +1 from Justin McLean,
> +1 from Christofer Dutz,
> +1 from Kevin A. McGrail
>
> Thus, I took the freedom to declare the Vote as Lazy as no futher positive
> votes are necessary and only a -1 Vote could cancel the vote.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Best,
>
> Xiangdong Huang
> Apache IoTDB
>
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院

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



Re: Remove PMC incubator page

2019-10-19 Thread Willem Jiang
Sounds good to me.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Oct 18, 2019 at 4:59 PM Justin Mclean  wrote:
>
> Hi,
>
> The page here [1] doesn’t really add anything that is not written out 
> elsewhere and seems redundant. If no-one objects I’ll remove it.
>
> Thanks,
> Justin
>
>
> 1. https://incubator.apache.org/guides/pmc.html
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: [VOTE] Accept APISIX into Apache Incubator

2019-10-10 Thread Willem Jiang
+1 (binding).

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Oct 10, 2019 at 4:55 PM Ming  wrote:
>
> Hi all,
>
> After the discussion of APISIX proposal
> (discussion thread:
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E),
> I would like to call a VOTE to accept it into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring APISIX into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring APISIX into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> = APISIX Proposal =
>
> == Abstract ==
>
> APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security,
> open source and scalable platform for all your APIs and microservices.
>
> APISIX is based on OpenResty and etcd, and has dynamic routing and
> plug-in hot loading,
>  which is especially suitable for API management under micro-service system.
>
> == Proposal ==
>
> The goal of this proposal is to bring the existing APISIX
> <https://github.com/iresty/apisix> codebase and existing developers
> and community
> into the Apache Software Foundation (ASF) in order to build a global,
> diverse and self-governed open source community in API gateway field.
>
> Zhiliu is submitting this proposal to donate the APISIX sources code
> and associated artifacts
> (documentation, web site content, wiki, etc.) to the Apache Software
> Foundation Incubator under the Apache License, Version 2.0.
>
> These artifacts are currently available on GitHub at
> https://github.com/iresty/apisix and include:
> - APISIX: The Cloud-Native Microservices API gateway.
> - APISIX-dashboard: The dashboard for APISIX API gateway.
>
> == Background ==
>
> Mircro-service and Cloud Native architecture are becoming more and more 
> popular,
> traditional monolithic applications are being replaced by microservices.
> This also brings more challenges for API gateways, not only handling
> north-south traffic,
> but also handling east-west traffic between microservices,
> and need to ensure high concurrency and very low latency at the same time.
>
> APISIX was open sourced on Github in in June 2019.
> At first, APISIX needs to interact directly with etcd to modify the
> configuration of routes and plugins.
> After we opened on the GitHub, the community gives the feedbacks about
> high level API and built-in dashboard.
> So in 0.6 version, APISIX provided REST admin API and dashboard to
> control the API gateway.
> Since then more and more contributors have joined in, and more plugins
> and features provided.
>
> == Rationale ==
>
> APISIX acts as an entry point for business traffic and plays an
> important role in the current system.
>  Making traffic more secure and faster to process is the ultimate goal
> of APISIX.
>
> APISIX includes these primary parts:
> - Provide the core of the API gateway, including various
> processing of requests and responses, dynamic upstream and dynamic SSL
> certificates,
> upstream active and passive health checks, etc. The core does not
> bind APISIX, other projects can be used directly.
> - Provide the plug-in hot plugging mechanism based on the core, to
> support gRPC transcoding,
>  identity authentication, rate limiting, OpenTracing etc. And
> provide a plugin development library,
>   users can easily write their own plugins.
> - Provide the admin API and dashboard to operate the API gateway,
> and also support updating with the yaml configuration file, which
> is friendly for Kubernetes.
>
> There is a strong need for an open, easy-to-use microservice API
> gateway to help developers
>  reduce duplication of code development and better manage APIs.
> We believe that by moving to Apache it will help us work in a more
> global and open way.
> Under Apache’s strong governance and existing processes, hope is also
> to make APISIX more reliable and encourage more developers to
> participate,
>  as is crucial for API gateway.
>
> == Current Status ==
>
> === Meritocracy ===
>
> APISIX was created in April 2019 and opened on github on June 6, 2019.
> The project now has contributors and users from a dozen companies;
> we have set up the PMC Team and Committer Team. New contributors are
> guided and reviewed by existed PMC members.
> When they are ready, PMC will start a vote to promote him/her to
> become a member of PMC or Committer Team,
> see the votes for Committer:
> https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> Contribution

Re: [VOTE] Release Apache ECharts (incubating) 4.4.0 (release candidate 1)

2019-10-08 Thread Willem Jiang
+1.

Checked the signed key and sh512.
License and NOTICE files look good to me.
DISCLAIM file is there
I can build the source kit without any issues.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Wed, Oct 9, 2019 at 5:31 AM SHUANG SU  wrote:
>
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.4.0 (release candidate 1).
>
> Apache ECharts community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/af24a7dfb3b9b9889141828aecc05503f4cbdf2a93cef6c95fad1ccd@%3Cdev.echarts.apache.org%3E
>
> Results thread:
> https://lists.apache.org/thread.html/5d6dd016aded1f16f43e6d7b1413a3a6bd70a10da73dce9f9d635814@%3Cdev.echarts.apache.org%3E
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.4.0-rc.1/
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> The Git commit for this release is:
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=b2b38d67
>
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.4.0-rc.1/RELEASE_NOTE.txt
>
> Build Guide:
> https://github.com/apache/incubator-echarts/blob/4.4.0-rc.1/README.md
>
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.4.0 (release candidate 1)
> by "2019-10-11T22:11:52.182Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
>
> Thanks,
> --
>  Su Shuang (100pah)
> --

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



Re: [DISCUSS] APISIX incubator proposal

2019-09-26 Thread Willem Jiang
Hi,

I had a good talk with Ming Wen and Yuansheng Wang last weekend,  I
think they already know the meaning of donate the project into Apache
and they already did lots of work to grow the community for the last
three month.
API gateway is a quite important services in Micro Services Archeture,
current we don't have this kind of project in Apache, so I'd like to
be the Champion of this project.
Currently we just have two mentors, please join us as mentor if you like.

Thanks,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

2019-08-25 Thread Willem Jiang
+1 (binding).


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Aug 23, 2019 at 9:39 AM Sheng Wu  wrote:
>
> Hi all,
>
> After the discussion of DolphinScheduler(was EasyScheduler) proposal
> (discussion thread:
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> ),
> I would like to call a VOTE to accept it into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring DolphinScheduler into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring DolphinScheduler into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> ==
> Abstract
>
> DolphinScheduler is a distributed ETL scheduling engine with powerful DAG
> visualization interface. DolphinScheduler focuses on solving the problem of
> 'complex task dependencies & triggers' in data processing. Just like its
> name, we dedicated to making the scheduling system out of the box.
>
> *Current project name of DolphinScheduler is EasyScheduler, will change it
> after it is accepted by Incubator.*
> Proposal
>
> DolphinScheduler provides many easy-to-use features to accelerate
> the engineering efficiency on data ETL workflow job. We propose a new
> concept of 'instance of process' and 'instance of task' to let developers
> to tuning their jobs on the running state of workflow instead of changing
> the task's template. Its main objectives are as follows:
>
>- Define the complex tasks' dependencies & triggers in a DAG graph by
>dragging and dropping.
>- Support cluster HA.
>- Support multi-tenant and parallel or serial backfilling data.
>- Support automatical failure job retry and recovery.
>- Support many data task types and process priority, task priority and
>relative task timeout alarm.
>
> For now, DolphinScheduler has a fairly huge community in China. It is also
> widely adopted by many companies and organizations
> <https://github.com/analysys/EasyScheduler/issues/57> as its ETL scheduling
> tool.
>
> We believe that bringing DolphinScheduler into ASF could advance
> development of a much more stronger and more diverse open source community.
>
> Analysys submits this proposal to donate DolphinScheduler's source codes
> and all related documentations to Apache Software Foundation. The codes are
> already under Apache License Version 2.0.
>
>- Code base: https://www.github.com/analysys/easyscheduler
>- English Documentations: https://analysys.github.io/easyscheduler_docs
>- Chinese Documentations:
>https://analysys.github.io/easyscheduler_docs_cn
>
> Background
>
> We want to find a data processing tool with the following features:
>
>- Easy to use,developers can build a ETL process with a very simple drag
>and drop operation. not only for ETL developers,people who can't write code
>also can use this tool for ETL operation such as system adminitrator.
>- Solving the problem of "complex task dependencies" , and it can
>monitor the ETL running status.
>- Support multi-tenant.
>- Support many task types: Shell, MR, Spark, SQL (mysql, postgresql,
>hive, sparksql), Python, Sub_Process, Procedure, etc.
>- Support HA and linear scalability.
>
> For the above reasons, we realized that no existing product met our
> requirements, so we decided to develop this tool ourselves. We designed
> DolphinScheduler at the end of 2017. The first internal use version was
> completed in May 2018. We then iterated several internal versions and the
> system gradually became stabilized.
>
> Then we open the source code of DolphinScheduler on March 2019. It soon
> gained lot's of ETL developers interest and stars on github.
> Rationale
>
> Many organizations (>30) (refer to Who is using DolphinScheduler
> <https://github.com/analysys/EasyScheduler/issues/57> ) already benefit
> from running DolphinScheduler to make data process pipelines more easier.
> More than 100 feature ideas
> <https://github.com/analysys/EasyScheduler/projects/1> come from
> DolphinScheduler community. Some 3rd-party projects also plan to integrate
> with DolphinScheduler through task plugin, such as Scriptis
> <https://github.com/WeBankFinTech/Scriptis>, waterdrop
> <https://github.com/InterestingLab/waterdrop>. These will strengthen the
> features of DolphinScheduler.
> Current StatusMeritocracy
>
> DolphinScheduler was incubated at Analysys in 2017 and open sourced on
> GitHub in March 2019. Once open sourced, we have been quickly adopted by
> multiple organizations,DolphinScheduler has

Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC2

2019-08-21 Thread Willem Jiang
+1 (binding)

I checked:

The artifacts has incubating in the name.
There is no binary in the release kit.
signature and hash is OK
DISCLAIMER file exists
LICENSE and NOTICE looks good to me.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Wed, Aug 21, 2019 at 1:15 PM Zhang Yonglun  wrote:
>
>  I have put the wrong link of Maven 2 staging repository, now it's updated
> to:
>
> Maven 2 staging repository:
> https://repository.apache.org/content/repositories/orgapacheshardingsphere-1022/org/apache/shardingsphere/
>
>
> Zhang Yonglun  于2019年8月20日周二 下午6:16写道:
>
> > Hello all,
> >
> > This is a call for vote to release Apache ShardingSphere (Incubating)
> > version 4.0.0-RC2.
> >
> > The Apache ShardingSphere community has voted on and approved a proposal
> > to release Apache ShardingSphere (Incubating) version 4.0.0-RC2.
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > ShardingSphere is an open-source ecosystem consisted of a set of
> > distributed database middleware solutions, including 2 independent
> > products, Sharding-JDBC & Sharding-Proxy.
> >
> > Sharding-JDBC is an enhanced JDBC driver that provides in-process
> > transparent distributed database by connecting to multiple database back
> > ends. It supports many ORM frameworks and database connection pools and
> > supports many back end databases that have JDBC interfaces: MySQL, Oracle,
> > SQLServer and PostgreSQL.
> >
> > Sharding-Proxy is a database proxy that runs in a separate process and
> > appears as a database server to multiple back end databases. It supports
> > multiple client front ends such as MySQL Command Client, MySQL Workbench,
> > Navicat etc. Current support is for MySQL and PostgreSQL.
> >
> > ShardingSphere community vote and result thread:
> >
> > https://lists.apache.org/thread.html/4b29490f433dd26cc85d0e00340def3bd0f7b64e4bd2f3512e568bcd@%3Cdev.shardingsphere.apache.org%3E
> >
> > Release notes:
> >
> > https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md
> >
> > The release candidates:
> > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/
> >
> > Maven 2 staging repository:
> >
> > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2
> >
> > Release Commit ID:
> >
> > https://github.com/apache/incubator-shardingsphere/commit/85f2ff877a7aaf122998964a0d03f7c9b2830e36
> >
> > Keys to verify the Release Candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS
> > GPG username: zhangyonglun
> >
> > Look at here for how to verify this release candidate:
> > https://shardingsphere.apache.org/community/en/contribute/release/
> >
> > 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
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> >
> > [ ] Checksums and PGP signatures are valid.
> >
> > [ ] DISCLAIMER is included.
> >
> > [ ] Source code artifacts have correct names matching the current release.
> >
> > [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo.
> >
> > [ ] All files have license headers if necessary.
> >
> > [ ] No compiled archives bundled in source archive.
> >
> > --
> > Zhang Yonglun
> > Apache ShardingSphere
> >
>
>
> --
> Zhang Yonglun
> Apache ShardingSphere

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



Re: [DISCUSS] Drop requirement that ASF members can join IPMC by just asking

2019-08-12 Thread Willem Jiang
+1 , we need a binding process to let the member know better about the
Incubating.
For me, even I attend serval Apache projects before I start mentoring
incubating project, there are still lot of thing I need to learn.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Aug 9, 2019 at 1:04 PM Justin Mclean  wrote:
>
> Hi,
>
> Current any ASF member can come along and ask to join the IPMC. I assume this 
> was put in place for two reasons: ( but don’t know the full history behind it)
> - There was a lack of mentors.
> - Is is assumed that if you are an ASF member you know enough about the 
> Apache Way to mentor a project.
>
> I’m not sure if this is the case anymore. And while the mentor situation has 
> improved I don’t think the above has solved the problem of having active 
> members or mentors having the required knowledge and skills they need.
>
> So if you want to be a IPMC member and mentor a project then I think you need 
> you have gone through the full incubation process yourself and/or help out 
> with other incubator duties and get voted in as an IPMC member. Just like 
> every other ASF project.
>
> What do other people think?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: [MENTORS] IPMC Policy change work in progress disclaimer

2019-08-03 Thread Willem Jiang
+1.  I cannot agree more with that.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Aug 2, 2019 at 2:17 PM Paul King  wrote:
>
> Kudos for progressing this idea. I really like it. It should allow
> improvements from the perspective of both podlings and reviewers.
>
> Cheers, Paul.
>
> On Fri, Aug 2, 2019 at 12:25 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > The work in progress progress disclaimer (DISCLAIMER-WIP) has been added
> > to the IPMC policy page. [1]
> >
> > Podlings can now select which disclaimer they want to use. If they want to
> > use the standard disclaimer then their releases must comply with all ASF
> > policy. If they want the incubator to be more lenient in voting on their
> > release or know that the release has some issues not in line with ASF
> > policy then the work in progress disclaimer can be used.
> >
> > Unless the release is simple and straightforward, I would recommend that a
> > podling uses the work in progress disclaimer for the first couple of
> > releases.
> >
> > For what is allowed under the work in progress disclaimer please see this
> > legal JIRA [2]. This allows a lot more in a release but not everything.
> > Certain things are required like having a LICENSE, NOTICE and
> > DISCLAIMER-WIP, and while it would be OK to include compiled code you still
> > need to comply with any licensing for that code.
> >
> > By the time a podling graduates it's expected that they are making
> > releases with the standard disclaimer.
> >
> > Here is the text of the DISCLAIMER-WIP where the Incubator is the sponsor:
> > 
> > Apache  #Podling-Name# is an effort
> > undergoing incubation at The Apache Software Foundation (ASF),
> > sponsored by the Apache Incubator. Incubation is required of all
> > newly accepted projects until a further review indicates that the
> > infrastructure, communications, and decision making process have
> > stabilized in a manner consistent with other successful ASF projects.
> > While incubation status is not necessarily a reflection of the
> > completeness or stability of the code, it does indicate that the
> > project has yet to be fully endorsed by the ASF.
> >
> > Some of the incubating project's releases may not be fully compliant
> > with ASF policy. For example, releases may have incomplete or
> > un-reviewed licensing conditions. What follows is a list of known
> > issues the project is currently aware of (note that this list, by
> > definition, is likely to be incomplete):
> > #List of known issues go here#
> >
> > If you are planning to incorporate this work into your
> > product/project, please be aware that you will need to conduct a
> > thorough licensing review to determine the overall implications of
> > including this work. For the current status of this project through the
> > Apache
> > Incubator visit:
> > http://incubator.apache.org/project/#Podling-Name#.html
> > 
> >
> > Just fill in #Podling-Name# with your podling name and list the known
> > issues in the correct place.
> >
> > Thanks,
> > Justin
> >
> > 1. https://incubator.apache.org/policy/incubation.html#disclaimers
> > 2. https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-469
> > -
> > 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



[jira] [Resolved] (INCUBATOR-241) IP clearance for ServiceComb Mesher

2019-07-15 Thread Willem Jiang (JIRA)


 [ 
https://issues.apache.org/jira/browse/INCUBATOR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang resolved INCUBATOR-241.

Resolution: Fixed

The code repo is transferred into Apache group.

> IP clearance for ServiceComb Mesher
> ---
>
> Key: INCUBATOR-241
> URL: https://issues.apache.org/jira/browse/INCUBATOR-241
> Project: Incubator
>  Issue Type: Task
>    Reporter: Willem Jiang
>Priority: Major
> Attachments: mesher-master.zip
>
>
> Tian xiaoliang is contributing the Mesher 
> The clearance tasks are in progress and recorded at: 
> https://incubator.apache.org/ip-clearance/servicecomb-mesher.html
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as mesher-master.zip
> md5sum mesher-master.zip
> MD5 (mesher-master.zip) = 9cbbc1a5ba09e1720c703614f158500e



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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



[jira] [Commented] (INCUBATOR-241) IP clearance for ServiceComb Mesher

2019-07-09 Thread Willem Jiang (JIRA)


[ 
https://issues.apache.org/jira/browse/INCUBATOR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881674#comment-16881674
 ] 

Willem Jiang commented on INCUBATOR-241:


IP Clearance IPMC request:  
https://lists.apache.org/thread.html/76c90a1c9ff7d7c6da4440d4ead8263913bca4de30147157710e580b@%3Cgeneral.incubator.apache.org%3E
 
IP Clearance IPMC result:  
https://lists.apache.org/thread.html/d0a957684ea24594f14e573de7c3ebe42d721193b56f28a735990e6b@%3Cgeneral.incubator.apache.org%3E
 


> IP clearance for ServiceComb Mesher
> ---
>
> Key: INCUBATOR-241
> URL: https://issues.apache.org/jira/browse/INCUBATOR-241
> Project: Incubator
>  Issue Type: Task
>    Reporter: Willem Jiang
>Priority: Major
> Attachments: mesher-master.zip
>
>
> Tian xiaoliang is contributing the Mesher 
> The clearance tasks are in progress and recorded at: 
> https://incubator.apache.org/ip-clearance/servicecomb-mesher.html
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as mesher-master.zip
> md5sum mesher-master.zip
> MD5 (mesher-master.zip) = 9cbbc1a5ba09e1720c703614f158500e



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



Re: [IP CLEARANCE] ServiceComb Mesher project contribution

2019-07-09 Thread Willem Jiang
72 hours passed. We got none -1 vote.

Based on lazy consensus, this vote passed. I will update the
ip-clearance page for the vote information.

Thanks,

Willem Jiang

On Sun, Jul 7, 2019 at 9:17 AM Willem Jiang  wrote:
>
> Hi Incubator PMC,
>
> The TLP Apache ServiceComb has been donated code for mesher being
> referred to as `servicecomb-mesher`[1], old hostsd at go mesher repo[2].
>
> This is the formal request for IP clearance to be checked as per [3].
> The donated code can be found at [4] .
>
> Please check the ip-clearance filed here[5] for more information.
> The PMC has voted and passed to accept this donation[6].
> The ICLA of major contributors, TianXiaoliang, JuZhen, Rajadeepan D
> Ramesh have been filed.
> The SGA from Huawei has been filed.
>
> Please vote to approve this contribution.
>
> This majority vote is open for at least 72 hours and as usual lazy
> consensus applies.
>
> [1]https://github.com/apache/servicecomb-mesher
> [2]https://github.com/go-mesh/mesher
> [3]https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling
> [4]https://issues.apache.org/jira/browse/INCUBATOR-241
> [5]https://incubator.apache.org/ip-clearance/servicecomb-mesher.html
> [6]https://lists.apache.org/thread.html/b2205334b6abf7fdde38830c3b40f114a736abb3e69b05ed367eaa8e@%3Cdev.servicecomb.apache.org%3E
>
> Willem Jiang
>
> On behalf of ServiceComb PMC.

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



[IP CLEARANCE] ServiceComb Mesher project contribution

2019-07-06 Thread Willem Jiang
Hi Incubator PMC,

The TLP Apache ServiceComb has been donated code for mesher being
referred to as `servicecomb-mesher`[1], old hostsd at go mesher repo[2].

This is the formal request for IP clearance to be checked as per [3].
The donated code can be found at [4] .

Please check the ip-clearance filed here[5] for more information.
The PMC has voted and passed to accept this donation[6].
The ICLA of major contributors, TianXiaoliang, JuZhen, Rajadeepan D
Ramesh have been filed.
The SGA from Huawei has been filed.

Please vote to approve this contribution.

This majority vote is open for at least 72 hours and as usual lazy
consensus applies.

[1]https://github.com/apache/servicecomb-mesher
[2]https://github.com/go-mesh/mesher
[3]https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling
[4]https://issues.apache.org/jira/browse/INCUBATOR-241
[5]https://incubator.apache.org/ip-clearance/servicecomb-mesher.html
[6]https://lists.apache.org/thread.html/b2205334b6abf7fdde38830c3b40f114a736abb3e69b05ed367eaa8e@%3Cdev.servicecomb.apache.org%3E

Willem Jiang

On behalf of ServiceComb PMC.

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



[jira] [Updated] (INCUBATOR-241) IP clearance for ServiceComb Mesher

2019-07-04 Thread Willem Jiang (JIRA)


 [ 
https://issues.apache.org/jira/browse/INCUBATOR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated INCUBATOR-241:
---
Attachment: mesher-master.zip

> IP clearance for ServiceComb Mesher
> ---
>
> Key: INCUBATOR-241
> URL: https://issues.apache.org/jira/browse/INCUBATOR-241
> Project: Incubator
>  Issue Type: Task
>    Reporter: Willem Jiang
>Priority: Major
> Attachments: mesher-master.zip
>
>
> Tian xiaoliang is contributing the Mesher 
> The clearance tasks are in progress and recorded at: 
> https://incubator.apache.org/ip-clearance/servicecomb-mesher.html
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as mesher-master.zip
> md5sum mesher-master.zip
> MD5 (mesher-master.zip) = 9cbbc1a5ba09e1720c703614f158500e



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Created] (INCUBATOR-241) IP clearance for ServiceComb Mesher

2019-07-04 Thread Willem Jiang (JIRA)
Willem Jiang created INCUBATOR-241:
--

 Summary: IP clearance for ServiceComb Mesher
 Key: INCUBATOR-241
 URL: https://issues.apache.org/jira/browse/INCUBATOR-241
 Project: Incubator
  Issue Type: Task
Reporter: Willem Jiang


Tian xiaoliang is contributing the Mesher 
The clearance tasks are in progress and recorded at: 
https://incubator.apache.org/ip-clearance/servicecomb-mesher.html

This issue is partly to track that and primarily to provide an official record 
of the code drop contribution. The contributed code is attached to this issue 
as mesher-master.zip

md5sum mesher-master.zip

MD5 (mesher-master.zip) = 9cbbc1a5ba09e1720c703614f158500e



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



Re: [VOTE] Release Apache Doris 0.10.0-incubating-rc04

2019-06-29 Thread Willem Jiang
+1.

I checked
The artifacts has incubating in the name.
There is no binary in the release kit.
signature and hash is OK
DISCLAIMER file exists
LICENSE and NOTICE looks good to me.

There is a license notice section in the README file need to be
polished, I think by default build we should exclude the libraries
which License is not compiled with ASL.
End user could enable the feature by building the binary himself with
some additional options.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jun 25, 2019 at 9:15 AM 陈明雨  wrote:
>
> Hi all,
>
>
> Please review and vote on Apache Doris 0.10.0-incubating-rc04 release.
>
>
> Apache Doris is an MPP-based interactive SQL data warehousing for reporting 
> and analysis.
>
>
> The Apache Doris community has voted on and approved this release:
> https://lists.apache.org/thread.html/a4b5c1102168769e6802aa7fe4db0482f7288d76210b58125b074355@%3Cdev.doris.apache.org%3E
>
>
> The vote result email is at end of this thread:
> https://lists.apache.org/thread.html/a4b5c1102168769e6802aa7fe4db0482f7288d76210b58125b074355@%3Cdev.doris.apache.org%3E
>
>
> The release candidate has been tagged in GitHub as 0.10.0-rc04, available 
> here:
> https://github.com/apache/incubator-doris/releases/tag/0.10.0-rc04
>
>
> = CHANGE LOG 
>
>
> New Features:
>
>
> * Support Routine Load
> Doris now support routine load job, which allow user to create a routine
> load job with simple instruction, and the data will be consumed and loaded
> into Doris automatically. More information and guide can be found in
> [Routine 
> Load](https://github.com/apache/incubator-doris/blob/master/docs/documentation/cn/administrator-guide/load-data/routine-load-manual.md).
>
>
> * Support Doris on ES
> Doris now support querying Elasticsearch. User can create an extern table
> with engine type `ES`, and query it as a normal table. Doris also support a
> new built-in function `es_query()`, which allow user to write special
> Elasticsearch query language in SQL. More information and guide can be
> found in 
> [Doris-On-ES](https://github.com/apache/incubator-doris/blob/master/docs/documentation/cn/extending-doris/doris-on-es.md)
>
>
> * Support UDF and UDAF
> Now user can write UDF and UDAF in C++ language.
>
>
> * New documentation framework
> All documents of Doris will be moved to the directory
> `docs/documentation/`. You can see [README](
> https://github.com/apache/incubator-doris/blob/master/docs/readme.md) to
> get more information, and help us complete the documentations. Any
> documents are welcome.
> There is also a new directory `samples/` which contains some samples of
> using Doris.
>
>
> Enhancement:
>
>
> * High performance Decimal type implementation.(#727)
> * Parallel execution of fragment instance (#851)
> * Support hll_union_agg in Analytic Function (#819)
> * Support hll_raw_agg in Aggregate Function (#832)
> * Support adding columns to multiple rollup indexes in one ALTER TABLE
> stmt (#931)
>
>
> Usability:
>
>
> * Add --daemon option to all start scripts (#642)
> * Remove the restrict that delete stmt must specify partition even for
> unpartitioned table (#668)
> * Remove restrict of that Analytic function must have partition by clause
> (#659)
> * Support `enable_insert_strict` session variable to control the insert
> request (#1013)
> * Support NEGATIVE keyword in Broker Load (#1101)
> * Support more functions which can be calculated in Frontends:
> unix_timestamp(), str_to_date(), current_user(), user()
> * Support more built-in functions: money_format(), left(), right()
> * New metrics: disk_state, tablet_distribution, scheduled_tablet_num
> * Forward some requests to Master Frontend to get accurate results (#944)
>
>
> Bug fixed:
>
>
> * A lot of bugs fixed. Please see 
> [ISSUES](https://github.com/apache/incubator-doris/issues) to get more
> information.
>
>
> ==
>
>
> The artifacts (source, signature and checksum) corresponding to this release 
> candidate can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.10/0.10.0-rc4/
>
>
> This has been signed with PGP key A30C9DA2, corresponding to 
> chenmin...@apache.org.
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.10/0.10.0-rc4/KEYS
> It is also listed here:
> https://people.apache.org/keys/committer/morningman.asc
>
>
> The vote will be open for at least 72 hours.
> [ ] +1 Approve the release
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
>
> To verify and build, you can refer to following instruction:
>
>
> Firstly, you must be install a

Re: Incubation Pain Points

2019-06-18 Thread Willem Jiang
It could be a grown pain for the new podlings if they need to go
through 10+ voting, but it could make the life more easier by
providing some tools to help the podling to find out the issues before
sending out the vote.
I know it is harder to provide an unify tool which could be useful for
all kind of project, but it could address most of common issues if
IPMC can build the tools together by sharing our experiences.

Regards,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Jun 17, 2019 at 5:37 PM Justin Mclean  wrote:
>
> Hi,
>
> > The biggest fix I’d suggest for the incubator is parallel voting
>
> Worthy of consideration (please start a thread), but IMO we want to be 
> careful it doesn’t overwhelm the IPMC. I’ve seen some RCs got through 10+ 
> votes, and most go through 2 or 3. That’s potentially 2 or 3 or 5x more calls 
> for votes on the IPMC list, unless we modify it somehow or somehow get more 
> IPMC members to vote on releases it’s going to need some careful 
> consideration.
>
> Some discussion on legal discuss and in the last board report may help reduce 
> the requirement for revotes like that.
>
> > after an IPMC vote failed yet again on some aspect that the
> > community is not interested in at all (but should be, but still isn’t).
>
> Or alternatively how could a podling get the community (or it's mentors) to 
> pick up these things before the IPMC vote? In theory your mentors should pick 
> up any issues that the IPMC finds, in practise that doesn't always happen.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



[jira] [Closed] (INCUBATOR-239) IP clearance for ServiceComb Toolkit

2019-06-17 Thread Willem Jiang (JIRA)


 [ 
https://issues.apache.org/jira/browse/INCUBATOR-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang closed INCUBATOR-239.
--
Resolution: Fixed

Close this issue as the vote is passed.

> IP clearance for ServiceComb Toolkit
> 
>
> Key: INCUBATOR-239
> URL: https://issues.apache.org/jira/browse/INCUBATOR-239
> Project: Incubator
>  Issue Type: Task
>    Reporter: Willem Jiang
>Priority: Major
> Attachments: servicecomb-toolkit.zip
>
>
> Mabin is contributing the Toolkit to Apache ServiceComb.
> The clearance tasks are in progress and recorded at: 
> https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as toolkit-master.zip
> md5sum toolkit-master.zip
> MD5 (toolkit-master.zip) = 8bbf00a59e0476192d3dced20e2565ef



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Commented] (INCUBATOR-239) IP clearance for ServiceComb Toolkit

2019-06-17 Thread Willem Jiang (JIRA)


[ 
https://issues.apache.org/jira/browse/INCUBATOR-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866091#comment-16866091
 ] 

Willem Jiang commented on INCUBATOR-239:


Here is the IPMC vote thread: 
https://lists.apache.org/thread.html/2f594db8765c0e66f29002b8bf262698177bf718f70c7559eb232806@%3Cgeneral.incubator.apache.org%3E
and result thread:
https://lists.apache.org/thread.html/19bf2061be6e6ad77c9f325b3bd8354665272b611eec87006e58d73a@%3Cgeneral.incubator.apache.org%3E


> IP clearance for ServiceComb Toolkit
> 
>
> Key: INCUBATOR-239
> URL: https://issues.apache.org/jira/browse/INCUBATOR-239
> Project: Incubator
>  Issue Type: Task
>    Reporter: Willem Jiang
>Priority: Major
> Attachments: servicecomb-toolkit.zip
>
>
> Mabin is contributing the Toolkit to Apache ServiceComb.
> The clearance tasks are in progress and recorded at: 
> https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as toolkit-master.zip
> md5sum toolkit-master.zip
> MD5 (toolkit-master.zip) = 8bbf00a59e0476192d3dced20e2565ef



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



Re: [IP CLEARANCE] ServiceComb Toolkit project contribution

2019-06-17 Thread Willem Jiang
72 hours passed. We got none -1 vote.

Based on lazy consensus, this vote passed. I will update the
ip-clearance page for the vote information.


Thanks.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Jun 12, 2019 at 9:31 PM Willem Jiang  wrote:
>
> Hi Incubator PMC,
>
> The TLP Apache ServiceComb has been donated code for a toolkit, being
> referred to as `servicecomb-toolkit`[1], old hostsd at MaBin's
> personal repo[2].
>
> This is the formal request for IP clearance to be checked as per [3].
> The donated code can be found at [4] .
>
> Please check the ip-clearance filed here[5] for more information.
> The PMC has voted and passed to accept this donation.
> The ICLA of major contributors, Bin Ma and Lisen Sun have been filed
> before.
> The SGA from Huawei has been filed.
>
> Please vote to approve this contribution.
>
> This majority vote is open for at least 72 hours and as usual lazy
> consensus applies.
>
> [1]https://github.com/apache/servicecomb-toolkit
> [2]https://github.com/MabinGo/toolkit
> [3]https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling
> [4]https://issues.apache.org/jira/browse/INCUBATOR-239
> [5]https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html
>
> Willem Jiang

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



[IP CLEARANCE] ServiceComb Toolkit project contribution

2019-06-12 Thread Willem Jiang
Hi Incubator PMC,

The TLP Apache ServiceComb has been donated code for a toolkit, being
referred to as `servicecomb-toolkit`[1], old hostsd at MaBin's
personal repo[2].

This is the formal request for IP clearance to be checked as per [3].
The donated code can be found at [4] .

Please check the ip-clearance filed here[5] for more information.
The PMC has voted and passed to accept this donation.
The ICLA of major contributors, Bin Ma and Lisen Sun have been filed
before.
The SGA from Huawei has been filed.

Please vote to approve this contribution.

This majority vote is open for at least 72 hours and as usual lazy
consensus applies.

[1]https://github.com/apache/servicecomb-toolkit
[2]https://github.com/MabinGo/toolkit
[3]https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling
[4]https://issues.apache.org/jira/browse/INCUBATOR-239
[5]https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html

Willem Jiang

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



[jira] [Updated] (INCUBATOR-239) IP clearance for ServiceComb Toolkit

2019-06-12 Thread Willem Jiang (JIRA)


 [ 
https://issues.apache.org/jira/browse/INCUBATOR-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated INCUBATOR-239:
---
Attachment: servicecomb-toolkit.zip

> IP clearance for ServiceComb Toolkit
> 
>
> Key: INCUBATOR-239
> URL: https://issues.apache.org/jira/browse/INCUBATOR-239
> Project: Incubator
>  Issue Type: Task
>    Reporter: Willem Jiang
>Priority: Major
> Attachments: servicecomb-toolkit.zip
>
>
> Mabin is contributing the Toolkit to Apache ServiceComb.
> The clearance tasks are in progress and recorded at: 
> https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as toolkit-master.zip
> md5sum toolkit-master.zip
> MD5 (toolkit-master.zip) = 8bbf00a59e0476192d3dced20e2565ef



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Created] (INCUBATOR-239) IP clearance for ServiceComb Toolkit

2019-06-12 Thread Willem Jiang (JIRA)
Willem Jiang created INCUBATOR-239:
--

 Summary: IP clearance for ServiceComb Toolkit
 Key: INCUBATOR-239
 URL: https://issues.apache.org/jira/browse/INCUBATOR-239
 Project: Incubator
  Issue Type: Task
Reporter: Willem Jiang


Mabin is contributing the Toolkit to Apache ServiceComb.

The clearance tasks are in progress and recorded at: 
https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html

This issue is partly to track that and primarily to provide an official record 
of the code drop contribution. The contributed code is attached to this issue 
as toolkit-master.zip

md5sum toolkit-master.zip

MD5 (toolkit-master.zip) = 8bbf00a59e0476192d3dced20e2565ef





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



Re: [VOTE] Release Apache Zipkin Reporter (incubating) version 2.8.3

2019-05-31 Thread Willem Jiang
+1 (binding)

Here are what I checked
* Built the kit from source
* Checked the release tag and release note
* There is no binary in the source release kit
* License and Notice are OK

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Tue, May 28, 2019 at 12:56 AM Jorge Quilcate
 wrote:
>
> Hello All,
>
> This is a call for vote to release Apache Zipkin Reporter
> (Incubating) version 2.8.3
>
> The Apache Zipkin community has voted on and approved a proposal to
> release Apache Zipkin Reporter (Incubating) version 2.8.3.
>
> We now kindly request the Incubator PMC members review and vote on
> this incubator release.
>
> Apache Zipkin Reporter (Incubating) is the component that send spans 
> collected on the client-side to the Zipkin Server, via different kind of 
> transports.
>
> Zipkin community vote and result thread: 
> https://lists.apache.org/thread.html/33ad2ce409c5d08e4193d317200bf0bb95a4cf217eefec424826ace0@%3Cdev.zipkin.apache.org%3E
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/zipkin/zipkin-reporter-java/2.8.3/
>
> Git tag for the release:
> https://github.com/apache/incubator-zipkin-reporter-java/tree/v2.8.3
>
> Hash for the release tag: e6791fcd4081fb58cd9d5f7e3eac42fbbb034d51
>
> Release Notes:
> https://github.com/apache/incubator-zipkin-reporter-java/releases/tag/v2.8.3
>
> The artifacts have been signed with Key : BB67A050, which can be found
> in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/zipkin/KEYS
>
> Verification Hints:
> For your convenience, the below includes detailed how-to on verifying
> a source release. Please note that this document is a work-in-progress
> https://cwiki.apache.org/confluence/display/ZIPKIN/Verifying+a+Source+Release
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Zipkin (Incubating) Team
>
> -
> To unsubscribe, e-mail:general-unsubscr...@incubator.apache.org
> For additional commands, e-mail:general-h...@incubator.apache.org
>

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



Re: [VOTE] Release Apache Zipkin Dependencies (incubating) version 2.2.0

2019-05-26 Thread Willem Jiang
+1.

I checked:

Built the source code,
Checked the License, Notices and DISCLAIMER files
Checked the signed key and sha
The artifact name has the incubating word

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, May 26, 2019 at 1:59 PM Raja Sundaram Ganesan
 wrote:
>
> Hello IPMC
> The Apache Zipkin community has voted on and approved a proposal to
> release Apache
> Zipkin Dependencies (incubating) version
> 2.2.0. The voting thread can be found here:
> https://lists.apache.org/thread.html/3e472622402e28eb16138fd2886f7dfc9207e5958ff3c617e65a957b@%3Cdev.zipkin.apache.org%3E
> Two binding +1 vote from mentors Sheng Wu and Andriy Redko carry over from
> the dev list thread.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Zipkin Dependencies is an Apache Spark job that will collect spans from
> your datastore, analyze links between services, and store them for later
> presentation in the web UI
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/zipkin/zipkin-dependencies/2.2.0/
>
> Git tag for the release:
> https://github.com/apache/incubator-zipkin-dependencies/tree/v2.2.0
>
> Hash for the release tag: 7d40f7be565116da3117f8ac24db3023a2183bd2
>
> Release Notes:
> https://github.com/apache/incubator-zipkin-dependencies/releases/tag/v2.2.0
>
> The artifacts have been signed with Key: DA805D02, which can be found in
> the keys file:
>
> https://www.apache.org/dist/incubator/zipkin/KEYS
>
> Verification Hints:
> For your convenience, the below includes a detailed how-to on verifying a
> source release. Please note that this document is a
> work-in-progress
> https://cwiki.apache.org/confluence/display/ZIPKIN/Verifying+a+Source+Release
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Zipkin (Incubating) Team
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@zipkin.apache.org
> For additional commands, e-mail: dev-h...@zipkin.apache.org

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



Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

2019-05-18 Thread Willem Jiang
Yes, we (mentors of Zipkin) were informed about the vote in private mail.
I think it should be fine to ping mentor privately about the release
vote, as we cannot always monitor the dev mailing list.
Otherwise, it will some time for us to response the release vote.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, May 18, 2019 at 5:39 PM Adrian Cole  wrote:
>
> > Can you point me to where the PPMC has a discussion about this?
>
> I nagged our mentors privately to vote and mentioned that I would be
> trying a concurrent vote.
>
> Everyone in our PPMC is aware of the vote delay problem and this
> thread. We have had numerous discussions about this topic since
> incubation.
>
> -
> 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 Zipkin (incubating) version 2.14.0

2019-05-18 Thread Willem Jiang
As mentor is member of PPMC and IPMC, it could speed up the voting
process by getting the mentor involved at the earlier stage.
Normally we just wait for the PPMC to do the technical check then we
go through the License check in the IPMC vote.
But for Zipkin,  there are lots of community releases which are built
on top of auto tools,  so I think it's much safer for us to start a
parallel vote both PPMC and IPMC.

Any thoughts?

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem



On Fri, May 17, 2019 at 4:54 PM Justin Mclean  wrote:
>
> Hi,
>
> > This vote is running concurrent with the above, carrying over 3
> > binding +1 votes from mentors Willem Ning Jiang, Sheng Wu and Andriy
> > Redko.
>
> Given that people can change their vote I would suggest you not do this in 
> future but wait until the podling vote is over. If an issue was found and the 
> vote cancelled then IPMC may not be so inclined to vote of future votes, it 
> also means you’re asking the IPMC to vote without full information on the 
> outcome of the podling vote. there are no carry over votes here because the 
> voting on the podling list has not been finished.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: [VOTE] Release Apache Weex (Incubating) 0.24.0-RC3

2019-05-18 Thread Willem Jiang
+1. (binding)

Here what I checked:
Signed key and hash code are OK
No binary in the source artifact
Notice and Disclaimer files are OK,
We need to polish the License file as Justin had mentioned in next release.
I also find a minor issue of License file
  I cannot find the License information about webkit from here[1],
but I find the license information here[2].
  I think we should update the License file for it.


[1]https://svn.webkit.org/repository/webkit/releases/WebKitGTK/webkit-2.17.4/
[2]https://webkit.org/licensing-webkit/

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, May 13, 2019 at 11:06 AM 申远  wrote:
>
> Dear community,
>
> This is a call for releasing Apache Weex(Incubating) 0.24.0-RC3.
>
> The Apache Weex community has voted and approved the proposal to release
> Apache Weex (Incubating) version 0.24.0-RC3, we now kindly request the
> Incubator PMC members to review and vote on this incubator release.
>
>- Vote thread:
>
> https://lists.apache.org/thread.html/af68fda5a0c5cbceadb6b0a93a1a35d8f9e13e13a3e3f69f7bf37886@%3Cdev.weex.apache.org%3E
>- Vote result thread:
>
> https://lists.apache.org/thread.html/dc1499106878f647da051b0e7e1c526f3853214af4f2208323e321da@%3Cdev.weex.apache.org%3E
>- Git tag for this Release:
>https://github.com/apache/incubator-weex/tree/0.24.0-RC3
>- The source tarball could be found at :
> *https://dist.apache.org/repos/dist/dev/incubator/weex/0.24.0/RC3/apache-weex-incubating-0.24.0-RC3-src.tar.gz
>
> <https://dist.apache.org/repos/dist/dev/incubator/weex/0.24.0/RC3/apache-weex-incubating-0.24.0-RC3-src.tar.gz>*
>- The signature of the source tarball could be found at :
> *https://dist.apache.org/repos/dist/dev/incubator/weex/0.24.0/RC3/apache-weex-incubating-0.24.0-RC3-src.tar.gz.asc
>
> <https://dist.apache.org/repos/dist/dev/incubator/weex/0.24.0/RC3/apache-weex-incubating-0.24.0-RC3-src.tar.gz.asc>*
>- The SHA-512 checksum of the source tarball could be found at :
> *https://dist.apache.org/repos/dist/dev/incubator/weex/0.24.0/RC3/apache-weex-incubating-0.24.0-RC3-src.tar.gz.sha512
>
> <https://dist.apache.org/repos/dist/dev/incubator/weex/0.24.0/RC3/apache-weex-incubating-0.24.0-RC3-src.tar.gz.sha512>*
>- The source tarball is signed with Key: EC0B28566883F364, which could
>be found in the key file: https://dist.apache.org/repos/dist/release
>/incubator/weex/KEYS
>- ChangeLog about this version:
>https://github.com/apache/incubator-weex/blob/0.24.0-RC3/CHANGELOG.md
>
> One can build the binary from source according to
> https://github.com/apache/incubator-weex/blob/0.24.0-RC3/HOW-TO-BUILD.md#build-all-by-script
> with
> corresponding compiling tools.
>
> Note:
>
>- The building scripts of Weex relies on XCode/NPM/Android SDK/Android
>NDK 13/Android NDK 16, *it would not be a surprise if your build fails
>on non-Mac environment or without corresponding software**.*
>- *Though PPMC members tested the building process in their computers,
>one may still meet compiling problems as the complexity of the compiling
>procedure (You are going to compile JS/Android/iOS/C++ together in order to
>build Weex).*
>
> This vote will remain open for at least 72 hours.
> Please vote on releasing this RC.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Best Regards,
> YorkShen
>
> 申远

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



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

2019-05-02 Thread Willem Jiang
+1 (binding).

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 1, 2019 at 9:44 AM Huxing Zhang  wrote:
>
> Hi All,
>
> After discussion in the Apache Dubbo community on the dev mailing
> list[1], choosing PMC chair[2], forming the PMC members[3], completing
> the maturity model[4], discussing the resolution proposal[5], and
> voting for the graduation[6], the Dubbo community has presented the
> draft resolution for discussion[7] to the incubator community. In the
> discussion, the Dubbo community has cleared the branding issues for
> 3rd party Github group[8].
>
> Apache Dubbo entered incubator in February 2018. During incubation,
> there has been:
> - 11 releases with 7 different release managers.
> - 6 new PPMC members. (17 in total, excluding mentors). The PPMC
> members varies from Alibaba, Jingdong, Youzan, Weidian, Netease,
> Meituan-Dianping, Qunar. [9]
> - 15 new committers. The committers varies from Alibaba, Weidian,
> Jingdong, Qunar, Youzan, Netease, Meituan-Dianping, Rongguan,
> Handuyishe, Didi, NetsUnion, Caocaokeji, Huawei, GomeFinance,
> Asiainfo-sec, iFlytek, Keep and etc. [9]
> - 192 contributors grown from 70+ for the incubator-dubbo repository.
> - 1401 issues and 1168 pull requests closed.
> - 140+ companies using Dubbo in production.
> - 393 subscriber for the dev@ mailing list
> - 5209 emails sent by 261 people, divided into 2160 topics
>
> Now the Dubbo community are bringing the attached draft resolution up
> for a formal IPMC VOTE.
>
> Please take a minute to vote on whether or not Apache Dubbo should
> graduate to a Top Level Project by responding with one of the following:
>
> [ ] +1 Apache Dubbo should graduate.
> [ ] +0 No opinion
> [ ] -1 Apache Dubbo should not graduate (please provide the reason)
>
> The VOTE is open for a minimum of 72 hours.
>
> -
> Establish the Apache Dubbo 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 high-performance, lightweight, java based RPC framework.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Dubbo Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Dubbo Project be and hereby is responsible for
> the creation and maintenance of software related to a high-performance,
> lightweight, java based RPC framework; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Dubbo" 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 Dubbo
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Dubbo 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 Dubbo Project:
>
>  * Huxing Zhang   
>  * Ian Luo
>  * Jun Liu
>  * Justin Mclean  
>  * Kimm King  
>  * Liang Zhang
>  * Liujie Qin 
>  * Mercy Ma   
>  * Minxuan Zhuang 
>  * Shang Zonghai  
>  * Von Gosling
>  * Xin Wang   
>  * Yong Zhu   
>  * Yuhang Xiu 
>  * YunKun Huang   
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ian Luo be appointed to the
> office of Vice President, Apache Dubbo, to serve in accordance with and
> subject to the direction of the Board of Directors and the Bylaws of the
> Foundation until death, resignation, retirement, removal or
> disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the Apache Dubbo Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Dubbo podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Dubbo podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
> -
>
> [1] 
> https://lists.apache.org/thread.html/767da61f249789f09665a52a241e3b352d168fec051ee7dd1dd7c20b@%3Cdev.dubbo.apache.org%3E
> [2] 
> https://lists.apache.org/thread.html/537a7a88ab19ffee31c0b642ff6239372aa063985846febe2ad11d91@%3Cdev.dubbo.apache.org%3E
> [3] 
> https://lists.apache.org/thread.html/b7218b3b441f7a96e1d339e1eeea60e8bba9b06295e73b56659524c0@%3Cdev.dubbo.apache.org%3E
> [4] 
> https://github.com/apache/inc

Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project

2019-05-02 Thread Willem Jiang
I'm happy to see the common Dubbo release practices could guide other
incubating project. It's not a rocket science, we just need pay more
attentions on the first and second around release to setup right
release procedure and building scripts.  Please make sure the team
member aware of this guide when they doing the release.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 1, 2019 at 11:43 PM Ian Luo  wrote:
>
> We have a concrete release guide [1]  to guide team to perform an apache
> release. @adrianfcole tweet this:
>
> I am always referencing #dubbo's Apache release guide. It probably needs to
> > move to be..Apache's release guide.
>
>
> But I like your idea of a release manager team. We will have much more
> Dubbo relevant projects after we finish transferring them from dubbo group
> to ASF. Those who have release experience should take closer eyes in this
> area, but in my own opinion, we will encourage more committers to take
> release engineer role, only if they strictly follow Dubbo's release guide.
>
> Regards,
> -Ian.
>
>
> 1.
> http://dubbo.apache.org/en-us/docs/developers/committer-guide/release-guide_dev.html
>
> On Wed, May 1, 2019 at 4:27 PM Willem Jiang  wrote:
>
> > As there are some new subproject join the dubbo project. I think it
> > could be a challenge to make sure all these new sub projects are
> > following the Apache release rules. Did you have any plan to do this?
> > Maybe a release manager team could help the new committer to do the
> > first few release check.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Apr 30, 2019 at 2:52 PM Huxing Zhang  wrote:
> > >
> > > Hi community,
> > >
> > > It looks like all the questions and concerns have been cleared.
> > > If there is no other comments, I am planning to start the formal vote
> > tomorrow.
> > >
> > > --
> > > Best Regards!
> > > Huxing
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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



Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project

2019-05-02 Thread Willem Jiang
Yeah, it's a good plan that the experienced PPMC can help other new
project members.
We just need to make sure it's on the good track.

It's good to see Dubbo is near graduation by the way.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 1, 2019 at 11:33 PM Huxing Zhang  wrote:
>
> Hi,
>
> On Wed, May 1, 2019 at 4:27 PM Willem Jiang  wrote:
> >
> > As there are some new subproject join the dubbo project. I think it
> > could be a challenge to make sure all these new sub projects are
> > following the Apache release rules. Did you have any plan to do this?
>
> I was thinking about this. IMO, the new coming projects will not be
> able to do any releases because the project owners/contributors does
> not have write access to it. However,  the PPMC need to keep a close
> eye on the projects and the external repository like npm, pip, docker
> hub, etc. to make sure there is no unapproved releases.
> The Dubbo PPMC will vote them in as committers with standard Apache
> way, after that the PPMC will work with them to make their first
> Apache releases, just like how IPMC help Dubbo to make the releases.
> Because the Dubbo community has conducted 11 releases with 7 release
> managers since incubation, and the release guide is well documented[1]
> with checklist and scripts. I think the Dubbo community has
> demonstrated the ability to make release that complies Apache release
> policy.
> How do you think?
>
> [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
>
> > Maybe a release manager team could help the new committer to do the
> > first few release check.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Apr 30, 2019 at 2:52 PM Huxing Zhang  wrote:
> > >
> > > Hi community,
> > >
> > > It looks like all the questions and concerns have been cleared.
> > > If there is no other comments, I am planning to start the formal vote 
> > > tomorrow.
> > >
> > > --
> > > Best Regards!
> > > Huxing
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> --
> Best Regards!
> Huxing
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project

2019-05-01 Thread Willem Jiang
As there are some new subproject join the dubbo project. I think it
could be a challenge to make sure all these new sub projects are
following the Apache release rules. Did you have any plan to do this?
Maybe a release manager team could help the new committer to do the
first few release check.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Apr 30, 2019 at 2:52 PM Huxing Zhang  wrote:
>
> Hi community,
>
> It looks like all the questions and concerns have been cleared.
> If there is no other comments, I am planning to start the formal vote 
> tomorrow.
>
> --
> Best Regards!
> Huxing
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: [VOTE] Release Apache Zipkin Layout Factory (incubating) version 0.0.5

2019-05-01 Thread Willem Jiang
+1 (binding)

I did these verifications
1.  Checked singed key and sha512
2.  Checked LICENSE , NOTICE and DISCLAIMER
3.  Built from the source


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Apr 29, 2019 at 7:01 PM Jorge Quilcate  wrote:
>
> Hello All,
>
> This is a call for vote to release Apache Zipkin Layout Factory
> (Incubating) version 0.0.5
>
> The Apache Zipkin community has voted on and approved a proposal to
> release Apache Zipkin Layout Factory (Incubating) version 0.0.5.
>
> We now kindly request the Incubator PMC members review and vote on
> this incubator release.
>
> Apache Zipkin Layout Factory (Incubating) is a Spring Boot layout used by 
> Zipkin plugable components (e.g. collectors) during building process.
>
> Zipkin community vote and result thread: 
> https://lists.apache.org/thread.html/d9119b0c8f7b8dd87627c69d23ef5bf257f1a9d9a8ed9018be017b7b@%3Cdev.zipkin.apache.org%3E
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/zipkin/zipkin-layout-factory/0.0.5/
>   <https://dist.apache.org/repos/dist/dev/incubator/zipkin/brave-karaf/0.1.2/>
>
> Git tag for the release:
> https://github.com/apache/incubator-zipkin-layout-factory/tree/v0.0.5  
> <https://github.com/apache/incubator-zipkin-brave-karaf/tree/v0.1.2>
>
> Hash for the release tag:
> 23dbddb426b4113c4b8633808b9ff0df3454e201
>
> Release Notes:
> https://github.com/apache/incubator-zipkin-layout-factory/releases/tag/v0.0.5 
>  <https://github.com/apache/incubator-zipkin-brave-karaf/releases/tag/v0.1.2>
>
> The artifacts have been signed with Key : BB67A050, which can be found
> in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/zipkin/KEYS
>
> Verification Hints:
> For your convenience, the below includes detailed how-to on verifying
> a source release. Please note that this document is a work-in-progress
> https://cwiki.apache.org/confluence/display/ZIPKIN/Verifying+a+Source+Release
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Zipkin (Incubating) Team
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: Re: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]

2019-04-22 Thread Willem Jiang
I think we could put it into the wiki page to let other community
developers know about the policy.
BTW, we could also put the license check into the checklist of release
candidate.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Apr 22, 2019 at 1:38 PM kezhenxu94  wrote:
>
> Hi All,
>   I've excluded the `hibernate-core` dependency and verified as follows:
>
>
> $ mvn license:add-third-party -Dlicense.useMissingFile
> $ cat dubbo-admin-server/target/generated-sources/license/THIRD-PARTY.txt | 
> grep "General Public License"
>
>
> here is the output
>
>
>  (Eclipse Public License - v 1.0) (GNU Lesser General Public License) 
> Logback Classic Module (ch.qos.logback:logback-classic:1.2.3 - 
> http://logback.qos.ch/logback-classic)
>  (Eclipse Public License - v 1.0) (GNU Lesser General Public License) 
> Logback Core Module (ch.qos.logback:logback-core:1.2.3 - 
> http://logback.qos.ch/logback-core)
>
>
> also, I've tested that the functionality introduced together with this 
> dependency[1] works well.
>
>
> I'll check the license next time when I need to introduce new dependencies.
> [1] https://github.com/apache/incubator-dubbo-admin/pull/324
>
>
> Thanks
>
>
> At 2019-04-22 10:17:43, "Huxing Zhang"  wrote:
> >Hi,
> >
> >On Sun, Apr 21, 2019 at 11:11 PM Sheng Wu  wrote:
> >>
> >> Hi.
> >>
> >> > 1. Stop distribute the binary of incubator-dubbo-admin
> >>
> >> I think "stop distribute the binary" would NOT change the fact the source
> >> release could lead users to use `hiberante-core`. I doubt this is an 
> >> option.
> >
> >That option is based on my understanding that linking to
> >"hibernate-core" does not create a derivative work of
> >"hibernate-core".
> >Yes, when compiling the source code and run the incubator-dubbo-admin
> >code, the hibernate-core binary will be included, this
> >will create a derivative work of "hibernate-core". As long as user do
> >not distribute it, I think it is fine to use it.
> >This is the same case as using "spring-boot-starter-data-jpa".
> >However, it becomes a problem when user want to distributed the
> >incubator-dubbo-admin binary, it must not be licensed as Apache
> >license, but should only be GPL/LGPL licensed.
> >This creates a risk that some user won't use this software because of
> >the potential license issue, which is not what we want.
> >So as long as an Apache project does not distribute the binary, IMO it is 
> >fine.
> >That is my understanding of why this is an option. It is not a good
> >option, but I think it is an option.
> >
> >>
> >> Also based on the license issue, you should consider canceling this vote,
> >> and move the further discussion to dev ml.
> >
> >I agree that cancel this vote is the safest way for now, before
> >everything is cleared.
> >
> >>
> >>
> >> Sheng Wu 吴晟
> >>
> >> Apache SkyWalking, ShardingSphere, Zipkin
> >> Twitter, wusheng1108
> >>
> >>
> >> Huxing Zhang  于2019年4月21日周日 下午11:02写道:
> >>
> >> > Hi,
> >> >
> >> > I am thinking why spring-boot-starter-data-jpa depends on LGPL
> >> > licensed library "hibernate-core", and can still be Apache 2.0
> >> > licensed.
> >> > I am reading [1]. In section 5 it says:
> >> >
> >> > A program that contains no derivative of any portion of the Library,
> >> > but is designed to work with the Library by being compiled or linked
> >> > with it, is called a "work that uses the Library". Such a work, in
> >> > isolation, is not a derivative work of the Library, and therefore
> >> > falls outside the scope of this License.
> >> >
> >> > I think spring-boot-starter-data-jpa falls in to this case. It is a
> >> > "work that uses the Library".
> >> >
> >> > The source code of incubator-dubbo-admin should also falls into this
> >> > case, because it does not contain any portion of the hibernate-core.
> >> > Based on it and explanation here[2], I think the source code can be
> >> > released anyway. Is my understanding correct?
> >> >
> >> > Next, the LGPL license says:
> >> >
> >> > However, linking a "work that uses the Library" with the Library
> >> > creates an executable that is a derivative of the Library (because it

Re: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]

2019-04-19 Thread Willem Jiang
Hi,

EclipseLink[1] is a JPA implementation which we can use in Apache Product.
You can fix the issue by replace Hibernate dependencies with EclipseLink.

You can take ServiceComb-Pack[2] as an example, we used to have the
dependency of Hibernate by using the spring-boot-jpa by default, but
we changed it when we move the project into Apache.

[1]https://www.eclipse.org/eclipselink/
[2]https://github.com/apache/servicecomb-pack/blob/master/persistence/persistence-jpa/pom.xml#L62

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Apr 19, 2019 at 9:44 AM Minxuan Zhuang  wrote:
>
> Hi Willem Jiang:
> there's no EcpliseLink for the hibernate library we include in the
> binary release:  https://github.com/hibernate/hibernate-orm/tree/5.2.7
>
> On Fri, Apr 19, 2019 at 8:24 AM Willem Jiang  wrote:
>
> > Hi,
> >
> > I just checked the binary release kit, it has the third party
> > dependency of LGPL (Hibernate core) which is belonged to Cataloge
> > X[1],  it cannot be included in Apache Product.
> > I had to vote -1 for it. We can change the ORM lib to Eclipse Link to
> > fix this issue, I just fill an issue here[2].
> >
> > [1]https://www.apache.org/legal/resolved.html#category-x
> > [2]https://github.com/apache/incubator-dubbo-admin/issues/366
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Mon, Apr 15, 2019 at 10:24 AM Minxuan Zhuang 
> > wrote:
> > >
> > > Hello Incubator Community,
> > >
> > > The Apache Dubbo community has voted on and approved a proposal to
> > release
> > > Apache Dubbo Admin (Incubating) version 0.2.0.
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > Apache Dubbo™ (incubating) is a high-performance, java based, open source
> > > RPC framework. Dubbo offers three key functionalities, which include
> > > interface based remote call, fault tolerance & load balancing, and
> > > automatic service registration & discovery.
> > >
> > >
> > > Dubbo community vote and result thread:
> > >
> > https://lists.apache.org/thread.html/fc71a5f8c93b8c3606338b97a08c044af64ca3165e226aed37295a45@%3Cdev.dubbo.apache.org%3E
> > >
> > > The release candidates (RC3):
> > > *
> > https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0
> > > <
> > https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0/
> > >/*
> > >
> > >
> > > Git tag for the release (RC3):
> > > https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
> > >
> > > Hash for the release tag:
> > > 37e23a7354e3da50914e075eb4676c7c2875ffa7
> > >
> > > Release Notes:
> > > https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
> > >
> > >
> > > The artifacts have been signed with Key :
> > > DA2108479B0C1E71, which can be
> > > found in the keys file:
> > > *https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
> > > <https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS>*
> > >
> > > The vote will be open for at least 72 hours or until necessary number of
> > > votes are reached.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Thanks,
> > > The Apache Dubbo (Incubating) Team
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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



Re: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]

2019-04-19 Thread Willem Jiang
If you extract the dubbo-admin-0.2.0.jar from the
apache-dubbo-admin-incubating-0.2.0-bin.zip, you can find the
hibernate-core-5.2.17.Final.jar in the BOOT-INF/lib directory.
I found this issue by going through the License file of the bin.zip
file, it lists the LGPL library of Hibernate.
Event you just have the dependency of spring-boot-jpa, you still need
to check final dependencies of spring-boot application.

[1]https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0/apache-dubbo-admin-incubating-0.2.0-bin.zip

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Apr 19, 2019 at 1:36 PM Minxuan Zhuang  wrote:
>
> hi Craig:
>we do not depend hibernate directly, they are imported by spring boot web
>
> On Fri, Apr 19, 2019 at 11:31 AM Craig Russell  wrote:
>
> > I don't know if it helps, but there are Apache Projects for both
> > relational database (Derby) and ORM (OpenJPA) that can be included in
> > binary releases.
> >
> > So we should never need to bundle LGPL or Category X projects with binary
> > releases.
> >
> > Craig
> >
> > > On Apr 18, 2019, at 5:23 PM, Willem Jiang 
> > wrote:
> > >
> > > Hi,
> > >
> > > I just checked the binary release kit, it has the third party
> > > dependency of LGPL (Hibernate core) which is belonged to Cataloge
> > > X[1],  it cannot be included in Apache Product.
> > > I had to vote -1 for it. We can change the ORM lib to Eclipse Link to
> > > fix this issue, I just fill an issue here[2].
> > >
> > > [1]https://www.apache.org/legal/resolved.html#category-x
> > > [2]https://github.com/apache/incubator-dubbo-admin/issues/366
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Mon, Apr 15, 2019 at 10:24 AM Minxuan Zhuang 
> > wrote:
> > >>
> > >> Hello Incubator Community,
> > >>
> > >> The Apache Dubbo community has voted on and approved a proposal to
> > release
> > >> Apache Dubbo Admin (Incubating) version 0.2.0.
> > >>
> > >> We now kindly request the Incubator PMC members review and vote on this
> > >> incubator release.
> > >>
> > >> Apache Dubbo™ (incubating) is a high-performance, java based, open
> > source
> > >> RPC framework. Dubbo offers three key functionalities, which include
> > >> interface based remote call, fault tolerance & load balancing, and
> > >> automatic service registration & discovery.
> > >>
> > >>
> > >> Dubbo community vote and result thread:
> > >>
> > https://lists.apache.org/thread.html/fc71a5f8c93b8c3606338b97a08c044af64ca3165e226aed37295a45@%3Cdev.dubbo.apache.org%3E
> > >>
> > >> The release candidates (RC3):
> > >> *
> > https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0
> > >> <
> > https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0/
> > >/*
> > >>
> > >>
> > >> Git tag for the release (RC3):
> > >> https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
> > >>
> > >> Hash for the release tag:
> > >> 37e23a7354e3da50914e075eb4676c7c2875ffa7
> > >>
> > >> Release Notes:
> > >> https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
> > >>
> > >>
> > >> The artifacts have been signed with Key :
> > >> DA2108479B0C1E71, which can be
> > >> found in the keys file:
> > >> *https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
> > >> <https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS>*
> > >>
> > >> The vote will be open for at least 72 hours or until necessary number of
> > >> votes are reached.
> > >>
> > >> Please vote accordingly:
> > >>
> > >> [ ] +1 approve
> > >> [ ] +0 no opinion
> > >> [ ] -1 disapprove with the reason
> > >>
> > >> Thanks,
> > >> The Apache Dubbo (Incubating) Team
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > Craig L Russell
> > c...@apache.org
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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



Re: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]

2019-04-18 Thread Willem Jiang
Hi,

I just checked the binary release kit, it has the third party
dependency of LGPL (Hibernate core) which is belonged to Cataloge
X[1],  it cannot be included in Apache Product.
I had to vote -1 for it. We can change the ORM lib to Eclipse Link to
fix this issue, I just fill an issue here[2].

[1]https://www.apache.org/legal/resolved.html#category-x
[2]https://github.com/apache/incubator-dubbo-admin/issues/366

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Apr 15, 2019 at 10:24 AM Minxuan Zhuang  wrote:
>
> Hello Incubator Community,
>
> The Apache Dubbo community has voted on and approved a proposal to release
> Apache Dubbo Admin (Incubating) version 0.2.0.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Dubbo™ (incubating) is a high-performance, java based, open source
> RPC framework. Dubbo offers three key functionalities, which include
> interface based remote call, fault tolerance & load balancing, and
> automatic service registration & discovery.
>
>
> Dubbo community vote and result thread:
> https://lists.apache.org/thread.html/fc71a5f8c93b8c3606338b97a08c044af64ca3165e226aed37295a45@%3Cdev.dubbo.apache.org%3E
>
> The release candidates (RC3):
> *https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0
> <https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0/>/*
>
>
> Git tag for the release (RC3):
> https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
>
> Hash for the release tag:
> 37e23a7354e3da50914e075eb4676c7c2875ffa7
>
> Release Notes:
> https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
>
>
> The artifacts have been signed with Key :
> DA2108479B0C1E71, which can be
> found in the keys file:
> *https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
> <https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS>*
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Dubbo (Incubating) Team

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



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

2019-04-09 Thread Willem Jiang
+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Apr 9, 2019 at 6:41 PM Geertjan Wielenga
 wrote:
>
> Hi all,
>
> The Apache NetBeans podling community brings the resolution, after
> discussion[1], to become a top level Apache project up for the IPMC vote.
> The PPMC community vote[2] resulted in 64 +1 votes and no 0 or -1 votes,
> further details about the project and what has been done is found in the
> related discussion thread[1].
>
> We have had a long and eventful incubation period and are looking forward
> to graduating and continuing our development and community work with and
> around Apache NetBeans.
>
> The vote is open for 72 hours, assuming that at that stage there are at
> least 3 +1 votes and nothing left open for discussion.
>
> Thanks,
>
> Geertjan
> on behalf of Apache NetBeans PPMC
>
> 1.
> https://lists.apache.org/thread.html/648834cdb10ce55aff2c6c8dd3c32454a74711c6289f385e456b74d8@%3Cgeneral.incubator.apache.org%3E
> 2.
> https://lists.apache.org/thread.html/72e59c722580fef2cbaa637735691a549756aeaa72c4cbf52265fbe0@%3Cdev.netbeans.apache.org%3E
>
> -
>
> Establish the Apache NetBeans 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 providing a development environment, tooling platform, and application
> framework.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache NetBeans Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache NetBeans Project be and hereby is responsible for
> the creation and maintenance of software related to providing a development
> environment, tooling platform, and application framework; and be it further
>
> RESOLVED, that the office of "Vice President, Apache NetBeans" 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 NetBeans Project, and
> to have primary responsibility for management of the projects within the
> scope of responsibility of the Apache NetBeans 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 NetBeans Project:
>
> * Anton Epple 
> * Antonio Vieiro 
> * Aristides Villarreal 
> * Arunava Sinha 
> * Ate Douma 
> * Attila Kelemen 
> * Bertrand Delacretaz 
> * Bruno Flávio 
> * Bruno Souza 
> * Christian Lenz 
> * Constantin Drabo 
> * David Heffelfinger 
> * Daniel Gruno 
> * Dusan Balek 
> * Eirik Bakke 
> * Emilian Bold 
> * Emmanuel Hugonnet 
> * Eric Barboni 
> * Florian Vogler 
> * Geertjan Wielenga 
> * Glenn Holmer 
> * Ivar Grimstad 
> * James Gosling 
> * Jan Lahoda 
> * Jan Pirek 
> * Jaroslav Tulach 
> * Jean-Marc Borer 
> * Jiří Kovalský 
> * Joerg Michelberger 
> * Johan Vos 
> * John Kostaras 
> * John McDonnell 
> * Josh Juneau 
> * José Pereda 
> * Junichi Yamamoto 
> * Kirk Pepperdine 
> * Lars Bruun-Hansen 
> * Laszlo Kishalmi 
> * Leonardo Zanivan 
> * Mark Stephens 
> * Mark Struberg 
> * Martin Entlicher 
> * Martin Klähn 
> * Matthias Bläsing 
> * Michael Müller 
> * Michael Nascimento 
> * Michel Graciano 
> * Neil C Smith 
> * Ralph Benjamin Ruijs 
> * Reema Taneja 
> * Shai Almog 
> * Simon Phipps 
> * Svatopluk Dedic 
> * Sven Reimers 
> * Thilina Ranathunga 
> * Timon Veenstra 
> * Tomas Mysik 
> * Tomas Zezula 
> * Tushar Joshi 
> * Vladimir Voskresensky 
> * Wade Chandler 
> * Zoran Sevarac 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Geertjan Wielenga be appointed
> to the office of Vice President, Apache NetBeans, to serve in accordance
> with and subject to the direction of the Board of Directors and the Bylaws
> of the Foundation until death, resignation, retirement, removal or
> disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the Apache NetBeans Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator NetBeans podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> NetBeans podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

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



Re: [VOTE]: Release Apache Dubbo (Incubating) 2.7.1 [RC1]

2019-03-25 Thread Willem Jiang
+1 (binding)

I checked
the signed key and sha512 are OK
There is incubating name in the released kits.
Checked the License headers of source kit with RAT.
License and Notice file are OK
DISCLAIMER file is OK
I can build the source without any error.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Mar 22, 2019 at 5:09 PM Ian Luo  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache Dubbo (Incubating) version 2.7.1.
>
> The Apache Dubbo community has voted on and approved a proposal to release
> Apache Dubbo (Incubating) version 2.7.1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Dubbo™ (incubating) is a high-performance, java based, open source
> RPC framework. Dubbo offers three key functionalities, which include
> interface based remote call, fault tolerance & load balancing, and
> automatic service registration & discovery.
>
> Dubbo community vote and result thread:
> https://lists.apache.org/thread.html/3c651acf5116895bc5d816ab78858a8bdd198b5b47be9eb9641681e5@%3Cdev.dubbo.apache.org%3E
>
> The release candidates (RC1):
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.7.1
>
> Git tag for the release (RC1):
> https://github.com/apache/incubator-dubbo/tree/dubbo-2.7.1
>
> Hash for the release tag:
> a36cc7520e0150d07d30e8baa0c61d5f9f11e6ed
>
> Release Notes:
> https://github.com/apache/incubator-dubbo/blob/dubbo-2.7.1/CHANGES.md
>
> The artifacts have been signed with Key: 9C44B5A6884984DB, which can be
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
>
> Look at here for how to verify this release candidate:
> https://github.com/apache/incubator-dubbo-website/blob/asf-site/blog/en-us/prepare-an-apache-release.md#prepare-apache-release
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Dubbo (Incubating) Team

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



Re: Incubator wiki being deprecated

2019-03-24 Thread Willem Jiang
Hi WuSheng,

cwiki is LDAP enabled, you should have the access right if you login
with your Apache ID.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Mar 24, 2019 at 9:26 AM 吴晟 Sheng Wu  wrote:
>
> Hi Justin
>
>
> Besides the contents, I think we need to grant access again. I just use my 
> username(wusheng) to login, no right to edit page.
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "justin";
> Date:  Sun, Mar 24, 2019 09:02 AM
> To:  "general";
>
> Subject:  Incubator wiki being deprecated
>
>
>
> Hi,
>
> If you didn’t know the wiki.apache.org system using Moin software is being 
> decommissioned in May 2019. Currently how incubator reports are being created 
> depend on this system and this will need to change.
>
> I’ve created an incubator space [1] and we shovel think about mobbing the 
> content over. There’s a self help migration tool, but given the size of the 
> incubator wiki I’m not 100% sure if that’a a good idea to run.
>
> Thanks,
> Justin
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR
> -
> 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] Recommend 'Apache SkyWalking graduation to Top Level Project' resolution to board

2019-03-21 Thread Willem Jiang
+1 (binding)
It's good to see SkyWalking is growing up.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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

Re: [VOTE] Release Apache Myriad 0.3.0 (incubating) [rc1]

2019-03-17 Thread Willem Jiang
+1. (Binding)

I checked:
+1 (binding)

I checked
Verified the signature and sha512
DISCLAIMER
LICENSE
NOTICE
Can build the key from source.

Here are some minor suggestions which we can fix in next release.
1.  It's a common practice that we add the apache prefix on the artifacts
2.  We could just keep one the config file of checkstyle and findbugs
for all the submodules.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem



Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Tue, Mar 5, 2019 at 11:34 PM Javi Roman  wrote:
>
> Dear all,
>
> The Apache Myriad incubator community has voted on and approved a proposal
> to release Apache Myriad (Incubating) version 0.3.0.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Myriad (incubating) enables co-existence of Apache Hadoop YARN and
> Apache Mesos together on the same cluster and allows dynamic resource
> allocations.
> By running Hadoop YARN as a Mesos framework, YARN applications and Mesos
> frameworks can run side-by-side, dynamically sharing cluster resources (Hadoop
> YARN as a Service).
>
> 1. Apache Myriad PPMC vote thread:
> https://lists.apache.org/thread.html/594992bcf75906abdba2c78aa16ebe26bcac0e13d19696615e961f68@%3Cdev.myriad.apache.org%3E
>
> 2. Apache Myriad PPMC vote result:
> https://lists.apache.org/thread.html/384eacb64de8ee14d89e1b5a1fcdf18bccc90329b7ed6ff62a003e8b@%3Cdev.myriad.apache.org%3E
>
> 3. Here’s the release notes (section 6):
> https://docs.google.com/document/d/1ZZdBFVKyBtQlKRK_O1d_obi5wjRAfmoHFPo_sye7wQY/edit?usp=sharing
>
> 4. The commit to be voted upon is tagged with
> "myriad-0.3.0-incubating-rc1" and is available here:
> https://gitbox.apache.org/repos/asf?p=incubator-myriad.git;a=tree;h=21624e87827dcc1f9899c37e6c35718181efff4a;hb=47d23f5a82cb061ed1e57c4011acf49cff9a1507
>
> 5. The artifacts to be voted upon are located below. Please note that
> this is a Source Release:
> https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.3.0-incubating-rc1/
>
> 6. Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/javiroman.asc
>
> 7. Please note that the release tar ball does not include the gradlew
> script to build. You need to generate one in order to build:
> $ gradle wrapper --gradle-version 2.9
> $ ./gradlew build
>
> We request the permission of IPMC to publish the above release candidate as
> Apache Myriad 0.3.0-incubating. Please try out the package and vote.
>
> The vote is open for a minimum of 72 hours or until the necessary number of
> votes (3 binding +1s) is reached.
>
> [ ] +1 Release this package as Apache Myriad 0.3.0-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Many thanks!
>
> (Volunteer Release Manager of Apache Myriad, incubating 0.3.0
> on behalf on the Apache Myriad PPMC)
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> Apache Id: javiroman
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: [VOTE] Accept DataSketches into the Apache Incubator

2019-03-15 Thread Willem Jiang
+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Mar 15, 2019 at 5:23 AM Kenneth Knowles  wrote:
>
> Hi all,
>
> We've discussed the proposal for the DataSketches project in [1] and [2].
> The
> proposal itself has been put on the wiki [3].
>
> Per incubator rules [4] I'd like to call a vote to accept the new
> "DataSketches" project as a podling in the Apache Incubator.
>
> A vote for accepting a new Apache Incubator podling is a majority vote.
> Everyone is welcome to vote, only Incubator PMC member votes are binding.
> It would be helpful (but not required) if you could add a comment stating
> whether your vote is binding or non-binding.
>
> This vote will run for at least 72 hours (but I expect to keep it open for
> longer). Please VOTE as follows:
>
> [ ] +1 Accept DataSketches into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept DataSketches into the Apache Incubator because ...
>
> Thanks to everyone who contributed to the proposal and discussions.
>
> Kenn
>
> [1]
> https://lists.apache.org/thread.html/329354bd6a463dab56c2539972cfa2d6c6da7c75900216d785db4e3b@%3Cgeneral.incubator.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/c9873cd4fcdc6367bcf530d8fa1ef09f3035f38e7c435e1a79a93885@%3Cgeneral.incubator.apache.org%3E
> [3] https://wiki.apache.org/incubator/DataSketchesProposal
> [4] https://incubator.apache.org/guides/proposal.html#the_vote

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



Re: [VOTE] Release Apache ECharts (incubating) 4.2.1 (release candidate 3)

2019-03-15 Thread Willem Jiang
+1 (binding)

I checked
Verified the signature and sha512
DISCLAIMER
LICENSE
NOTICE
Can build the key from source.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Mar 6, 2019 at 2:58 PM SHUANG SU  wrote:
>
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.2.1 (release candidate 3).
>
> Apache ECharts community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/6f555bdb3bdc23ac9e260116738af779d4dff7b7e21f77c0a3369905@%3Cdev.echarts.apache.org%3E
>
> Results thread:
> https://lists.apache.org/thread.html/54a63e2208330dd68c39bdcb5bd444301d0eb8580d433d1ac3fe4500@%3Cdev.echarts.apache.org%3E
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> The Git commit for this release is:
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=1a2e990
>
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/RELEASE_NOTE.txt
>
> Some shell commands for validating the release:
>
> ```shell
> # Download the release:
> curl
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/apache-echarts-4.2.1-rc.3-incubating-src.zip
> -o apache-echarts-4.2.1-rc.3-incubating-src.zip
> unzip apache-echarts-4.2.1-rc.3-incubating-src.zip -d
> apache-echarts-4.2.1-rc.3-incubating-src > /dev/null
>
> # Rebuild the project (Node.js environment is required):
> cd "apache-echarts-4.2.1-rc.3-incubating-src" && npm install && cd ..
> node "apache-echarts-4.2.1-rc.3-incubating-src/build/build.js" --release
> # (See help: `node
> "apache-echarts-4.2.1-rc.3-incubating-src/build/build.js" --help`)
> ```
>
>
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.2.1 (release candidate 3)
> by "2019-03-09T07:42:38.040Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
>
> --
>  Su Shuang (100pah)
> --

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



Re: [VOTE] Accept Apache TVM into the incubator

2019-03-02 Thread Willem Jiang
+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Feb 28, 2019 at 12:44 PM Markus Weimer  wrote:
>
> Hi everyone,
>
> we've discussed the proposal for the TVM project in [1]. The proposal itself 
> can
> be found on the wiki [2].
>
> According to the Incubator rules[3] I'd like to call a vote to accept the new
> TVM project as a podling in the Apache Incubator.
>
> A vote for accepting a new Apache Incubator podling is a majority vote. 
> Everyone
> is welcome to vote, only Incubator PMC member votes are binding. It would be
> helpful (but not required) if you could add a comment stating whether your 
> vote
> is binding or non-binding.
>
> This vote will run for at least 72 hours (but I expect to keep it open for
> longer). Please VOTE as follows:
>
> [ ] +1 Accept TVM into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept TVM into the Apache Incubator because ...
>
> Thank you for everyone who decided to join in in the past discussions!
>
> Markus
>
> [1]: 
> https://lists.apache.org/thread.html/e2b1fe9ca76422ec80b146a6b120091f2419e2f1c27d57080f39cf6f@%3Cgeneral.incubator.apache.org%3E
>
> [2]: https://wiki.apache.org/incubator/TVMProposal
>
> [3]: https://incubator.apache.org/guides/proposal.html#the_vote
>
> -
> 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: Binary jars in the source release which are only for testing

2019-02-26 Thread Willem Jiang
Thanks all the help from IPMC. I'm sorry I didn't make it clear enough earlier.

Actually, this question is related to recently release check of Apache
Camel[1].  I just found there are some tests jar in the source kit by
applying what I learned from IPMC.  I already submit a quick fix to
eliminate those jars.

[1]https://issues.apache.org/jira/browse/CAMEL-13240

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Feb 26, 2019 at 12:19 AM Craig Russell  wrote:
>
> Hi Willem,
>
> It will help focus this discussion if you tell us what the binary artifacts 
> are and why your normal build process doesn't already build them.
>
> Mark and Christopher described a couple of possible binary files and how to 
> handle them.
>
> But it would be really useful for you to tell us what these files are.
>
> Regards,
>
> Craig
>
> > On Feb 23, 2019, at 11:06 PM, Willem Jiang  wrote:
> >
> > Hi Ted,
> >
> > You made a good point,  I think my solution could be building the jars
> > from source and then using it for testing.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sun, Feb 24, 2019 at 10:02 AM Ted Dunning  wrote:
> >>
> >> Willem,
> >>
> >> This issue of embedded binaries for testing purposes has come up before.
> >> Examples include network intercepts for testing malware detection or class
> >> files for a byte code manipulator. The network files can't easily be
> >> recreated since they were observed in the wild and the class files might
> >> have been produced by a specific (possibly broken) compiler version that
> >> isn't widely available.
> >>
> >> The key question is whether these binaries are derived from some source
> >> that could be compiled instead of distributing the binary objects. Failing
> >> that, can the provenance and justification for the binary object be
> >> described?
> >>
> >>
> >>
> >>
> >> On Sat, Feb 23, 2019 at 6:49 PM Willem Jiang  
> >> wrote:
> >>
> >>> Hi
> >>>
> >>> Thanks Justin for the clarification.  I guess the policy imply the
> >>> source materials cannot have any binary.
> >>> But what if the binary is only for testing, which cannot be part of
> >>> the released software.
> >>> From my point of view, we don't need to modify the source materials
> >>> testing binary to do the software release as it is not a part of the
> >>> binary release of the software.
> >>>
> >>> Any thoughts?
> >>>
> >>> Regards,
> >>>
> >>> Willem Jiang
> >>>
> >>> Twitter: willemjiang
> >>> Weibo: 姜宁willem
> >>>
> >>> On Sat, Feb 23, 2019 at 2:41 PM Justin Mclean 
> >>> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>>> [1]http://www.apache.org/legal/release-policy.html#what
> >>>>
> >>>> It’s explained in that link there i.e.  "The Apache Software Foundation
> >>> produces open source software. All releases are in the form of the source
> >>> materials needed to make changes to the software being released”.
> >>>>
> >>>> Thanks,
> >>>> Justin
> >>>> -
> >>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org <mailto:c...@apache.org> http://db.apache.org/jdo 
> <http://db.apache.org/jdo>

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



Re: Binary jars in the source release which are only for testing

2019-02-23 Thread Willem Jiang
Hi Ted,

You made a good point,  I think my solution could be building the jars
from source and then using it for testing.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Feb 24, 2019 at 10:02 AM Ted Dunning  wrote:
>
> Willem,
>
> This issue of embedded binaries for testing purposes has come up before.
> Examples include network intercepts for testing malware detection or class
> files for a byte code manipulator. The network files can't easily be
> recreated since they were observed in the wild and the class files might
> have been produced by a specific (possibly broken) compiler version that
> isn't widely available.
>
> The key question is whether these binaries are derived from some source
> that could be compiled instead of distributing the binary objects. Failing
> that, can the provenance and justification for the binary object be
> described?
>
>
>
>
> On Sat, Feb 23, 2019 at 6:49 PM Willem Jiang  wrote:
>
> > Hi
> >
> > Thanks Justin for the clarification.  I guess the policy imply the
> > source materials cannot have any binary.
> > But what if the binary is only for testing, which cannot be part of
> > the released software.
> > From my point of view, we don't need to modify the source materials
> > testing binary to do the software release as it is not a part of the
> > binary release of the software.
> >
> > Any thoughts?
> >
> > Regards,
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sat, Feb 23, 2019 at 2:41 PM Justin Mclean 
> > wrote:
> > >
> > > Hi,
> > >
> > > > [1]http://www.apache.org/legal/release-policy.html#what
> > >
> > > It’s explained in that link there i.e.  "The Apache Software Foundation
> > produces open source software. All releases are in the form of the source
> > materials needed to make changes to the software being released”.
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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



Re: Binary jars in the source release which are only for testing

2019-02-23 Thread Willem Jiang
Normally we don't distribute the test jar outside, I'm not sure if I
can find a good place to host these jars.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Feb 24, 2019 at 2:47 PM Alex Harui  wrote:
>
> Or, can you change your build script to download the jar instead of packaging 
> it in the source release?
>
> On 2/23/19, 6:02 PM, "Ted Dunning"  wrote:
>
> Willem,
>
> This issue of embedded binaries for testing purposes has come up before.
> Examples include network intercepts for testing malware detection or class
> files for a byte code manipulator. The network files can't easily be
> recreated since they were observed in the wild and the class files might
> have been produced by a specific (possibly broken) compiler version that
> isn't widely available.
>
> The key question is whether these binaries are derived from some source
> that could be compiled instead of distributing the binary objects. Failing
> that, can the provenance and justification for the binary object be
>     described?
>
>
>
>
> On Sat, Feb 23, 2019 at 6:49 PM Willem Jiang  
> wrote:
>
> > Hi
> >
> > Thanks Justin for the clarification.  I guess the policy imply the
> > source materials cannot have any binary.
> > But what if the binary is only for testing, which cannot be part of
> > the released software.
> > From my point of view, we don't need to modify the source materials
> > testing binary to do the software release as it is not a part of the
> > binary release of the software.
> >
> > Any thoughts?
> >
> > Regards,
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sat, Feb 23, 2019 at 2:41 PM Justin Mclean 
> > wrote:
> > >
> > > Hi,
> > >
> > > > 
> [1]https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Flegal%2Frelease-policy.html%23whatdata=02%7C01%7Caharui%40adobe.com%7Cf5a610c610a847bf492408d699fc1ad8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636865705492422828sdata=aLOPz6UB1Fz4oNJYUYf6LZKwNeTkGhfNC1Q9Nmq6vok%3Dreserved=0
> > >
> > > It’s explained in that link there i.e.  "The Apache Software 
> Foundation
> > produces open source software. All releases are in the form of the 
> source
> > materials needed to make changes to the software being released”.
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>

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



Re: [VOTE] Release Apache Zipkin Brave (incubating) for Apache Karaf version 0.1.2

2019-02-23 Thread Willem Jiang
Hi,

Just forwarding my +1 bind from dev list.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Sat, Feb 23, 2019 at 8:54 AM Adrian Cole  wrote:
>
> Hello All,
>
> This is a call for vote to release Apache Zipkin Brave (incubating)
> for Apache Karaf version 0.1.2
>
> The Apache Zipkin community has voted on and approved a proposal to
> release Apache Zipkin Brave (incubating) for Apache Karaf version
> 0.1.2.
>
> We now kindly request the Incubator PMC members review and vote on
> this incubator release.
>
> Apache Zipkin Brave (incubating) for Apache Karaf sets up tracing
> components such that tools built Karaf needn't configure these
> explicitly.
>
> Zipkin community vote and result thread:
> https://lists.apache.org/thread.html/32baf4b4b65644dd1dd8e2bf0cb360c94f8f939d61c5444b8f4ef45b@%3Cdev.zipkin.apache.org%3E
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/zipkin/brave-karaf/0.1.2/
>
> Git tag for the release:
> https://github.com/apache/incubator-zipkin-brave-karaf/tree/v0.1.2
>
> Hash for the release tag:
> 3cf4ac6577eb0d4775d20f24814e7a0852fa1635
>
> Release Notes:
> https://github.com/apache/incubator-zipkin-brave-karaf/releases/tag/v0.1.2
>
> The artifacts have been signed with Key : BB67A050, which can be found
> in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/zipkin/KEYS
>
> Verification Hints:
> For your convenience, the below includes detailed how-to on verifying
> a source release. Please note that this document is a work-in-progress
> https://cwiki.apache.org/confluence/display/ZIPKIN/Verifying+a+Source+Release
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Zipkin (Incubating) Team
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Re: Binary jars in the source release which are only for testing

2019-02-23 Thread Willem Jiang
Hi

Thanks Justin for the clarification.  I guess the policy imply the
source materials cannot have any binary.
But what if the binary is only for testing, which cannot be part of
the released software.
>From my point of view, we don't need to modify the source materials
testing binary to do the software release as it is not a part of the
binary release of the software.

Any thoughts?

Regards,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Feb 23, 2019 at 2:41 PM Justin Mclean  wrote:
>
> Hi,
>
> > [1]http://www.apache.org/legal/release-policy.html#what
>
> It’s explained in that link there i.e.  "The Apache Software Foundation 
> produces open source software. All releases are in the form of the source 
> materials needed to make changes to the software being released”.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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



Binary jars in the source release which are only for testing

2019-02-22 Thread Willem Jiang
Hi,

I just have a question about the Binary jars in the source release.
According the Apache release policy, I cannot find any rule about the
binary jars cannot be in the source release[1]. If we just have jars
for testing purposes and those jar won't be a part of convenience
binary release, I think it doesn't break the rule below:

"In all such cases, the binary/bytecode package must have the same
version number as the source release and may only add binary/bytecode
files that are the result of compiling that version of the source code
release.".

Is it OK to ship those test binary jars in the source release kit?

[1]http://www.apache.org/legal/release-policy.html#what

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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



Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

2019-02-19 Thread Willem Jiang
I don't think there are some trouble to access apache project website
from China. ServiceComb project has a chinese version[1]. We didn't
get any complain about having trouble to access it from China.

[1]http://servicecomb.apache.org/cn/

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Feb 18, 2019 at 3:08 PM 申远  wrote:
>
> Hi, there
>
> I am a PPMC member of incubator-weex, there is some confusion about
> third-party domain and it seems like difficult to resolve in dev@ mailing
> list, maybe someone here could give a hand to solve the problem of domains.
>
> 1.I 'd like to know if there is a formal rule that projects should use
> xxx.apache.org instead of xxx.io, which is shorter and easier to remember.
> 2. we have another domain  weex-project.io for fast access of Çhinese
> Developers as GFW have some confluence on https://weex.apache.org/cn/. Is
> this against rules for apache project.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> -- Forwarded message -
> From: Dan 
> Date: 2019年2月15日周五 下午2:39
> Subject: [DISCUSS] can we use weex.io as the short domain name for the
> apache project
> To: 
>
>
> Hi, Myrle/Willem,
>
> Currently, we have a domain name of weex.io and want to use it to replace
> the previous weex-project.io domain name for the following reasons:
>
> 1. The domain name is shorter and easier to remember.
> 2. Apache's website has slower access to the developer in China, so there
> is a mirror website weex-project.io for Chinese developer.
> 3. We expect to support https on this website and support some of our own
> server functions, such as Q robots, article blog posts, etc.
>
> I would like to ask if apache has any restrictions on this third-party
> domain name, and look forward to hearing from you.
>
> Thanks,
> Dan

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



  1   2   3   >