Re: Incubator podling reports due today

2019-09-06 Thread zhangli...@apache.org
Hi,

I got the point. The community will follow the instruction and has already
started to discuss how to attract new contributors and how to set
committers bar.

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Sheng Wu  于2019年9月7日周六 上午4:24写道:

> Hi Justin
>
> Yes. I got the point. I will talk to them. Thanks.
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> Twitter, wusheng1108
>
>
> Justin Mclean  于2019年9月6日周五 下午1:08写道:
>
> > Hi,
> >
> > > Is the shardingsphere report not accepted because of not enough mentors
> > > sign?
> >
> > No see my email to the dev list and my comment on the report.
> >
> > Thanks,
> > Justin
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>


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

2019-08-23 Thread zhangli...@apache.org
+1 (not binding), good luck

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Felix Cheung  于2019年8月24日周六 上午12:29写道:

> +1
>
> On Fri, Aug 23, 2019 at 8:11 AM ShaoFeng Shi 
> wrote:
>
> > +1 (binding)
> >
> > I believe the DolphinScheduler project will bring value to ASF. The team
> is
> > very open and the community is already very active. Glad to see it to
> join
> > the incubator.
> >
> > Best regards,
> >
> > Shaofeng Shi 史少锋
> > Apache Kylin PMC
> > Email: shaofeng...@apache.org
> >
> > Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> > Join Kylin user mail group: user-subscr...@kylin.apache.org
> > Join Kylin dev mail group: dev-subscr...@kylin.apache.org
> >
> >
> >
> >
> > Furkan KAMACI  于2019年8月23日周五 下午5:32写道:
> >
> > > Hi,
> > >
> > > +1!
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> > > 23 Ağu 2019 Cum, saat 12:25 tarihinde Sheng Wu <
> > wu.sheng.841...@gmail.com>
> > > şunu yazdı:
> > >
> > > > Julian Feinauer  于2019年8月23日周五
> 下午5:20写道:
> > > >
> > > > > Hi,
> > > > >
> > > > > Your proposal looks good and the initiual PPMC already looks
> > 'diverse'.
> > > > > Furthermore, it seems like you have a good mentoring team on board.
> > > > >
> > > > > One 'minor' concern is that I think it is best to use Apaches Infra
> > for
> > > > CI
> > > > > and Issue tracking.
> > > > > Which I would greatly prefer over using Github issues.
> > > > >
> > > >
> > > > Hi Julian
> > > >
> > > > Thanks for your supports.
> > > >
> > > > In the proposal, Jenkins means Apache INFRA Jenkins. I just changed
> the
> > > > proposal text to `Apache Jenkins`.
> > > >
> > > > I think GitHub Issue tracker is an open option, as many ASF projects
> > are
> > > > using it already, and GitHub issue notifications have been achieved
> in
> > > the
> > > > mail list.
> > > > Due to the team requires to use that, I think should be OK.
> > > >
> > > > Sheng Wu 吴晟
> > > >
> > > > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> > > > Twitter, wusheng1108
> > > >
> > > >
> > > >
> > > > >
> > > > > But overall, a clear +1 (binding) from my side.
> > > > >
> > > > > Julian
> > > > >
> > > > > Am 23.08.19, 11:14 schrieb "Kevin Ratnasekera" <
> > > djkevincr1...@gmail.com
> > > > >:
> > > > >
> > > > > +1
> > > > >
> > > > > On Fri, Aug 23, 2019 at 7:09 AM Sheng Wu 
> > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > After the discussion of DolphinScheduler(was EasyScheduler)
> > > > proposal
> > > > > > (discussion thread:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> > > > > > ),
> > > > > > I would like to call a VOTE to accept it into the Apache
> > > Incubator.
> > > > > >
> > > > > > Please cast your vote:
> > > > > >
> > > > > >   [ ] +1, bring DolphinScheduler into Incubator
> > > > > >   [ ] +0, I don't care either way
> > > > > >   [ ] -1, do not bring DolphinScheduler into Incubator,
> > > because...
> > > > > >
> > > > > > The vote will open at least for 72 hours and only votes from
> > the
> > > > > Incubator
> > > > > > PMC are binding.
> > > > > >
> > > > > > ==
> > > > > > Abstract
> > > > > >
> > > > > > DolphinScheduler is a distributed ETL scheduling engine with
> > > > > powerful DAG
> > > > > > visualization interface. DolphinScheduler focuses on solving
> > the
> > > > > problem of
> > > > > > 'complex task dependencies & triggers' in data processing.
> Just
> > > > like
> > > > > its
> > > > > > name, we dedicated to making the scheduling system out of the
> > > box.
> > > > > >
> > > > > > *Current project name of DolphinScheduler is EasyScheduler,
> > will
> > > > > change it
> > > > > > after it is accepted by Incubator.*
> > > > > > Proposal
> > > > > >
> > > > > > DolphinScheduler provides many easy-to-use features to
> > accelerate
> > > > > > the engineering efficiency on data ETL workflow job. We
> > propose a
> > > > new
> > > > > > concept of 'instance of process' and 'instance of task' to
> let
> > > > > developers
> > > > > > to tuning their jobs on the running state of workflow instead
> > of
> > > > > changing
> > > > > > the task's template. Its main objectives are as follows:
> > > > > >
> > > > > >- Define the complex tasks' dependencies & triggers in a
> DAG
> > > > > graph by
> > > > > >dragging and dropping.
> > > > > >- Support cluster HA.
> > > > > >- Support multi-tenant and parallel or serial backfilling
> > > data.
> > > > > >- Support automatical failure job retry and recovery.
> > > > > >- Support many data task types and process priority, task
> > > > > priority and
> > > > > >relative task timeout alarm.
> > > > > >
> > > > > > For now, 

Re: Showcase your project at ApacheCON at a Podling's Shark Tank

2019-08-15 Thread zhangli...@apache.org
I am interesting. I hope bring podling ShardingSphere to take part in Shark
Tank for ACNA & ACEU both if passable.


--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Myrle Krantz  于2019年8月15日周四 下午6:14写道:

> Y'all this is a great opportunity to highlight your community to potential
> contributors, and to network with other Apache Software Foundation
> contributors.  I highly recommend this event.
>
> Roman, once you get a tweet out, let me know and I'll retweet.  : o)
>
> Best Regards,
> Myrle
>
> On Wed, Aug 14, 2019 at 10:45 PM Roman Shaposhnik  wrote:
>
> > Hi Podlings!
> >
> > in less than a month we're going to have our first
> > ApacheCON this year -- the one in Las Vegas. In
> > about two month there will be one more in Berlin.
> >
> > These are not your regular ApacheCONs -- these are
> > 20th Anniversary of ASF ApacehCONs! In other words,
> > these are not to be missed!
> >
> > And even if your talk didn't get accepted -- you still
> > get an opportunity to highlight your project to, what's
> > likely going to be the biggest audience attending.
> >
> > Here's how: if you (or any community member who's
> > passionate about your project) are going to be at either
> > of those ApacheCONs consider signing up for
> > Podling's Shark Tank
> > events:
> > https://www.apachecon.com/acna19/s/#/scheduledEvent/1038
> > https://aceu19.apachecon.com/session/podlings-shark-tank
> >
> > Each project presenting will get ~10 min for the pitch and ~5 min
> > of panel grilling them on all sorts of things. Kind of like this ;-)
> >  https://www.youtube.com/watch?v=wmenN7NEdBc
> >
> > You've got nothing to lose (in fact, the opposite: you're likely to get
> > a prize!) and you will get a chance to receive feedback that might
> > actually help you grow your community and ultimately graduate to the
> > TLP status. And! Given our awesome panel of judges:
> >  * Myrle Krantz
> >  * Justin Mclean
> >  * Craig Russel
> >  * Shane Curcuru
> > We guarantee this to be a fun and useful event for your community!
> >
> > We will be tracking signups over here:
> >  https://wiki.apache.org/apachecon/ACNA19PodlingSharkTank
> >  https://wiki.apache.org/apachecon/ACEU19PodlingSharkTank
> > but for now:
> >
> > SIMPLY REPLY TO THIS EMAIL if you're interested.
> >
> > It is first come, first serve -- so don't delay -- sign up today!
> >
> > Thanks,
> > Roman.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>


Re: Missing podling logos

2019-05-14 Thread zhangli...@apache.org
Thank you for reminder.
The logo of ShardingSphere has already put on [1] and [2].

1. https://www.apache.org/img/
2. http://www.apache.org/logos/
--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Kenneth Knowles  于2019年5月14日周二 上午6:42写道:

> +d...@datasketches.apache.org 
>
> A logo was submitted alongside the SGA. Would using this logo be
> acceptable? I don't have experience with this (just doc reading and my
> working knowledge of ASF) since Beam was a merger that was extremely
> distinct from its pre-Apache existence.
>
> Kenn
>
> *From: *Justin Mclean 
> *Date: *Sat, May 11, 2019 at 9:47 PM
> *To: * 
> *Cc: * 
>
> Hi,
> >
> > My second list for the logos  [1] had a few errors as it assumed .svg
> > files existed for all projects. Try this one instead:
> >
> > Logos misisng:
> > amaterasu
> > annotator
> > batchee
> > brpc
> > datasketches
> > dlab
> > flagon
> > gobblin
> > hudi
> > iotdb
> > marvin
> > omid
> > pinot
> > ratis
> > rya
> > s2graph
> > samoa
> > sdap
> > shardingsphere
> > singa
> > tamaya
> > training
> > tephra
> > toree
> > tuweni
> > tvm
> > weex
> > zipkin
> >
> > Thanks,
> > Justin
> >
> > 1. http://www.apache.org/logos/
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>


Re: [ANNOUNCE] Apache ShardingSphere 4.0.0-RC1 available

2019-04-21 Thread zhangli...@apache.org
Thank you for suggestion. I will remind issues next time.

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


sebb  于2019年4月21日周日 下午7:22写道:

> Congrats on the release, however there are some issues with the announce
> mail.
>
> 1) it should include the Incubation disclaimer.
> 2) Download links must not use dist.apache.org. They must point to a
> download page.
>
> Perhaps simplify the description of the product; IMO there's too much
> detail for a general announce mail.
> Also the vote thread link is not relevant to end users
>
> On Sun, 21 Apr 2019 at 11:52, zhangli...@apache.org
>  wrote:
> >
> > Hi all,
> >
> > Apache ShardingSphere (incubating) Team is glad to announce the first
> > release of Apache ShardingSphere Incubating 4.0.0-RC1.
> >
> > 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.
> >
> >
> > Vote Thread:
> >
> https://lists.apache.org/thread.html/25c11b46dd3a58d4048dd35be71d21f86db6f5278480eb7083149af1@%3Cgeneral.incubator.apache.org%3E
> >
> > Download Links:
> >
> https://dist.apache.org/repos/dist/release/incubator/shardingsphere/4.0.0-RC1/
> >
> > Release Notes:
> >
> https://github.com/apache/incubator-shardingsphere/releases/tag/4.0.0-RC1/
> >
> > Website: https://shardingsphere.apache.org/
> >
> > ShardingSphere Resources:
> >
> > - Issue: https://github.com/apache/incubator-shardingsphere/issues
> > - Mailing list: d...@shardingsphere.apache.org
> > - Documents: https://shardingsphere.apache.org/document/current
> >
> > --
> >
> > Liang Zhang (John)
> > Apache ShardingSphere & Dubbo
>


[ANNOUNCE] Apache ShardingSphere 4.0.0-RC1 available

2019-04-21 Thread zhangli...@apache.org
Hi all,

Apache ShardingSphere (incubating) Team is glad to announce the first
release of Apache ShardingSphere Incubating 4.0.0-RC1.

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.


Vote Thread:
https://lists.apache.org/thread.html/25c11b46dd3a58d4048dd35be71d21f86db6f5278480eb7083149af1@%3Cgeneral.incubator.apache.org%3E

Download Links:
https://dist.apache.org/repos/dist/release/incubator/shardingsphere/4.0.0-RC1/

Release Notes:
https://github.com/apache/incubator-shardingsphere/releases/tag/4.0.0-RC1/

Website: https://shardingsphere.apache.org/

ShardingSphere Resources:

- Issue: https://github.com/apache/incubator-shardingsphere/issues
- Mailing list: d...@shardingsphere.apache.org
- Documents: https://shardingsphere.apache.org/document/current

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


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

2019-04-21 Thread zhangli...@apache.org
Thank for your remind, I will remind mentor to make vote clear next time.

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Justin Mclean  于2019年4月21日周日 下午5:50写道:

> Hi,
>
> > I saw the following mail from Willem, but this mail goes to dev@. My
> mail
> > achieved them in the same thread(maybe because of the title).
>
> No issue he vote is still binding and you have the 3 +1 votes, it just
> good to clear :-)
>
> Thanks,
> Justin
>
>
> -
> 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-RC1

2019-04-21 Thread zhangli...@apache.org
We’ve received 3 +1 binding votes and 0 +1 non-binding vote:

+1 binding, Willen Jiang
+1 binding, Sheng Wu
+1 binding, Gosling Von

Thank you everyone for taking the time to review the release and help us.
I will process to publish the release and send ANNOUNCE.


--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


zhangli...@apache.org  于2019年4月21日周日 下午4:50写道:

> Sorry, Let me correct. I will  statistics vote result here, not for new
> thread.
>
> --
>
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>
>
> zhangli...@apache.org  于2019年4月21日周日 下午4:46写道:
>
>> Thank you every one.
>> The vote has already opened for at least 72 hours and necessary number of
>> votes are reached.
>> Release vote is passed, I will sent a new thread to statistics all
>> participant mentors and paste thread link here.
>>
>> --
>>
>> Liang Zhang (John)
>> Apache ShardingSphere & Dubbo
>>
>>
>> Gosling Von  于2019年4月17日周三 上午10:15写道:
>>
>>> 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
>&g

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

2019-04-21 Thread zhangli...@apache.org
Sorry, Let me correct. I will  statistics vote result here, not for new
thread.

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


zhangli...@apache.org  于2019年4月21日周日 下午4:46写道:

> Thank you every one.
> The vote has already opened for at least 72 hours and necessary number of
> votes are reached.
> Release vote is passed, I will sent a new thread to statistics all
> participant mentors and paste thread link here.
>
> --
>
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>
>
> Gosling Von  于2019年4月17日周三 上午10:15写道:
>
>> 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/conte

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

2019-04-21 Thread zhangli...@apache.org
Thank you every one.
The vote has already opened for at least 72 hours and necessary number of
votes are reached.
Release vote is passed, I will sent a new thread to statistics all
participant mentors and paste thread link here.

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Gosling Von  于2019年4月17日周三 上午10:15写道:

> 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 

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

2019-04-16 Thread zhangli...@apache.org
I am sorry to make a bit confusing, dev list just for cc, we have already
finished ShardingSphere' s community internal vote.
This thread is for IPMC vote only.

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


 于2019年4月16日周二 下午4:57写道:

> Hi,
>
> > Have a vote on the dev list finished or are you just telling teh IPMC
> that you are voting on the dev list? If it the later then there is no need
> to do although I guess sit may possibly manage to get a few more IPMC
> votes. However sending the vote to two lists at once could also be a bit
> confusing.
>
> Sorry ignore that I should read more carefully,you are calling for IPMC
> votes.
>
> How many mentors / IPMC members have already voted on your release?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


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

2019-04-16 Thread zhangli...@apache.org
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


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

2019-03-19 Thread zhangli...@apache.org
+1 no binding

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Luke Han  于2019年3月19日周二 下午8:39写道:

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

Re: [Incubator Wiki] Update of "February2019" by LiangZhang

2019-02-01 Thread zhangli...@apache.org
I just removed unapproved releases and updated the wiki of Incubator PMC
report for February 2019. The release url now is [1].

[1] https://github.com/apache/incubator-shardingsphere/releases

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


zhangli...@apache.org  于2019年1月30日周三 下午4:01写道:

> Hi, Justin
> Thank you for advice. We will do it after all mentors come to a
> conclusion. Before do it, we are discussing on mail list first.
>
> --
>
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>
>
> Justin Mclean  于2019年1月30日周三 下午3:32写道:
>
>> Hi,
>>
>> > +   Discuss about how to deal with unapproved legacy release before
>> repo transfer.
>> > +   The details of email is:
>> https://lists.apache.org/thread.html/879089eb1dba43f6f159f8c3fde96c2a56d03edc9804f70dd7b94b6b@%3Cdev.shardingsphere.apache.org%3E\
>> <https://lists.apache.org/thread.html/879089eb1dba43f6f159f8c3fde96c2a56d03edc9804f70dd7b94b6b@%3Cdev.shardingsphere.apache.org%3E%5C>
>>
>> As mentioned in my email to your dev list these don’t appear to be legacy
>> releases and were released after you entered incubation. PPMC must not
>> release or distribute unapproved material. [1]
>>
>> Thanks,
>> Justin
>>
>> 1.  https://www.apache.org/dev/release-distribution#unreleased <
>> https://www.apache.org/dev/release-distribution#unreleased>
>
>


Re: Unapproved Sharding Sphere releases

2019-02-01 Thread zhangli...@apache.org
I updated wiki for remove unapproved releases.

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


吴晟 Sheng Wu  于2019年2月1日周五 下午10:51写道:

> Hi
>
>
> By following the Apache policy, besides the suggestions I gave and done.
> Just a moment ago, I deleted the recent two unapproved releases, 3.1.0.m1
> and 3.1.0 at GitHub release page[1].
>
>
> In further, I will help the shardingsphere community to follow the policy.
>
>
>
>
> [1] https://github.com/apache/incubator-shardingsphere/releases
>
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
>
> From Wu Sheng 's phone.
>
>
> -- Original --
> From: 吴晟 Sheng Wu 
> Date: Wed,Jan 30,2019 5:54 PM
> To: dev , dev <
> d...@shardingsphere.apache.org>
> Cc: Justin Mclean , jmclean 
> Subject: Re: Unapproved Sharding Sphere releases
>
>
>
> Hi
>
>
> I think I agree the Justin's points.
> No matter the release happens in Apache org repo or not, it still happened
> after you asked and accepted by Incubator. So, it is not encouraged and not
> following the Apache way.
>
>
> I propose these adjustments
> 1. Add statement in GitHub release versions. Saying these are not Apache
> release.
> 2. Add statement in you website home, document and download pages, saying
> all available releases are not Apache releases
> 3. After the first approved release, you only says before this
> version(4.0.0 maybe) are not Apachre releases.
> 4. Add statement in GitHub project readme.md for the same thing.
>
>
> Especially for document pages, this needs to be tagged in clear way.
> I know, those releases in maven central repo are hard to release, and not
> good for the existing community. So, I hope my proposals are good enough.
>
>
>
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
>
> From Wu Sheng 's phone.
>
>
> -- Original --
> From: zhangli...@apache.org 
> Date: Wed,Jan 30,2019 0:03 PM
> To: dev 
> Cc: Justin Mclean , jmclean 
> Subject: Re: Unapproved Sharding Sphere releases
>
>
>
> Hello Justin,
>
> Thanks for your advice.
> This is a legacy release, which we have discussed on the dev mail list[1]
> before.
> This release is done before the transfer to ASF repo and package rename.
> We are now preparing apache release which begins with new version(4.0.0).
> We will not release non-Apache version any more in the future.
> Any suggestion to identify versions like these kind of releases?
>
>
> [1]
>
> https://lists.apache.org/thread.html/a3bba7e53bfed6d18924b592ecf0533aebc8d307f8c7e399a7fec2cf@%3Cdev.shardingsphere.apache.org%3E
>
> --
>
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>
>
> Justin Mclean  于2019年1月30日周三 上午6:23写道:
>
> > Hi,
> >
> > Looking at [1] there seems to have been releases made after you have
> > entered incubation. All releases must be approved by the PPMC and the
> IPMC
> > (usually by voting). Can you please remove these releases and include in
> > your upcoming incubator report what you will do to stop this happening
> > going forward.
> >
> > Thanks,
> > Justin
> >
> > P.S please CC me on any replies as I'm not subscribed to this list
> >
> > 1.https://github.com/apache/incubator-shardingsphere/releases
> >
> >


Re: [Incubator Wiki] Update of "February2019" by LiangZhang

2019-01-30 Thread zhangli...@apache.org
Hi, Justin
Thank you for advice. We will do it after all mentors come to a conclusion.
Before do it, we are discussing on mail list first.

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Justin Mclean  于2019年1月30日周三 下午3:32写道:

> Hi,
>
> > +   Discuss about how to deal with unapproved legacy release before repo
> transfer.
> > +   The details of email is:
> https://lists.apache.org/thread.html/879089eb1dba43f6f159f8c3fde96c2a56d03edc9804f70dd7b94b6b@%3Cdev.shardingsphere.apache.org%3E\
> 
>
> As mentioned in my email to your dev list these don’t appear to be legacy
> releases and were released after you entered incubation. PPMC must not
> release or distribute unapproved material. [1]
>
> Thanks,
> Justin
>
> 1.  https://www.apache.org/dev/release-distribution#unreleased <
> https://www.apache.org/dev/release-distribution#unreleased>


Re: Incubator Wiki write access

2018-12-02 Thread zhangli...@apache.org
Hello,

Because of Due 5th December for Incubator Podling Report, so any one setup
wiki write access for me, thank you very much.

--

Liang Zhang (John)
Apache Sharding-Sphere & Dubbo


zhangli...@apache.org  于2018年11月30日周五 下午12:44写道:

> Hello,
>
> I'm a PPMC of Apache ShardingSphere(incubating),  I need a write access to
> the incubator wiki to write incubator report of ShardingSphere.
> Could someone help me to setup it?
> My username of wiki is LiangZhang.
>
> --
>
> Liang Zhang (John)
> Apache Sharding-Sphere & Dubbo
>


Incubator Wiki write access

2018-11-29 Thread zhangli...@apache.org
Hello,

I'm a PPMC of Apache ShardingSphere(incubating),  I need a write access to
the incubator wiki to write incubator report of ShardingSphere.
Could someone help me to setup it?
My username of wiki is LiangZhang.

--

Liang Zhang (John)
Apache Sharding-Sphere & Dubbo


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

2018-11-11 Thread zhangli...@apache.org
+1 (no binding)

Best Regards,
John (Liang Zhang) from ShardingSphere

fisherman  于2018年11月12日周一 上午10:45写道:

> +1 (no binding)
>
> Dave Fisher  于2018年11月9日周五 上午3:28写道:
>
> > 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 <
> > https://github.com/chenzhangyi> frozen@gmail.com  > 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 <
> 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 

Re: [VOTE] Sharding-Sphere incubation proposal

2018-11-06 Thread zhangli...@apache.org
e value and reputation that the Apache brand would
> > bring to Sharding-Sphere. However, our primary interest is in the
> > excellent community provided by Apache Software Foundation, in which
> > all the projects could gain stability for long-term development.
> >
> > = Documentation =
> > A complete set of Sharding-Sphere documentations is provided on
> > shardingsphere.io in both English and Simplified Chinese.
> >
> >* [[http://shardingsphere.io/document/current/en/overview/|English]]
> >* [[http://shardingsphere.io/document/current/cn/overview/|Chinese]]
> >
> > = Initial Source =
> > The project consists of three distinct codebases: core, example and
> > document. The address of three existed git repositories are as
> > follows:
> >
> >* https://github.com/sharding-sphere/sharding-sphere
> >* https://github.com/sharding-sphere/sharding-sphere-example
> >* https://github.com/sharding-sphere/sharding-sphere-doc
> >
> > = Source and Intellectual Property Submission Plan =
> > The codes are currently under Apache License Version 2.0 and have been
> > verified to have no intellectual property or license issues before
> > being released to open source by Dangdang in 2016. Dangdang will
> > provide SGA and all committers will sign ICLA after Sharding-Sphere is
> > accepted into the Incubator.
> >
> > = External Dependencies =
> >
> > As all dependencies are managed using Apache Maven, none of the
> > external libraries need to be packaged in a source distribution. All
> > dependencies have Apache compatible licenses except MySQL (GPL-2.0).
> >
> > We will remove MySQL dependencies in future. MySQL JDBC driver is
> > adopted by Sharding-Proxy to connect MySQL now; We will use SPI to
> > load JDBC driver, so MySQL JDBC driver is no longer provided on
> > Sharding-Sphere.
> >
> >* Guava Apache-2.0
> >* Guava Retrying Apache-2.0
> >* commons-codec Apache-2.0
> >* commons-pool Apache-2.0
> >* commons-dbcp Apache-2.0
> >* netty Apache-2.0
> >* curator Apache-2.0
> >* grpc Apache-2.0
> >* protobuf BSD 3-clause
> >* lombok MIT
> >* groovy Apache-2.0
> >* snakeyaml Apache-2.0
> >* spring-context-support Apache-2.0
> >* spring-context-test Apache-2.0
> >* spring-boot-starter Apache-2.0
> >* spring-boot-configuration-processor Apache-2.0
> >* spring-boot-starter-test Apache-2.0
> >* slf4j MIT
> >* logback EPL-1.0
> >* junit EPL-1.0
> >* hamcrest BSD 3-clause
> >* mockito MIT
> >* h2 MPL-2.0/EPL-1.0
> >* mysql GPL-2.0 Will remove before first apache release, use SPI
> instead of it
> >* postgresql BSD
> >* mssql-jdbc MIT
> >* HikariCP Apache-2.0
> >* ANTLR BSD
> >* OpenTracing BSD
> >
> > = Required Resources =
> > == Git Repositories ==
> >* https://github.com/sharding-sphere/sharding-sphere.git
> >* https://github.com/sharding-sphere/sharding-sphere-example.git
> >* https://github.com/sharding-sphere/sharding-sphere-doc.git
> >
> >
> > == Issue Tracking ==
> >
> > The community would like to continue using GitHub Issues.
> >
> > == Continuous Integration tool ==
> > Travis
> >
> > == Mailing Lists ==
> >* Sharding-Sphere-dev: for development discussions
> >* Sharding-Sphere-private: for PPMC discussions
> >* Sharding-Sphere-notifications: for users notifications, and
> > notifications from GitHub
> >
> > == Initial Committers ==
> >* 张亮, Liang Zhang, zhangli...@apache.org
> >* 曹昊, Hao Cao,
> >* 吴晟, Sheng Wu, wush...@apache.org
> >* 高洪涛, Hongtao Gao, hanahm...@apache.org
> >* 张永伦, Yonglun Zhang
> >* 潘娟, Juan Pan
> >* 赵俊, Jun Zhao
> >* 岳令, Ling Yue
> >* 马晓光, Xiaoguang Ma
> >* 陈清阳, QingYang Chen
> >* 彭勇升, Yongsheng Peng, pen...@apache.org
> >
> > == Affiliations ==
> >* JD: Liang Zhang, Yonglun Zhang, Juan Pan, Jun Zhao
> >* Dangdang: Hao Cao, Ling Yue
> >* CHINA TELECOM Bestpay: QingYang Chen
> >* Individuals: Sheng Wu, Hongtao Gao, Xiaoguang Ma
> >
> > = Sponsors =
> > == Champion ==
> >* Roman Shaposhnik (rvs at apache dot org)
> >
> > == Mentors ==
> >* Craig L Russell (clr at apache dot org)
> >* Benjamin Hindman (benh at apache dot org)
> >* Willem Ning Jiang (ningjiang at apache dot org)
> >
> > == 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
> >
> --
> Thanks,
> Bruno
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [DISCUSS] Sharding-Sphere incubation proposal

2018-11-01 Thread zhangli...@apache.org
Hi, Yongsheng Peng

Welcome, after Sharding-Sphere enter to incubation, we can discuss more
details.

—
John (Zhang Liang) from Sharding-Sphere

彭勇升 Peng Yongsheng <8082...@qq.com> 于2018年10月31日周三 下午10:16写道:

> Hi, ZhangLiang:
> This project looks so interesting, I wana to join.
>
> —
> Yongsheng Peng
> Apache SkyWalking PPMC member
>
>
>
> > 在 2018年10月29日,17:27,zhangli...@apache.org 写道:
> >
> > Dear Apache Incubator Community,
> >
> > I would like to start a discussion about the incubation of
> Sharding-Sphere
> > at Apache.
> >
> > Please accept the Sharding-Sphere podling into the Incubator.
> >
> > We have 4 mentors, also we are welcome other volunteers to mentor us.
> >
> > The proposal can be found at
> > https://wiki.apache.org/incubator/ShardingSphereProposal . Here is the
> text
> > of it:
> >
> >
> > = 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
> > 

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

2018-10-30 Thread zhangli...@apache.org
Glad to see SkyWalking graduate soon. A good project and wonderful
community!
Good luck!

Regards,
-John (Zhang Liang)

Bertrand Delacretaz  于2018年10月30日周二 下午4:27写道:

> Hi,
>
> On Tue, Oct 30, 2018 at 8:21 AM Mick Semb Wever  wrote:
> > ...RESOLVED, that the initial Apache SkyWalking PMC be and hereby is
> tasked
> > with the creation of a set of bylaws...
>
> You should remove this paragraph - this needs to be clarified and
> better documented but the current consensus is that projects shouldn't
> create their own bylaws. They might create community guidelines, but
> that doesn't need to be mentioned in the resolution.
>
> Apart from that the resolution looks good to me.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


[DISCUSS] Sharding-Sphere incubation proposal

2018-10-29 Thread zhangli...@apache.org
-1.0
  * junit EPL-1.0
  * hamcrest BSD 3-clause
  * mockito MIT
  * h2 MPL-2.0/EPL-1.0
  * mysql GPL-2.0 Will remove before first apache release, use SPI instead
of it
  * postgresql BSD
  * mssql-jdbc MIT
  * HikariCP Apache-2.0
  * ANTLR BSD
  * OpenTracing BSD

= Required Resources =
== Git Repositories ==
  * https://github.com/sharding-sphere/sharding-sphere.git
  * https://github.com/sharding-sphere/sharding-sphere-example.git
  * https://github.com/sharding-sphere/sharding-sphere-doc.git


== Issue Tracking ==

The community would like to continue using GitHub Issues.

== Continuous Integration tool ==
Travis

== Mailing Lists ==
  * Sharding-Sphere-dev: for development discussions
  * Sharding-Sphere-private: for PPMC discussions
  * Sharding-Sphere-notifications: for users notifications, and
notifications from GitHub

== Initial Committers ==
  * 张亮, Liang Zhang, zhangli...@apache.org
  * 曹昊, Hao Cao,
  * 吴晟, Sheng Wu, wush...@apache.org
  * 高洪涛, Hongtao Gao, hanahm...@apache.org
  * 张永伦, Yonglun Zhang
  * 潘娟, Juan Pan
  * 赵俊, Jun Zhao
  * 岳令, Ling Yue
  * 马晓光, Xiaoguang Ma
  * 陈清阳, QingYang Chen

== Affiliations ==
  * JD: Liang Zhang, Yonglun Zhang, Juan Pan, Jun Zhao
  * Dangdang: Hao Cao, Ling Yue
  * CHINA TELECOM Bestpay: QingYang Chen
  * Individuals: Sheng Wu, Hongtao Gao, Xiaoguang Ma

= Sponsors =
== Champion ==
  * Roman Shaposhnik (rvs at apache dot org)

== Mentors ==
  * Craig L Russell (clr at apache dot org)
  * Benjamin Hindman (benh at apache dot org)
  * Willem Ning Jiang (ningjiang at apache dot org)

== Sponsoring Entity ==
We are expecting the Apache Incubator could sponsor this project.


Best Regards,
John(Zhang Liang) from Sharding-Sphere


subscribe apache incubator email list

2018-10-23 Thread zhangli...@apache.org
subscribe apache incubator email list