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

[Huxing Zhang]

Hi,

On Mon, Apr 22, 2019 at 1:38 PM kezhenxu94  wrote:
>
> Hi All,
>   I've excluded the `hibernate-core` dependency and verified as follows:
>
>
> $ mvn license:add-third-party -Dlicense.useMissingFile
> $ cat dubbo-admin-server/target/generated-sources/license/THIRD-PARTY.txt | 
> grep "General Public License"
>
>
> here is the output
>
>
>  (Eclipse Public License - v 1.0) (GNU Lesser General Public License) 
> Logback Classic Module (ch.qos.logback:logback-classic:1.2.3 - 
> http://logback.qos.ch/logback-classic)
>  (Eclipse Public License - v 1.0) (GNU Lesser General Public License) 
> Logback Core Module (ch.qos.logback:logback-core:1.2.3 - 
> http://logback.qos.ch/logback-core)
>

These are dual licensed dependencies, so we can choose the most
permissive one. In this case EPL is compatible with Apache so no issue
here.
Be aware that General Public License is just on of the keyword, other
keywords might also be check like GPL.

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

Re: 2.7.2 release plan

[Huxing Zhang]

Hi,


On Thu, Apr 18, 2019 at 7:43 PM victory  wrote:
>
> Hello everyone,
>
>  I volunteer to take release manager role for 2.7.2 release. This main
> feature of 2.7.2 is as follow:
>
>- Support nacos as register center and config center.

I'd like to take this. I am also planning to support etcd as metadata center.

>- Integrate other metrics.
>- Optimize registration way, support to register data by application but
>not single service.
>- Fix some compatible issues with dubbo 2.6.x.
>
> Besides, we also have a quite long list [1] of issues targeted to 2.7.2,
> which apparently need to triage to be short enough to meet to code freeze
> date, May. 17th. Hopefully we can release 2.7.2 by May. 27th.
>
>
> Pls. take a look at milestone 2.7.2 [1], and let me know which issues are
> must have for this release. We will triage the list soon :)
> https://github.com/apache/incubator-dubbo/milestone/25
>
> --
>
> Best Regard!
> cvictory



-- 
Best Regards！
Huxing

Re: 2.7.2 release plan

[Minxuan Zhuang]

I'll take the metrics part.

On Mon, Apr 22, 2019 at 3:33 PM Huxing Zhang  wrote:

> Hi,
>
>
> On Thu, Apr 18, 2019 at 7:43 PM victory  wrote:
> >
> > Hello everyone,
> >
> >  I volunteer to take release manager role for 2.7.2 release. This main
> > feature of 2.7.2 is as follow:
> >
> >- Support nacos as register center and config center.
>
> I'd like to take this. I am also planning to support etcd as metadata
> center.
>
> >- Integrate other metrics.
> >- Optimize registration way, support to register data by application
> but
> >not single service.
> >- Fix some compatible issues with dubbo 2.6.x.
> >
> > Besides, we also have a quite long list [1] of issues targeted to 2.7.2,
> > which apparently need to triage to be short enough to meet to code freeze
> > date, May. 17th. Hopefully we can release 2.7.2 by May. 27th.
> >
> >
> > Pls. take a look at milestone 2.7.2 [1], and let me know which issues are
> > must have for this release. We will triage the list soon :)
> > https://github.com/apache/incubator-dubbo/milestone/25
> >
> > --
> >
> > Best Regard!
> > cvictory
>
>
>
> --
> Best Regards！
> Huxing
>

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

[Minxuan Zhuang]

Hi, this LGPL License issue has been fixed, thanks kezhenxu94, I'll cancel
this vote and start a new one

On Mon, Apr 22, 2019 at 3:09 PM Huxing Zhang  wrote:

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

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

[Huxing Zhang]

Hi,


On Mon, Apr 22, 2019 at 4:08 PM Minxuan Zhuang  wrote:
>
> Hi, this LGPL License issue has been fixed, thanks kezhenxu94, I'll cancel
> this vote and start a new one

Could you please cancel it on general@ as well?

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

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

[Minxuan Zhuang]

On Mon, Apr 22, 2019 at 4:08 PM Minxuan Zhuang  wrote:

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

Re: Projects Can Apply Individually for Google Season of Docs

[Huxing Zhang]

Hi,

Sorry for catching this late. The deadline is April 23, 2019 at 20:00 UTC.
To participate this event, we need to record some ideas by filling
this form[1], and 2 mentors.
I am trying to add some ideas.
If you have any ideas, please let me know.

[1] https://cwiki.apache.org/confluence/display/COMDEV/Season+of+Docs+2019



On Thu, Apr 4, 2019 at 9:55 AM Huxing Zhang  wrote:
>
> Hi,
>
> I looks like we have to apply for GSoD by ourselves. I am planning to
> take a look at it next week.
>
> On Thu, Apr 4, 2019 at 4:55 AM  wrote:
> >
> > Hi All
> >
> > Initially the ASF as an organisation was planning to apply as a
> > mentoring organisation for Google Season of Docs on behalf of all Apache
> > projects but if accepted the maximum number of technical writers we
> > could allocated is two. Two technical writers would probably not be
> > enough to cover the potential demand from all our projects interested in
> > participating.
> >
> > We've received feedback from Google that individual projects can apply.
> > I will withdraw the ASF application so that any Apache project
> > interested can apply individually for Season of Docs and so have the
> > potential of being allocated a technical writer.
> >
> > Applications for Season of Docs is open now and closes on 23^rd April
> > 2019. If your project would like to apply then please see the following
> > link:
> >
> > https://developers.google.com/season-of-docs/docs/get-started/
> >
> > Good luck everyone!
> >
> > Thanks
> > Sharan
> >
> >
>
>
> --
> Best Regards！
> Huxing



--
Best Regards！
Huxing

Re: Projects Can Apply Individually for Google Season of Docs

[Huxing Zhang]

Hi,

I am thinking of the following ideas:
- Add documentation of how Dubbo work with registry center like etcd,
consul, following the zookeeper documentation[1]
- Add documentation of how to use various load balancing strategies,
like Random, Consistent Hashing, etc. , based on [2]

Not quite sure how the tech writer know about Dubbo, I am thinking of
writing some introduction to the features that is commonly known.

How do you think?

[1]  http://dubbo.apache.org/en-us/blog/dubbo-zk.html
[2]  http://dubbo.apache.org/en-us/docs/user/demos/loadbalance.html

On Mon, Apr 22, 2019 at 4:38 PM Huxing Zhang  wrote:
>
> Hi,
>
> Sorry for catching this late. The deadline is April 23, 2019 at 20:00 UTC.
> To participate this event, we need to record some ideas by filling
> this form[1], and 2 mentors.
> I am trying to add some ideas.
> If you have any ideas, please let me know.
>
> [1] https://cwiki.apache.org/confluence/display/COMDEV/Season+of+Docs+2019
>
>
>
> On Thu, Apr 4, 2019 at 9:55 AM Huxing Zhang  wrote:
> >
> > Hi,
> >
> > I looks like we have to apply for GSoD by ourselves. I am planning to
> > take a look at it next week.
> >
> > On Thu, Apr 4, 2019 at 4:55 AM  wrote:
> > >
> > > Hi All
> > >
> > > Initially the ASF as an organisation was planning to apply as a
> > > mentoring organisation for Google Season of Docs on behalf of all Apache
> > > projects but if accepted the maximum number of technical writers we
> > > could allocated is two. Two technical writers would probably not be
> > > enough to cover the potential demand from all our projects interested in
> > > participating.
> > >
> > > We've received feedback from Google that individual projects can apply.
> > > I will withdraw the ASF application so that any Apache project
> > > interested can apply individually for Season of Docs and so have the
> > > potential of being allocated a technical writer.
> > >
> > > Applications for Season of Docs is open now and closes on 23^rd April
> > > 2019. If your project would like to apply then please see the following
> > > link:
> > >
> > > https://developers.google.com/season-of-docs/docs/get-started/
> > >
> > > Good luck everyone!
> > >
> > > Thanks
> > > Sharan
> > >
> > >
> >
> >
> > --
> > Best Regards！
> > Huxing
>
>
>
> --
> Best Regards！
> Huxing



-- 
Best Regards！
Huxing

Re: Projects Can Apply Individually for Google Season of Docs

[yuhang xiu]

Hi,huxing

It looks like a good choice.

But from the point of view [1], seems like the technical writer will try to
improve the doc of the entire project?

It seems that we need to make two materials:

   1. A brief introduction to dubbo as u said (tell them what dubbo is)
   2. An official doc template (tell them how to begin writing)



[1] https://cwiki.apache.org/confluence/display/COMDEV/Season+of+Docs+2019

Huxing Zhang  于2019年4月22日周一 下午5:43写道：

> Hi,
>
> I am thinking of the following ideas:
> - Add documentation of how Dubbo work with registry center like etcd,
> consul, following the zookeeper documentation[1]
> - Add documentation of how to use various load balancing strategies,
> like Random, Consistent Hashing, etc. , based on [2]
>
> Not quite sure how the tech writer know about Dubbo, I am thinking of
> writing some introduction to the features that is commonly known.
>
> How do you think?
>
> [1]  http://dubbo.apache.org/en-us/blog/dubbo-zk.html
> [2]  http://dubbo.apache.org/en-us/docs/user/demos/loadbalance.html
>
> On Mon, Apr 22, 2019 at 4:38 PM Huxing Zhang  wrote:
> >
> > Hi,
> >
> > Sorry for catching this late. The deadline is April 23, 2019 at 20:00
> UTC.
> > To participate this event, we need to record some ideas by filling
> > this form[1], and 2 mentors.
> > I am trying to add some ideas.
> > If you have any ideas, please let me know.
> >
> > [1]
> https://cwiki.apache.org/confluence/display/COMDEV/Season+of+Docs+2019
> >
> >
> >
> > On Thu, Apr 4, 2019 at 9:55 AM Huxing Zhang  wrote:
> > >
> > > Hi,
> > >
> > > I looks like we have to apply for GSoD by ourselves. I am planning to
> > > take a look at it next week.
> > >
> > > On Thu, Apr 4, 2019 at 4:55 AM  wrote:
> > > >
> > > > Hi All
> > > >
> > > > Initially the ASF as an organisation was planning to apply as a
> > > > mentoring organisation for Google Season of Docs on behalf of all
> Apache
> > > > projects but if accepted the maximum number of technical writers we
> > > > could allocated is two. Two technical writers would probably not be
> > > > enough to cover the potential demand from all our projects
> interested in
> > > > participating.
> > > >
> > > > We've received feedback from Google that individual projects can
> apply.
> > > > I will withdraw the ASF application so that any Apache project
> > > > interested can apply individually for Season of Docs and so have the
> > > > potential of being allocated a technical writer.
> > > >
> > > > Applications for Season of Docs is open now and closes on 23^rd April
> > > > 2019. If your project would like to apply then please see the
> following
> > > > link:
> > > >
> > > > https://developers.google.com/season-of-docs/docs/get-started/
> > > >
> > > > Good luck everyone!
> > > >
> > > > Thanks
> > > > Sharan
> > > >
> > > >
> > >
> > >
> > > --
> > > Best Regards！
> > > Huxing
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
>
>
>
> --
> Best Regards！
> Huxing
>

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

[Minxuan Zhuang]

Hello Dubbo Community,

This is a call for the vote to release Apache Dubbo  Admin(Incubating)
version 0.2.0

The release candidates(RC4):
0.2.0:
*https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0/
*

Git tag for this release:
0.2.0:  *https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
*

Hash for the release tag:
0.2.0: 93decb64f9f47f92cb169b6ed0a81382197fa026

Release Notes:
0.2.0:
https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0

The artifacts have been signed with Key: DA2108479B0C1E71, which can be
found in
the keys file:

*https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
*

The vote will be open for at least 72 hours or until the necessary number
of votes are reached.

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
The Apache Dubbo (Incubating) Team

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

[柏才 盟]

+0








At 2019-04-23 08:46:49, "Minxuan Zhuang"  wrote:
>Hello Dubbo Community,
>
>This is a call for the vote to release Apache Dubbo  Admin(Incubating)
>version 0.2.0
>
>The release candidates(RC4):
>0.2.0:
>*https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0/
>*
>
>Git tag for this release:
>0.2.0:  *https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
>*
>
>Hash for the release tag:
>0.2.0: 93decb64f9f47f92cb169b6ed0a81382197fa026
>
>Release Notes:
>0.2.0:
>https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
>
>The artifacts have been signed with Key: DA2108479B0C1E71, which can be
>found in
>the keys file:
>
>*https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
>*
>
>The vote will be open for at least 72 hours or until the necessary number
>of votes are reached.
>
>Please vote accordingly:
>
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove with the reason
>
>Thanks,
>The Apache Dubbo (Incubating) Team

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

[Willem Jiang]

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

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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

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

[Huxing Zhang]

Hi,

On Tue, Apr 23, 2019 at 9:54 AM Willem Jiang  wrote:
>
> I think we could put it into the wiki page to let other community
> developers know about the policy.
> BTW, we could also put the license check into the checklist of release
> candidate.

I've already added to release guide:
https://github.com/apache/incubator-dubbo-website/blob/asf-site/docs/en-us/developers/committer-guide/release-guide_dev.md#check-third-party-dependencies

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

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

[Huxing Zhang]

Hi,

-1 to release.

I found the files in the src.zip are different with Github tag.

$ diff -r apache-dubbo-admin-incubating-0.2.0-src incubator-dubbo-admin -q
...
Files 
apache-dubbo-admin-incubating-0.2.0-src/dubbo-admin-ui/src/components/Management.vue
and incubator-dubbo-admin/dubbo-admin-ui/src/components/Management.vue
differ
Files 
apache-dubbo-admin-incubating-0.2.0-src/dubbo-admin-ui/src/components/governance/AccessControl.vue
and 
incubator-dubbo-admin/dubbo-admin-ui/src/components/governance/AccessControl.vue
differ
Files 
apache-dubbo-admin-incubating-0.2.0-src/dubbo-admin-ui/src/components/governance/LoadBalance.vue
and 
incubator-dubbo-admin/dubbo-admin-ui/src/components/governance/LoadBalance.vue
differ
Files 
apache-dubbo-admin-incubating-0.2.0-src/dubbo-admin-ui/src/components/governance/Overrides.vue
and incubator-dubbo-admin/dubbo-admin-ui/src/components/governance/Overrides.vue
differ
Files 
apache-dubbo-admin-incubating-0.2.0-src/dubbo-admin-ui/src/components/governance/RoutingRule.vue
and 
incubator-dubbo-admin/dubbo-admin-ui/src/components/governance/RoutingRule.vue
differ
Files 
apache-dubbo-admin-incubating-0.2.0-src/dubbo-admin-ui/src/components/governance/TagRule.vue
and incubator-dubbo-admin/dubbo-admin-ui/src/components/governance/TagRule.vue
differ
Files 
apache-dubbo-admin-incubating-0.2.0-src/dubbo-admin-ui/src/components/governance/WeightAdjust.vue
and 
incubator-dubbo-admin/dubbo-admin-ui/src/components/governance/WeightAdjust.vue
differ
Files 
apache-dubbo-admin-incubating-0.2.0-src/dubbo-admin-ui/src/components/public/Toolbar.vue
and incubator-dubbo-admin/dubbo-admin-ui/src/components/public/Toolbar.vue
differ
Files 
apache-dubbo-admin-incubating-0.2.0-src/dubbo-admin-ui/src/components/test/ServiceMock.vue
and incubator-dubbo-admin/dubbo-admin-ui/src/components/test/ServiceMock.vue
differ
...

The contents are the same. I think this is due to some CRLF issue
we've encountered before.

On Tue, Apr 23, 2019 at 8:47 AM Minxuan Zhuang  wrote:
>
> Hello Dubbo Community,
>
> This is a call for the vote to release Apache Dubbo  Admin(Incubating)
> version 0.2.0
>
> The release candidates(RC4):
> 0.2.0:
> *https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0/
> *
>
> Git tag for this release:
> 0.2.0:  *https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
> *
>
> Hash for the release tag:
> 0.2.0: 93decb64f9f47f92cb169b6ed0a81382197fa026
>
> Release Notes:
> 0.2.0:
> https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0
>
> The artifacts have been signed with Key: DA2108479B0C1E71, which can be
> found in
> the keys file:
>
> *https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
> *
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Dubbo (Incubating) Team



--
Best Regards！

Huxing