Re:[DISCUSS] rename apache/dubbo-go-pixiu to apache/pixiu

[KimmKing]

Hi, Alex,
IMO, if apache/dubbo-go-pixiu project want to apache/pixiu project, it 
should be voted to an incubating project and then named incubator-pixiu.After a 
period of time graduating from Apache Incubator to a TLP, finally it's 
apache/pixiu.










--

Kimm King(kimmk...@apache.org/kimmk...@163.com)
Apache Dubbo PMC Member
github: kimmking





At 2021-10-18 14:21:04, "stocks alex"  wrote:
>Hi, all
>
>As we dubbo-go community plans t o add more features for the proj
>apache/dubbo-go-pixiu to let it become a sidecar, such as event mesh/db
>mesh, and it also has the ability to communicate with gRPC/SpringCloud, its
>ability is more than Dubbo.
>
>When I communicate with our users, I spend a lot of time to let them know
>apache/dubbo-go-pixiu is  not confined in Dubbo. The function of Pixiu is
>beyond Dubbo now.   So I suggest that we should rename its name from
>apache/dubbo-go-pixiu to apache/pixiu.
>
>Alex

Re:[DISCUSS] Announce 2.6.x coming to an end.

[KimmKing]

Hi, everyone.
More active branches split community, and I guess it's a good news for 
Dubbo project.
BTW, the 2.6.x branch has an end. It'a big issue for community, and then 
more feedback discussed about it here from different users is necessary. 
Let's go forward.




--

Kimm King(kimmk...@apache.org/kimmk...@163.com)
Apache Dubbo PMC Member
github: kimmking





At 2021-09-29 17:07:54, "Jun Liu"  wrote:
>Hi, all
>
>This mail is about to initiate a discussion of ending the maintenance of 2.6.x 
>branch in the next 6 months.
>
>The community currently have 3 active branches, which are 2.6.x, 2.7.x and 
>3.0.x, evolving at the same time. Since 2.7.x and 2.6.x are almost completely 
>compatible with each other regarding features, the migration routine from 
>2.6.x to 2.7.x is relatively smooth for most users, so we are seeing an 
>emerging trend of users migrating from 2.6.x to 2.7.x, some in progress and 
>some have finished migration. 
>
>I think we should stop the maintenance of 2.6.x and only provide security 
>patches in the next 6 months before we announce it to reach its End Of Life.
>
>Jun

Re:Re: [Discussion] About native image

[KimmKing]

I am interested in this topic too.

With native image, we can improve dubbo performance and more usage in cloud 
native cases.




--

Kimm King(kimmk...@apache.org/kimmk...@163.com)
Apache Dubbo PMC Member
github: kimmking





At 2021-05-11 10:50:46, "Jun Liu"  wrote:
>Hi
>
>This is really an interesting topic worth discussion and attention.
>
>I noticed some developers in our community also have mentioned this topic 
>several times in different occasions. Some of them already have a in-depth 
>research in this filed and the possibility of adapting Dubbo this way. I 
>believe it will have great help for us if we can invite them to join this 
>discussion to share their thoughts or even leading the development effort.
>
>Jun
>
>> On May 11, 2021, at 10:35 AM, YunKun Huang  wrote:
>> 
>> hey all,
>> 
>> Recently I try to use Spring Native Beta in some projects and it's
>> really really a great improvement with much lower memory usage and
>> fast start up speed.
>> 
>> I can see those are some open source projects also trying native
>> image, for example hibernate-graalvm.
>> 
>> Not sure if anyone is using native image for a project with apache dubbo?
>> Could anyone share some experience or advise what needs to be done to
>> make it happen?
>> 
>> Maybe it's something we can plan in the near future?
>> 
>> Regards,
>> Yunkun
>

Re:[Suggention] Join Open Source Promotion Plan - Summer 2021

[KimmKing]

+1  awesome.

--

Kimm King(kimmk...@apache.org/kimmk...@163.com)
Apache Dubbo PMC Member
github: kimmking





At 2021-05-08 15:16:36, "Albumen Kevin"  wrote:
>Hi, community
>
>I have noticed that there is an awesome activity, called Open Source
>Promotion Plan - Summer 2021,
>for college students to join the open source software community. It aims to
>encourage college students
>to actively participate in the development and maintenance of open source
>software and promote the
>vigorous development of an excellent open source software community.
>
>I think we can join them and at the same time bring more contributors and
>activity to the community.
>
>The website of Summer 2021：https://summer.iscas.ac.cn/#/homepage
>The help website of Summer 2021: https://summer.iscas.ac.cn/#/help
>
>
>Albumen

Re:[VOTE] Release Apache Dubbo 2.7.11 RC1

[KimmKing]

+1 







--

Kimm King(kimmk...@apache.org/kimmk...@163.com)
Apache Dubbo PMC Member
github: kimmking





At 2021-05-07 01:26:09, "Albumen Kevin"  wrote:
>Hello Community,
>
>This is a call for vote to release Apache Dubbo version 2.7.11
>
>The release candidates:
>https://dist.apache.org/repos/dist/dev/dubbo/dubbo/2.7.11/
>
>The staging repo:
>https://repository.apache.org/content/repositories/orgapachedubbo-1170/
>
>Git tag for the release:
>https://github.com/apache/dubbo/tree/dubbo-2.7.11
>
>Hash for the release tag:
>30616ea7fa945da7d76b703c2c2d29d123a6dfb0
>
>Release Notes:
>https://github.com/apache/dubbo/releases/tag/dubbo-2.7.11
>
>The artifacts have been signed with Key 2B249EDD, which can be
>found in the keys file:
>https://dist.apache.org/repos/dist/dev/dubbo/KEYS
>
>The vote will be open for at least 72 hours or until necessary number of
>votes are reached.
>
>Please vote accordingly:
>
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove with the reason
>
>Thanks,
>The Apache Dubbo Team

Re:Re: [VOTE] Release Apache Dubbo API Docs 2.7.8.3 RC1

[KimmKing]

+1. binding







--

Kimm King(kimmk...@apache.org/kimmk...@163.com)
Apache Dubbo PMC Member
github: kimmking





At 2021-04-28 17:38:43, "绿色心梦"  wrote:
>+1
>
>
>
>---Original---
>From: "ranke"Date: Wed, Apr 28, 2021 17:37 PM
>To: "dev"Subject: [VOTE] Release Apache Dubbo API Docs 2.7.8.3 RC1
>
>
>Hello Community,
>
>This is a call for vote to release Apache Dubbo API Docs version 2.7.8.3.
>Dubbo API Docs is currently existing as a submodule of the
>apache/dubbo-spi-extensions[1] project, the Apache release package contains
>only the API Docs source code.
>
>The release candidates:
>https://dist.apache.org/repos/dist/dev/dubbo/dubbo-spi-extensions/dubbo-api-docs/2.7.8.3/
>
>The staging repo:
>https://repository.apache.org/content/repositories/orgapachedubbo-1165
>
>Git tag for the release:
>https://github.com/apache/dubbo-spi-extensions/tree/v2.7.8.3
>
>Hash for the release tag:
>b5823267a240cbb1c70a337f6ca95adc6b49e267
>
>Release Notes:
>https://github.com/apache/dubbo-spi-extensions/releases/tag/v2.7.8.
><https://github.com/apache/dubbo-spi-extensions/releases/tag/v2.7.8.23
>
>The artifacts have been signed with Key 21C12FEAC580F98D, which can be
>found in the keys file:
>https://dist.apache.org/repos/dist/dev/dubbo/KEYS
>
>The vote will be open for at least 72 hours or until necessary number of
>votes are reached.
>
>Please vote accordingly:
>
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove with the reason
>
>1.
>https://github.com/apache/dubbo-spi-extensions/tree/v2.7.8.3/dubbo-api-docs
><https://github.com/apache/dubbo-spi-extensions/tree/v2.7.8.2/dubbo-api-docs;
>
>Thanks,
>The Apache Dubbo Team

Re:[VOTE] Accept the donation of dubbo-go-pixiu

[KimmKing]

+1 


At 2021-03-13 19:24:29, "wongoo"  wrote:
>Hi All,
>
>This is a formal vote to donate dubbogo/dubbo-go-pixiu[1] to apache.
>
>dubbo-go-pixiu is a gateway based on dubbo-go. It provides a general
>solution that supports calling dubbo services through other protocols. At
>present, it supports HTTP and gRPC[developing].
>
>All contributors[3] agree to donate it to the Dubbo community, and have
>already signed the ICLA. In the discussion[2], the community also supports
>the donation.
>
>
>Please vote:
>[ ] +1 Accept
>[ ] +0 No Opinion
>[ ] -1 Reject because...
>
>
>[1] https://github.com/dubbogo/dubbo-go-pixiu/
>[2]
>https://lists.apache.org/thread.html/r765a243e534ff36f524227776a8ab7c067678d1952141a4cf461200c%40%3Cdev.dubbo.apache.org%3E
>[3] pixiu contributors:
>- williamfeng323, ICLA signed
>- mark4z, ICLA signed
>- xiaoliu10, ICLA signed
>- oaoit, ICLA signed
>- xianlezheng, ICLA signed
>- ztelur, ICLA signed
>- zhangshen023, ICLA signed
>- cityiron/IronCity, dubbo commiter
>- zouyx, dubbo PMC
>- pantianying, dubbo commiter
>- AlexStocks, dubbo PMC
>
>-- 
>Regards,
>Wongoo

Re:[DISCUSSION] donate dubbo-go-pixiu to Dubbo community

[KimmKing]

hi, wongoo,
how about pixiu and other similar solutions?





At 2021-03-10 10:33:17, "wongoo"  wrote:
>Hello Dubbo community,
>
>I would like to initiate a discussion about donating dubbo-go-pixiu to the
>Dubbo community.
>
>We are developing the dubbo-go-pixiu, a gateway based on dubbo-go, which
>provides a general solution that supports calling dubbo services through
>other protocols. At present, it supports HTTP and gRPC[developing].
>
>The development of dubbo-go-pixiu is driven by the dubbo-go community, all
>contributors agree to donate it to Dubbo community, and we have signed the
>ICLA. The source code is available here:
>https://github.com/dubbogo/dubbo-go-pixiu.
>
>-- 
>Regards,
>Wongoo

Re:Re: Remove FastJSON dependency

[KimmKing]

+1, keep gson and remove fastjson.





At 2021-02-20 14:15:30, "Yeauty YE"  wrote:
>
>First of all, dubbo is positioned as a lightweight framework, so in theory, 
>only one framework needs to be kept for json. Secondly, the scene of json 
>operation is not the most frequent main scene, so it will not affect dubbo’s 
>performance. Finally, since it is a framework for internationalization, 
>security is very important among them. In summary, keep Gson and abandon 
>FastJson.
>
>In order to prevent dependency problems caused by user upgrades, I suggest:
>* delete FastJSON from `dubbo-all pom.xml` and `dubbo-common pom.xml` (Ensure 
>the purity of the Dubbo core)
>* Fastjson serialization module should be preserved
>
>
>On 2021/02/18 06:43:27, Jun Liu  wrote: 
>> Hi,> 
>> 
>> > For so long, Dubbo has both Gson and FastJSON, and many modules rely on> 
>> > these two json serialization tools.> 
>> 
>> 
>> I think there’s no need to use two libraries as they provide almost the same 
>> ability. Personally, I have no inclination about which one to keep. > 
>> 
>> >  I am worried that removing one will> 
>> > cause compatibility and stability issues.> 
>> 
>> Here’re the possible impacts that I can think of at this moment:> 
>> * Fastjson serialization module should be preserved> 
>> * Internal dependency of Dubbo on json can be unified into a library, and 
>> most scenarios should have no compatibility problems> 
>> * dubbo-all  pom.xml introduces the transmission dependency of both Gson and 
>> Fastjson. Removing one of them may bring dependency problems to users who 
>> want to upgrade. Considering that fastjson has just been added in 2.7.8, I 
>> think we can choose to remove Fastjson for long time maintenance good, Or, 
>> we can choose to keep both in pom.xml for the time being.> 
>> 
>> Jun> 
>> 
>> > On Feb 18, 2021, at 12:09 PM, Albumen Kevin  wrote:> 
>> > > 
>> > Hi community,> 
>> > > 
>> > There is a pull request removing FastJSON dependency for apache/dubbo:> 
>> > > 
>> > https://github.com/apache/dubbo/pull/7187> 
>> > > 
>> > For so long, Dubbo has both Gson and FastJSON, and many modules rely on> 
>> > these two json serialization tools. I am worried that removing one will> 
>> > cause compatibility and stability issues.> 
>> > > 
>> > Albumen> 
>> 
>> 

Re:[VOTE] Release Apache Dubbo-Hessian-Lite 3.2.8 RC1

[KimmKing]

I check the following and give +1 Approval.

[v]  Are release files in correct location?
[v] Are the digital signature and hashes correct?
[v] Do LICENSE and NOTICE files exists?
[v] Is the LICENSE and NOTICE text correct?

[v] Is the NOTICE year correct?




At 2020-06-29 18:33:56, "Jun Liu"  wrote:
>Hello Dubbo Community,
>
>This is a call for a vote to release Apache Dubbo-hessian-lite version 3.2.8
>
>The release candidates:
>https://dist.apache.org/repos/dist/dev/dubbo/dubbo-hessian-lite/
>
>Git tag for the release:
>https://github.com/apache/dubbo-hessian-lite/tree/v3.2.8
>
>The hash for the release tag:
>ae090564e1f0ee759c7253c66266f838d57640c8
>
>Release Notes:
>https://github.com/apache/dubbo-hessian-lite/releases/tag/V3.2.8
>
>The artifacts have been signed with Key: 28681CB1, which can be found in
>the KEYS file:
>https://dist.apache.org/repos/dist/dev/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 Team

Re:[ANN] Welcome a new committer Patrick Jiang (baze)

[KimmKing]

Congratuations.
: )

At 2020-05-09 12:45:35, "stocks alex"  wrote:
>Hello, guys,
>
>On behalf of the Apache Dubbo PMC, it is my honor to announce that Patrick
>Jiang[1] has been voted in as a new Dubbo committer.
>
>Please join me to say congratulations to him!
>
>Patrick, would you give us a briefly introduce of yourself to the community?
>
>1. https://github.com/Patrick0308
>
>Yours,
>Alex.

Re:Re: 4.26会议纪要

[KimmKing]

Thanks for the summary.
1. XDS is awesome feature and an important component to adapt cloud native 
infrastructure such as istio, it's a good news for community and users. If 
there is any more further improvement, plz let us know and try.
2. Documents is a big issue, can we splitting it to several details tasks and 
launch a community issue to track it in progress, with more contributors 
working in?

At 2020-04-27 14:08:25, "deng ming"  wrote:
>Hi all,
>
>I'm sorry for that we do not follow the community rules.
>
>Here is the meeting summary:
>
>We discussed about dubbo-go's problems and what we will do in next month.
>
>1. dubbo-go try the best to keep compitable with Dubbo. And we will try to
>implement some new features, like supporting XDS;
>2. supporting service mesh will be suspended until we actually need this
>feature;
>3. No hurry to pulish dubbo-go v1.5. Quality is the most important thing.
>4. Find more users and collect the feebacks. Now some users are lack
>of enthusiasm to participate in community discussion.
>5. We should pay more attention to improve performance, quality.
>6. Writing more documents, comments and samples.
>
>The plan for v1.5.x:
>1. 1.5.x will focus on bug fix, code optimization;
>2. Writing user document;
>3. Everyone should write the documents, and then one person will be
>responsible to collate those documents;
>4. Writing comments for existed codes;
>5. Improve the quality of samples;
>
>Regards,
>
>Ming Deng
>
>stocks alex  于2020年4月27日周一 下午1:19写道：
>
>> Welcome to join us to make it perfect.
>>
>> 一直以来 <279377...@qq.com> 于2020年4月26日周日 下午9:36写道：
>>
>> > 大跃进式的开发我们不会接受 我们需要bug最少 文档尽量完善 新的特性对我们基本没有用
>> > 我们只想用的舒服 文档全 
>> >
>> >
>> >
>> > 发自我的iPhone
>> >
>> >
>> > -- 原始邮件 --
>> > 发件人: Ming Deng > > 发送时间: 2020年4月26日 21:33
>> > 收件人: dev > > 主题: 回复：4.26会议纪要
>>

Re:回复：4.26会议纪要

[KimmKing]

Hi, guys,
English only here.




And I suggest if we have the next meetings, send a mail to dev or committer 
list to invent more persons in community join to disccus.
Dubbo is open community, and community first, rather than codes.


Thx.

在 2020-04-26 21:36:10，"一直以来" <279377...@qq.com> 写道：
>大跃进式的开发我们不会接受 我们需要bug最少 文档尽量完善 新的特性对我们基本没有用 我们只想用的舒服 
>文档全 
>
>
>
>发自我的iPhone
>
>
>-- 原始邮件 --
>发件人: Ming Deng 发送时间: 2020年4月26日 21:33
>收件人: dev 主题: 回复：4.26会议纪要

Re:[VOTE] Release Apache dubbo-go v1.4.0 RC2

[KimmKing]

+1 

I checked:
- signatures and hashes 
- LICENSE and NOTICE 
- No unexpected binary files
- All source file have ASF headers






At 2020-04-16 14:22:30, "wongoo"  wrote:
>Hello Dubbo/Dubbogo Community,
>
> This is a call for vote to release Apache dubbo-go version v1.4.0 RC2.
>
> The release candidates:
>https://dist.apache.org/repos/dist/dev/dubbo/dubbo-go/v1.4.0-rc2/
> Git tag for the release: https://github.com/apache/dubbo-go/tree/1.4
> Hash for the release tag: 320e307b92edb5466ad55db10342ad3eee95c982
> Release Notes: https://github.com/apache/dubbo-go/blob/1.4/CHANGE.md
> The artifacts have been signed with Key :7DB68550D366E4C0, which can be
>found in the keys file:
> https://dist.apache.org/repos/dist/dev/dubbo/KEYS
>
> The vote will be open for at least 72 hours or until necessary number of
>votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Dubbo-go Team

Re:[VOTE]: Release Apache Dubbo Spring Boot 2.7.6 [RC1]

[KimmKing]

+1, I check:
- [x] release notes
- [x] release sourcecode
- [x] gpg verification


And a tip, this release file signed with the key 'A7F508EFDA68B4F5'(Mercy Ma's 
pub key) in KYES file，not  the key '28681CB1'(it's liujun's pub key).

At 2020-04-02 00:03:34, "Mercy Ma"  wrote:
>Hi, All
>
>This is a call for a vote to release Apache Dubbo Spring Boot version 2.7.6.
>
>The release candidates (there will be only source release in this version):
>https://dist.apache.org/repos/dist/dev/dubbo/dubbo-spring-boot/2.7.6/ <
>https://dist.apache.org/repos/dist/dev/dubbo/dubbo-spring-boot/2.7.6/>
>
>Git tag for the release:
>https://github.com/apache/dubbo-spring-boot-project/tree/2.7.6 <
>https://github.com/apache/dubbo-spring-boot-project/tree/2.7.6>
>
>Hash for the release tag:
>38289415d4103a75292ae264fd12d367b27263dc
>
>Release Notes:
>https://github.com/apache/dubbo-spring-boot-project/releases/tag/2.7.6 <
>https://github.com/apache/dubbo-spring-boot-project/releases/tag/2.7.6>
>
>The artifacts have been signed with Key: 28681CB1, which can be
>found in the keys file:
>https://dist.apache.org/repos/dist/dev/dubbo/KEYS <
>https://dist.apache.org/repos/dist/dev/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 Team

Re:[ANN] Welcome a new committer Zouyx

[KimmKing]

Cons to Zouyx.



At 2020-03-09 11:48:00, "郑泽超"  wrote:
>
>Welcome !
>
>Thanks for your contribution.
>
>-chao

Re:Re: [VOTE] Release Apache Dubbo 2.6.8 RC2

[KimmKing]

One more suggestion: 
>  Release Notes:
> Backport some changes from 2.7 to 2.6


Maybe explaining what happen here will be better for our users 

At 2020-02-28 22:59:51, "Ian Luo"  wrote:
>-1 disapprove with the reason.
>
>Everything looks good except for the following two minor issues:
>
>1. Lots of .flattened-pom.xml which are unexpected.
>2. In NOTICE, 2018-2020 should be used instead of 2018-2019.
>
>Regards,
>-Ian.
>
>
>On Wed, Feb 26, 2020 at 10:09 PM Jun Liu  wrote:
>
>> Hello Dubbo Community,
>>
>> This is a call for vote to release Apache Dubbo version 2.6.8.
>>
>> The release candidates:
>> https://dist.apache.org/repos/dist/dev/dubbo/dubbo/2.6.8/ <
>> https://dist.apache.org/repos/dist/dev/dubbo/dubbo/2.6.8/>
>>
>> Git tag for the release:
>> https://github.com/apache/dubbo/tree/dubbo-2.6.8 <
>> https://github.com/apache/dubbo/tree/dubbo-2.6.8>
>>
>> Hash for the release tag:
>> 8c2141cd1c08cc4335ee68527fb1127ed51dacd3
>>
>> Release Notes:
>> Backport some changes from 2.7 to 2.6
>>
>> The artifacts have been signed with Key: 28681CB1, which can be
>> found in the keys file:
>> https://dist.apache.org/repos/dist/dev/dubbo/KEYS <
>> https://dist.apache.org/repos/dist/dev/dubbo/KEYS>
>>
>> The vote will be open for at least 72 hours or until necessary number of
>> votes are reached.
>>
>> Please vote accordingly:
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>>
>> Thanks,
>> The Apache Dubbo Team

Re:[VOTE]: Release Apache dubbo-go v1.3.0 RC3

[KimmKing]

+1
Good news, this version contain a lot awesome features.



At 2020-02-24 21:07:12, "方银城"  wrote:
>Hello Dubbo/Dubbogo Community,
>
>  This is a call for vote to release Apache dubbo-go version v1.3.0 RC3.
>
>  The release candidates:
>https://dist.apache.org/repos/dist/dev/dubbo/dubbo-go/v1.3.0-rc3/
>
>  Git tag for the release: https://github.com/apache/dubbo-go/tree/v1.3.0
>
>  Hash for the release tag: 082cc62be11ae4ad3b04dfd0cbcca5dd2df1992d
>
>  Release Notes: https://github.com/apache/dubbo-go/blob/1.3/CHANGE.md
>
>  The artifacts have been signed with Key :F6C6A49DB4A11314, which can be
>found in the keys file: https://dist.apache.org/repos/dist/dev/dubbo/KEYS
>
>  The vote will be open for at least 72 hours or until necessary number of
>votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Dubbo-go Team

Re:Re: [ANN] Welcome a new committer Zouyx

[KimmKing]

Congratulations, zouyx.

在 2020-02-21 11:37:06，"xinming he"  写道：
>Congratulations！
>
>tianying pan  于2020年2月21日周五 上午11:12写道：
>
>> Welcome !
>>
>> stocks alex  于2020年2月21日周五 上午11:01写道：
>>
>> > Hi, Community,
>> >
>> > On behalf of the Dubbo PMC, I am pleased to announce that zouyx[1] has
>> been
>> > voted in as a new Dubbo committer.
>> >
>> > Please join me to say congratulations to him!
>> >
>> > Zouyx, would you please briefly introduce yourself to the community?
>> >
>> > 1. https://github.com/zouyx
>> >
>> > Yours,
>> > Alex.
>> >
>>

Re: [VOTE]: Release Apache Dubbo Spring Boot 2.7.4.1 [RC1]

[KimmKing]

+1 binding

And as Justin's suggestion，I guess moving these article to dubbo website is
a good idea.



Mercy Ma  于2019年11月5日周二 下午4:14写道：

> Hi,
>
> +1 binding,
>
> I checked:
> - signatures and hashes fine
> - LICENSE and NOTICE OK
> - no unexpected binary files
> - source files have ASF headers
> - can compile from source
>
> Kind regards,
> Mercy Ma
>
> On Mon, Nov 4, 2019 at 9:51 AM Jun Liu  wrote:
>
> > +1 binding,
> >
> > I checked:
> >  * signature and hash are good
> >  * no binary files in source package
> >  * source match with github tag
> >  * can compile from souce
> >
> > Jun
> >
> > > On Oct 30, 2019, at 5:18 PM, Mercy Ma  wrote:
> > >
> > > These links come from my Github blog, it's appeared a long time. Could
> > they
> > > leave there?
> > >
> > > Kind regards,
> > > Mercy
> > >
> > > On Wed, Oct 30, 2019 at 4:58 PM Justin Mclean <
> jus...@classsoftware.com>
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> I notice the documentation refers to external non-Apache websites is
> > there
> > >> a reason for this?
> > >>
> > >> 5. [Dubbo Annotation-Driven (Chinese)](
> > >>
> >
> https://github.com/mercyblitz/blogs/blob/master/java/dubbo/Dubbo-Annotation-Driven.md
> > >> )
> > >> 6. [Dubbo Externalized Configuration (Chinese)](
> > >>
> >
> https://github.com/mercyblitz/blogs/blob/master/java/dubbo/Dubbo-Externalized-Configuration.md
> > >> )
> > >>
> > >> Thanks,
> > >> Justin
> > >
> > >
> > >
> > > --
> > >
> > > *Mercy Ma*
> > > GMail:mercybl...@gmail.com
> > > Yahoo: mercy.bl...@yahoo.com
> > > Wetchat: mercyblitz-1985
> > > Twitter : @mercyblitz 
> > > Blog: https://mercyblitz.github.io/
> >
> >
>
> --
>
> *Mercy Ma*
> GMail:mercybl...@gmail.com
> Yahoo: mercy.bl...@yahoo.com
> Wetchat: mercyblitz-1985
> Twitter : @mercyblitz 
> Blog: https://mercyblitz.github.io/
>

Re:Dubbo as OSGi Remote Service Distribution

[KimmKing]

Thanks, Scott, 

Integration with other popular frameworks is always in Dubbo Ecosystem 
Principles.
I am familiar with OSGi, and can you guide me how to implement this Dubbo 
extensibility.
Asynchronous events for disconnection or failure to reconnect is not supported 
now, should we complete this feature first for ECF?


At 2019-08-31 06:05:31, "Scott Lewis"  wrote: >Hi, > >I'm 
the project lead for the Eclipse Communication Framework [1].   >Among other 
things, ECF provides an implementation of the OSGi R7 Remote >Services/Remote 
Service Admin specifications [2]. > >ECF supports pluggable 'distribution 
providers', responsible for the >rpc, serialization/marshalling, and wire 
protocol.   We have upwards of >10 distribution providers [3] created by us and 
others. > >I've recently learned about Apache Dubbo, and decided to use it to 
>create a new ECF Remote Service Distribution Provider [4]. What this >means is 
that Apache Dubbo can now be used as a distribution impl for >any OSGi remote 
service.   This also makes it quite possible to have  >Other Runtimes -> OSGi 
and OSGi->Other runtimes and retain all the OSGi >service dynamics, injection 
through declarative services, etc. > >If the Dubbo dev community is interested, 
I could easily describe how >Dubbo extensibility could be exposed via the OSGi 
service >registry/remote services.   This would make it possible for Dubbo to 
be >easily extended using the OSGi service registry. > >If Dubbo folks wanted 
to expose Dubbo modules as OSGi bundles, I believe >this could also be easily 
done and would be happy to contribute it back >to Dubbo. > >One technical 
question:  With Dubbo, is it possible to listen for >asynchronous events (such 
as disconnection/failed reconnect requests) >and respond to them?  If so are 
there docs or examples of how to do >this? (java API best). > >Thanks. > >Scott 
> >[1] http://www.eclipse.org/ecf https://wiki.eclipse.org/ECF > >[2] 
>https://osgi.org/specification/osgi.cmpn/7.0.0/service.remoteserviceadmin.html 
> >[3] https://wiki.eclipse.org/Distribution_Providers > >[4] 
https://github.com/ECF/DubboProvider

Re:Re: [ANN] Welcome new committer: Xinming He

[KimmKing]

Congratulations！
在 2019-08-03 00:14:47，"Ian Luo"  写道：
>Congratulations！
>
>On Sat, Jul 27, 2019 at 3:21 PM Stocks Alex 
>wrote:
>
>> Cgts to our dubbogo community big boss, Mr He.
>>
>>  原始邮件
>> 发件人: caojiele1225
>> 收件人: dev
>> 发送时间: 2019年7月26日(周五) 23:38
>> 主题: Re: [ANN] Welcome new committer: Xinming He
>>
>>
>> Congratulations！
>>
>>
>>
>> | |
>> 曹杰乐
>> 邮箱：caojiele1...@126.com
>> |
>>
>> 签名由 网易邮箱大师 定制
>>
>> On 07/26/2019 18:06, Huxing Zhang wrote:
>> Hi Community,
>>
>> On behalf of the Dubbo PMC, I am pleased to announce that Xinming
>> He[1], has been voted in as a new Dubbo committer.
>>
>> Please join me to say congratulations to him!
>>
>> Xinming, would you please briefly introduce yourself to the community?
>>
>> [1] https://github.com/hxmhlt
>>
>> --
>> Best Regards！
>> Huxing
>>
>>

Re:Re: [Proposal]Write A Book(Apache Dubbo: The Definitive Guide)

[KimmKing]

你发的这个是kirito带头做的dubbo in action

我提议的这个是definitive guide
相互补充

在 2019-07-08 16:14:20，"caojiele1225"  写道：
>Hi,
>
>
>Kimm 
>神，想问下您这个写书的计划和这个plan有关系吗？https://github.com/apache/dubbo-website/issues/172
>
>
>--
>Best Regards！
>Jiele
>
>
>原始邮件
>发件人:Ian luoian@gmail.com
>收件人:dev...@dubbo.apache.org
>发送时间:2019年7月8日(周一) 15:49
>主题:Re: [Proposal]Write A Book(Apache Dubbo: The Definitive Guide)
>
>
>+1. On Thu, Jun 6, 2019 at 7:30 PM KimmKing kimmk...@apache.org wrote:  Hi, 
>Community，  随着微服务架构越来越流行，Apache  
>Dubbo项目越来越火，最近我们的各种技术会议、沙龙，Dubbo的曝光和传播也越来越多。配合Dubbo社区生态的发展建设，目前我们非常适合推出一系列不同层次和侧重的Dubbo书籍了。就我了解，yiji和jingzhu将要出版一本
>  深入Apache Dubbo与实战，kirito也计划推出一本 Dubbo实战。越多Dubbo的书涌现，就意味着Dubbo的生态越发达。  
>像其他各类开源技术一样，我们可以组织一下社区，直接整理修订官方文档，成为一本Dubbo的入门基础工具书（Apache  Dubbo权威指南，Apache 
>Dubbo: The Definitive  Guide），作为前面两本书的补充。目前的官方文档比较全面，后续也可以基于英文文档推出英文版。   
>这本书可以按照Dubbo社区的名义来出版，并将未来的版税作为Dubbo技术的发展经费来使用，比如第一笔版税全部用来购买初次印刷的本书籍，然后分发给各个Committer和Contributor作为后续一段时间内技术分享和技术沙龙时，跟现场参与者交互的赠品。
>   
>此外，我私下问了几个contributor也都愿意参与这件有益于Dubbo发展的好事，我本人可以尝试组织人员启动这个项目，在1-2月左右完成初稿，在Q3结束前完成出版的各项准备工作。
>  大家有什么想法和建议， 非常期待大家的回复。Hi, Community,  As the micro-service architecture 
>becomes more and more popular, the  Apache Dubbo project is so hot. Recently, 
>we have various technical  conferences, salons, and Dubbo have more and more 
>exposures and spreads.  With the development of the Dubbo community ecology, 
>we are now very  suitable to launch a series of Dubbo books of different 
>levels and focuses.  As far as I know, yiji and jingzhu will publish a book 
>deep into Apache  Dubbo quickly, kirito also plans to launch a Dubbo in 
>Action. The more  Dubbo's books emerge, the more developed Dubbo's ecology.   
>Like other open source project, we can organize the community, directly  
>polish and revise the official documentation, and become a Dubbo beginners'  
>reference book (Apache Dubbo: The Definitive Guide), supplemented by the  
>previous two books. The current official documentation is more  comprehensive, 
>and the follow-up can also be a English Version book based  on English 
>documents.  The book can be published in the name of the Dubbo Community, and 
>future  royalties are used as development funds for Dubbo technology. For 
>example,  the first royalties are all used to purchase the first printed book, 
>and  then distributed to each Committer and Contributor as a follow-up  
>paragraph. Giveaways to interact with live participants during technical  
>sharing and technical salons.   In addition, I privately asked a few 
>contributors who are also willing to  participate in this task that is good 
>for Dubbo development. I can try to  organize several contributors to start 
>the project, complete the first  draft around 1-2 months, and be ready of 
>publication at the end of Q3.  Everyone has any ideas and suggestions? I look 
>forward to your reply.-  kimmking  2019-06-06

Re:Re: it is neccesary to support to encode 'Object[]' of java in hessian2

[KimmKing]

+1



An object traveled all the world and back home,  it must be himself now.



At 2019-07-08 10:29:41, "Ian Luo"  wrote:
>+1
>
>On Mon, Jul 1, 2019 at 9:55 AM 望哥  wrote:
>
>> suggest:
>> - golang slice -> java arraylist
>> - golang interface {} array ->  java Object[]
>>
>> On Fri, Jun 28, 2019 at 6:53 PM xinming he  wrote:
>>
>> > oh，I do not think add a new struct in dubbogo/hessian2 is  a good idea.
>> The
>> > more definitions we create, the higher the learning cost of users. There
>> > are slice and array  in Golang which slice is a dynamic array . So why we
>> > not create  slice of interface{} type in go and arrayList (means a
>> dynamic
>> > array)  in java mapping, array of interface{} type in go and object array
>> > in java mapping ?
>> >
>> >
>> >
>> > 方银城  于2019年6月28日周五 下午4:57写道：
>> >
>> > > Hi dubbogo community,
>> > >
>> > >
>> > > Today, we found a problem about hessian2
>> > > . What type does 'Object[]' of
>> java
>> > > correspond to in golang?
>> > >
>> > > 'Object' of java will be decoded to 'interface{}' in golang, so
>> > > 'Object[]' should be decoded to '[]interface{}'. However,
>>  '[]interface'
>> > > of golang  will be decoded to 'ArrayList' of java.
>> > > Then, we should distinguish 'Object[]' from 'ArrayList' in golang.
>> > And
>> > > I will describe a case:
>> > >
>> > > 1. Define a Object to describe the Object in
>> > > java.(hessian2/list.go)
>> > > [image: image.png]
>> > >
>> > >2. Add mapping from 'hessian.Object' to '[object'.
>> > > [image: image.png]
>> > >
>> > >3. Now, '[]interface{}' is equal to 'ArrayList' and '[]Object'
>> > > is equal to 'Object[]'.
>> > >
>> > >Looking forward to different opinions!
>> > >
>> > > Yours,
>> > >
>> > > Yincheng Fang
>> > >
>> >
>>
>>
>> --
>> Regards,
>> 望哥
>>
>> 
>> http://sisopipo.com/blog
>>

Re:Re: About jprofile license for opensource project

[KimmKing]

Nice job.

> In addition, after communicating with Jprofile, they will provide a license
> for all Committer to use.
And a link on Project Thanks Pages should be necessary to respect Jprofile team.




At 2019-07-07 08:57:28, "Huxing Zhang"  wrote:
>Hi,
>
>On Fri, Jul 5, 2019 at 4:29 PM yuhang xiu  wrote:
>>
>> Hi, everyone.
>>
>> It seems that we have no other opinions on the license of Jprofile.
>>
>> I will start the two things above.
>>
>> In addition, after communicating with Jprofile, they will provide a license
>> for all Committer to use.
>>
>> Regarding the maintenance of this license, I think it should not appear in
>> any public place, it should be maintained by PMCs, and any Committer that
>> needs to use it needs to apply on the dev list. This is a security measure
>> used to ensure that this license is not overused.
>>
>> What do you think?
>
>Any ASF project has a private svn to store private information, such
>as password, private keys, and etc.
>I think we can store it there, and send the notice to committers and
>document on the new committer guide.
>If they are willing to use it, they are ask on the PMC member list.
>
>
>
>>
>> yuhang xiu  于2019年7月4日周四 上午10:24写道：
>>
>> > Hi,
>> >
>> > I took a look at this guide. It seems that we need to do a few things:
>> >
>> > 1. Agree with the PMCs to confirm that we are using Jprofile and agree to
>> > add the official link to Jprofile.
>> > 2. Add a thanks page to the current official website[1]. I personally
>> > think that we should also thank Intellij Idea for supporting the project.
>> >
>> > By the way, after we have done the above, how do we go through the last
>> > step mentioned in the guide?
>> >
>> > > Project Thanks Pages should include a closing overview paragraph that
>> > links to the formal Sponsorship and Donations/Contributing web pages at the
>> > ASF level.
>> >
>> > [1] http://dubbo.apache.org/en-us/
>> >
>> > Shane Curcuru  于2019年7月3日周三 下午10:05写道：
>> >
>> >> Justin Mclean wrote on 2019-7-3 4:47AM EDT:
>> >> > Hi,
>> >> >
>> >> >> I think it will be good to have free jprofile license for open source.
>> >> >
>> >> > Looking here [1] they require a link on the web site. That should be OK
>> >> as long as it not seen as an endorsement and that link goes on a support 
>> >> or
>> >> thanks page. [2]
>> >>
>> >> Apache Brand Management has a specific page for how projects should
>> >> include these kinds of corporate links, which should be easy to follow:
>> >>
>> >>   http://www.apache.org/foundation/marks/linking
>> >>
>> >> >> It sounds more like a legal question, are we able to do it?
>> >> >
>> >> > IMO Yes.
>> >> >
>> >> > Thanks,
>> >> > Justin
>> >> >
>> >> > 1. https://www.ej-technologies.com/buy/jprofiler/openSource/enter
>> >> > 2. https://www.apache.org/foundation/marks/responsibility#independent
>> >>
>> >> --
>> >>
>> >> - Shane
>> >>   Legal Affairs Committee
>> >>   The Apache Software Foundation
>> >>
>> >
>
>
>
>--
>Best Regards！
>Huxing

Re:Re: [ANN] Welcome new committer: Alex Stocks

[KimmKing]

Congratulations!：）


At 2019-07-08 10:42:21, "Ian Luo"  wrote:
>Congratulations!
>
>On Thu, Jun 20, 2019 at 6:54 AM Huxing Zhang  wrote:
>
>> Hi Community,
>>
>> On behalf of the Dubbo PMC, I am pleased to announce that
>> Alex Stocks[1], has been voted in as a new Dubbo committer.
>>
>> Please join me to say congratulations to him!
>>
>> Alex, would you please briefly introduce yourself to the community?
>>
>> [1] https://github.com/AlexStocks
>> --
>> Best Regards！
>> Huxing
>>

Re:Re: [VOTE] Accept dubbogo/hessian2 donation

[KimmKing]

+1 Accept
在 2019-07-08 11:42:52，"Mercy Ma"  写道：
>+1 Accept
>
>On Mon, Jul 8, 2019 at 11:18 AM yuhang xiu  wrote:
>
>> +1 accept
>>
>> Ian Luo  于2019年7月8日周一 上午10:26写道：
>>
>> > +1 Accept
>> >
>> > On Thu, Jul 4, 2019 at 11:20 AM Stocks Alex 
>> > wrote:
>> >
>> > > 1
>> > >
>> > >  原始邮件
>> > > 发件人: Huxing Zhang
>> > > 收件人: dev
>> > > 发送时间: 2019年7月4日(周四) 10:00
>> > > 主题: [VOTE] Accept dubbogo/hessian2 donation
>> > >
>> > >
>> > > Hi All,
>> > >
>> > > This is a formal vote to bring dubbogo/hessian2[1], which is depended
>> > > by dubbo-go, to Apache Dubbo project.
>> > >
>> > > Please vote:
>> > >
>> > > [ ] +1 Accept
>> > > [ ] +0 No Opinion
>> > > [ ] -1 Reject because...
>> > >
>> > > [1] https://github.com/dubbogo/hessian2
>> > >
>> > > --
>> > > Best Regards！
>> > > Huxing
>> > >
>> > >
>> >
>>

Re:[DISCUSS] Dubbo weekly

[KimmKing]

Hi, huxing,
I'm invited to BigData OpenSource Forum and give a speed about apache dubbo 
roadmap yesterday in Beijing [1].


1.https://www.huodongxing.com/event/2495015864500
At 2019-06-17 10:44:47, "Huxing Zhang"  wrote:
>Hi,
>
>I am planning to write a weekly report for Dubbo to summarize what is
>going on for Dubbo and maybe its ecosystem this week.
>
>The purpose is to let more user to have brief idea of what Dubbo
>community is doing, in case they do not have time to follow the
>activities of mailing list.
>
>The idea is inspired by "This week in Spring" series[1]. I am not sure
>I can make it or not, but I would like to give a try. Maybe the
>community can help out.
>
>Any comments or suggestions?
>
>[1] https://spring.io/blog/2019/06/10/this-week-in-spring-june-11th-2019
>
>-- 
>Best Regards！
>Huxing

Re:[ANN] Welcome new committer, Yuneng Xie

[KimmKing]

Congratulations!

At 2019-06-12 10:18:29, "Jun Liu"  wrote:
>Hi Community,
>
>On behalf of the Dubbo PMC, I am pleased to announce that
>Yuneng Xie[1], a.k.a uglycow, has been voted in as a new Dubbo committer.
>
>Please join me to say congratulations to him!
>
>Yuneng, would you please briefly introduce yourself to the community?
>
>[1] https://github.com/uglycow
>
>Jun
>

[Proposal]Write A Book(Apache Dubbo: The Definitive Guide)

[KimmKing]

Hi, Community，
随着微服务架构越来越流行，Apache 
Dubbo项目越来越火，最近我们的各种技术会议、沙龙，Dubbo的曝光和传播也越来越多。配合Dubbo社区生态的发展建设，目前我们非常适合推出一系列不同层次和侧重的Dubbo书籍了。就我了解，yiji和jingzhu将要出版一本
 深入Apache Dubbo与实战，kirito也计划推出一本 Dubbo实战。越多Dubbo的书涌现，就意味着Dubbo的生态越发达。
像其他各类开源技术一样，我们可以组织一下社区，直接整理修订官方文档，成为一本Dubbo的入门基础工具书（Apache Dubbo权威指南，Apache 
Dubbo: The Definitive Guide），作为前面两本书的补充。目前的官方文档比较全面，后续也可以基于英文文档推出英文版。
这本书可以按照Dubbo社区的名义来出版，并将未来的版税作为Dubbo技术的发展经费来使用，比如第一笔版税全部用来购买初次印刷的本书籍，然后分发给各个Committer和Contributor作为后续一段时间内技术分享和技术沙龙时，跟现场参与者交互的赠品。
此外，我私下问了几个contributor也都愿意参与这件有益于Dubbo发展的好事，我本人可以尝试组织人员启动这个项目，在1-2月左右完成初稿，在Q3结束前完成出版的各项准备工作。
   大家有什么想法和建议， 非常期待大家的回复。


Hi, Community,
As the micro-service architecture becomes more and more popular, the Apache 
Dubbo project is so hot. Recently, we have various technical conferences, 
salons, and Dubbo have more and more exposures and spreads. With the 
development of the Dubbo community ecology, we are now very suitable to launch 
a series of Dubbo books of different levels and focuses. As far as I know, yiji 
and jingzhu will publish a book deep into Apache Dubbo quickly, kirito also 
plans to launch a Dubbo in Action. The more Dubbo's books emerge, the more 
developed Dubbo's ecology.

Like other open source project, we can organize the community, directly polish 
and revise the official documentation, and become a Dubbo beginners' reference 
book (Apache Dubbo: The Definitive Guide), supplemented by the previous two 
books.  The current official documentation is more comprehensive, and the 
follow-up can also be a English Version book based on English documents.
The book can be published in the name of the Dubbo Community, and future 
royalties are used as development funds for Dubbo technology. For example, the 
first royalties are all used to purchase the first printed book, and then 
distributed to each Committer and Contributor as a follow-up paragraph. 
Giveaways to interact with live participants during technical sharing and 
technical salons.

In addition, I privately asked a few contributors who are also willing to 
participate in this task that is good for Dubbo development. I can try to 
organize several contributors to start the project, complete the first draft 
around 1-2 months, and be ready of publication at the end of Q3. 
Everyone has any ideas and suggestions?  I look forward to your reply.


-
kimmking
2019-06-06

Re:回复：[ANN] New PMC member: Victory Cao

[KimmKing]

Congratulations！








Congratulations！
在 2019-06-03 20:39:38，"caojiele1225"  写道：
>Congratulations！
>
>
>-- Best Regards！
>Jiele
>
>
>原始邮件
>发件人:Huxing zhanghux...@apache.org
>收件人:dev...@dubbo.apache.org
>发送时间:2019年6月3日(周一) 17:47
>主题:[ANN] New PMC member: Victory Cao
>
>
>Hi Community, On behalf of the Dubbo PMC, I am pleased to announce that 
>Victory Cao[1] has been voted in as a new Dubbo PMC member. Please join me to 
>say congratulations to him! [1] https://github.com/cvictory -- Best Regards！ 
>Huxing

Re:Re: [ANN] Apache Dubbo as a Top-level project

[KimmKing]

Congratulations !
在 2019-05-22 22:45:32，"Walter Wang"  写道：
>Congratulations !
>
>On Wed, May 22, 2019 at 6:09 PM caojiele1225  wrote:
>
>> Congratulations !
>> I recommend this exciting news should be added to the official website. : )
>> -- Best Regards！ Jlele
>> 原始邮件
>> 发件人:Huxing zhanghux...@apache.org
>> 收件人:dev...@dubbo.apache.org
>> 发送时间:2019年5月21日(周二) 10:53
>> 主题:[ANN] Apache Dubbo as a Top-level project
>>
>>
>> Hi, Today ASF officially announced Apache Dubbo as a Top-level project[1].
>> Congratulations to Dubbo! [1]
>> https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces52
>> -- Best Regards！ Huxing

Re: [DISCUSS] Migrating projects under dubbo group

[KimmKing]

yes

Huxing Zhang  于2019年4月26日周五 下午7:14写道：

> Hi,
>
> On Fri, Apr 26, 2019 at 6:53 PM kimm king  wrote:
> >
> > Of course, dubbo-dotnet is also need to transfer.
>
> I am assuming you can finish the transfer before May 31th, am I right?
>
>
> >
> > Huxing Zhang  于2019年4月26日周五 下午5:56写道：
> >
> > > Hi,
> > >
> > > On Fri, Apr 26, 2019 at 5:50 PM kimm king 
> wrote:
> > > >
> > > > I will transfer jms-for-apache-dubbo rpc-xmlrpc-for-apache-dubbo
> > > awesome-dubbo to ASF before the end of May.
> > >
> > > There is a pull request to merge rpc-xmlrpc-for-apache-dubbo into
> > > incubator-dubbo, so I think there is no need to transfer.
> > > What about dubbo-dotnet project?
> > >
> > >
> > > >
> > > > Huxing Zhang  于2019年4月26日周五 下午4:01写道：
> > > >>
> > > >> On Thu, Apr 25, 2019 at 4:02 PM Huxing Zhang 
> wrote:
> > > >> >
> > > >> > Hi All,
> > > >> >
> > > >> > As is discussed in the graduation proposal in general@ mailing
> list,
> > > >> > the github.com/dubbo group has some potential branding issue. To
> > > avoid
> > > >> > it completely, we need to decide the short-term plan and long-term
> > > >> > plan.
> > > >> >
> > > >> > For the short-term plan, there are two way proposed:
> > > >> >
> > > >> > 1. Rename dubbo group to another one, let's say A.
> > > >> > 2. Create a new group A, and migrate all the project to under A,
> and
> > > >> > keep the dubbo group empty. The purpose is to avoid someone to
> abuse
> > > >> > it in the future.
> > > >> >
> > > >> > I am leaning towards option 2. But I'd like to hear what other may
> > > think.
> > > >> >
> > > >> > The next step is to decide what A is.  Actually naming a thing is
> one
> > > >> > of the most difficult thing to do... I am trying to find something
> > > >> > related. I checked the wikipedia page for Dubbo[1], in the history
> > > >> > section, it says  Dubbo is now thought to be a mispronunciation
> of the
> > > >> > local Wiradjuri word "Thubbo" or "Tubbo".
> > > >> >
> > > >> > I think thubbo and tubbo both are good. thubbo is more different
> to
> > > >> > dubbo than tubbo. So I prefer thubbo. How do you think?
> > > >> >
> > > >> >
> > > >> > For the long-term plan:
> > > >> >
> > > >> > 1. Like discussed before, all projects under group A are expected
> to
> > > >> > be transferred to Apache (if the owner) agree with an ETA. I
> talked to
> > > >> > most of the owners and they basically agree, the multi-language
> > > >> > project are TODOs. I am trying to pull them onto list.
> > > >> >
> > > >> > This projects that still listed under dubbo group includes:
> > > >> >
> > > >> > * js-for-apache-dubbo
> > > >> > * py-client-for-apache-dubbo
> > > >> > * rpc-xmlrpc-for-apache-dubbo
> > > >> > * jmeter-plugins-for-apache-dubbo
> > > >> > * go-for-apache-dubbo
> > > >> > * php-framework-for-apache-dubbo
> > > >> > * dotnet-for-apache-dubbo
> > > >> > * serialization-native-hessian-for-apache-dubbo
> > > >> > * jms-for-apache-dubbo
> > > >> > * dubbo.github.io
> > > >> > * metrics
> > > >> > * hessian-lite
> > > >> > * dubbo-sentinel-support
> > > >> > * awesome-dubbo
> > > >> > * dubbo-remoting-js
> > > >> > * egg-dubbo-rpc
> > > >> > * rpc-native-thrift-for-apache-dubbo
> > > >> > * intellij-idea-plugin
> > > >> > * initializr
> > > >> >
> > > >> >
> > > >> > If you are the project owner, could you please confirm that:
> > > >> >
> > > >> > 1) are you willing to transferred to ASF or not.
> > > >> > 2) if so, please give an estimated time when will you can finish
> > > transfer.
> > > >> > What you will need to do includes:
> > > >> > - Find the all the contributors and ask them to sign the Apache
> > > >> > ICLA[2], if the contribution is trivial, this can be ignore
> > > >> > - If the code belongs to your company, you need to sign the SGA[3]
> > > >> > - request ASF infra to transfer the project
> > > >> > 3) if not, please indicate that which group you will transfer to.
> > > >> >
> > > >> > 2. Gain write access to your project after transfer
> > > >> >
> > > >> > If your project has been transferred to ASF, you will lose write
> > > >> > access temporally. The Dubbo community will vote you in as
> committer
> > > >> > by following standard ASF way. This means you have to contribute
> to
> > > >> > the project for some time in order to earn enough merit.
> > > >> >
> > > >> > 3. After the transition is done, delete group A.
> > > >> >
> > > >> > The community will summarize and keep track of the status here[4].
> > > >> >
> > > >> >
> > > >> > [1] https://en.wikipedia.org/wiki/Dubbo
> > > >> > [2]
> > >
> http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html
> > > >> > [3]
> > >
> http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html
> > > >> > [4]
> > >
> https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Best Regards！
> > > >> > Huxing
> > > >>
> > > >>
> > > >>
> > > 

Re:[IMPORTANT][PPMC] Invitation to be Dubbo PMC member

[KimmKing]

YES


At 2019-04-09 10:12:41, "Huxing Zhang"  wrote:
>Dear Dubbo PPMC members,
>
>(bcc to all PPMC members)
>
>The Dubbo community is discussing the graduation of Dubbo to be a Top
>Level project of Apache Software Foundation in the dev mailing list.
>As one of the steps towards graduation, the community needs to set up
>list of Project Management Committees (PMC) members after graduation,
>which will be included in the graduation resolution.
>
>The role of the PMC is included as follows[1]:
>
>The role of the PMC from a Foundation perspective is oversight. The
>main role of the PMC is not code and not coding - but to ensure that
>all legal issues are addressed, that procedure is followed, and that
>each and every release is the product of the community as a whole.
>That is key to our litigation protection mechanisms.
>
>Secondly the role of the PMC is to further the long term development
>and health of the community as a whole, and to ensure that balanced
>and wide scale peer review and collaboration does happen. Within the
>ASF we worry about any community which centers around a few
>individuals who are working virtually uncontested. We believe that
>this is detrimental to quality, stability, and robustness of both code
>and long term social structures.
>
>If you are willing to be a PMC member after graduation, please respond
>YES to this thread by replying to dev@dubbo.apache.org no later than
>2019-04-12 (Friday).
>If you are not subscribing the private list, please remember to
>subscribe to the private@ list.
>
>
>[1] http://www.apache.org/foundation/how-it-works.html#pmc
>-- 
>Best Regards！
>Huxing

Re:Re: Guide for adding a new module to Dubbo

[KimmKing]

And after this guide, we can create a new study project for new contributor to 
add a component demo to it.



At 2019-04-04 10:10:05, "徐靖峰"  wrote:
>It will help a lot.
>
>> 在 2019年4月3日，下午1:41，Huxing Zhang  写道：
>> 
>> Hi All,
>> 
>> Recently I've created several issues to add external ecosystem project
>> into Dubbo, when reviewing the pull request, I've seen some common
>> issues.
>> 
>> So I am thinking that it is necessary to have a documentation to guide
>> user to add a module to Dubbo.
>> 
>> For example (Incomplete, please feel free to add more)
>> 1. Update dubbo-all/pom.xml
>> 2. Add your dependency to dubbo-bom/pom.xml
>> 3. External dependencies should go to dubbo-dependency-pom/pom.xml
>> 4. Add your dependency to dubbo-distribution/pom.xml
>> 5. Update dubbo-dependencies if necessary
>> 6. Check the License of your dependencies to make sure they are
>> compatible with Apache
>> 
>> How do you think?
>> 
>> -- 
>> Best Regards！
>> Huxing
>> 

Re:GSoC Proposal

[KimmKing]

I read your proposal and give you some suggestion，
Enjoy your dubbo-dev-trip.


At 2019-04-05 03:23:24, "Daniela Morais"  wrote:
>Hey,
>
>I'm still discussing the new load balancer on Jira. I submitted my draft 
>proposal in GSoC and you can read here:
>https://docs.google.com/document/d/1h2CoVc-i7ToEeHHxkNMhWIhv1Zx-BU_YLnezoqrt8FI/edit?usp=sharing
> 
>
>
>I really appreciate any help and suggestions. 
>
>Thanks,
>--
>
>Daniela Morais
>Computer Science student at University Of Campinas
>danielammorais.com 
>

Re:Re: [ANN] New PPMC member: Kimm King

[KimmKing]

Thanks all of you.



: )

在 2019-04-01 10:52:26，"华 钟明"  写道：
>Congraduations ! __
>
>Best Regards！
>Zhongming Hua
> 
>
>在 2019/4/1 上午10:50，“Jun Alpha” 写入:
>
>Congraduations
>
>徐靖峰  于2019年4月1日周一 上午10:24写道：
>
>> 666 Congraduations!
>>
>> > 在 2019年4月1日，上午10:13，Taosheng, Wei  写道：
>> >
>> > Congraduations :)
>> >
>> >
>> >
>> >
>> > -- Original --
>> > From: Huxing Zhang 
>> > Date: Mon,Apr 1,2019 10:12 AM
>> > To: dev 
>> > Subject: Re: [ANN] New PPMC member: Kimm King
>> >
>> >
>> >
>> > Hi Community,
>> >
>> > On behalf of the Dubbo PPMC, I am pleased to announce that Kimm King[1]
>> > has been voted in as a new Dubbo PPMC member.
>> >
>> > Please join me to say congratulations to him!
>> >
>> > [1] https://github.com/kimmking
>> >
>> > --
>> > Best Regards！
>> > Huxing
>>
>>
>>
>>
>

Re:[DISCUSS] Graduate Apache Dubbo(incubating) as a Top Level Project

[KimmKing]

I think it's time to graduate now.Apache Dubbo has been a mature framework and 
lively community, and then we will move on and make it better and better.

At 2019-03-30 18:00:29, "Huxing Zhang"  wrote:
>Hi All,
>
>It has been more than 1 year since Dubbo joins the ASF
>incubator(2018-02-16). During incubation I think Dubbo community has
>been growing in a fast and healthy way, and also learned a lot about how
>to collaborate in Apache way.
>
>I think it is time to discuss the graduation as a Top level project for Dubbo.
>
>Until now, what we've achieved:
>
>### Releases
>Totally 10 release since incubation
>- Dubbo:  2.6.2, 2.6.3, 2.6.4, 2.6.5, 2.6.6, 2.7.0, 2.7.1
>- Dubbo spring boot starter: 0.2.1 & 0.1.2, 2.7.0
>- Dubbo ops: 0.1
>The release process has been well-documented and there are 6 different
>release managers: Jun Liu, Yong Zhu, Victory Cao, Huxing Zhang, Mercy
>Ma, Ian Luo.
>
>### Community building:
>- PPMC 19(+8 since incubation, excluding mentors)
>- committers 35(+18 since incubation)
>The committers varies from Alibaba, Weidian, Jingdong, Qunar, Youzan,
>Netease, Meituan-Dianping, Rongguan, Handuyishe, Didi, NetsUnion,
>Caocaokeji, Huawei, GomeFinance, Asiainfo-sec, iFlytek, Keep and etc.
>- The number of contributors has grown from 70+ to 186, the number of
>stars has grown from ~16k to 25k+, the number of forks are grown from
>12k+ to 16k+ since incubation. One thing that worthing mentioning is
>that there are 92 contributors for the website project.
>- 1401 issues and 1168 pull requests are closed since incubation.
>- 140+ companies are using Dubbo in production since incubation.
>- Discussion are happening on the mailing list. 376 subscriber for the
>dev@ mailing list. Below is some stats in recent few months:
>  * March 2019: 375 emails sent by 52 people, divided into 75 topics
>  * Feb 2019: 260 emails sent by 45 people, divided into 61 topics
>  * Jan 2019: 448 emails sent by 62 people, divided into 83 topics
>  * Dec 2018: 427 emails sent by 48 people, divided into 78 topics
>  * Nov 2018: 235 emails sent by 38 people, divided into 44 topics
>  * Oct 2018: 154 emails sent by 31 people, divided into 32 topics
>We are happy to see that more and more users joined the discussion.
>
>### IP clearance
>- The IP clearance is completed for Dubbo, dubbo-spring-boot-starter,
>and dubbo-ops project.
>- The transfer plan for external Dubbo group has been discussed[1],
>and progress has been made steadily.
>- Podling website check complete [2]
>- Podling name search completed [3]
>- Promote the ASF download link in the official website[4]
>- A list of committers is shown in the official website[5]
>- The Dubbo incubation status page[6] has been kept up-to-date
>
>Based on the data above, I think Dubbo is ready for graduation.
>How do you folks think?
>
>[1] 
>https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status
>[2] https://whimsy.apache.org/pods/project/dubbo
>[3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-152
>[4] http://dubbo.apache.org/en-us/blog/download.html
>[5] http://dubbo.apache.org/en-us/docs/developers/developers_dev.html
>[6] https://incubator.apache.org/projects/dubbo.html
>
>-- 
>Best Regards！
>Huxing

Re:Re: [Discussion] Provide different documentation for each release

[KimmKing]

+1 good idea








+1  good idea
At 2019-03-01 10:37:51, "Huxing Zhang"  wrote:
>+1 to have each release documented.
>
>At least we should have a blog post for each release introducing the
>major changes.
>
>On Thu, Feb 28, 2019 at 11:09 PM Taosheng Wei  wrote:
>>
>> Hi Community,
>> Now the documentations of dubbo do not associate each release version.
>> I find some projects, like spring, have a complete documentation for each
>> stable release. Maybe most contents of a document of each release are
>> identical, but if the features are added or changed, or api has been
>> changed, the document can provide the latest guide to users.
>>
>> So I think we can follow projects like spring, to provide a complete
>> documentation for each release. Maybe we do not need to patch all the
>> releases that have been not latest. We can provide a new complete
>> documentation from a future release. And we can continue providing complete
>> documentations for releases after the first release which have a complete
>> one.
>>
>> What's your opinions?
>>
>> Best regards,
>> Taosheng
>
>
>
>-- 
>Best Regards！
>Huxing

Re:Re: Etcd support in 2.7.x

[KimmKing]

Good  idea

在 2019-02-27 16:52:16，"Mercy"  写道：
>Great news!
>
>Kind regards,
>
>Mercy Ma
>
>在 2019/2/27 下午2:44, Huxing Zhang 写道:
>> Hi,
>>
>> On Wed, Feb 27, 2019 at 2:05 PM yuhang xiu  wrote:
>>> good news!
>>>
>>> I remember that yiji is familiar with etcd3, and he may give us some advice.
>> I am working based on this implementation[1], which is done by yiji.
>> The first step is to merge in into Dubbo repository.
>>
>> [1] https://github.com/dubbo/dubbo-registry-etcd
>>
>>> YunKun Huang  于2019年2月27日周三 上午11:54写道：
>>>
 +1
 good to have official support for etcd.

  From my personal experience, etcd is common and many companies already
 have it in their IT infrastructure.

 On 2019/02/26 15:00:34, Huxing Zhang  wrote:
> Hi,
>
> Since Dubbo 2.7, the registry metadata and configuration metadata has
> been split, which make Dubbo easier to support more popular projects
> like nacos, etcd, and consul
>
> I am planning to work on the etcd support for 2.7.x including:
> - simplified registry url
> - etcd as configuration center
> - etcd as metadata report
>
> Hopefully will get it done before 2.7.1 release :)
>
> --
> Best Regards！
> Huxing
>
>>
>>

Re:[DISCUSS] Next Dubbo meetup

[KimmKing]

Hi, guys,

I suggest setup a meetup in beijing early in 2019.

在 2018-12-04 16:08:35，"王蓉(涂南)"  写道：

Hi guys,


I'm Amber, organizer of Dubbo meetup.


Since 2018, Dubbo community has been touring around China!
We have been to Beijing, Chengdu, Shenzhen, Shanghai, and Hangzhou.
More than 30K developers have either come to the meetup or watched our live 
streaming videos.
What a wonderful journey!

Now you got to choose where our 2019 first meetup is going to be held!
We're planning to hold another meetup on Jan 19th.
Let us know your thoughts!


Ballot here ‍http://sc-meetup.mikecrm.com/7hZFeTl
Deadline for this ballot is Dec.14.




|
|
| |
王蓉Amber
阿里巴巴
电话：057128223456-83770759
邮箱：tunan...@alibaba-inc.com
地址：浙江-杭州-余杭-西溪园区 8-6-S-30
| |


| | | 阿里巴巴 | 企业主页 | | |


|
邮件信息安全声明已开启

??????????Dubbo??????????????????

[KimmKing]

??dubbo
??RPC??
dubbo??RPC







| |
??
??kimmk...@163.com
|

??  

??2018??10??28?? 11:34?? ??
??Dubbo
   
??RPC
   
Dubbo??
   
??
   
??dubbo??DubboDubbo


   ??





 
:aaron_yang...@foxmail.com

Re:Re: pull request #2647: [Dubbo-2578]Smooth Round Robin selection

[KimmKing]

Thanks for a good pr first.
But I think old-way is better useful.
When we need a balance, it means so much invoking occurs, so the most important 
point is:

* Lightweight and Performance
Then accuracy and smoothness are not so much prior.
And actually nobody would have more than 100 providers for a single service, so 
the number of invokers is small,
we could not care about its change, check stage is not a key point.



At 2018-10-24 17:48:31, "Jason Joo"  wrote:
>hi, xiu
>
>After some deeper research on the algorithm i found it seemed like thread-safe.
>
>I updated my PR and unit test on it so we can examine if it acts as expected.
>
>So the recycle logic I change it into an optimistic lock.
>
>NGINX is a single-process model which lead me to a wrong path.
>
>
>
>So it's lock-free and with memory recycler now.
>
>Let's check if it works correctly.
>
>
>best regards,
>
>Jason
>
>> On Oct 24, 2018, at 16:38, yuhang xiu  wrote:
>> 
>> Hi, jason
>> 
>> If we can have a good balance on synchronize, thread and memory, I support
>> the way of smooth.
>> We need more discussion and solutions on this issue. Looking forward to
>> your solutions. :)
>> 
>> Thx
>> 
>> Jason Joo  于2018年10月24日周三 下午4:32写道：
>> 
>>> hi, xiu
>>> 
>>> Good proposal.
>>> 
>>> The old not-very-smooth RoundRobin implementation can work fine in most
>>> conditions.
>>> Actually it depends the number of weight.
>>> That means 500:500:500 will be quite different from 1:1:1 and maybe we can
>>> simplify the weights when selecting.
>>> 
>>> 
>>> And i have another thought about the KEY.
>>> Now the key is defined by Method (which can make method's invocation RR).
>>> If we change it into by Service (which the method will not be RR if its
>>> invocations just match a round) the memory issue may looked better.
>>> 
>>> 
>>> So what do other guys think about?
>>> 
>>> 
>>> best regards,
>>> 
>>> Jason
>>> 
 On Oct 24, 2018, at 16:09, yuhang xiu  wrote:
 
 你好，
 
 我个人认为我们应该在smooth和性能之间做一个取舍。我个人倾向于使用非smooth的方式，原因：
 1.使用smooth需要增加线程开销或者增加内存开销，或者用锁来增加了性能开销，就像 @jason
 说的那样。而本身负载均衡是一个很轻量的组件，我们是否有必要把他做的这么复杂？
 
>>> 2.我承认smooth的方式更好，但是如果我们把一个provider的权重设置为特定的值，那么说明他能承受相应的请求量，不管是N个请求同时进行还是分开进行。如果这个provider承受不住同时进行N个请求，我们需要做的应该是把他的权重调低。
 
 
>>> 综上，我个人认为，当前的smooth实现方式不是很理想，我们没法在锁、线程和内存上都达到一个非常优秀的平衡。所以我认为可以不使用smooth的方式。
 
 谢谢。
 
 Jason Joo  于2018年10月24日周三 下午3:57写道：
 
> hi, Luo
> 
> Glad to receive your response. I posted a reply before including some
> minds about the lock:
> 
> * Separated recycle thread (more threads)
> 
> or
> 
> * Lock free (more memory in special conditions)
> 
> It's truly a struggling job to make a decision and we can do it
>>> together.
> For the lock-free implementation it will waste or even fail if the
> providers are fully dynamic deployed after running enough time(OOM?).
> 
> best regards,
> 
> Jason
> 
>> On Oct 24, 2018, at 14:50, Ian Luo  wrote:
>> 
>> Hi Jason,
>> 
>> I reviewed your pull request 2647 ( [Dubbo-2578]Smooth Round Robin
> selection) [1] today. It is an awesome implementation and I like it.
>> 
>> There's one particular issue you may need to consider further is I
>>> think
> we should avoid synchronized block. I have drop review comments on the
>>> pull
> request. Would you mind to consider this further. After that, I think
>>> this
> change is ready to go.
>> 
>> Thanks,
>> -Ian.
>> 
>> 1. https://github.com/apache/incubator-dubbo/pull/2647 <
> https://github.com/apache/incubator-dubbo/pull/2647>
> 
>>> 
>>> 
>

Re:Re: A preformance issue And Optimizing RoundRobinLoadBalance

[KimmKing]

hi， shuaijunlan
> wrote:
>> >> When calling the service seven times, the responding order is [A ,A, A,  
>> >> A, A, B, C].


Not at all， you can try it 7 times






At 2018-10-16 14:37:33, "Ian Luo"  wrote:
>I got your point, Jason, Would you mind to update your explanation on
>https://github.com/apache/incubator-dubbo/issues/2578? It is convenient for
>other people to revisit this issue later :)
>
>Thanks,
>-Ian.
>
>On Tue, Oct 16, 2018 at 2:25 PM Jason Joo  wrote:
>
>> Hi, lan
>>
>> I gave a sample from Nginx® Code in JAVA and gained better performance
>> compared to previous one(in that issue reply list).
>>
>> Junlan's point is not to shuffle the addresses list and to select a
>> different node every time as possible, eg:
>>
>> A:B:C = 1:2:3
>> [A, B, C, B, C, C,  A, B, C, B, C, C,A, B, C, B, C, C,
>>A, B, C, B, C, C, ..]
>>
>> especially the factor number is large as: [90 : 100 : 111]
>>
>> best regards,
>>
>> Jason
>>
>> > On Oct 16, 2018, at 14:12, Ian Luo  wrote:
>> >
>> > Hi Junlan,
>> >
>> > Are you suggesting we should shuffle the result address array?
>> >
>> > Thanks,
>> > -Ian.
>> >
>> > On Fri, Oct 12, 2018 at 4:24 PM Junlan Shuai 
>> wrote:
>> >
>> >> Hi,
>> >> The RoundRobinLoadBalance Algorithm is not smoothing.
>> >> For example, assuming that the weight of Server A is five, the weight of
>> >> Server
>> >> B is one, the weight of Server C is one.
>> >> When calling the service seven times, the responding order is [A ,A, A,
>> A,
>> >> A, B, C].
>> >> By this responding order, we can find that the first five callings
>> point to
>> >> Server A, it will cause Server A to be overloaded in a short period of
>> >> time.
>> >> Ideally, the call order would be [A ,A, B, A, C, A, A].
>> >> So, I think there may be a better way to do this.
>> >>
>> >> KimmKing  于2018年9月30日周日 下午4:09写道：
>> >>
>> >>> Hi, community.
>> >>>
>> >>>
>> >>> Dubbo user manzhizhen find a preformance bug in
>> >>> dubbo-cluster/RoundRobinLoadBalance and discuss in Github Is
>> >>> https://github.com/apache/incubator-dubbo/issues/2578
>> >>>
>> >>>
>> >>> Here I describe it shortly:
>> >>> 1. The new version RoundRobinLoadBalance algorithm use an iterator
>> from 0
>> >>> to maxWeight:
>> >>> for (int i = 0; i < maxWeight; i++) { // this is the reason
>> >>> for (Map.Entry each :
>> >>> invokerToWeightMap.entrySet()) {
>> >>>
>> >>> }
>> >>> }
>> >>> 2.If maxWeight is a number  much more than 100, then this select method
>> >>> will be executed so mush slowly.
>> >>> 3. When call it 1M times: maxWeight is 5000, then it need 60+ seconds;
>> >>> maxWeight is 5, then it need 10+ minutes.
>> >>> 4. And in a deep compare testing, RandomLoadBalance &
>> >>> RoundRobinLoadBalance (in 2.5.3, but implement is wrong) need 100-200ms
>> >>> while calling 1M times.
>> >>> 5. So we should Optimize RoundRobinLoadBalance to a new
>> high-performance
>> >>> algorithm implement, abandoning iterator from 0 to maxWeight.
>> >>> 6. Then gudegg submit a PR to Optimize RoundRobinLoadBalance correctly,
>> >>> the balance results by new PR is absolutely correct and only elapse
>> >>> 100-300ms in my test like step 3.
>> >>>
>> >>>
>> >>> Think it above over and over, I suggest we should merge the PR
>> recently.
>> >>> Any questions, buddies?
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Kimm King(kimmk...@apache.org/kimmk...@163.com)
>> >>> Apache Dubbo Committer/Alibaba Fastjson Developer/Aliyun MVP
>> >>>
>> >>>
>> >>
>> >> --
>> >> Junlan
>> >> Best regards!
>> >>
>>
>>

Re:dubbo网关咨询

[KimmKing]

So far, there is not a gateway in Dubbo framework.But you can use a API gateway 
such as zuul/zuul2/springcloudgateway to proxy and enhance your Rest API via 
dubbo rest protocol for all web/app/api accessing.
在 2018-10-18 09:57:17，"1009678728"  写道：
>您好：
>
>
>  
> 目前我公司这边有在用dubbo做微服务架构，目前准备做api网关，但是找了下都没有看下相关的解决方案，请求dubbo做微服务有什么好的api网关方案吗，还是需要自己用generic自建网关？
>
>
>谢谢
>
>
>--
>   黄明建
>   
> EMAIL：1009678...@qq.com
>   TEL：15280238325

Re:[DISCUSS] Introduce TagRouter, a new route feature.

[KimmKing]

Thanks kirito for making a new big feature at first time.
The key point is with current implement, an invocation with a tag can't return 
all invokers in TagRouter.

So I suggest here:
Add a forceTag flag(TAG_FORCE_KEY = "tag.force"), default value is false.
1. When it's true, TagRouter strickly match invokers' tag.
- An invocation with "black" tag only match invokers with "black" tag.
- An invocation with empty tag only match invokers withempty tag.
- An invocation match no invokers will return no invokers.
2. When it's false(default), TagRouter match invokers' tag by the most invokers 
strategy.
- An invocation with "black" tag match invokers with "black" tag. If no 
invokers with "black" tag, return all invokers.
- An invocation with empty tag will match all invokers.
- An invocation match no invokers will return all invokers.
Then we can cover all condition for using TagRouter.
And I pull request my codes with all tests here, we can review and complete it 
now:
https://github.com/apache/incubator-dubbo/pull/2343


在 2018-08-24 01:58:01，"徐靖峰"  写道：
>Hi, community. This mail is related to this issue.A simple and incomplete 
>TagRouter has merged into dubbo v2.7.0-snapshot，in this mail，i will introduce 
>what problem did it solve. At the end of the letter, i want to refer to your 
>opinion and proposal, decide the final behavior of  TagRouter .
>
>What is TagRouter
>
>TagRouter is a new implement of Router interface, other exsiting Router : 
>ConditionRouter, ScriptRouter, FileRouter.
>
>It makes any request can carry a request.tag and any service belong to a 
>certain tagTag will affect the default route behavior.
>
>Some pain points in the past
>
>
>
>fact1: some applications changed at the same time in different branch,like 
>A,B,C.fact2: some applications didn't change ,but deploy repeatedly，like 
>D,E.fact3: if a new feature need to be tested, all 5 application need to be 
>deployed.fact4: isolation by feature is not friendly to parallel development.
>
>Benefited from tag
>
>
>
>we consider the RED，YELLOW，BLUE as tagged service , the grey block as origin 
>service or normal service.
>
>The benefit we have is that we have reduced a lot of overhead about 
>application deployment. Only changed applications need deploy incrementally .
>
>A vivid example
>
>
>
>Usage
>
>consumer
>RpcContext.getContext().setAttachment("request.tag","red");
>I suggest you can use filter or SPI to set this attachment, notice that 
>RpcContext is bound to Thread.
>
>provider
>@Bean
>public ApplicationConfig applicationConfig() {
>ApplicationConfig applicationConfig = new ApplicationConfig();
>applicationConfig.setName("provider-book");
>// instruct tag router
>Map parameters = new HashMap<>();
>parameters.put(Constants.ROUTER_KEY, "tag");
>applicationConfig.setParameters(parameters);
>return applicationConfig;
>}
>Need more discussion
>
>
>If a tag request can not find any application of the same tag，should it use 
>other application of different tag (NOTICE : different tag is not the default 
>application with grey block)
>
>
>
>If a normal request can not find normal application，should it use any tag 
>application?(in my opinion，normal request should not reach the tag 
>application，also the current version).
>
>
>
>A forceTag flag  can be considered to decided the behavior of downgrade. 
>forceTag=true means all tag requests must strictly match the application's 
>tag；forceTag=false means tag requests will prefer the application of the same 
>tag，if there is no corresponding application， downgrade to other 
>application，ignore the tag.
>
>
>
>On the basis of 3.  what is default value of foreTag TRUE or FALSE.
>
>
>more suggestions are welcome to make.

Re:Re:[DISCUSS]A new Dubbo ascii logo is wanted

[KimmKing]

All logos in dubbo-logo.txt


I like varsity font.


At 2018-08-22 13:26:51, "秦金卫"  wrote:




sh logo.sh, you will get  dubbo logos for all fonts.






At 2018-08-22 12:16:20, "yuhang xiu"  wrote:
>Hello, community,
>
>Dubbo's current terminal LOGO is like this:
>
>▄   ████▄   ▀█▄   ▀█▄▄██▄
>███   ▀███  ██████████████████  ██████
>██████  ██████████████████  ██████
>██████  ██████   ▄███▄▄▄██▀▄███▄▄▄██▀   ██████
>██████  ██████  ▀▀███▀▀▀██▄   ▀▀███▀▀▀██▄   ██████
>██████  ███████████▄█████▄  ██████
>███   ▄███  ██████████████████  ██████
>▀   ▀   ▄█▀   ▄█▀▀██▀
>
>which is not not concise and beautiful.
>
>So I think we should call for a new ASCII LOGO. I found some nice LOGO on
>this site[1] like:
>
>  ___    
> |  __ \  | |  | | |  _ \  |  _ \   / __ \
> | |  | | | |  | | | |_) | | |_) | | |  | |
> | |  | | | |  | | |  _ <  |  _ <  | |  | |
> | |__| | | |__| | | |_) | | |_) | | |__| |
> |_/   \/  |/  |/   \/
>
>
>or
>
>.--. .   ..--. .--.  .--.
>|   :|   ||   )|   )::
>|   ||   ||--: |--: ||
>|   ;:   ;|   )|   ):;
>'--'  `-' '--' '--'  `--'
>
>and so on.
>
>In my opinion, it is better to make the LOGO design more concise. How
>about others?
>
>Welcome to reply directly to the email and post the LOGO that you
>think is good-looking.
>
>
>
>[1]https://devops.datenkollektiv.de/banner.txt/index.html





 1row

|) |_| ]3 ]3 () 

3-d

 ***   ** ** **   ** ***  
/**** /**/**/*** /***   **/** 
/**/**/**/**/*   /** /*   /**  ** //**
/**/**/**/**/**  /**  /**  /**
/**/**/**/**/* **/* **/**  /**
/**** /**/**/*/**/*/**//** ** 
/***  //*** /*** /***  //***  
//////  ///  //////   
3d_diagonal


 ,..
,---,,---,.  ,---,. /   /   \   
  .'  .' `\,--,,'  .'  \   ,'  .'  \   /   . :  
,---.' \ ,'_ /|  ,---.' .' | ,---.' .' |  .   /   ;.  \ 
|   |  .`\  |   .--. |  | :  |   |  |: | |   |  |: | .   ;   /  ` ; 
:   : |  '  | ,'_ /| :  . |  :   :  :  / :   :  :  / ;   |  ; \ ; | 
|   ' '  ;  : |  ' | |  . .  :   |;  :   |;  |   :  | ; | ' 
'   | ;  .  | |  | ' |  | |  |   : \ |   : \ .   |  ' ' ' : 
|   | :  |  ' :  | | :  ' ;  |   |   . | |   |   . | '   ;  \; /  | 
'   : | /  ;  |  ; ' |  | '  '   :  '; | '   :  '; |  \   \  ',  /  
|   | '` ,/   :  | : ;  ; |  |   |  | ;  |   |  | ;;   :/   
;   :  .' '  :  `--'   \ |   :   /   |   :   /  \   \ .'
|   ,.'   :  ,  .-./ |   | ,'|   | ,'`---`  
'---'  `--`' `'  `' 

3x5


##  # # ##  ##   #  
# # # # # # # # # # 
# # # # ##  ##  # # 
# # # # # # # # # # 
##  ### ##  ##   #  
5lineoblique

  
//) ) //   / / //   ) ) //   ) ) //   ) ) 
   /// / //   / / //___/ / //___/ / //   / /  
  /// / //   / / / __  (  / __  (  //   / /   
 /// / //   / / //) )//) )//   / /
/// / ((___/ / /// //// /((___/ / 
B1FF

|)|_||3|30
DANC4

'\   /`  \O#OO\O/#
  \ / |_|#   |#   _Y  
   Y /  |  / \  / \ _| |  
   O\# ./   |__\ /__\ /_   |_ 
ICL-1900

DUBBO
* ** 
*
 *   
 
  ** 
 
**   
 
*
 
 
 
acrobatic

  o__ __oo oo__ __o o__ __o o__ __o  
 <| v\  <|>   <|>  <| v\   <| v\   /v v\ 
 / \ <\ / \   / \  / \ <\  / \ <\ />   <\
 \o/   \o   \o/   \o/  \o/ o/  \o/ o/   o/   \o  
  | |>   | ||__  _<||__  _<|   <| |> 
 / \   //   < >   < >   |   \   |   \   \\   //  
 \o/  /  \ / // \ /
  |  oo   o |  o|  o   o   o 
 / \  __/><\__ __/>/ \  __/>   / \  __/>   <\__ __/> 
 
 
 
alligator

  :  ::::::   :   :    
 :+::+: :+::+:   :+::+:  :+:

Re:Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[KimmKing]

I think need not


At 2018-08-17 17:47:08, "Jerrick Zhu"  wrote:
>Another question, do we need to add these sub modules' binary classes to
>dubbo.jar , as the previous hessian-lite module?
>
>Or we also remove all of them from dubbo.jar?
>
>On Fri, Aug 17, 2018 at 5:36 PM Jerrick Zhu  wrote:
>
>> Great. Let's do it. I'll start an issue to track this proposal.
>>
>> On Fri, Aug 17, 2018 at 5:11 PM G C  wrote:
>>
>>> +1 Deep agree
>>> --
>>> Best Regards！
>>>
>>> cgfork
>>>
>>> On Fri, Aug 17, 2018 at 4:53 PM yuhang xiu  wrote:
>>> >
>>> > Deep agree with this proposal
>>> > :)
>>> >
>>> > Jerrick Zhu  于2018年8月17日周五 下午1:39写道：
>>> >
>>> > > I agree with keeping the following modules:
>>> > > * dubbo-registry-multicast,
>>> > > * dubbo-rpc-injvm,
>>> > > * dubbo-serialization-fastjson
>>> > > * dubbo-serialization-jdk
>>> > >
>>> > > They're useful for new users and develop experience.
>>> > >
>>> > > On Fri, Aug 17, 2018 at 11:10 AM Ian Luo  wrote:
>>> > >
>>> > > > wow, this is a big step but I have somewhat opposite opinion against
>>> > > > Jerrick's proposal. Instead of keeping recommended extensions only
>>> but
>>> > > > moving out others into eco system, I would like to revise it to
>>> keeping
>>> > > > most used extensions, use Jerrick's list as an example:
>>> > > >
>>> > > > * dubbo-registry-multicast <- should keep, it's good for dev
>>> experience
>>> > > > * dubbo-registry-redis <- should move, since not everyone needs this
>>> > > > feature
>>> > > > ...
>>> > > >
>>> > > > * dubbo-remoting-grizzly <- should move, ditto
>>> > > > * dubbo-remoting-p2p <- should move, ditto
>>> > > > * dubbo-remoting-zookeeper <- should move, ditto
>>> > > > * dubbo-remoting-mina <- should move, ditto
>>> > > > ...
>>> > > >
>>> > > > * dubbo-rpc-injvm <- should keep, since local-call is one necessary
>>> > > > feature, think about EJB's local call.
>>> > > > * dubbo-rpc-memcached <- should move
>>> > > > * dubbo-rpc-redis <- should move
>>> > > > * dubbo-rpc-thrift <- should move
>>> > > > * dubbo-rpc-webservice < - should move
>>> > > > ...
>>> > > >
>>> > > > * dubbo-serialization-fastjson <- should keep, very popular json
>>> library
>>> > > > * dubbo-serialization-fst <- should move
>>> > > > * dubbo-serialization-jdk <- should keep, last resort when other
>>> > > > serialization fails to work.
>>> > > >
>>> > > >
>>> > > > Just my two cents,
>>> > > > -Ian.
>>> > > >
>>> > > > On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu 
>>> wrote:
>>> > > >
>>> > > > > Hi, community
>>> > > > >
>>> > > > > As you can see, Dubbo now has an ecosystem:
>>> https://github.com/dubbo
>>> > > > > .There
>>> > > > > has a lot of interesting projects there, such as:
>>> > > > >
>>> > > > > * node, go, python and php implementations
>>> > > > > * dubbo rpc, serialization and registry extensions
>>> > > > > * dubbo samples and dubbo useful plugins and tools
>>> > > > >
>>> > > > > Now Dubbo core which is http://github.com/apache/incubator-dubbo
>>> ,
>>> > > it's
>>> > > > > too
>>> > > > > big. As a result, it takes nearly 30~40mins to finish travis CI.
>>> > > > >
>>> > > > > And also, there are a lot of sub modules have never been modified
>>> > > almost,
>>> > > > > such as:
>>> > > > >
>>> > > > > * dubbo-registry-multicast
>>> > > > > * dubbo-registry-redis
>>> > > > > ...
>>> > > > >
>>> > > > > * dubbo-remoting-grizzly
>>> > > > > * dubbo-remoting-p2p
>>> > > > > * dubbo-remoting-zookeeper
>>> > > > > * dubbo-remoting-mina
>>> > > > > ...
>>> > > > >
>>> > > > > * dubbo-rpc-injvm
>>> > > > > * dubbo-rpc-memcached
>>> > > > > * dubbo-rpc-redis
>>> > > > > * dubbo-rpc-thrift
>>> > > > > * dubbo-rpc-webservice
>>> > > > > ...
>>> > > > >
>>> > > > > * dubbo-serialization-fastjson
>>> > > > > * dubbo-serialization-fst
>>> > > > > * dubbo-serialization-jdk
>>> > > > > ...
>>> > > > >
>>> > > > > So I suggest, move the above sub modules to ecosystem, each of
>>> them as
>>> > > a
>>> > > > > single project, such as
>>> > > https://github.com/dubbo/dubbo-rpc-native-thrift
>>> > > > >
>>> > > > > Also, dubbo-demo also needs to move to ecosystem.
>>> > > > >
>>> > > > > What do u guys think?
>>> > > > >
>>> > > > > Sincerely.
>>> > > > >
>>> > > > > Jerrick
>>> > > > >
>>> > > >
>>> > >
>>>
>>

Re:Re:Re: reconstruction of dubbo ops

[KimmKing]

And you can see this project:
https://github.com/dubboclub/dubbokeeper





在 2018-08-16 19:54:31，"秦金卫"  写道：
>Wonderful,Admin need be reborn.
>在 2018-08-16 17:57:33，"Xin Wang"  写道：
>>Good job，
>> I think you can setup a gitthub project to manage this refactoring
>>issue，then more people can take part in it
>>
>>Minxuan Zhuang  于2018年8月16日周四 下午5:46写道：
>>
>>> Hi community:
>>> I've commit a pull request:
>>> https://github.com/apache/incubator-dubbo-ops/pull/87 this is a
>>> reconstruction of dubbo Ops，the structure looks like:
>>>
>>>dubbo-admin
>>>  ---dubbo-ops-frontend
>>>  ---dubbo-ops-backend
>>>
>>> the front end is based on Vuetify  and generated
>>> with Vue-cli, frontend-maven-plugin
>>>  is used to do npm
>>> build
>>> with maven. Now this reconstruction version contains only skeleton, so I
>>> suggest to open *a new branch* for this pull request, Thanks.
>>>

Re:Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[KimmKing]

Absolutely agree +1


Until now, Dubbo core repo contains too much contents, many components look 
like unnecessary in this repo.
In my opinion:
"Micro Kernel, Rich Ecosystem" should be a key principle to design, improve, 
maintain this project.
After separate these components（never been modified almost） to dubbo org as 
some independent repo, 
it will be easy to test and build by decreasing core repo codes.


At 2018-08-16 16:03:59, "Jerrick Zhu"  wrote:
>Dubbo core only keeps the api and recommended extension. Keep the core
>minimum.
>On Thu, Aug 16, 2018 at 4:00 PM Jerrick Zhu  wrote:
>
>> Hi, community
>>
>> As you can see, Dubbo now has an ecosystem: https://github.com/dubbo
>> .There has a lot of interesting projects there, such as:
>>
>> * node, go, python and php implementations
>> * dubbo rpc, serialization and registry extensions
>> * dubbo samples and dubbo useful plugins and tools
>>
>> Now Dubbo core which is http://github.com/apache/incubator-dubbo , it's
>> too big. As a result, it takes nearly 30~40mins to finish travis CI.
>>
>> And also, there are a lot of sub modules have never been modified almost,
>> such as:
>>
>> * dubbo-registry-multicast
>> * dubbo-registry-redis
>> ...
>>
>> * dubbo-remoting-grizzly
>> * dubbo-remoting-p2p
>> * dubbo-remoting-zookeeper
>> * dubbo-remoting-mina
>> ...
>>
>> * dubbo-rpc-injvm
>> * dubbo-rpc-memcached
>> * dubbo-rpc-redis
>> * dubbo-rpc-thrift
>> * dubbo-rpc-webservice
>> ...
>>
>> * dubbo-serialization-fastjson
>> * dubbo-serialization-fst
>> * dubbo-serialization-jdk
>> ...
>>
>> So I suggest, move the above sub modules to ecosystem, each of them as a
>> single project, such as https://github.com/dubbo/dubbo-rpc-native-thrift
>>
>> Also, dubbo-demo also needs to move to ecosystem.
>>
>> What do u guys think?
>>
>> Sincerely.
>>
>> Jerrick
>>

Re:Re: [incubator-dubbo-website] branch asf-site updated: Google Analytics support

[KimmKing]

 It's a good idea to add google analytics, github stars to dubbo web page .
At 2018-08-16 10:05:50, "Justin Mclean"  wrote:
>Hi,
>
>I know of other Apache projects that also use google analytics, that’s not to 
>say it right to do so, but currently we don’t really have any direction or 
>policy on this so it’s hard to know what to do.
>
>Thanks,
>Justin 

Re:Re: [ANN] New committer: kimmking & diecui1202

[KimmKing]

Hello, every buddy.
Thank all of you.It's my great honor.
I am a Java developer for more than 12 years in Beijing, and interested in 
RPC\SOA\MQ\MicroService Architecture etc.
I meet and like Dubbo since 2012, then I was an architect  in Alibaba inc(my 
nickname is yuhuang/禹皇).
My teams use Dubbo till now in most projects I working for after I left Alibaba.
And I will make more contribution to Apache Dubbo project with everyone in 
Community.


At 2018-08-09 15:35:28, "Jerrick Zhu"  wrote:
>hi, community
>
>It's my great honor to be voted as a Dubbo committer. Thanks for all your
>help on the road.
>
>I'm a Java developer for nearly 10 years.
>
>Dubbo is an amazing open source project, I've learned a lot when
>participating. Let's make Dubbo better together.
>
>Sincerely.
>
>Jerrick
>
>On Thu, Aug 9, 2018 at 2:00 PM Huxing Zhang  wrote:
>
>> Hi All,
>>
>> On behalf of the Dubbo PPMC, I am pleased to announce that both
>> kimmking and diecui1202 have been voted in as a new Dubbo committer.
>>
>> Please join me to say congratulations to them!
>>
>> kimmking & diecui1202,
>>
>> Would you please briefly introduce yourself to the community?
>>
>> --
>> Best Regards！
>> Huxing
>>

回复：[CANCEL][VOTE]: Release Apache Dubbo (Incubating) 2.6.3 [RC2]

[kimmking]

Agree,
And I think we should provide a check approach forcompatible problem with other 
versions when every release.


原始邮件
发件人:Jun liuliu...@apache.org
收件人:dev...@dubbo.apache.org
发送时间:2018年8月5日(周日) 21:01
主题:[CANCEL][VOTE]: Release Apache Dubbo (Incubating) 2.6.3 [RC2]


Hi All, I am afraid we have to cancel the release of RC2, Jason has found that 
this candidate has a compatible problem with eailier versions 2.5.9 and 
2.5.10[1]. This issue is not what we expected, so I think we should fix this 
issue and start a new vote round. 1. 
https://github.com/apache/incubator-dubbo/issues/2174 Best regards, Jun  On 31 
Jul 2018, at 11:51, Jun Liu liu...@apache.org wrote:   Hello Dubbo Community,   
This is a call for vote to release Apache Dubbo (Incubating) version 2.6.3.   
The release candidates (RC2):  
https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.3   Git tag for the 
release (RC2):  https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.3   
Hash for the release tag:  a8be0eaaddab198ed03b0150d4db03e2b22f023f   Release 
Notes:  https://github.com/apache/incubator-dubbo/blob/2.6.3-release/CHANGES.md 
  The artifacts have been signed with Key : 28681CB1, which can be found in the 
keys file:  https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS   The 
vote will be open for at least 72 hours or until necessary number of votes are 
reached.   Please vote accordingly:   [ ] +1 approve  [ ] +0 no opinion  [ ] -1 
disapprove with the reason   The previously RC1 vote thread:  
https://lists.apache.org/thread.html/6371153d4fd5645615c14518f70f423134b08148c2fba72e5bb63a55@%3Cdev.dubbo.apache.org%3E
   Thanks,  The Apache Dubbo (Incubating) Team   Best regards,  Jun