date:20190421

Hi,

On Mon, Apr 22, 2019 at 12:20 PM Justin Mclean  wrote:
>
> Hi,
>
> > From my understanding, I don't see any issues that stop us from
> > allowing product depend on LGPL licensed software…
>
> Expect that it is against ASF policy as it listed in Category X, and podlings 
> (and TLP) are expected to follow ASF legal / release policy. Please ask why 
> on legal discuss and not here. The incubator doesn’t set legal, release or 
> distribution policy and can only guide podlings on the practical aspects of 
> it.

I have no objection to it. I will consult with legal team about this issue.

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


-- 
Best Regards！
Huxing

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

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

Hi,

> From my understanding, I don't see any issues that stop us from
> allowing product depend on LGPL licensed software…

Expect that it is against ASF policy as it listed in Category X, and podlings 
(and TLP) are expected to follow ASF legal / release policy. Please ask why on 
legal discuss and not here. The incubator doesn’t set legal, release or 
distribution policy and can only guide podlings on the practical aspects of it.

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 Dubbo Admin(Incubating) 0.2.0 [RC3]

Hi,

Just FYI:

On Mon, Apr 22, 2019 at 10:22 AM Justin Mclean  wrote:
>
> Hi,
>
> Interesting to note that has been discuss at the board level but no 
> resolution was passed. This was back in 2005 so I’m not aware of the history 
> or why the resolution wasn’t passed [1] a search of the mailing lists from 
> that time may provide an answer.

I've attached the board meeting minutes as below:

28 Jul 2005: Allow product dependencies on LGPL-licensed libraries (tabled) [1]

E. V.P. of Legal Affairs [Cliff Schmidt]

   See Special Orders for two proposed resolutions.

   The first resolution allows PMCs to develop and distribute
   software that depends on the presence of LGPL-licensed
   libraries, *without* distributing the libraries themselves.
   After numerous discussions with the FSF, other LGPL licensors,
   and ASF counsel, Larry Rosen, it appears that such a policy
   should not impact the product licensing.  In order to allow
   PMCs to apply this policy to all useful LGPL-licensed
   libraries, the resolution does not require the PMCs to get
   an agreement from each copyright owner, but instead requires
   the PMC to register the use of the particular LGPL library
   with the VP of Legal Affairs.  See my post to the board@
   list for more details ("My recommendation for an ASF policy on
   the LGPL").

   The second resolution allows PMCs to redistribute MPL/NPL-
   licensed executables.  The key difference between the MPL/NPL
   and the LGPL regarding redistribution requirements is that the
   MPL/NPL allows redistribution under any license (provided that
   the distributor complies with the applicable terms of the
   MPL/NPL); the LGPL requires redistribution of either the source
   or executable of the library to be licensed only under the LGPL.

   While the MPL 1.0, MPL 1.1, NPL 1.0, and NPL 1.1 are nearly
   identical in their treatment of redistribution of executables,
   it is important to note that the NPL licenses are not OSI-
   approved, as they discriminate in favor of Netscape, weakening
   the terms that Netscape has to comply with relative to other
   users.  See my post to the board@ list for more details ("MPL/NPL
   Issue: My recommendation for an ASF policy on the MPL/NPL").

   NOTE: Larry Rosen has agreed with my analysis of the MPL/NPL
   licenses as described in the referenced post; however, yesterday
   he suggested that I confirm that Mitchell Baker also agrees
   (author of the licenses).  I have not yet received her response.
   This could be a reason to table this resolution.

17 Aug 2005: Allow product dependencies on LGPL-licensed libraries (tabled) [2]

E. V.P. of Legal Affairs [Cliff Schmidt]

   I've inserted slightly edited versions of the same MPL/NPL
   and LGPL resolutions, which were tabled last month.

   Since last month's meeting, I have:
 - confirmed with a second member of ASF's legal counsel
   that the proposed LGPL policy does not put our product
   licensing at risk;
 - posted and discussed the proposed LGPL policy on the
   legal-discuss list, where no new concerns were raised
   about the licensing ramifications; however there was
   concern raised by both outside lawyers and Apache
   committers that dependencies on LGPL libraries was not
   in the best interests of some Apache users;
 - engaged with representatives of the Mozilla Foundation
   to discuss the proposed MPL/NPL licensing policy.  While
   they have *not* yet formally indicated their agreement
   with our interpretation, they have not yet raised any
   new concerns.

   Future action items include resolving the BXA/crypto issue
   and investigating and proposing policies for the CPL, EPL,
   and CDDL licenses.

   Finally, one of my short-term objectives is to overhaul the
   legal STATUS file to reflect the current priorities and
   status.

16 Nov 2005: LGPL resolution (tabled) [3]

LGPL: I'm still waiting on feedback from Eben on my
Java/LGPL position paper that I sent him last month. He
wanted to refrain from giving me feedback until
discussing the matter with the FSF. I expect to have
something any day now, since that meeting should have
recently happened.  I recommend we hold off any decision
to allow distribution of LGPL components within non-
incubating product JARs until getting this one last
opinion from Eben and then bouncing it off the rest of
our counsel.  However, I do not think we should have any
legal concern about separately distributing the LGPL and
ASF component that depends on it; both Jason and Larry
have signed off on this question.

The

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

Hi

> That option is based on my understanding that linking to
> "hibernate-core" does not create a derivative work of
> "hibernate-core".
> Yes, when compiling the source code and run the incubator-dubbo-admin
> code, the hibernate-core binary will be included, this
> will create a derivative work of "hibernate-core". As long as user do
> not distribute it, I think it is fine to use it.
> This is the same case as using "spring-boot-starter-data-jpa".
> However, it becomes a problem when user want to distributed the
> incubator-dubbo-admin binary, it must not be licensed as Apache
> license, but should only be GPL/LGPL licensed.
> This creates a risk that some user won't use this software because of
> the potential license issue, which is not what we want.
> So as long as an Apache project does not distribute the binary, IMO it is
fine.
> That is my understanding of why this is an option. It is not a good
> option, but I think it is an option.

As an Apache project, we should make sure re-distribution friendly, no
matter what the user intends to do.
So I still think only keep them optional, and the user could download and
use them if they want by themselves.

For the license part, I am not an expert, even not close, but I prefer to
follow the Apache suggestion at this moment. Unless the board or legal team
change that.

As it belongs to Catalog X[1] now and also supported by your answer, LGPL
is not friendly to re-distribution.
I still consider this a license issue.

Also, you could bring this discussion to legal ml, I think.

[1] https://apache.org/legal/resolved.html#category-x

Sheng Wu 吴晟

Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


Huxing Zhang  于2019年4月22日周一 上午10:18写道：

> Hi,
>
> On Sun, Apr 21, 2019 at 11:11 PM Sheng Wu 
> wrote:
> >
> > Hi.
> >
> > > 1. Stop distribute the binary of incubator-dubbo-admin
> >
> > I think "stop distribute the binary" would NOT change the fact the source
> > release could lead users to use `hiberante-core`. I doubt this is an
> option.
>
> That option is based on my understanding that linking to
> "hibernate-core" does not create a derivative work of
> "hibernate-core".
> Yes, when compiling the source code and run the incubator-dubbo-admin
> code, the hibernate-core binary will be included, this
> will create a derivative work of "hibernate-core". As long as user do
> not distribute it, I think it is fine to use it.
> This is the same case as using "spring-boot-starter-data-jpa".
> However, it becomes a problem when user want to distributed the
> incubator-dubbo-admin binary, it must not be licensed as Apache
> license, but should only be GPL/LGPL licensed.
> This creates a risk that some user won't use this software because of
> the potential license issue, which is not what we want.
> So as long as an Apache project does not distribute the binary, IMO it is
> fine.
> That is my understanding of why this is an option. It is not a good
> option, but I think it is an option.
>
> >
> > Also based on the license issue, you should consider canceling this vote,
> > and move the further discussion to dev ml.
>
> I agree that cancel this vote is the safest way for now, before
> everything is cleared.
>
> >
> >
> > Sheng Wu 吴晟
> >
> > Apache SkyWalking, ShardingSphere, Zipkin
> > Twitter, wusheng1108
> >
> >
> > Huxing Zhang  于2019年4月21日周日 下午11:02写道：
> >
> > > Hi,
> > >
> > > I am thinking why spring-boot-starter-data-jpa depends on LGPL
> > > licensed library "hibernate-core", and can still be Apache 2.0
> > > licensed.
> > > I am reading [1]. In section 5 it says:
> > >
> > > A program that contains no derivative of any portion of the Library,
> > > but is designed to work with the Library by being compiled or linked
> > > with it, is called a "work that uses the Library". Such a work, in
> > > isolation, is not a derivative work of the Library, and therefore
> > > falls outside the scope of this License.
> > >
> > > I think spring-boot-starter-data-jpa falls in to this case. It is a
> > > "work that uses the Library".
> > >
> > > The source code of incubator-dubbo-admin should also falls into this
> > > case, because it does not contain any portion of the hibernate-core.
> > > Based on it and explanation here[2], I think the source code can be
> > > released anyway. Is my understanding correct?
> > >
> > > Next, the LGPL license says:
> > >
> > > However, linking a "work that uses the Library" with the Library
> > > creates an executable that is a derivative of the Library (because it
> > > contains portions of the Library), rather than a "work that uses the
> > > library". The executable is therefore covered by this License.
> > >
> > > The binary distribution of incuabator-dubbo-admin falls into this case
> > > because it creates an executable that contains binary of
> > > hibernate-core. Therefore it is a "work based on the library". As a
> > > derivative of hibernate-core, it must be licensed with LGPL/GPL, which
> > > is not allowed as an Apache

Re: Setting up DataSketches (name search in progress)

2019-04-21 Thread Kenneth Knowles

Just an update here is that we are done with DNS, LDAP, mailing lists and
name search (we didn't gate on it, but it finished before other things
anyhow). We are making sure everyone has their ICLAs and is subscribed to
the lists and will discuss next steps there. I believe the need to discuss
DataSketches on general@incubator.apache.org is done. So if you are
interested, please subscribe to d...@datasketches.apache.org.

Kenn

On Wed, Apr 3, 2019 at 8:18 AM Dave Fisher  wrote:

>
>
> > On Apr 2, 2019, at 8:39 PM, Kenneth Knowles  wrote:
> >
> > Hi all,
> >
> > I have added DataSketches to podlings.xml with help from Dave Fisher [1].
> > The name search is underway, credit to Lee Rhodes [2].
> >
> > Next steps as I understand them are to set up:
> >
> >   - podling status page
> >   - DNS
> >   - LDAP
> >   - web site
> >   - mailing lists
>
> Get initial committers who do not have apache ids to send their ICLAs to
> the secretary indicating their preferred Apache ID and DataSketches as
> their project.
> Make sure that all initial committers subscribe to all of the mailing
> lists especially private@.
>
> >   - git repo
>
> For GitHub access.
> (1) id.apache.org make sure that users associate their GitHub username.
> (2) On Github.com two factor authentication (2FA) must be enabled for the
> Github username.
>
> >
> > I am not confident on which of these is very easy to rename versus which
> > are best to leave until after name search. By default, leaving them all
> > until after name search.
>
> I would not necessarily gate on the Name Search. I think Tuweni was
> special and unusual here since it was a near certainty that Cava was a
> conflict. Many podlings do not do a name search until near graduation. I’ve
> taken a look at yours and IMO I don’t think VP, Brand is going to have an
> issue, but that’s not my call.
>
> Regards,
> Dave
>
> >
> > Kenn
> >
> > [1] http://svn.apache.org/viewvc?view=revision=1856700
> > [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-168
>
>
> -
> 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]

On Mon, Apr 22, 2019 at 10:17 AM Justin Mclean  wrote:
>
> HI,
>
> > However, LGPL software does not fit into this case, because in [2]
> > section 5, it says linking to a LGPL software is not considered to
> > create a derivative work.
>
> It still places restriction above and beyond what the ALv2 does and that why 
> it’s listing in Category X. [1]
>
> > Basically I am trying to figure out, why in ASF policy, linking to
> > LGPL code is not allowed. I just want to discuss this issue
> > technically. No other meanings.
>
> I suggest you ask on the legal discuss list they are likely to be able to 
> provide a better answer.

Thanks, I am planning to do that. :-) This issue has confused me for a while.

>
> Thanks,
> Justin
>
> 1. https://apache.org/legal/resolved.html#category-x 
> 



-- 
Best Regards！
Huxing

-
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]

Hi,

Interesting to note that has been discuss at the board level but no resolution 
was passed. This was back in 2005 so I’m not aware of the history or why the 
resolution wasn’t passed [1] a search of the mailing lists from that time may 
provide an answer.

Thanks,
Justin

1,https://www.apache.org/foundation/board/calendar-2005-2009.html

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

Hi,

On Sun, Apr 21, 2019 at 11:11 PM Sheng Wu  wrote:
>
> Hi.
>
> > 1. Stop distribute the binary of incubator-dubbo-admin
>
> I think "stop distribute the binary" would NOT change the fact the source
> release could lead users to use `hiberante-core`. I doubt this is an option.

That option is based on my understanding that linking to
"hibernate-core" does not create a derivative work of
"hibernate-core".
Yes, when compiling the source code and run the incubator-dubbo-admin
code, the hibernate-core binary will be included, this
will create a derivative work of "hibernate-core". As long as user do
not distribute it, I think it is fine to use it.
This is the same case as using "spring-boot-starter-data-jpa".
However, it becomes a problem when user want to distributed the
incubator-dubbo-admin binary, it must not be licensed as Apache
license, but should only be GPL/LGPL licensed.
This creates a risk that some user won't use this software because of
the potential license issue, which is not what we want.
So as long as an Apache project does not distribute the binary, IMO it is fine.
That is my understanding of why this is an option. It is not a good
option, but I think it is an option.

>
> Also based on the license issue, you should consider canceling this vote,
> and move the further discussion to dev ml.

I agree that cancel this vote is the safest way for now, before
everything is cleared.

>
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
> Huxing Zhang  于2019年4月21日周日 下午11:02写道：
>
> > Hi,
> >
> > I am thinking why spring-boot-starter-data-jpa depends on LGPL
> > licensed library "hibernate-core", and can still be Apache 2.0
> > licensed.
> > I am reading [1]. In section 5 it says:
> >
> > A program that contains no derivative of any portion of the Library,
> > but is designed to work with the Library by being compiled or linked
> > with it, is called a "work that uses the Library". Such a work, in
> > isolation, is not a derivative work of the Library, and therefore
> > falls outside the scope of this License.
> >
> > I think spring-boot-starter-data-jpa falls in to this case. It is a
> > "work that uses the Library".
> >
> > The source code of incubator-dubbo-admin should also falls into this
> > case, because it does not contain any portion of the hibernate-core.
> > Based on it and explanation here[2], I think the source code can be
> > released anyway. Is my understanding correct?
> >
> > Next, the LGPL license says:
> >
> > However, linking a "work that uses the Library" with the Library
> > creates an executable that is a derivative of the Library (because it
> > contains portions of the Library), rather than a "work that uses the
> > library". The executable is therefore covered by this License.
> >
> > The binary distribution of incuabator-dubbo-admin falls into this case
> > because it creates an executable that contains binary of
> > hibernate-core. Therefore it is a "work based on the library". As a
> > derivative of hibernate-core, it must be licensed with LGPL/GPL, which
> > is not allowed as an Apache product, and eventually causes the
> > incompatibility.
> >
> > If my understanding is correct, there are at least 4 ways to solve this
> > issue:
> > 1. Stop distribute the binary of incubator-dubbo-admin
> > 2. Make the feature optional, as explained here[3]
> > 3. Stop depending on hiberante-core
> > 4. Choose other Apache compatible equivalent
> >
> > I recommend to go with number 3 in my last thread.
> >
> >
> > [1] https://opensource.org/licenses/LGPL-2.1
> > [2] https://www.apache.org/legal/resolved.html#prohibited
> > [3] https://www.apache.org/legal/resolved.html#optional
> >
> > On Sun, Apr 21, 2019 at 10:40 AM Huxing Zhang  wrote:
> > >
> > > Hi,
> > >
> > > ccing dev@dubbo
> > >
> > > On Fri, Apr 19, 2019 at 8:24 AM Willem Jiang 
> > wrote:
> > > >
> > > > Hi，
> > > >
> > > > I just checked the binary release kit, it has the third party
> > > > dependency of LGPL (Hibernate core) which is belonged to Cataloge
> > > > X[1],  it cannot be included in Apache Product.
> > > > I had to vote -1 for it. We can change the ORM lib to Eclipse Link to
> > > > fix this issue, I just fill an issue here[2].
> > >
> > > I did some dig for this issue and confirm that this is introduced by
> > > this pull request[1].
> > > The purpose of this pull request is to introduce the pagination to
> > > service query.
> > > In this pull request a dependency to spring-boot-starter-data-jpa was
> > added,
> > > which introduce the LGPL licensed dependency hibernate-core.
> > > The detailed dependency tree is shown below:
> > >
> > > [INFO] +-
> > org.springframework.boot:spring-boot-starter-data-jpa:jar:2.0.2.RELEASE:compile
> > > [INFO] |  +-
> > org.springframework.boot:spring-boot-starter-aop:jar:2.0.2.RELEASE:compile
> > > [INFO] |  |  \- org.aspectj:aspectjweaver:jar:1.8.13:compile
> > > [INFO] |  +-
> >

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

HI,

> However, LGPL software does not fit into this case, because in [2]
> section 5, it says linking to a LGPL software is not considered to
> create a derivative work.

It still places restriction above and beyond what the ALv2 does and that why 
it’s listing in Category X. [1]

> Basically I am trying to figure out, why in ASF policy, linking to
> LGPL code is not allowed. I just want to discuss this issue
> technically. No other meanings.

I suggest you ask on the legal discuss list they are likely to be able to 
provide a better answer.

Thanks,
Justin

1. https://apache.org/legal/resolved.html#category-x

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

Hi,

On Mon, Apr 22, 2019 at 8:18 AM Justin Mclean  wrote:
>
> Hi,
>
> > I am thinking why spring-boot-starter-data-jpa depends on LGPL
> > licensed library "hibernate-core", and can still be Apache 2.0
> > licensed.
>
> That may be the case for a non ASF project, but it is ASF policy to not 
> depends on GPL code. [1][2]

I understand it is ASF policy to not depend on GPL code. In [1] it
clears states:

We avoid GPLv3 software because merely linking to it is considered by
the GPLv3 authors to create a derivative work

However, LGPL software does not fit into this case, because in [2]
section 5, it says linking to a LGPL software is not considered to
create a derivative work.

Basically I am trying to figure out, why in ASF policy, linking to
LGPL code is not allowed. I just want to discuss this issue
technically. No other meanings.

>
> In short "The Apache Software Foundation does not allow its own projects to 
> distribute software under licenses more restrictive than the Apache License,"

IMO, if what state in [2], section 5, is the case, the source code of
incubator-dubbo-admin, could still be distributed with Apache License.

Maybe I am missing something here, I'd be appreciated if someone could
point it out.

[1]  https://www.apache.org/licenses/GPL-compatibility.html
[2]  https://opensource.org/licenses/LGPL-2.1

>
> Thanks,
> Justin
>
> 1. https://www.apache.org/licenses/GPL-compatibility.html
> 2. https://www.apache.org/legal/resolved.html#category-x
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-- 
Best Regards！
Huxing

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

Re: [VOTE] Release Apache OpenWhisk Composer 0.11.0 (incubating)

Hi,

Can someone please confirm this is the case and the vote was not just on the 
GitHub repo?

> Assuming the artefact voted on was [1].
> 
> 1. 
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.11.0-incubating-rc2/

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 Dubbo Admin(Incubating) 0.2.0 [RC3]

Hi,

> I am thinking why spring-boot-starter-data-jpa depends on LGPL
> licensed library "hibernate-core", and can still be Apache 2.0
> licensed.

That may be the case for a non ASF project, but it is ASF policy to not depends 
on GPL code. [1][2]

In short "The Apache Software Foundation does not allow its own projects to 
distribute software under licenses more restrictive than the Apache License,"

Thanks,
Justin

1. https://www.apache.org/licenses/GPL-compatibility.html
2. https://www.apache.org/legal/resolved.html#category-x
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Incubator Wiki spring clean

Hi,

I’ve went through and organised teh incubator wiki a little;
- Reports page have been organised user [1]. Some are missing I’ve raise an 
INFRA JIRA for this.
- A lot off pages can be deleted I’ve moved these to “To Delete” [2]
- People have been moved to [3]. I think the majority of these can be deleted.
- Pages of historical interest I’ve moved to here [4]
- Proposals I’ve moved to here [5]
- I’ve updated the front page to remove outdated information and fix the report 
table but more could be done here.

It still needs a little clean up. If anyone notices any other missing pages 
please speak up. Please feel free to update or point out anything that is 
duplicated elsewhere or is out of date.

Thanks,
Justin

1. https://cwiki.apache.org/confluence/display/INCUBATOR/Reports
2,.https://cwiki.apache.org/confluence/display/INCUBATOR/To+Delete
3. https://cwiki.apache.org/confluence/display/INCUBATOR/People
4. https://cwiki.apache.org/confluence/display/INCUBATOR/Historical+Interest
5. https://cwiki.apache.org/confluence/display/INCUBATOR/Proposals
-
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]

Hi.

> 1. Stop distribute the binary of incubator-dubbo-admin

I think "stop distribute the binary" would NOT change the fact the source
release could lead users to use `hiberante-core`. I doubt this is an option.

Also based on the license issue, you should consider canceling this vote,
and move the further discussion to dev ml.


Sheng Wu 吴晟

Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


Huxing Zhang  于2019年4月21日周日 下午11:02写道：

> Hi,
>
> I am thinking why spring-boot-starter-data-jpa depends on LGPL
> licensed library "hibernate-core", and can still be Apache 2.0
> licensed.
> I am reading [1]. In section 5 it says:
>
> A program that contains no derivative of any portion of the Library,
> but is designed to work with the Library by being compiled or linked
> with it, is called a "work that uses the Library". Such a work, in
> isolation, is not a derivative work of the Library, and therefore
> falls outside the scope of this License.
>
> I think spring-boot-starter-data-jpa falls in to this case. It is a
> "work that uses the Library".
>
> The source code of incubator-dubbo-admin should also falls into this
> case, because it does not contain any portion of the hibernate-core.
> Based on it and explanation here[2], I think the source code can be
> released anyway. Is my understanding correct?
>
> Next, the LGPL license says:
>
> However, linking a "work that uses the Library" with the Library
> creates an executable that is a derivative of the Library (because it
> contains portions of the Library), rather than a "work that uses the
> library". The executable is therefore covered by this License.
>
> The binary distribution of incuabator-dubbo-admin falls into this case
> because it creates an executable that contains binary of
> hibernate-core. Therefore it is a "work based on the library". As a
> derivative of hibernate-core, it must be licensed with LGPL/GPL, which
> is not allowed as an Apache product, and eventually causes the
> incompatibility.
>
> If my understanding is correct, there are at least 4 ways to solve this
> issue:
> 1. Stop distribute the binary of incubator-dubbo-admin
> 2. Make the feature optional, as explained here[3]
> 3. Stop depending on hiberante-core
> 4. Choose other Apache compatible equivalent
>
> I recommend to go with number 3 in my last thread.
>
>
> [1] https://opensource.org/licenses/LGPL-2.1
> [2] https://www.apache.org/legal/resolved.html#prohibited
> [3] https://www.apache.org/legal/resolved.html#optional
>
> On Sun, Apr 21, 2019 at 10:40 AM Huxing Zhang  wrote:
> >
> > Hi,
> >
> > ccing dev@dubbo
> >
> > On Fri, Apr 19, 2019 at 8:24 AM Willem Jiang 
> wrote:
> > >
> > > Hi，
> > >
> > > I just checked the binary release kit, it has the third party
> > > dependency of LGPL (Hibernate core) which is belonged to Cataloge
> > > X[1],  it cannot be included in Apache Product.
> > > I had to vote -1 for it. We can change the ORM lib to Eclipse Link to
> > > fix this issue, I just fill an issue here[2].
> >
> > I did some dig for this issue and confirm that this is introduced by
> > this pull request[1].
> > The purpose of this pull request is to introduce the pagination to
> > service query.
> > In this pull request a dependency to spring-boot-starter-data-jpa was
> added,
> > which introduce the LGPL licensed dependency hibernate-core.
> > The detailed dependency tree is shown below:
> >
> > [INFO] +-
> org.springframework.boot:spring-boot-starter-data-jpa:jar:2.0.2.RELEASE:compile
> > [INFO] |  +-
> org.springframework.boot:spring-boot-starter-aop:jar:2.0.2.RELEASE:compile
> > [INFO] |  |  \- org.aspectj:aspectjweaver:jar:1.8.13:compile
> > [INFO] |  +-
> org.springframework.boot:spring-boot-starter-jdbc:jar:2.0.2.RELEASE:compile
> > [INFO] |  |  +- com.zaxxer:HikariCP:jar:2.7.9:compile
> > [INFO] |  |  \- org.springframework:spring-jdbc:jar:5.0.6.RELEASE:compile
> > [INFO] |  +- org.hibernate:hibernate-core:jar:5.2.17.Final:compile
> > [INFO] |  |  +-
> >
> org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final:compile
> > [INFO] |  |  +- antlr:antlr:jar:2.7.7:compile
> > [INFO] |  |  +- org.jboss:jandex:jar:2.0.3.Final:compile
> > [INFO] |  |  +- dom4j:dom4j:jar:1.6.1:compile
> > [INFO] |  |  \-
> >
> org.hibernate.common:hibernate-commons-annotations:jar:5.0.1.Final:compile
> > [INFO] |  +- javax.transaction:javax.transaction-api:jar:1.2:compile
> > [INFO] |  +-
> org.springframework.data:spring-data-jpa:jar:2.0.7.RELEASE:compile
> > [INFO] |  |  +-
> > org.springframework.data:spring-data-commons:jar:2.0.7.RELEASE:compile
> > [INFO] |  |  +- org.springframework:spring-orm:jar:5.0.6.RELEASE:compile
> > [INFO] |  |  \- org.springframework:spring-tx:jar:5.0.6.RELEASE:compile
> > [INFO] |  \- org.springframework:spring-aspects:jar:5.0.6.RELEASE:compile
> >
> > Actually the hiberate-core dependency is never used when implementing
> > the feature,
> > I think it can be excluded quietly. This is the safest way to solve this
> issue.
> >

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

Hi,

I am thinking why spring-boot-starter-data-jpa depends on LGPL
licensed library "hibernate-core", and can still be Apache 2.0
licensed.
I am reading [1]. In section 5 it says:

A program that contains no derivative of any portion of the Library,
but is designed to work with the Library by being compiled or linked
with it, is called a "work that uses the Library". Such a work, in
isolation, is not a derivative work of the Library, and therefore
falls outside the scope of this License.

I think spring-boot-starter-data-jpa falls in to this case. It is a
"work that uses the Library".

The source code of incubator-dubbo-admin should also falls into this
case, because it does not contain any portion of the hibernate-core.
Based on it and explanation here[2], I think the source code can be
released anyway. Is my understanding correct?

Next, the LGPL license says:

However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.

The binary distribution of incuabator-dubbo-admin falls into this case
because it creates an executable that contains binary of
hibernate-core. Therefore it is a "work based on the library". As a
derivative of hibernate-core, it must be licensed with LGPL/GPL, which
is not allowed as an Apache product, and eventually causes the
incompatibility.

If my understanding is correct, there are at least 4 ways to solve this issue:
1. Stop distribute the binary of incubator-dubbo-admin
2. Make the feature optional, as explained here[3]
3. Stop depending on hiberante-core
4. Choose other Apache compatible equivalent

I recommend to go with number 3 in my last thread.

[1] https://opensource.org/licenses/LGPL-2.1
[2] https://www.apache.org/legal/resolved.html#prohibited
[3] https://www.apache.org/legal/resolved.html#optional

On Sun, Apr 21, 2019 at 10:40 AM Huxing Zhang  wrote:
>
> Hi,
>
> ccing dev@dubbo
>
> On Fri, Apr 19, 2019 at 8:24 AM Willem Jiang  wrote:
> >
> > Hi，
> >
> > I just checked the binary release kit, it has the third party
> > dependency of LGPL (Hibernate core) which is belonged to Cataloge
> > X[1],  it cannot be included in Apache Product.
> > I had to vote -1 for it. We can change the ORM lib to Eclipse Link to
> > fix this issue, I just fill an issue here[2].
>
> I did some dig for this issue and confirm that this is introduced by
> this pull request[1].
> The purpose of this pull request is to introduce the pagination to
> service query.
> In this pull request a dependency to spring-boot-starter-data-jpa was added,
> which introduce the LGPL licensed dependency hibernate-core.
> The detailed dependency tree is shown below:
>
> [INFO] +- 
> org.springframework.boot:spring-boot-starter-data-jpa:jar:2.0.2.RELEASE:compile
> [INFO] |  +- 
> org.springframework.boot:spring-boot-starter-aop:jar:2.0.2.RELEASE:compile
> [INFO] |  |  \- org.aspectj:aspectjweaver:jar:1.8.13:compile
> [INFO] |  +- 
> org.springframework.boot:spring-boot-starter-jdbc:jar:2.0.2.RELEASE:compile
> [INFO] |  |  +- com.zaxxer:HikariCP:jar:2.7.9:compile
> [INFO] |  |  \- org.springframework:spring-jdbc:jar:5.0.6.RELEASE:compile
> [INFO] |  +- org.hibernate:hibernate-core:jar:5.2.17.Final:compile
> [INFO] |  |  +-
> org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final:compile
> [INFO] |  |  +- antlr:antlr:jar:2.7.7:compile
> [INFO] |  |  +- org.jboss:jandex:jar:2.0.3.Final:compile
> [INFO] |  |  +- dom4j:dom4j:jar:1.6.1:compile
> [INFO] |  |  \-
> org.hibernate.common:hibernate-commons-annotations:jar:5.0.1.Final:compile
> [INFO] |  +- javax.transaction:javax.transaction-api:jar:1.2:compile
> [INFO] |  +- 
> org.springframework.data:spring-data-jpa:jar:2.0.7.RELEASE:compile
> [INFO] |  |  +-
> org.springframework.data:spring-data-commons:jar:2.0.7.RELEASE:compile
> [INFO] |  |  +- org.springframework:spring-orm:jar:5.0.6.RELEASE:compile
> [INFO] |  |  \- org.springframework:spring-tx:jar:5.0.6.RELEASE:compile
> [INFO] |  \- org.springframework:spring-aspects:jar:5.0.6.RELEASE:compile
>
> Actually the hiberate-core dependency is never used when implementing
> the feature,
> I think it can be excluded quietly. This is the safest way to solve this 
> issue.
> To dig further, the only dependency that required to be added is just
> spring-data-commons,
> which is Apache 2.0 Licensed[2]. (I just confirm the code can compile
> and start correctly with spring-data-commons,
> it might need to check more at runtime to ensure everything is working)
>
> We need to be very careful when new dependency is added,  and ensure
> all the license (including transitive dependencies) are compatible
> with Apache.
>
> The community has identified several similar issues [3][4] for
> incubator-dubbo project, and similar actions should be done to
> incubator-dubbo-admin as well.
>
> To identify the issue

Re: [ANNOUNCE] Apache ShardingSphere 4.0.0-RC1 available

Hi Liang

The introduction is a little too long. One or two sentences for project
description is good and clear for everyone.
And be good for clear project landscape.

Let's start a discussion in dev mail.

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

> 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
>
-- 
Sheng Wu
SkyWalking, Shardingsphere and Zipkin

Re: [ANNOUNCE] Apache ShardingSphere 4.0.0-RC1 available

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
>

Re: [ANNOUNCE] Apache ShardingSphere 4.0.0-RC1 available

2019-04-21 Thread sebb

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

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

[ANNOUNCE] Apache ShardingSphere 4.0.0-RC1 available

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

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

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

Hi Justin

Yes. You are right. Sorry, my misread.

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).
```
+1 (binding)
Forward my VOTE from dev@ list
```

Hi Liang Zhang

Please notice this, if face this again, please manually forward the +1 from
dev to incubator, or remind the mentor to do that.

Sheng Wu 吴晟

Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


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

> Hi,
>
> > I saw three +1 votes, including two mentors, Willem and Gosling, and I
> > gave +1 too.
>
> AFACS Willem's vote didn’t end up in this thread [1] but ended up on your
> dev list [2]. I think this confusion happed as you sent the initial vote
> email to both lists.
>
> Thanks,
> Justin
>
> 1.
> https://lists.apache.org/thread.html/25c11b46dd3a58d4048dd35be71d21f86db6f5278480eb7083149af1@%3Cgeneral.incubator.apache.org%3E
> 2.
> https://lists.apache.org/thread.html/445bf1e41648b042e14a6b77d8bc2364eb9a0406764f59a5fb0231c5@%3Cdev.shardingsphere.apache.org%3E
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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

Hi,

> I saw three +1 votes, including two mentors, Willem and Gosling, and I
> gave +1 too.

AFACS Willem's vote didn’t end up in this thread [1] but ended up on your dev 
list [2]. I think this confusion happed as you sent the initial vote email to 
both lists.

Thanks,
Justin

1. 
https://lists.apache.org/thread.html/25c11b46dd3a58d4048dd35be71d21f86db6f5278480eb7083149af1@%3Cgeneral.incubator.apache.org%3E
2. 
https://lists.apache.org/thread.html/445bf1e41648b042e14a6b77d8bc2364eb9a0406764f59a5fb0231c5@%3Cdev.shardingsphere.apache.org%3E


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

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

Hi Justin

I saw three +1 votes, including two mentors, Willem and Gosling, and I
gave +1 too.

Sheng Wu 吴晟

Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


Justin Mclean  于2019年4月21日周日 下午4:54写道：

> Hi,
>
> > The vote has already opened for at least 72 hours and necessary number of
> > votes are reached.
>
> There’s only 2 +1 votes I count here and you need 3 for a vote to pass.
> Did you have the rIPMC member vote on your dev list?
>
> 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

Hi,

> The vote has already opened for at least 72 hours and necessary number of
> votes are reached.

There’s only 2 +1 votes I count here and you need 3 for a vote to pass. Did you 
have the rIPMC member vote on your dev list?

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

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
>>> 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

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

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

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