Re: [VOTE] Distribution guidelines for platforms

[Gosling Von]

Hi,

+1, binding.

I've been quietly following similar discussion in some different threads, 
because I've had the same issues with mentoring incubators, including help some 
pmc members to release in some TLPs. According to my understanding, whether it 
is incubation project or top-level project, there are some unclear places in 
the distribution, especially after more and more package management tools 
appear, PyPI, NuGet, Helm, DockerHub and so on. I highly respect the 
foundation's concern and effort on intellectual property and brand legal. From 
the perspective of the development of the project, we may need to have more 
flexible mechanisms to ensure that our products are easy to be distributed. 
thus improving the speed of iteration and release flexibility of the products. 
In that point, clarification in incubators is a great thing, and projects can 
learn to adapt to the rules as soon as they are hatched. But I'm also concerned 
about whether the rules should be applied to the top-level projects(Maybe this 
discussion goes beyond IPMC), and I would be totally supportive of such 
continuity and compliance between Podlings and TLPs.


Best Regards,
Von Gosling

> On Jul 21, 2020, at 10:42 AM, Justin Mclean  wrote:
> 
> Hi,
> 
>> This has been in discussion in many threads for more than a year [1] so a 
>> few more days is not a big deal.
> 
> Anyone have anything to add at this point?
> 
> 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: [DISCUSS] project proposal - Apache Sedona

[Gosling Von]

Hi,

This is a very interesting geospatial data processing project. You’ve got a 
good set of mentors!

If you are looking for a fourth mentor then I volunteer if you are interested.

Best Regards,
Von Gosling

> On Jul 9, 2020, at 9:12 PM, Felix Cheung  wrote:
> 
> Hi,
> 
> We would like to propose Apache Sedona, currently known in its community as
> GeoSpark, as a new project under 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 proposal can be found at
> https://cwiki.apache.org/confluence/display/INCUBATOR/Sedona+Proposal
> 
> The project can benefit from and is seeking more experienced mentor.
> 
> Any thought or feedback is appreciated!
> Regards
> Felix


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

[RESULT][VOTE] Accept Pegasus into The Apache Incubation

[Gosling Von]

Hi,

Thanks for reviewing and voting for Pegasus into Apache Incubation, I am happy 
to announce the release voting has passed with 7 +1 binding votes, no +0 or -1 
votes. Details are as follows, the voting thread is here[1].


[Binding]

- Justin Mclean
- Duo Zhang
- Gosling Von
- Byung-Gon Chun
- Michael Wall
- Furkan KAMACI
- Kevin A. McGrail


[Not binding]

- Yingchun Lai
- lidong dai
- Guangxu Cheng
- agile6v
- Yu Li
- zhangliang
- Ming Wen


Many thanks for everyone. Pegasus is a very promising project in distributed kv 
storage, and welcome to be involved in the community. Next, we will be working 
on Podling Infrastructure Setup :-)


[1] 
https://lists.apache.org/thread.html/r8930baccc2a55bb2ddd56d7539708dc7f8053ec965b640e5460c4688%40%3Cgeneral.incubator.apache.org%3E
 
<https://lists.apache.org/thread.html/r8930baccc2a55bb2ddd56d7539708dc7f8053ec965b640e5460c4688@%3Cgeneral.incubator.apache.org%3E>


Best Regards,
Von Gosling

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

[Gosling Von]

Hi,


+1, binding

I really feel the same way, It seems that everyone is very positive in 
promoting the rapid development of the whole community, we could catch a 
glimpse of case from more than 200 emails everyday. 

Best Regards,
Von Gosling

> On Jun 18, 2020, at 9:31 AM, Justin Mclean  wrote:
> 
> I'll also note that has been one of the easiest podling I've mentored as they 
> have from the start proactively seek out how to comply with ASF policy and 
> how to develop their community under the Apache Way. They have set a low 
> committer bar and continue to grow their community.

Re: [VOTE] Accept Pegasus into the Apache incubation

[Gosling Von]

+1, binding


Best Regards,
Von Gosling

> On Jun 16, 2020, at 5:41 PM, Tao Wu  wrote:
> 
> Hi,
> 
> After [the discussion of Pegasus proposal](
> https://lists.apache.org/thread.html/d2dc725389e1e6d0b525f85201c6219973a568ed075837601fd6bd0b%40%3Cgeneral.incubator.apache.org%3E),
> I would like to call a vote to accept this project into the Apache
> Incubator.
> 
> The proposal is here:
> https://cwiki.apache.org/confluence/display/INCUBATOR/PegasusProposal
> 
> Please cast your vote:
> 
>  [ ] +1, bring Pegasus into Incubator
>  [ ] +0, I don't care either way
>  [ ] -1, do not bring Pegasus 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,
> Wu Tao


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

Re: [DISCUSS] PegasusProposal for Apache Incubation

[Gosling Von]

Hi,

Proposal has been transferred to Apache wiki[1]. We would like to hear more 
voices :-)



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



Best Regards,
Von Gosling

> On Jun 8, 2020, at 8:04 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> The ASF allows 3rd party code to be included in releases. It wouldn’t be part 
> of the grant and still remain the original headers and  copyright. The ASF 
> also doesn’t fork other communities code, but given this is unmaintained and 
> no longer in active development [1] from what I can see I don’t any issues 
> here.
> 
> Thanks,
> Justin
> 
> 1. https://github.com/microsoft/rDSN
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Accept Apache BlueMarlin in the incubator

[Gosling Von]

+1(binding)

Best Regards,
Von Gosling

> On May 25, 2020, at 2:28 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 
> 
> 
> 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] Apache Hudi (incubating) 0.5.2 RC2

[Gosling Von]

Hi,

+1 (binding)

I checked:
- signatures and hashes fine
- LICENSE and NOTICE looks OK
- All necessary files have license headers
- No compiled archives bundled in source archive

P.s. adding release note may be a better way to inform those guys who care 
about this mainly improvement..

Best Regards,
Von Gosling


> On Mar 24, 2020, at 5:30 PM, vino yang  wrote:
> 
> Dear IPMC,
> 
> It has been more than two days since the voting began.
> 
> Currently, there is only one binding vote for Apache Hudi (incubating)
> 0.5.2 RC2.
> 
> Please take your precious time to vote.
> 
> Thank you very much!
> 
> Best,
> Vino
> 
> Justin Mclean  于2020年3月23日周一 上午6:07写道：
> 
>> Hi,
>> 
>>> There appears to be conflicting information in [1].
>> 
>> Not quite (se below).
>> 
>>> "Under normal circumstances, there is no need to modify NOTICE.”
>> 
>> That applies to anything bundled with  MIT/BSD style license.
>> 
>>> "If the dependency supplies a NOTICE file, its contents must be analyzed
>>> and the relevant portions bubbled up into the top-level NOTICE file.”
>> 
>> That applies to anything bundled with a Apache (v2) license.
>> 
>> 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] Graduate Apache ShardingSphere (incubating)

[Gosling Von]

+1, binding


Best Regards,
Von Gosling

> On Mar 14, 2020, at 1:29 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: [VOTE] Release Apache brpc(incubating) 0.9.7-rc03

[Gosling Von]

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

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

[Gosling Von]

Carry my +1 binding from dev

Best Regards,
Von Gosling

> On Dec 25, 2019, at 10:22 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] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[Gosling Von]

+1, binding

Best Regards,
Von Gosling

> On 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, that all responsibility pertaining to the Apache
> Incubator Druid 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] Accept NuttX into the Apache Incubator

[Gosling Von]

+1 (binding)

Best Regards,
Von Gosling


> On Dec 4, 2019, at 1:31 PM, 俊平堵  wrote:
> 
> Hi folks,
> 
> 
> The [DISCUSS] thread on NuttX has died down.
> 
> 
> Accordingly, I would like to call a VOTE to accept NuttX into the
> 
> Apache Incubator.
> 
> 
> Please cast your vote:
> 
> 
>  [ ] +1, bring NuttX into the Incubator
> 
>  [ ] +0, I don't care either way
> 
>  [ ] -1, do not bring NuttX 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=
> 
> NuttX is a mature, real-time embedded operating system (RTOS).  It has wide
> usage in IoT projects, control systems, robotics, drones, and many other
> systems.  Unique properties of NuttX are its strict adherence to standards
> and its scalability. NuttX follows the Unix standards as defined
> by OpenGroup.org (POSIX, ANSI, and others).  This allows for a high degree
> of portability. Scalability is supported through a configuration system
> that allows NuttX to run on the smallest embedded platforms and through
> high end single board computers.
> 
> 
> =Proposal=
> 
> NuttX was released under a BSD 3-Clause license on February 17, 2007.  From
> that time until now it has been managed by a single person, Gregory Nutt.
> The user base of NuttX has grown to probably thousands of projects and
> perhaps a hundred active developments at any time.  The code base has grown
> to around 1.5 million lines of code (according to OpenHub.com).
> 
> NuttX has benefited from this single person management because this has
> resulted in a consistent architecture and controlled growth.  But now it is
> time to open this project to the participation of others because this
> consistent architecture assures solid future growth, and because the
> magnitude of effort required to support the RTOS exceeds the capability of
> a single person, but also because users of NuttX require a stable road map
> going forward that does not depend on a single person.
> 
> For these reasons, I propose that NuttX enter the Apache Incubator as a
> first step in opening the project to wider participation.
> 
> 
> =Initial Goals=
> 
> The initial goal will be to move the existing BSD code base to Apache and
> integrate with the Apache development process and infrastructure. A primary
> goal of incubation will be to grow and diversify the NuttX community. We
> will convert that code base to the Apache license during incubation.
> 
> 
> =Current Status=
> 
> As previously mentioned, NuttX is a mature, stable product in wide use in
> embedded 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.
> 
> Being a mature project, NuttX already has an extensive user base with many
> people who understand the software, who have committed hundreds of changes,
> and are happy to participate in the project.  I believe that with a little
> guidance and formalization, a PMC and a large group of experienced
> committers can quickly be established.
> 
> 
> ==Community==
> 
> NuttX has a large, active community.  Communication is via a Google group
> at https://groups.google.com/forum/#!forum/nuttx where there are 395
> members as of this writing.  Code is currently maintained
> at Bitbucket.org at https://bitbucket.org/nuttx/.  Other communications are
> through Bitbucket issues and also via Slack for focused, interactive
> discussions.
> 
> Keeping up with the communications, requests for help, issues, and
> contributions is more than a full time job at this time.
> 
> 
> ==Core Developers==
> 
> NuttX was initially developed by Gregory Nutt, released as an open source
> project on February 17, 2007, and is still under active development.  There
> are several dozen, active, frequent contributors involved with the project.
> The core OS can be considered finished at this point, but development
> continues in specialized areas of networking, IoT, cryptography, tools, and
> other more specialized functions.
> 
> 
> =Alignment=
> 
> NuttX is an original development with some small percentage of ported
> code.  It stands alone depends on no other projects.
> 
> 
> =Known Risks=
> 
> ==Orphaned Products==
> 
> We are committed to the future development of NuttX and understand that
> graduation to a TLP, while preferable, is not the only positive outcome of
> incubation.
> 
> Should the NuttX project be accepted by the Incubator, the prospective PPMC
> would be willing to agree to a target incubation period of 2 years or less,
> knowing that every Incubator project incurs a certain cost in terms of ASF
> infrastructure and volunteer time.
> 
> 
> ==Inexperience with Open Source==
> 
> N

Re: [VOTE] Release Apache IoTDB 0.9.0

[Gosling Von]

Hi,

+1 (binding)

I’v checked:
- LICENSE and NOTICE files are good.
- No binary file in the source kit.
- DISCLAIMER is included.
- All files have license headers if necessary.



Best Regards,
Von Gosling

> On 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
> 
> 
> 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] Release Apache ShardingSphere (Incubating) 4.0.0-RC3

[Gosling Von]

Hi,

+1, binding

I checked:

- Incubating in name
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- No unexpected binary files
- Checked PGP signatures and checksums
- All files have license headers if necessary.

Best Regards,
Von Gosling

> On Nov 18, 2019, at 5:40 PM, Juan Pan  wrote:
> 
> Hello everyone,
> 
> This is a call for vote to release Apache ShardingSphere (Incubating) version 
> 4.0.0-RC3.
> 
> The Apache ShardingSphere community has voted on and approved a proposal to 
> release
> Apache ShardingSphere (Incubating) version 4.0.0-RC3.
> 
> We now kindly request the Incubator IPMC 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. 
> 
> Sharding-JDBC defines itself as a lightweight Java framework that provides 
> extra service at Java JDBC layer.  It can be considered as an enhanced JDBC 
> driver, which is fully compatible with JDBC and all kinds of ORM frameworks.
> 
> Sharding-Proxy defines itself as a transparent database proxy, providing a 
> database server that encapsulates database binary protocol to support 
> heterogeneous languages. 
> 
> ShardingSphere community vote and result threads:
> https://lists.apache.org/thread.html/460965b2c3ec65e8f6d38c39805d6fbc1f9096a625d5c56ffad04acd@%3Cdev.shardingsphere.apache.org%3E
> 
> https://lists.apache.org/thread.html/82f902861f37268183bd88d245e444211cf82dbb525d1a4e046ec79e@%3Cdev.shardingsphere.apache.org%3E
> 
> Release notes:
> https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md
> 
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/
> 
> Maven 2 staging repository:
> https://repository.apache.org/content/repositories/orgapacheshardingsphere-1027/org/apache/shardingsphere/
> 
> Git tag for the release:
> https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/
> 
> Release Commit ID:
> https://github.com/apache/incubator-shardingsphere/commit/78a67e8c088ffc0b6f0e2c7418b0217cdc3bb87d
> 
> Keys to verify the Release Candidate:
> 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 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.
> 
> 
> 
> Juan Pan
> 
> 
> panj...@apache.org
> Juan Pan(Trista), Apache ShardingSphere
> 


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

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[Gosling Von]

+1, binding


Best Regards,
Von Gosling

> On 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 help us build a diverse, sustainable community.
> 
> =Alignment=
> 
> TubeMQ utilizes other Apache projects such as Hadoop, HBase and
> Zookeeper. We anticipate integration with additional Apache projects
> as the TubeMQ community and interest in the project grows.
> 
> =Known Risks=
> 
> ==Orphaned Products==
> 
> Tencent is committe

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

[Gosling Von]

+1, binding

p.s. dropped lazy keyword, release can not be lazy consensus; the default name 
could be polished. I found the apache-iotdb-0.8.1-incubating 2 name when 
unzipped source and release files at the same directory :-)


Best Regards,
Von Gosling

> On Oct 21, 2019, at 1:46 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: [VOTE] Accept APISIX into Apache Incubator

[Gosling Von]

s://github.com/iresty/apisix
>- https://github.com/iresty/apisix_dashboard
> 
> == Source and Intellectual Property Submission Plan ==
> 
> As soon as APISIX is approved to join Apache Incubator, zhiliu will
> provide the Software Grant Agreement(SGA)
> and initial committers will submit ICLA(s).
> The code is already licensed under the Apache Software License, version 2.0.
> 
> == External Dependencies ==
> 
> As all backend code dependencies are managed using Luarocks
> <https://github.com/iresty/apisix/blob/master/rockspec/apisix-dev-1.0-0.rockspec>,
> none of the external libraries need to be packaged in a source distribution.
> 
> All of dependencies have Apache compatible licenses，and the detail as follows:
> 
> Dependency License Comments
> 
> lua-resty-session BSD 2-clause
> lua-resty-httpBSD 2-clause
> lua-resty-balancerBSD 2-clause
> lua-resty-templateBSD 3-clause
> lua-resty-cookie  BSD 3-clause
> lua-resty-etcdApache-2.0
> lua-resty-ngxvar  Apache-2.0
> lua-resty-openidc Apache-2.0
> lua-resty-healthcheck-iresty  Apache-2.0
> lua-resty-jwt Apache-2.0
> opentracing-openresty Apache-2.0
> lua-resty-radixtree   Apache-2.0
> lua-resty-iputils MIT
> lua-protobuf  MIT
> lua-resty-jit-uuidMIT
> lua-tinyyaml  MIT
> lua-rapidjson MIT
> luafilesystem MIT
> iresty-nginx-lua-prometheus   MIT
> 
> As all front-end dashboard dependencies are managed using NPM
> <https://github.com/iresty/apisix_dashboard/blob/master/package.json>,
> none of the external libraries need to be packaged in a source distribution.
> 
> All of dependencies have Apache compatible licenses，and the detail as follows:
> 
> Dependency License Comments
> 
> fuse.js   Apache-2.0
> echarts   Apache-2.0
> axios MIT
> element-uiMIT
> js-cookie MIT
> normalize.css MIT
> nprogress MIT
> path-to-regexpMIT
> register-service-worker   MIT
> screenfullMIT
> uuid  MIT
> vue   MIT
> vue-class-component   MIT
> vue-count-to  MIT
> vue-i18n  MIT
> vue-property-decoratorMIT
> vue-routerMIT
> vue-svgicon   MIT
> vuex  MIT
> vuex-classMIT
> vuex-module-decoratorsMIT
> 
> == Required Resources ==
> 
> === Git Repositories ===
> 
>- https://github.com/iresty/apisix.git
>- https://github.com/iresty/apisix_dashboard.git
> 
> === Issue Tracking ===
> 
> The community would like to continue using GitHub Issues.
> 
> === Continuous Integration tool ===
> 
> Travis CI
> 
> === Mailing Lists ===
> 
>- APISIX-dev: for development discussions
>- APISIX-private: for PPMC discussions
>- APISIX-notifications: for users notifications
> 
> == Initial Committers ==
> 
>- Ming Wen(moonbingb...@gmail.com)
>- Yuansheng Wang(membp...@gmail.com)
>- Zhiyuan Ju(jjzhiy...@gmail.com)
>- Junxu Chen(4061...@qq.com)
>- Yong Li(chnliy...@hotmail.com)
>- Suo Zhang(coolsoul0...@qq.com)
>- Ke Tang(itangke1...@gmail.com)
>- Chunlin Wu(lin...@live.com)
>- Lang Wang(gk...@qq.com)
>- Hui Li(794089...@qq.com)
>- Zhiyong Li(lizhiyong4...@gmail.com)
>- Jinchao Shuai(shuaijinc...@gmail.com)
> 
> == Affiliations ==
> 
>- zhiliu: Ming Wen, Yuansheng Wang
>- Meizu: Junxu Chen
>- Dasouche: Yong Li
>- Individuals: Zhiyuan Ju
>- Yanhuang Online: Suo Zhang
>- GangRong Tech: Ke Tang
>- Axinfu: Chunlin Wu
>- Learnta: Lang Wang
>- Tencent: Hui Li
>- Zero tone Tech: Zhiyong Li
>- TAL Education: Jinchao Shuai
> 
> == Sponsors ==
> 
> === Champion ===
> 
>- Willem Ning Jiang, ningji...@apache.org
> 
> === Mentors ===
> 
>- Willem Ning Jiang, ningji...@apache.org
>- Justin Mclean, jmcl...@apache.org
>- Kevin Ratnasekera, djkevincr1...@gmail.com
>- Gosling Von, fengji...@gmail.com
> 
> === Sponsoring Entity ===
> 
> We are expecting the Apache Incubator could sponsor this project.


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

Re: [DISCUSS] APISIX incubator proposal

[Gosling Von]

Hi,

It seems to be a very interesting project, which is very close to kong's 
positioning. I personally feel that future support for asynchrony may be a 
direction that this project may need to consider. 
In addition, I am interested in helping the project podling in apache.



Best Regards,
Von Gosling

> On Sep 27, 2019, at 10:59 AM, Willem Jiang  wrote:
> 
> 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
>>  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 

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

[Gosling Von]

+1 (binding), forward my vote from PPMC.

Best Regards,
Von Gosling

> On Aug 20, 2019, at 6:16 PM, Zhang Yonglun  wrote:
> 
> 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


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

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

[Gosling Von]

+1, binding




Best Regards,
Von Goslng

> On Jul 8, 2019, at 11:14 PM, David P Grove  wrote:
> 
> 
> 
> The Apache OpenWhisk 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 19 +1 votes and no 0 or -1 votes.
> Further details on how the community has developed during incubation are
> summarized in the discussion thread [1].
> 
> This 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,
> 
> --dave
> on behalf of the Apache OpenWhisk PPMC
> 
> [1]
> https://lists.apache.org/x/thread.html/ee66864bb39279833a19d9c4c5aa2f7d96463efdafc93594e7f32af1@%3Cgeneral.incubator.apache.org%3E
> [2]
> https://lists.apache.org/x/thread.html/ee66864bb39279833a19d9c4c5aa2f7d96463efdafc93594e7f32af1@%3Cgeneral.incubator.apache.org%3E
> 
> -
> 
> Establish the Apache OpenWhisk 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 platform for building serverless applications
> with functions.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache OpenWhisk Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache OpenWhisk Project be and hereby is
> responsible for the creation and maintenance of software related to a
> platform for building serverless applications with functions; and be
> it further
> 
> RESOLVED, that the office of "Vice President, Apache OpenWhisk" 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
> OpenWhisk Project, and to have primary responsibility for management
> of the projects within the scope of responsibility of the Apache
> OpenWhisk 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 OpenWhisk
> Project:
>Bertrand Delacretaz, bdelacre...@apache.org
>Carlos Santana, csantan...@apache.org
>Chetan Mehrotra, chet...@apache.org
>Dave Grove, dgr...@apache.org
>Dominic Kim, styl...@apache.org
>Dragos Dascalita Haut, dra...@apache.org
>James Dubee, du...@apache.org
>James Thomas, jamestho...@apache.org
>Jeremias Werner, jeremiaswer...@apache.org
>Krzysztof Sobkowiak, ksobkow...@apache.org
>Markus Thömmes, markusthoem...@apache.org
>Matt Rutkowski, mrutkow...@apache.org
>Matt Sicker, mattsic...@apache.org
>Michele Sciabarra, msciaba...@apache.org
>Olivier Tardieu, tard...@apache.org
>Rob Allen, akra...@apache.org
>Rodric Rabbah, rab...@apache.org
>Sven Lange-Last, sla...@apache.org
>Tyson Norris, tysonnor...@apache.org
>Vincent Hou, houshen...@apache.org
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Grove be appointed
> to the office of Vice President, Apache OpenWhisk, 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 OpenWhisk Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> OpenWhisk podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> OpenWhisk podling encumbered upon the Apache Incubator Project are
> hereafter discharged.


-
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

[Gosling Von]

+1, binding

Best Regards,
Von Gosling

> On 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/incubator-dubbo/wiki/Apache-Maturity-Model-Assessment-for-Dubbo
> [5] 
> https://lists.apache.org/thread.html/2b9fb2c565656308dcce5281c5352da41d5aabc56020af084c6888d3@%3Cdev.dubbo.apache.org%3E
> [6] 
> https://lists.apache.org/thread.html/cb00b308011770f4cf2e4eac4ab0ddec397fe83e4ee92d246a450d73@%3Cdev.dubbo.apache.org%3E
> [7] 
> https://lists.apache.org/thread.html

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

[Gosling Von]

Hi,

+1(binding)

I checked:
- incubating in name
- signatures and hashed format(SHA512) fine
- DISCLAIMER exists
- LICENSE and NOTICE good
- No unexpected binary files
- All source files have ASF headers
- can compile from source

Best Regards,
Von Gosling


> On Apr 16, 2019, at 4:32 PM, zhangli...@apache.org wrote:
> 
> Hello all,
> 
> This is a call for vote to release Apache ShardingSphere (Incubating)
> version 4.0.0-RC1.
> 
> The Apache ShardingSphere community has voted on and approved a proposal to
> release
> Apache ShardingSphere (Incubating) version 4.0.0-RC1.
> 
> 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 database in 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 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 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 client access (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 compatible of client end that is compatible of
> MySQL and PostgreSQL protocol.
> 
> 
> ShardingSphere community vote and result thread:
> https://lists.apache.org/thread.html/7818fb3400ca4404d4d9c47407f4589281ba4a499e0a798b7d714c32@%3Cdev.shardingsphere.apache.org%3E
> 
> Release notes:
> https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-d5d2dc137c82994bbaac
> 
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC1/
> 
> 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-RC1
> 
> Release Commit ID:
> https://github.com/apache/incubator-shardingsphere/commit/2c1d23f9569e5cbe74074a578931c77dfa800800
> 
> Keys to verify the Release Candidate:
> 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 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.
> 
> --
> 
> 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: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]

[Gosling Von]

Hi,

+1, binding

I checked:
- incubating in name
- signatures and hashed format(SHA512) fine
- DISCLAIMER exists
- LICENSE and NOTICE good
- No unexpected binary files
- All source files have ASF headers
- can compile from source

Best Regards,
Von Gosling


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

[Gosling Von]

+1 ( binding)


Von Gosling,
Best Regards

> On 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 Spring Boot Project (Incubating) 2.7.1

[Gosling Von]

Hi,

+ 1, binding

I checked,
- incubating in name
- signature and hashes good
- DISCLAIMER exists
- LICENSE and NOTICE exists
- No unexpected binary files in release
- All source files have ASF headers
- Can compile from source


Best Regards,
Von Gosling

> On Apr 4, 2019, at 11:42 AM, Mercy  wrote:
> 
> Hello all,
> 
> This is a call for the vote to release Apache Dubbo Spring Boot Project 
> (Incubating) version 2.7.1
> 
> The Apache Dubbo community has voted on and approved a proposal to release
> Apache Dubbo Spring Boot Project (Incubating) 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/ded40621ad7572a84c71cc6ad5a9843c3e073e405d051e7053e8700b@%3Cdev.dubbo.apache.org%3E
>  
> 
> 
> The release candidates :
> 2.7.1:https://dist.apache.org/repos/dist/dev/incubator/dubbo/spring-boot-project/2.7.1
>  
> 
> 
> The staging repo:
> https://repository.apache.org/content/repositories/orgapachedubbo-1017 
> 
> 
> Git tag for the release:
> 2.7.1:  
> https://github.com/apache/incubator-dubbo-spring-boot-project/releases/tag/2.7.1
>  <>
> 
> Hash for the release tag:
> 2.7.1: 01fbe79c71f73f65ae1fa1239f9fba30a8300192
> 
> Release Notes:
> 2.7.1: 
> https://github.com/apache/incubator-dubbo-spring-boot-project/releases/tag/2.7.1
>  
> 
> 
> The artifacts have been signed with Key: 
> 87F025027A831ED2B86E7F08A7F508EFDA68B4F5, which can be found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS 
> 
> 
> The vote will be open for at least 72 hours or until the necessary number of 
> votes are reached.
> 
> Please vote accordingly:
> 
> [ ] +1 approve 
> [ ] +0 no opinion 
> [ ] -1 disapprove with the reason
> 
> Thanks,
> The Apache Dubbo (Incubating) Team
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept DataSketches into the Apache Incubator

[Gosling Von]

+1, binding

Best Regards,
Von Gosling

> 在 2019年3月15日，上午5:23，Kenneth Knowles  写道：
> 
> 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] Accept Apache TVM into the incubator

[Gosling Von]

+1, binding


Best Regards,
Von Gosling

> 在 2019年2月28日，下午12:44，Markus Weimer  写道：
> 
> 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: [VOTE] Release Apache Dubbo OPS (Incubating) 0.1 [RC3]

[Gosling Von]

Hi,

+1 binding(only on source)

I checked:
- incubating in name
- DISCLAIMER exits
- LICENSE and NOTICE are fine. I notice you have listed some css dependencies 
as APL 2.0 license. But some other dependency such as vue.js is also the same 
case. If we could hope for list all dependencies for completeness, more details 
see here[1].
- Al source file have ASF headers
- No unexpected binary files
- Can compile from source

P.S. Console is distributed as the binary according to common sense. I also 
noticed we are discussing the binary distribution problem in anther thread. As 
a transitional stage. I vote for release source code. Hopefully this clarifies 
the discussion that follows. 


[1] http://www.apache.org/dev/licensing-howto.html#bundle-asf-product


Best Regards,
Von Gosling

> 在 2019年2月12日，下午7:06，Minxuan Zhuang  写道：
> 
> Hi community,
> 
> Dubbo OPS 0.1 RC3 is still waiting for 3 binding votes to get it passed.
> Would you please help to review and vote for the candidate?
> 
> 
> On Thu, Feb 7, 2019 at 11:01 PM Minxuan Zhuang  wrote:
> 
>> Hello Incubator Community,
>> 
>> The Apache Dubbo community has voted on and approved a proposal to release
>> Apache Dubbo OPS (Incubating) version 0.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/61b7e43b5813c794ef45e7d95dff9c0744ac2d70556ae7ff195405ee@%3Cdev.dubbo.apache.org%3E
>> 
>> The release candidates (RC3):
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-ops/0.1/
>> 
>> 
>> Git tag for the release (RC3):
>> https://github.com/apache/incubator-dubbo-ops/releases/tag/0.1
>> 
>> Hash for the release tag:
>> 7e7b2c4421f54f86980dd2128fa58007f118a8d4
>> 
>> Release Notes:
>> *https://github.com/apache/incubator-dubbo-ops/releases/tag/0.1
>> *
>> 
>> 
>> 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
>> *
>> 
>> 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] Accept Training into the Apache Incubator

[Gosling Von]

+1 binding,

It seems to be some overlapping duty with Apache Infra. Anyway, would be 
helpful for Apache Projects or external open source projects. Very looking 
forward to the further step :-)

Best Regards,
Von Gosling

> 在 2019年2月13日，下午3:57，Lars Francke  写道：
> 
> Hi everyone,
> 
> we've discussed the proposal for the Training project in [1] and [2]. The
> proposal itself can be found on the wiki[3].
> 
> According to the Incubator rules[4] I'd like to call a vote to accept the
> new "Training" 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 Training into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Training into the Apache Incubator because ...
> 
> Thank you for everyone who decided to join in in the past discussions!
> Lars
> 
> [1] <
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
>> 
> 
> [2] <
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
>> 
> 
> [3] 
> 
> [4] <
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
>> 


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

Re: [VOTE]: Release Apache Dubbo Spring Boot Project (Incubating) 2.7.0

[Gosling Von]

Hi,

+1 binding.

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


P.S.: Netty dependency has removed from the NOTICE, great following.

Best Regards,
Von Gosling


> 在 2019年2月11日，下午1:24，Mercy  写道：
> 
> Hello all,
> 
> This is a call for the vote to release Apache Dubbo Spring Boot Project 
> (Incubating) version 2.7.0
> 
> The Apache Dubbo community has voted on and approved a proposal to release
> Apache Dubbo Spring Boot Project (Incubating) 2.7.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/afde64853c6d06280a42389d93d0fea72aa4253059bfaa18a21739da@%3Cdev.dubbo.apache.org%3E
>  
> 
> 
> The release candidates (RC4):
> 2.7.0:https://dist.apache.org/repos/dist/dev/incubator/dubbo/spring-boot-project/2.7.0
>  
> 
> 
> The staging repo:
> https://repository.apache.org/content/repositories/orgapachedubbo-1010 
> 
> 
> Git tag for the release (RC4):
> 2.7.0: 
> https://github.com/apache/incubator-dubbo-spring-boot-project/releases/tag/2.7.0
>  
> 
> 
> Hash for the release tag:
> 2.7.0: 4ee35b9d2108990ac7773ffe5edf534f29122a78
> 
> Release Notes:
> 2.7.0: 
> https://github.com/apache/incubator-dubbo-spring-boot-project/releases/tag/2.7.0
>  
> 
> 
> The artifacts have been signed with Key: 28681CB1, which can be found in the 
> keys file:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS 
> 
> 
> The vote will be open for at least 72 hours or until the necessary number of 
> votes are reached.
> 
> Please vote accordingly:
> 
> [ ] +1 approve 
> [ ] +0 no opinion 
> [ ] -1 disapprove with the reason
> 
> Thanks,
> The Apache Dubbo (Incubating) Team
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Dubbo (Incubating) 2.7.0 [RC2]

[Gosling Von]

+1 binding

I focused on the license and notice files since some podling projects have many 
minor problems in here.

In addition to the problems as Justin said. I have found some of the 
non-optional dependency modules such as javaassit, spring-context not exist in 
NOTICE file. Please fix it in the next time[1].


[1] http://www.apache.org/dev/licensing-howto.html#bundle-asf-product 


Best Regards,
Von Gosling

> 在 2019年1月24日，下午10:28，Huxing Zhang  写道：
> 
> Hello Incubator Community,
> 
> The Apache Dubbo community has voted on and approved a proposal to release
> Apache Dubbo (Incubating) version 2.7.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/60b3ef868d8acd127c18584968d98dd6191c41dd3a426f98703f68f6@%3Cdev.dubbo.apache.org%3E
> 
> The release candidates (RC2):
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.7.0
> 
> The staging repo:
> https://repository.apache.org/content/repositories/orgapachedubbo-1005
> 
> Git tag for the release (RC2):
> https://github.com/apache/incubator-dubbo/tree/dubbo-2.7.0
> 
> Hash for the release tag:
> 614bcebc01336ee5047a98f96b28915680c0399c
> 
> Release Notes:
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md
> 
> The artifacts have been signed with Key :
> AF1B3C2AC648B9E8C9AC6F26CD69F886A620E8EC, which can be
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
> 
> The vote will be open for at least 72 hours or until 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] Shut down unused/inactive incubator lists

[Gosling Von]

+1

it seems to be inactive from the last activity, and general@/private@ as 
appropriate.

Best Regards,
Von Gosling

> 在 2019年1月21日，上午8:11，sebb  写道：
> 
> The following lists are all but inactive:
> 
> announce@ Last post Jan 2008
> android-interest@ Last post Mar 2011
> dev@ - only general circulars
> jaxws-tck@ (private) Last post 2012
> projects@ Last post Jul 2011
> user@ - only general circulars
> 
> I think they should be shut down.
> 
> Please vote so an Infra Jira can be raised to shut them down.
> They can have a bounce message added to direct posters to
> general@/private@ as appropriate
> 
> [  ] +1
> [  ] -1 - give a reason please
> 
> Please vote by end January 2019
> 
> Sebb.
> 
> -
> 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 Hudi into the Apache Incubator

[Gosling Von]

+1(binding)

Best Regards,
Von Gosling

> 在 2019年1月14日，上午6:34，Thomas Weise  写道：
> 
> Hi all,
> 
> Following the discussion of the Hudi proposal in [1], this is a vote
> on accepting Hudi into the Apache Incubator,
> per the ASF policy [2] and voting rules [3].
> 
> 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.
> 
> This vote will run for at least 72 hours. Please VOTE as
> follows:
> 
> [ ] +1 Accept Hudi into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Hudi into the Apache Incubator because ...
> 
> The proposal is included below, but you can also access it on
> the wiki [4].
> 
> Thanks for reviewing and voting,
> Thomas
> 
> [1]
> https://lists.apache.org/thread.html/12e2bdaa095d68dae6f8731e473d3d43885783177d1b7e3ff2f65b6d@%3Cgeneral.incubator.apache.org%3E
> 
> [2]
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> 
> [3] http://www.apache.org/foundation/voting.html
> 
> [4] https://wiki.apache.org/incubator/HudiProposal
> 
> 
> 
> = Hudi Proposal =
> 
> == Abstract ==
> 
> Hudi is a big-data storage library, that provides atomic upserts and
> incremental data streams.
> 
> Hudi manages data stored in Apache Hadoop and other API compatible
> distributed file systems/cloud stores.
> 
> == Proposal ==
> 
> Hudi provides the ability to atomically upsert datasets with new values in
> near-real time, making data available quickly to existing query engines
> like Apache Hive, Apache Spark, & Presto. Additionally, Hudi provides a
> sequence of changes to a dataset from a given point-in-time to enable
> incremental data pipelines that yield greater efficiency & latency than
> their typical batch counterparts. By carefully managing number of files &
> sizes, Hudi greatly aids both query engines (e.g: always providing
> well-sized files) and underlying storage (e.g: HDFS NameNode memory
> consumption).
> 
> Hudi is largely implemented as an Apache Spark library that reads/writes
> data from/to Hadoop compatible filesystem. SQL queries on Hudi datasets are
> supported via specialized Apache Hadoop input formats, that understand
> Hudi’s storage layout. Currently, Hudi manages datasets using a combination
> of Apache Parquet & Apache Avro file/serialization formats.
> 
> == Background ==
> 
> Apache Hadoop distributed filesystem (HDFS) & other compatible cloud
> storage systems (e.g: Amazon S3, Google Cloud, Microsoft Azure) serve as
> longer term analytical storage for thousands of organizations. Typical
> analytical datasets are built by reading data from a source (e.g: upstream
> databases, messaging buses, or other datasets), transforming the data,
> writing results back to storage, & making it available for analytical
> queries--all of this typically accomplished in batch jobs which operate in
> a bulk fashion on partitions of datasets. Such a style of processing
> typically incurs large delays in making data available to queries as well
> as lot of complexity in carefully partitioning datasets to guarantee
> latency SLAs.
> 
> The need for fresher/faster analytics has increased enormously in the past
> few years, as evidenced by the popularity of Stream processing systems like
> Apache Spark, Apache Flink, and messaging systems like Apache Kafka. By
> using updateable state store to incrementally compute & instantly reflect
> new results to queries and using a “tailable” messaging bus to publish
> these results to other downstream jobs, such systems employ a different
> approach to building analytical dataset. Even though this approach yields
> low latency, the amount of data managed in such real-time data-marts is
> typically limited in comparison to the aforementioned longer term storage
> options. As a result, the overall data architecture has become more complex
> with more moving parts and specialized systems, leading to duplication of
> data and a strain on usability.
> 
> Hudi takes a hybrid approach. Instead of moving vast amounts of batch data
> to streaming systems, we simply add the streaming primitives (upserts &
> incremental consumption) onto existing batch processing technologies. We
> believe that by adding some missing blocks to an existing Hadoop stack, we
> are able to a provide similar capabilities right on top of Hadoop at a
> reduced cost and with an increased efficiency, greatly simplifying the
> overall architecture in the process.
> 
> Hudi was originally developed at Uber (original name “Hoodie”) to address
> such broad inefficiencies in ingest & ETL & ML pipelines across Uber’s data
> ecosystem that required the upsert & incremental consumption primitives
> supported by Hudi.
> 
> == Rationale ==
> 
> We truly believe the capabilities supported by Hudi would be increasingly
> useful for big-data ecosystems, as data volumes & need for faster data
> continue to increase. A detailed description of target use-cases can be
> found 

Re: [DISCUSS] Hudi Incubation Proposal

[Gosling Von]

Hi,

I just looked through the proposal for the Hudi and very interested in this 
project, and also willing to be a Hudi mentor.



Best Regards,
Von Gosling

> 在 2019年1月4日，上午6:10，Justin Mclean  写道：
> 
> Hi,
> 
> There's one issue I think needs to be addressed, if the proposed mentors 
> could follow up on my email sent a few weeks back on private@ that would be 
> appreciated.
> 
> 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: Release checklist application

[Gosling Von]

Hi,

Very appreciate your works @Justin, we will try to followup and give some 
feedback in practice :-)

Best Regards,
Von Gosling

> 在 2018年12月17日，下午5:46，Justin Mclean  写道：
> 
> Hi,
> 
> Hopefully everyone is familiar with the incubator checklist that was created 
> a few months back [1]
> 
> I run into a company called Safety Culture [2] that does an online/mobile 
> compliance application and repurposed it to use the incubator release check 
> list. It works quite nicely and may be a useful tool when checking releases. 
> Coincidentally an IPMC member Brett Porter currently works there and is 
> willing to help out. Hopefully we can get access to a wider audience, but 
> currently if you want to take a look just ask and I’ll grant you access.
> 
> Thanks,
> Justin
> 
> 1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
> 2. https://safetyculture.com
> -
> 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: December report - Mentor sign off due end of today

[Gosling Von]

Hi,

I have noticed in brpc incubator comments:


IPMC/Shepherd notes:
Dave Fisher: I wrote up this report and made the mailing list request.
Justin Mclean: LDAP and DNS also feel between the cracks. Mentors were
 pinged but no response. I think it would be good for this project to
 have an extra mentor.

I have signed my name in mentor roster and contacted the brpc teams offline to 
learn more about the start status in podling.


Best Regards,
Von Gosling

> 在 2018年12月11日，上午4:47，Justin Mclean  写道：
> 
> Hi,
> 
> Just a reminder mentor sign-off is due today and some projects still have no 
> sing-offs and will be asked to report next month if they don’t get any.
> 
> These projects are:
> BRPC
> Myriad
> 
> Projects that could do with more sign-offs (as they only have one sign-off) 
> include:
> DLab
> Daffodil
> Hivemall
> Ponytail
> Samoa
> Singa
> Superset
> Taverna
> Warble
> 
> The board likes to see more than one sign off and it’s a good indicator if 
> mentors are paying attention.
> 
> 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 Druid (incubating) 0.13.0 [RC4]

[Gosling Von]

Hi,

+1(binding)

For the initial release under the Apache podling stage, we must be serious for 
some of the ip clearance problems. I strongly suggest our druid guys comment 
the todo list to track the problems in jira(as Justin pointed out). I also 
would like to help to re-check the problems in your next release.

BTW, I checked:
- incubating in name
- DISCLAIMER exists
- No unexpected binary files

For the license, I kindly suggest you could using some of the template just as 
we guys doing in Apache RocketMQ[1], and use checkstyle to re-check it when 
compiling or assembling :-)


[1] http://rocketmq.apache.org/docs/code-guidelines/ 

[2] https://github.com/apache/rocketmq/tree/master/style/copyright 



Best Regards,
Von Gosling


> 在 2018年12月6日，上午10:27，David Lim  写道：
> 
> Hi IPMC,
> 
> The Apache Druid community has voted on and approved a proposal to release
> Apache Druid (incubating) 0.13.0 (rc4).
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> Project description: Apache Druid (incubating) is a high-performance,
> column-oriented, distributed data store.
> 
> The community voting thread can be found here:
> https://www.mail-archive.com/dev@druid.apache.org/msg01489.html
> 
> The release notes are available here:
> https://github.com/apache/incubator-druid/issues/6442
> 
> The release candidate has been tagged in GitHub as
> druid-0.13.0-incubating-rc4 (cf15aac), available here:
> https://github.com/apache/incubator-druid/releases/tag/druid-0.13.0-incubating-rc4
> 
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/druid/0.13.0-incubating-rc4
> 
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachedruid-1002/
> 
> Release artifacts are signed with the key [7183DE56]:
> https://people.apache.org/keys/committer/davidlim.asc (also available here:
> http://pgp.mit.edu/pks/lookup?search=davidlim%40apache.org&op=index)
> 
> This key and the key of other committers can also be found in the project's
> KEYS file here: https://dist.apache.org/repos/dist/dev/incubator/druid/KEYS
> 
> As part of the validation process, the binary release artifacts can be
> generated from source by running: mvn clean install
> -Papache-release,dist,rat
> 
> This vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
> 
> [ ] +1 Release this package as Apache Druid (incubating) 0.13.0
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
> 
> 
> Thank you IPMC! We appreciate your efforts in helping the Apache Druid
> community to validate this release.
> 
> On behalf of the Apache Druid PPMC,
> David

Re: [PROPOSAL] Changing requirements for IPMC

[Gosling Von]

- I think we should explicitly look at the proposal and mentors listed and then 
express any concerns.


I am not sure am I missing some important discussion for the qualification of 
the IPMC :-) I read some of the reply carefully and very agree with explicitly 
list some concerns when we guide podling for their initial proposal, release 
notice. I have learn some points from the John and Justin share at ApacheCon. 
But with few green mentors to join the IPMC, Could we consider list it 
explicitly? I would like to see the Apache Projects could be more innovative 
and diversity.  

Best Regards,
Von Gosling

> 在 2018年11月8日，上午2:10，Dave Fisher  写道：
> 
> - I think we should explicitly look at the proposal and mentors listed and 
> then express any concerns.

Re: brpc project setup

[Gosling Von]

Thanks Justin. I think the initial good works in podling is the beginning of 
the success for the brpc team.

Best Regards,
Von Gosling

> 在 2018年11月30日，上午11:30，Justin Mclean  写道：
> 
> e project only had 2 m

Re: brpc project setup

[Gosling Von]

Hi,

I would like to help the brpc team to startup and guide podling, would you like 
to add me to the mentor camp?

Best Regards,
Von Gosling

> 在 2018年11月30日，上午5:26，Justin Mclean  写道：
> 
> Hi,
> 
> I notice this podling was voted in 2 weeks ago but the email lists have not 
> been created yet. 
> 
> Does the podling need help with on-boarding / bootstrapping? Are your mentors 
> helping out (presumably off ist)?
> 
> Thanks,
> Justin
> 
> P.S You have a board report due in a week, and while it may not contain much 
> other then “still setting up stuff” it’s still needed.
> -
> 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.20.0 [RC1]

[Gosling Von]

+1 (binding)

I've checked the following:
* Disclaimer
* License
* Notice
* Compile from source
* Rat checks for headers

Notice: During podling stage, we are assigned apache email, it would be better 
if we could use the apache email to signature the src release.


Best Regards,
Von Gosling

> 在 2018年11月26日，下午10:11，Jonathan Dong  写道：
> 
> Dear IPMC members,
> 
> This is a call for the vote to release Apache Weex (Incubating) version 
> 0.20.0.
> 
> The Apache Weex community has voted and approved a proposal to release Apache 
> Weex (Incubating) version 0.20.0, we now kindly request the Incubator PMC 
> members to review and vote on this incubator release.
> 
> Vote thread:
> https://lists.apache.org/thread.html/fa0634ea9936171700a74547cb8541ec4c435db9b9a61a04ca0b3950@%3Cdev.weex.apache.org%3E
> 
> Vote result thread:
> https://lists.apache.org/thread.html/f8bd059fe324bc7d1c11ed33e9d3c1f70d6c61c0ae7928fef34ead6f@%3Cdev.weex.apache.org%3E
> 
> The tag to be voted upon:
> https://github.com/apache/incubator-weex/releases/tag/0.20.0-rc1
> 
> Hash for the release tag:
> 97eda0bbd91ee8ac05ca7b81ba73970217467e4a
> 
> The source tarball can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.20.0/RC1/apache-weex-incubating-0.20.0-RC1-src.tar.gz
> 
> The SHA-512 checksum for the artifact can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.20.0/RC1/apache-weex-incubating-0.20.0-RC1-src.tar.gz.sha512
> 
> The signature can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.20.0/RC1/apache-weex-incubating-0.20.0-RC1-src.tar.gz.asc
> 
> The artifacts have been signed with Key : EACFA1A9BD14A270, which can be 
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
> 
> The compilation documentation can be found at:
> https://github.com/apache/incubator-weex/blob/0.20.0-rc1/HOW-TO-BUILD.md
> 
> Release note about this version:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320726&version=12343286
> 
> 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)
> 
> Cheers,
> 
> Jonathan Dong


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

Re: [Vote] call a vote for IoTDB incubation proposal

[Gosling Von]

+1

Good luck ~

Von Gosling


> 在 2018年11月7日，下午3:46，hxd  写道：
> 
> Hi,
> Sorry for the previous mail with bad format.
> I'd like to call a VOTE to accept IoTDB project, a database for managing 
> large amounts of time series data  from IoT sensors in industrial 
> applications, into the Apache Incubator. 
> The full proposal is available on the wiki: 
> https://wiki.apache.org/incubator/IoTDBProposal
> and it is also attached below for your convenience.
> 
> Please cast your vote:
> 
>  [ ] +1, bring IoTDB into Incubator
>  [ ] +0, I don't care either way,
>  [ ] -1, do not bring IoTDB into Incubator, because...
> 
> The vote will open at least for 72 hours.
> 
> Thanks,
> Xiangdong Huang.
> 
> = IoTDB Proposal  =
> v0.1.1
> 
> 
> == Abstract ==
> IoTDB is a data store for managing large amounts of time series data such as 
> timestamped data from IoT sensors in industrial applications.
> 
> == Proposal ==
> IoTDB is a database for managing large amount of time series data with 
> columnar storage, data encoding, pre-computation, and index techniques. It 
> has SQL-like interface to write millions of data points per second per node 
> and is optimized to get query results in few seconds over trillions of data 
> points. It can also be easily integrated with Apache Hadoop MapReduce and 
> Apache Spark for analytics.
> 
> == Background ==
> 
> A new class of data management system requirements is becoming increasingly 
> important with the rise of the Internet of Things. There are some database 
> systems and technologies aimed at time series data management.  For example, 
> Gorilla and InfluxDB which are mainly built for data centers and monitoring 
> application metrics. Other systems, for example, OpenTSDB and KairosDB, are 
> built on Apache HBase and Apache Cassandra, respectively. 
> 
> However, many applications for time series data management have more 
> requirements especially in industrial applications as follows:
> 
> * Supporting time series data which has high data frequency. For example, a 
> turbine engine may generate 1000 points per second (i.e., 1000Hz), while each 
> CPU only reports 1 data points per 5 seconds in a data center monitoring 
> application.
> 
> * Supporting scanning data multi-resolutionally. For example, aggregation 
> operation is important for time series data.
> 
> * Supporting special queries for time series, such as pattern matching, time 
> series segmentation, time-frequency transformation and frequency query.
> 
> * Supporting a large number of monitoring targets (i.e. time series). An 
> excavator may report more than 1000 time series, for example, revolving speed 
> of the motor-engine, the speed of the excavator, the accelerated speed, the 
> temperature of the water tank and so on, while a CPU or an application 
> monitor has much fewer time series.
> 
> * Optimization for out-of-order data points. In the industrial sector, it is 
> common that equipment sends data using the UDP protocol rather than the TCP 
> protocol. Sometimes, the network connect is unstable and parts of the data 
> will be buffered for later sending.
> 
> * Supporting long-term storage. Historical data is precious for equipment 
> manufacturers. Therefore, removing or unloading historical data is highly 
> desired for most industrial applications. The database system must not only 
> support fast retrieval of historical data, but also should guarantee that the 
> historical data does not impact the processing speed for “hot” or current 
> data.
> 
> * Supporting online transaction processing (OLTP) as well as complex 
> analytics. It is obvious that supporting analyzing from the data files using 
> Apache Spark/Apache Hadoop MapReduce directly is better than transforming 
> data files to another file format for Big Data analytics.
> 
> * Flexible deployment either on premise or in the cloud.  IoTDB is as simple 
> and can be deployed on a Raspberry Pi handling hundreds of time series. 
> Meanwhile, the system can be also deployed in the cloud so that it supports 
> tens of millions ingestions per second, OLTP queries in milliseconds, and 
> analytics using Apache Spark/Apache Hadoop MapReduce.
> 
> * * (1) If users deploy IoTDB on a device, such as a Raspberry Pi, a wind 
> turbine, or a meteorological station, the deployment of the chosen database 
> is designed to be simple. A device may have hundreds of time series (but less 
> than a thousand time series) and the database needs to handle them.
> * * (2) When deploying IoTDB in a data center, the computational resources 
> (i.e., the hardware configuration of servers) is not a problem when compared 
> to a Raspberry Pi. In this deployment, IoTDB can use more computation 
> resources, and has the ability to handle more time seires (e.g., millions of 
> time series).
> 
> Based on these requirements, we developed IoTDB, a new data store system for 
> managing time series data. 
> 
> IoTDB started as a Tsinghua University research project

Re: [VOTE] Sharding-Sphere incubation proposal

[Gosling Von]

+1

Von Gosling

> 在 2018年11月6日，下午2:41，Roman Shaposhnik  写道：
> 
> Hi!
> 
> on behalf of Sharding-Sphere community, I'd like to call
> a VOTE to accept it into the Apache Incubator. The full
> proposal is available on the wiki:
>https://wiki.apache.org/incubator/ShardingSphereProposal
> and it is also attached below for your convenience.
> 
> Please cast your vote:
> 
>  [ ] +1, bring Sharding-Sphere into Incubator
>  [ ] +0, I don't care either way,
>  [ ] -1, do not bring Sharding-Sphere into Incubator, because...
> 
> The vote will open at least for 72 hours.
> 
> Thanks,
> Roman.
> 
> = Abstract =
> Sharding-Sphere is an ecosystem of transparent distributed database
> middleware, focusing on data sharding, distributed transaction and
> database orchestration. It provides maximum compatibility for
> applications through Sharding-JDBC (a driver to implement JDBC) or
> Sharding-Proxy (a proxy to implement database protocol).
> 
> = Proposal =
> With a large number of end users, Sharding-Sphere has a fairly huge
> community in China. It is also widely adopted by many
> [[http://shardingsphere.io/community/en/company/|companies and
> organizations]] as a solution to process their massive amounts of
> data.
> 
> We believe that bringing Sharding-Sphere into Apache Software
> Foundation could advance development of a stronger and more diverse
> open source community.
> 
> Dangdang submits this proposal to donate Sharding-Sphere's source
> codes and all related documentations to Apache Software Foundation.
> The codes are already under Apache License Version 2.0.
> 
>  * Code base: https://github.com/sharding-sphere/sharding-sphere
> 
>  * Web site: http://shardingsphere.io/
> 
>  * Documentations: http://shardingsphere.io/document/current/
> 
>  * Community: http://shardingsphere.io/community/
> 
> = Background =
> 
> Relational database hardly supports such huge amounts of data any more
> which has increased rapidly in recent years, but for reason of
> technique maturity, developers and DBAs still want to use it to
> persist core data.
> 
> Sharding-Sphere was open sourced on Github in 2016. At the very
> beginning, Sharding-Sphere is just a JDBC driver for data sharding
> (name as Sharding-JDBC) at Dangdang internal framework; now it offers
> data sharding, distributed transaction and database orchestration.
> Besides JDBC, proxy to implement MySQL database protocol is also
> supported at present. Furthermore, our roadmap includes Proxy for
> PostgreSQL protocol, Sidecar model, data repica and elastic data
> scalability function as well.
> 
> Due to the extension of project, we provide proxy model and sidecar
> model in addition to JDBC model. Therefore, we rename it to
> Sharding-Sphere by
> [[https://github.com/sharding-sphere/sharding-sphere/issues/788|a
> public vote]], which refers to a sharding ecosphere with
> Sharding-JDBC, Sharding-Proxy and Sharding Sidecar as its three
> sub-projects.
> 
> Sharding-JDBC has won the
> [[http://www.oschina.net/project/top_cn_2016|TOP 20 most popular open
> source projects in China 2016]].
> 
> = Rationale =
> 
> Relational database still plays a very important role on current
> application system. The maturity of products and surrounding
> ecosystem, the friendliness of its data query and developers' and
> DBAs' mastery of it, cannot be completely replaced with other types of
> database in the near future. However, current relational database
> cannot support cloud native very well and it is not friendly to
> distributed system.
> 
> It is the ultimate goal of Sharding-Sphere, which manages the
> databases scattering around the system, to make user use distributed
> databases as simply as using a single one.
> 
> Without extra cost, Sharding-JDBC directly connects database with Java
> application to get the best performance.
> 
> Sharding-Proxy is deployed as a stateless server and supports MySQL
> protocol at present. In the paper
> [[https://db.cs.cmu.edu/papers/2016/pavlo-newsql-sigmodrec2016.pdf|What’s
> Really New with NewSQL?]], three types of NewSQL are introduced, among
> which Sharding-Proxy is a Transparent Sharding Middleware.
> 
> Sharding-Sidecar can be understood as a data panel in Service Mesh.
> The interaction between the application and the database provides a
> mesh layer. The concept of Database Mesh is similar to Service Mesh,
> and it focuses on how to connect data access applications to the
> database. Database Mesh will set up a huge grid system between
> applications and databases. Applications and databases need be placed
> in the grid system. They are all objects managed by the meshing layer.
> 
> = Current Status =
> == Meritocracy ==
> Sharding-Sphere was incubated at Dangdang in 2015 and open sourced on
> GitHub in 2016. In 2017, Jingdong recognized its value and determined
> to sponsor this project. Sharding-Sphere has contributors and users
> from many companies; we have set up the PMC Team and Committer Team.
> New contributors a