[RESULT] [VOTE] Sharding-Sphere incubation proposal

[Roman Shaposhnik]

On Mon, Nov 5, 2018 at 10:41 PM Roman Shaposhnik  wrote:
>
> 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...

With 7 +1 binding votes, 7 +1 non-binding votes and NO +/-0
or -1 votes, this VOTE passes. Thanks to everyone who voted!

Bellow is a voting tally:

Binding
  Craig Russell
  Justin Mclean
  Willem Jiang
  Matt Sicker
  Dave Fisher
  Benjamin Hindman
  Roman Shaposhnik

Non-binding
   Sheng Wu
   Xin Wang
   Von Gosling
   Bruno Mahé
   Zhang Liang
   XIAORUI Wang
   Raja Sundaram Ganesan

Thanks,
Roman.

> 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 

Re: [VOTE] Sharding-Sphere incubation proposal

[Roman Shaposhnik]

On Mon, Nov 5, 2018 at 10:41 PM Roman Shaposhnik  wrote:
>
> 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...

+1 (binding)

Thanks,
Roman.

> 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 

Re: [VOTE] Ratis-thirdparty 0.1.0rc1

[Jitendra Pandey]

+1 (binding)

verified signatures
LICENSE and NOTICE look good
ASF headers good
Builds from the source.

On 11/9/18, 11:42 AM, "Josh Elser"  wrote:

Thanks, Justin.

Will take an action-item for the file extensions.

On 11/8/18 11:09 PM, Justin Mclean wrote:
> Hi,
> 
> +1 (binding)
> 
> I checked:
> - incubating in name
> - signature and hashes fine, but you may want to check the file 
extensions as policy changed a little while back to what was allowed
> - LICENSE and NOTICE good
> - no binary files
> - no source files, but poms have ASF headers
> - can compile from “source"
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

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




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

Re: [VOTE] Apache Toree 0.3.0-incubating (RC1)

[Eric Friedrich -X (efriedri - TRITON UK BIDCO LIMITED c/o Alter Domus (UK) Limited -OBO at Cisco)]

Hi-
  A few notes on the release package. Structure and contents look fine, but 
I’ve included some suggestions on some of the supporting things

Git tag not signed. I dont think this is a hard requirement but is good practice
$ git tag -v v0.3.0-incubating-rc1
error: v0.3.0-incubating-rc1: cannot verify a non-tag object of type commit.

Commit is empty in dist/toree/VERSION (but is correct in the binary release)
$ cat dist/toree/VERSION
VERSION: 0.3.0-incubating
COMMIT:

Was not able to build from source using Vagrant, perhaps something is wrong 
with my environment. 
$ vagrant up
$ export USE_VAGRANT=true
$ make

Getting Scala 2.12.6 (for sbt)...
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
5 artifacts copied, 0 already retrieved (19632kB/72ms)
java.lang.UnsupportedClassVersionError: scala/Option : Unsupported major.minor 
version 52.0

I checked:
- sigs and hashes good
- Licenses present and correct
- NOTICE file present
- No binary files

Thanks,
Eric

> On Nov 9, 2018, at 12:15 PM, Ryan Blue  wrote:
> 
> +1 (binding, carried over from the podling vote)
> 
> On Thu, Nov 8, 2018 at 7:54 PM Justin Mclean 
> wrote:
> 
>> Hi,
>> 
>> +1 (binding)
>> 
>> I checked:
>> - incubating in name (although I notice the pip package doesn’t - is this
>> a limitation?)
>> - signatures and hashes all good
>> - DISCLAIMER exists
>> - LICENSE and NOTICE file
>> - all source files have ASF headers
>> - No binary files in release
>> - Can compile from source
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
> 
> -- 
> Ryan Blue
> Software Engineer
> Netflix

Re: [VOTE] Ratis-thirdparty 0.1.0rc1

[Josh Elser]

Thanks, Justin.

Will take an action-item for the file extensions.

On 11/8/18 11:09 PM, Justin Mclean wrote:

Hi,

+1 (binding)

I checked:
- incubating in name
- signature and hashes fine, but you may want to check the file extensions as 
policy changed a little while back to what was allowed
- LICENSE and NOTICE good
- no binary files
- no source files, but poms have ASF headers
- can compile from “source"

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: [NEW MENTORS REQUIRED] Apache SensSoft

[loompa]

Hi Lewis,

I'd be up for helping too.

Cheers,
Dave

On Thu, 8 Nov 2018 at 22:06, lewis john mcgibbney 
wrote:

> Hi Folks,
> We are looking for new motivated mentors for the Apache SensSoft
> (Incubating) project [0] look at that kick ass Website :)
> In a nutshell SensSoft is a generalized user behavioral logging platform
> for web pages and thin-client applications.
> The podling was accepted into the Apache Incubator on 2016-07-13 so has
> been maturing and has made one release during that timeframe.
> We have been struggling somewhat with active mentorship which has
> attributed to the podling struggling with the final push through to
> graduation.
> Interestingly the SensSoft community is also going through the process of a
> PODLINGNAMESEARCH meaning that we will no longer be SensSoft but something
> else. This is an excellent time for a mentor or two to come aboard and help
> us drive onwards to TLP status.
> Please let us know at d...@senssoft.apache.org if you are interested,
> Lewis
>
> [0] http://senssoft.apache.org/
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>

[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk

[Dave Grove (JIRA)]

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

Dave Grove commented on INCUBATOR-222:
--

[~bdelacretaz] – All contributors are happy to proceed with the iCLAs that were 
already on file.  

> Donation of ibm-functions/composer code to Apache OpenWhisk
> ---
>
> Key: INCUBATOR-222
> URL: https://issues.apache.org/jira/browse/INCUBATOR-222
> Project: Incubator
>  Issue Type: New Feature
>Reporter: Dave Grove
>Priority: Major
> Attachments: composer-master-8403e58.20181003.tar.bz2
>
>
> IBM is donating the implementation of Composer (previously available  
> [https://github.com/ibm-functions/composer] at under the Apache 2 license) to 
> the Apache OpenWhisk project.
> This code base has 6 contributors.  Five of them are IBM employees who have 
> Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, 
> Kerry Chang, Nick Mitchell).  The 6th contributor does not have an Apache CLA 
> on file, but his contribution was a trivial fix of a typo in the 
> docs/README.md file 
> ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).]
> Attached is a tarball of the donated code at git commit hash 
> 8403e587ed73097b4794096e7afa7b166012f912.  This code will be submitted as a 
> PR to the github repository github.com/apache/incubator-openwhisk-composer by 
> IBM.
>  



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

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

Re: [VOTE] Apache Toree 0.3.0-incubating (RC1)

[Ryan Blue]

+1 (binding, carried over from the podling vote)

On Thu, Nov 8, 2018 at 7:54 PM Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name (although I notice the pip package doesn’t - is this
> a limitation?)
> - signatures and hashes all good
> - DISCLAIMER exists
> - LICENSE and NOTICE file
> - all source files have ASF headers
> - No binary files in release
> - Can compile from source
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Ryan Blue
Software Engineer
Netflix

[jira] [Created] (INCUBATOR-226) IP Clearance for OpenWhisk Composer

[Bertrand Delacretaz (JIRA)]

Bertrand Delacretaz created INCUBATOR-226:
-

 Summary: IP Clearance for OpenWhisk Composer
 Key: INCUBATOR-226
 URL: https://issues.apache.org/jira/browse/INCUBATOR-226
 Project: Incubator
  Issue Type: Task
Reporter: Bertrand Delacretaz


The donation of that module was discussed in INCUBATOR-222 and the IP clearance 
form has been created at 
http://incubator.apache.org/ip-clearance/openwhisk-composer.html but the 
Incubator PMC vote to accept the IP clearance has not happened.

[~dgrove] before I start that vote, I have added a note to that IP clearance 
form stating that "as explained above, a Software Grant is not required, all 
contributors have an iCLA on file"

Does that work for you? If yes I'll start the IP clearance vote. Sorry for the 
delay, this slipped through the cracks after the LEGAL-420 discussions.



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

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

Re: [VOTE] Accept the brpc Project into the Apache Incubator.

[Li,De(BDG)]

+1 (non-binding)

The brpc is very broadly used in Baidu, and I’m sure it will benefit to
many projects too.

On 2018/11/9 上午9:04， "Willem Jiang"  wrote:

>+1(binding)
>
>Willem Jiang
>
>Twitter: willemjiang
>Weibo: 姜宁willem
>
>On Fri, Nov 9, 2018 at 3:28 AM Dave Fisher  wrote:
>>
>> Hi -
>>
>> This is a VOTE to accept the brpc Project into the Apache Incubator.
>>
>> It will last for at least 72 hours and will pass if at least 3 +1 IPMC
>>Votes and more IPMC Votes are +1 than -1.
>>
>> [ ] +1, accept the brpc proposal.
>> [ ] -1, reject the brpc proposal
>>
>> Regards,
>> Dave
>>
>> = brpc Proposal =
>>
>> === Abstract ===
>>
>> brpc is an industrial-grade RPC framework for building reliable and
>>high-performance services.
>>
>>
>> === Proposal ===
>>
>> We propose to contribute the brpc codebase and associated
>>artifacts(e.g. documentation etc.) to the Apache Software Foundation,
>>and aim to  build a wider open community around it in the 'Apache Way'.
>>
>> === Background ===
>>
>> The RPC framework used in Baidu before 2014 was developed at 2008 and
>>limited in protocols and performance, and there were also serveral
>>implementations focused on their own scenarios from Baidu's different
>>BU. As an infrastructural team in Baidu, we tried to build a new
>>framework to unify all RPC scenarios inside. The framework was named
>>"baidu-rpc" internally the early versions were adopted and online at
>>late 2014. The framework was rapidly iterated at 2015-2017, and
>>thousands kinds of services and almost all core services adopted it. And
>>in 2017, we opensourced it as "brpc" and hope to get more adoptions and
>>contributions from outside. At the time of opensourcing, there're more
>>than 1 million instances inside Baidu using baidu-rpc (not counting
>>clients).
>>
>>
>> === Rationale ===
>>
>> brpc has been approved inside baidu, since many high performance core
>>services are using it.
>> And since its open source, it has been adopted by several other
>>companies, including Iqiyi, Didi, Sougou, BiliBili etc.
>>
>>
>> === Current Status ===
>>
>> brpc has been an open source project on GitHub
>>(https://github.com/brpc/brpc ) since 2017.
>>
>> Currently it has more than 7.3k stars, 1.6k forks, and is one of the
>>most popular repositories in topic of rpc category in GitHub rpc
>>catelogy.
>> It has been widely used in Baidu, with 1,000,000+ instances and
>>thousands kinds of services.
>> Besides, many other companies have already used it also, such as Iqiyi,
>>Didi, Sougou, BiliBili etc.
>>
>>
>> === Meritocracy ===
>>
>> brpc was originally created by Ge Jun and Chen zhangyi inside baidu
>>from 2014.
>> Since its opensource in 2017, it has already followed meritocracy
>>principles.
>> It accepts multiple contributions from other companies.
>> And now, the core developers are from several different companies.
>>
>> We will follow Apache way to encourage more developers to contribute in
>>this project.
>> We know that only active and committed developers from a diverse set of
>>backgrounds
>> can make brpc a successful project.
>>
>>
>> === Community ===
>>
>> brpc has been building an active community since its open source.
>>Currently,
>> the community includes over 31 contributors.
>> The core developers of brpc are listed below.
>>
>> === Core Developers ===
>>
>>   * Ge Jun(https://github.com/jamesge 
>>jge...@gmail.com )
>>   * Chen Zhangyi(https://github.com/chenzhangyi
>> frozen@gmail.com
>>)
>>   * Jiang Rujie(https://github.com/old-bear
>> jrjb...@gmail.com
>>)
>>   * Zhu Jiashun(http://github.com/zyearn 
>>zhujiashun2...@gmail.com )
>>   * Wang Yao(https://github.com/ipconfigme
>> ipconfi...@gmail.com
>>)
>>
>> === Alignment ===
>>
>> brpc is useful for building reliable and high-performance applications.
>> Since ASF has many famous performance-related and rpc-related projects,
>> we believe that ASF is a perfect choice to help brpc project to attract
>> more developers and users as well as having more cooperation with
>>existing projects.
>>
>> === Known Risks ===
>>  Orphaned products 
>>
>> Since our core developers are from different companies and many
>>companies are using it,
>> the risk of the project being abandoned is minimal.
>> For example, Baidu is extensively using it in their production
>>environment
>> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use
>>it in their production applications.
>>
>>  Inexperience with Open Source 
>>
>> brpc has been an active open source project for more than one year.
>> During that time, the project has attracted 30+ contributors and gained
>>a lot of attention.
>> The core developers are all