Re: On a user list

[Mark Thomas]

On 08/03/18 08:09, jun liu wrote:
> Thanks for your advice to dubbo community, Adrian. 
> 
> I agree with the potential problems or even challenges you mentioned. But 
> when other channels are not forced to be closed, people can still have 
> discussions on github issues or gitter channels, only remember to bring the 
> decision making ones here the @dev list.

My strong recommendation is that all development discussion moves to the
dev@ list.

Projects can have a range of user support channels (IRC, Gitter,
HipChat, mailing list, Stack overflow) as the project feels necessary.

> Finally, i’d like to see the github issue to be a pure place for tracking 
> determined requirements, enhancements, bugs or high suspicious bugs,

That seems sensible to me. Mixing bugs and support issues in the same
tracker might make it hard for people to work with.

> while casual discussions or decisions can be raised here. I don’t know  
> whether a github issue should working that way, but a user/dev list would 
> definitely helps to reach there, so i would choose to be a good boy and 
> follow the mentor’s guidance, see what will happen using both mailing list 
> and github issue at the incubator phase.
> 
> I expect to see the amazing features happen: any issues raised with apache 
> github will be sent to the @dev list automatically after a proper repo 
> migration.

Given Dubbo has an issues@ list I'd expect it to go there but the Dubbo
community can choose how it wants to handle that.

Mark


> Also only my own opinion, a new fellow in apache and the github community.
> 
> Best regards,
> Jun Liu
> 
> 
>> On 7 Mar 2018, at 4:46 PM, Adrian Cole  wrote:
>>
>> Hi, folks.
>>
>> I understand that conventionally apache incubator projects don't have
>> user lists. I suspect someone more familiar can give the whole story
>> on that, but I assume the rationale is to be a bit cautious while the
>> project matures. Notably, this is maturing in the Apache way, conduct
>> and community.
>>
>> That said, I was a bit alarmed to see a suggestion that all users
>> should be routed to the dev list from github.
>> https://github.com/alibaba/dubbo/issues/1393
>>
>> The reason I was concerned was just the huge following dubbo has..
>> 2.7k watchers if not ignoring will receive this advice :) Perhaps
>> prematurely, I'm worried that redirecting routine users to the dev
>> list will be hard to undo once people establish a pattern. I feel we
>> could stop that pattern up-front by having a user list and suggesting
>> that instead.
>>
>> Please bear in mind that I don't have a lot of experience with dubbo
>> and people communicating on the "wrong list" isn't necessarily bad. I
>> might just be a bit scared due to the scale of the existing community
>> here.
>>
>> Thoughts welcome, and if none, thanks for letting me express myself :)
>>
>> -A
> 

Re: On a user list

[jun liu]

Thanks for your advice to dubbo community, Adrian. 

I agree with the potential problems or even challenges you mentioned. But when 
other channels are not forced to be closed, people can still have discussions 
on github issues or gitter channels, only remember to bring the decision making 
ones here the @dev list. Finally, i’d like to see the github issue to be a pure 
place for tracking determined requirements, enhancements, bugs or high 
suspicious bugs, while casual discussions or decisions can be raised here. I 
don’t know  whether a github issue should working that way, but a user/dev list 
would definitely helps to reach there, so i would choose to be a good boy and 
follow the mentor’s guidance, see what will happen using both mailing list and 
github issue at the incubator phase.

I expect to see the amazing features happen: any issues raised with apache 
github will be sent to the @dev list automatically after a proper repo 
migration.

Also only my own opinion, a new fellow in apache and the github community.

Best regards,
Jun Liu


> On 7 Mar 2018, at 4:46 PM, Adrian Cole  wrote:
> 
> Hi, folks.
> 
> I understand that conventionally apache incubator projects don't have
> user lists. I suspect someone more familiar can give the whole story
> on that, but I assume the rationale is to be a bit cautious while the
> project matures. Notably, this is maturing in the Apache way, conduct
> and community.
> 
> That said, I was a bit alarmed to see a suggestion that all users
> should be routed to the dev list from github.
> https://github.com/alibaba/dubbo/issues/1393
> 
> The reason I was concerned was just the huge following dubbo has..
> 2.7k watchers if not ignoring will receive this advice :) Perhaps
> prematurely, I'm worried that redirecting routine users to the dev
> list will be hard to undo once people establish a pattern. I feel we
> could stop that pattern up-front by having a user list and suggesting
> that instead.
> 
> Please bear in mind that I don't have a lot of experience with dubbo
> and people communicating on the "wrong list" isn't necessarily bad. I
> might just be a bit scared due to the scale of the existing community
> here.
> 
> Thoughts welcome, and if none, thanks for letting me express myself :)
> 
> -A

Ask for release process

[Jun Liu]

Hi, mentors

The dubbo core project has fixed some critical bugs and enhancements, and it 
should be released now according to the original plan, with version upgrade to 
2.5.10. But dubbo is in Apache Incubator now, should we start a vote before 
release?

There’s no doubt that from the next version, all processes from requirements 
collection, development to release should be fully discussed and voted by the 
community here before it is actually done. But this version may be a special 
one, most of the works have started before incubator, and also, some users 
really expect for patches in this version. The contents to be released, mainly 
bugfix and enhancements:

https://github.com/alibaba/dubbo/milestone/14 


Should we still raise a vote for the next release(2.5.10)?

Best regards,
Jun Liu

Re: On double dubbo starters

[Mark Thomas]

On 07/03/18 11:41, Ian Luo wrote:
> Hi Mark,
> 
> Pls. check my comments below.

Thanks for the additional information.

Until the code transitions to the ASF (which I hope is fairly soon), and
especially if the community needs a release, then you are able to
publish releases as you have done previously.

Once the code transitions to the ASF, the ASF release policy applies.
Depending on where you start from, it can take a little work to get
everything aligned to the policy but that only needs to be done once.

Mark


> 
> Thanks,
> -Ian.
> 
> 
>> On 7 Mar 2018, at 6:09 PM, Mark Thomas  wrote:
>>
>> On 07/03/18 09:49, Ian Luo wrote:
>>> Hi Adrian,
>>>
>>> First of all, my apology for the confusion. The project under dubbo [1] 
>>> group is the official project we plan to maintain in long term for Spring 
>>> Boot support. I encourage you try it first and share your feedback if 
>>> there’s any. 
>>>
>>> In order to not block Adrian’s work, I suggest to publish it with the 
>>> existing groupId/artifactId since we can always republish with the new 
>>> groupId/artifactId in the next release cycle after the transition finishes.
>>>
>>> To dubbo’s mentors, I am not sure if it is appropriated for my proposal. 
>>> Pls. correct me once you read the message since we plan to release 
>>> spring-boot-starter officially very soon (by the end of this week or the 
>>> early of the next week).
>>>
>>> Thanks,
>>> -Ian. 
>>>
>>> 1.  https://github.com/dubbo/dubbo-spring-boot-project 
>>
>> Hi,
>>
>> I need a little more information before offering an opinion.
>>
>> 1. Who is the "we" that intends to publish the release?
> 
> [iluo]: Here “we” means dubbo development team. 
> 
>>
>> 2. How will the release be named (including Maven co-ordinates)?
> 
> [iluo]: It will be com.alibaba.boot:dubbo-spring-boot-starter at this moment. 
> 
>>
>> 3. Is it intended that this code will become part of Apache Dubbo? If
>> so, what stage is this code at in its transition to the ASF?
> 
> [iluo]: It’s a side project [1] of Apache Dubbo. All projects under dubbo 
> group [2] will be included in this transition, you could check details from 
> JIRA issue DUBBO-3 [3].
> 
> 
> 1. https://github.com/dubbo/dubbo-spring-boot-project
> 2. https://github.com/dubbo
> 3. https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3
> 
>>
>> Thanks,
>>
>> Mark
>>
>>
>>>
>>>
 On 7 Mar 2018, at 5:04 PM, Adrian Cole  wrote:

 Hi, all

 I'm working on spring-cloud-sleuth tracing integration with dubbo.
 We've had users requesting dubbo for a while now for spring boot
 applications.

 https://github.com/spring-cloud/spring-cloud-sleuth/issues/710

 One of the commitments we made was to have dubbo tracing included for
 spring boot 2 applications, leveraging the efforts we made in the
 Zipkin library Brave (which similarly had a backlog of dubbo
 interest).

 The good news is that, I've been able to get this working, which is 
 awesome.

 https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing

 I'm only waiting a couple small patches and we are ready to go! The
 community have been great and the plugin changes quickly in the right
 direction.

 I ran into a glitch as I was told that the plugin I use, the "alibaba"
 variant, is not official. Rather, the "dubbo" one was.

 https://github.com/alibaba/dubbo-spring-boot-starter < I am using this
 and it works
 https://github.com/dubbo/dubbo-spring-boot-project < haven't tried this, 
 yet

 I would like to try the other version, but it seems to be in release
 limbo. For example, it is not published anywhere and there are some
 concerns about publishing it while apache takes its course.

 https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3

 Meanwhile, I actually like the plugin I am using and the person
 maintaining it is good. This is a tough situation to be in where what
 is working is not recommended, and what is recommended I have to build
 or consume snapshot of.

 How should we proceed on this?
 -A
> 
> 

Re: On a user list

[Ian Luo]

> On 8 Mar 2018, at 5:47 PM, Mark Thomas  wrote:
> 
> On 08/03/18 08:09, jun liu wrote:
>> Thanks for your advice to dubbo community, Adrian. 
>> 
>> I agree with the potential problems or even challenges you mentioned. But 
>> when other channels are not forced to be closed, people can still have 
>> discussions on github issues or gitter channels, only remember to bring the 
>> decision making ones here the @dev list.
> 
> My strong recommendation is that all development discussion moves to the
> dev@ list.
> 
> Projects can have a range of user support channels (IRC, Gitter,
> HipChat, mailing list, Stack overflow) as the project feels necessary.
> 
>> Finally, i’d like to see the github issue to be a pure place for tracking 
>> determined requirements, enhancements, bugs or high suspicious bugs,
> 
> That seems sensible to me. Mixing bugs and support issues in the same
> tracker might make it hard for people to work with.

This makes sense to me too. Github issue is a good place for general 
discussion, but we did experience too many irrelevant issues filed on dubbo 
issue. We plan to guide people to use dev mail list for general discussion so 
that we can spend less time in triaging github issues :)

> 
>> while casual discussions or decisions can be raised here. I don’t know  
>> whether a github issue should working that way, but a user/dev list would 
>> definitely helps to reach there, so i would choose to be a good boy and 
>> follow the mentor’s guidance, see what will happen using both mailing list 
>> and github issue at the incubator phase.
>> 
>> I expect to see the amazing features happen: any issues raised with apache 
>> github will be sent to the @dev list automatically after a proper repo 
>> migration.
> 
> Given Dubbo has an issues@ list I'd expect it to go there but the Dubbo
> community can choose how it wants to handle that.
> 
> Mark
> 
> 
>> Also only my own opinion, a new fellow in apache and the github community.
>> 
>> Best regards,
>> Jun Liu
>> 
>> 
>>> On 7 Mar 2018, at 4:46 PM, Adrian Cole  wrote:
>>> 
>>> Hi, folks.
>>> 
>>> I understand that conventionally apache incubator projects don't have
>>> user lists. I suspect someone more familiar can give the whole story
>>> on that, but I assume the rationale is to be a bit cautious while the
>>> project matures. Notably, this is maturing in the Apache way, conduct
>>> and community.
>>> 
>>> That said, I was a bit alarmed to see a suggestion that all users
>>> should be routed to the dev list from github.
>>> https://github.com/alibaba/dubbo/issues/1393
>>> 
>>> The reason I was concerned was just the huge following dubbo has..
>>> 2.7k watchers if not ignoring will receive this advice :) Perhaps
>>> prematurely, I'm worried that redirecting routine users to the dev
>>> list will be hard to undo once people establish a pattern. I feel we
>>> could stop that pattern up-front by having a user list and suggesting
>>> that instead.
>>> 
>>> Please bear in mind that I don't have a lot of experience with dubbo
>>> and people communicating on the "wrong list" isn't necessarily bad. I
>>> might just be a bit scared due to the scale of the existing community
>>> here.
>>> 
>>> Thoughts welcome, and if none, thanks for letting me express myself :)
>>> 
>>> -A
>> 
> 

Re: On double dubbo starters

[Ian Luo]

Sure, then we will not publish anything to maven repository until transition is 
done.

Adrian, I guess this decision shouldn’t stop your further development work 
since you could depend on the snapshot build anyway. We will try our best to 
work with Mark and other apache mentors to boost the transition as fast as 
possible.

Thanks,
-Ian.



> On 8 Mar 2018, at 5:40 PM, Mark Thomas  wrote:
> 
> On 07/03/18 11:41, Ian Luo wrote:
>> Hi Mark,
>> 
>> Pls. check my comments below.
> 
> Thanks for the additional information.
> 
> Until the code transitions to the ASF (which I hope is fairly soon), and
> especially if the community needs a release, then you are able to
> publish releases as you have done previously.
> 
> Once the code transitions to the ASF, the ASF release policy applies.
> Depending on where you start from, it can take a little work to get
> everything aligned to the policy but that only needs to be done once.
> 
> Mark
> 
> 
>> 
>> Thanks,
>> -Ian.
>> 
>> 
>>> On 7 Mar 2018, at 6:09 PM, Mark Thomas  wrote:
>>> 
>>> On 07/03/18 09:49, Ian Luo wrote:
 Hi Adrian,
 
 First of all, my apology for the confusion. The project under dubbo [1] 
 group is the official project we plan to maintain in long term for Spring 
 Boot support. I encourage you try it first and share your feedback if 
 there’s any. 
 
 In order to not block Adrian’s work, I suggest to publish it with the 
 existing groupId/artifactId since we can always republish with the new 
 groupId/artifactId in the next release cycle after the transition finishes.
 
 To dubbo’s mentors, I am not sure if it is appropriated for my proposal. 
 Pls. correct me once you read the message since we plan to release 
 spring-boot-starter officially very soon (by the end of this week or the 
 early of the next week).
 
 Thanks,
 -Ian. 
 
 1.  https://github.com/dubbo/dubbo-spring-boot-project 
>>> 
>>> Hi,
>>> 
>>> I need a little more information before offering an opinion.
>>> 
>>> 1. Who is the "we" that intends to publish the release?
>> 
>> [iluo]: Here “we” means dubbo development team. 
>> 
>>> 
>>> 2. How will the release be named (including Maven co-ordinates)?
>> 
>> [iluo]: It will be com.alibaba.boot:dubbo-spring-boot-starter at this 
>> moment. 
>> 
>>> 
>>> 3. Is it intended that this code will become part of Apache Dubbo? If
>>> so, what stage is this code at in its transition to the ASF?
>> 
>> [iluo]: It’s a side project [1] of Apache Dubbo. All projects under dubbo 
>> group [2] will be included in this transition, you could check details from 
>> JIRA issue DUBBO-3 [3].
>> 
>> 
>> 1. https://github.com/dubbo/dubbo-spring-boot-project
>> 2. https://github.com/dubbo
>> 3. https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3
>> 
>>> 
>>> Thanks,
>>> 
>>> Mark
>>> 
>>> 
 
 
> On 7 Mar 2018, at 5:04 PM, Adrian Cole  wrote:
> 
> Hi, all
> 
> I'm working on spring-cloud-sleuth tracing integration with dubbo.
> We've had users requesting dubbo for a while now for spring boot
> applications.
> 
> https://github.com/spring-cloud/spring-cloud-sleuth/issues/710
> 
> One of the commitments we made was to have dubbo tracing included for
> spring boot 2 applications, leveraging the efforts we made in the
> Zipkin library Brave (which similarly had a backlog of dubbo
> interest).
> 
> The good news is that, I've been able to get this working, which is 
> awesome.
> 
> https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing
> 
> I'm only waiting a couple small patches and we are ready to go! The
> community have been great and the plugin changes quickly in the right
> direction.
> 
> I ran into a glitch as I was told that the plugin I use, the "alibaba"
> variant, is not official. Rather, the "dubbo" one was.
> 
> https://github.com/alibaba/dubbo-spring-boot-starter < I am using this
> and it works
> https://github.com/dubbo/dubbo-spring-boot-project < haven't tried this, 
> yet
> 
> I would like to try the other version, but it seems to be in release
> limbo. For example, it is not published anywhere and there are some
> concerns about publishing it while apache takes its course.
> 
> https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3
> 
> Meanwhile, I actually like the plugin I am using and the person
> maintaining it is good. This is a tough situation to be in where what
> is working is not recommended, and what is recommended I have to build
> or consume snapshot of.
> 
> How should we proceed on this?
> -A
>> 
>> 
> 

Re: On a user list

[Huxing Zhang]

Hi,

On Thu, Mar 8, 2018 at 5:47 PM, Mark Thomas  wrote:
> On 08/03/18 08:09, jun liu wrote:
>> Thanks for your advice to dubbo community, Adrian.
>>
>> I agree with the potential problems or even challenges you mentioned. But 
>> when other channels are not forced to be closed, people can still have 
>> discussions on github issues or gitter channels, only remember to bring the 
>> decision making ones here the @dev list.
>
> My strong recommendation is that all development discussion moves to the
> dev@ list.
>
> Projects can have a range of user support channels (IRC, Gitter,
> HipChat, mailing list, Stack overflow) as the project feels necessary.
>
>> Finally, i’d like to see the github issue to be a pure place for tracking 
>> determined requirements, enhancements, bugs or high suspicious bugs,
>
> That seems sensible to me. Mixing bugs and support issues in the same
> tracker might make it hard for people to work with.
>
>> while casual discussions or decisions can be raised here. I don’t know  
>> whether a github issue should working that way, but a user/dev list would 
>> definitely helps to reach there, so i would choose to be a good boy and 
>> follow the mentor’s guidance, see what will happen using both mailing list 
>> and github issue at the incubator phase.
>>
>> I expect to see the amazing features happen: any issues raised with apache 
>> github will be sent to the @dev list automatically after a proper repo 
>> migration.
>
> Given Dubbo has an issues@ list I'd expect it to go there but the Dubbo
> community can choose how it wants to handle that.

+1 for separating dev@ and issues@

>
> Mark
>
>
>> Also only my own opinion, a new fellow in apache and the github community.
>>
>> Best regards,
>> Jun Liu
>>
>>
>>> On 7 Mar 2018, at 4:46 PM, Adrian Cole  wrote:
>>>
>>> Hi, folks.
>>>
>>> I understand that conventionally apache incubator projects don't have
>>> user lists. I suspect someone more familiar can give the whole story
>>> on that, but I assume the rationale is to be a bit cautious while the
>>> project matures. Notably, this is maturing in the Apache way, conduct
>>> and community.
>>>
>>> That said, I was a bit alarmed to see a suggestion that all users
>>> should be routed to the dev list from github.
>>> https://github.com/alibaba/dubbo/issues/1393
>>>
>>> The reason I was concerned was just the huge following dubbo has..
>>> 2.7k watchers if not ignoring will receive this advice :) Perhaps
>>> prematurely, I'm worried that redirecting routine users to the dev
>>> list will be hard to undo once people establish a pattern. I feel we
>>> could stop that pattern up-front by having a user list and suggesting
>>> that instead.
>>>
>>> Please bear in mind that I don't have a lot of experience with dubbo
>>> and people communicating on the "wrong list" isn't necessarily bad. I
>>> might just be a bit scared due to the scale of the existing community
>>> here.
>>>
>>> Thoughts welcome, and if none, thanks for letting me express myself :)
>>>
>>> -A
>>
>

-- 
Best Regards！
Huxing

Re: Re: On double dubbo starters

[Kimm King]

I think mentor means in another thread:
 we could publish something to maven central repository as usual until 
transition is done.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
From: Ian Luo
Date: 2018-03-08 21:40
To: dev
Subject: Re: On double dubbo starters
 
> On 8 Mar 2018, at 9:22 PM, Ian Luo  wrote:
> 
> Sure, then we will not publish anything to maven repository until transition 
> is done.
> 
 
Oops, I think I misunderstood. Mark, could you pls. confirm we could still 
publish release from the “old” repositories during the transition?
 
Thanks,
-Ian.
 
 
> Adrian, I guess this decision shouldn’t stop your further development work 
> since you could depend on the snapshot build anyway. We will try our best to 
> work with Mark and other apache mentors to boost the transition as fast as 
> possible.
> 
> Thanks,
> -Ian.
> 
> 
> 
>> On 8 Mar 2018, at 5:40 PM, Mark Thomas  wrote:
>> 
>> On 07/03/18 11:41, Ian Luo wrote:
>>> Hi Mark,
>>> 
>>> Pls. check my comments below.
>> 
>> Thanks for the additional information.
>> 
>> Until the code transitions to the ASF (which I hope is fairly soon), and
>> especially if the community needs a release, then you are able to
>> publish releases as you have done previously.
>> 
>> Once the code transitions to the ASF, the ASF release policy applies.
>> Depending on where you start from, it can take a little work to get
>> everything aligned to the policy but that only needs to be done once.
>> 
>> Mark
>> 
>> 
>>> 
>>> Thanks,
>>> -Ian.
>>> 
>>> 
 On 7 Mar 2018, at 6:09 PM, Mark Thomas  wrote:
 
 On 07/03/18 09:49, Ian Luo wrote:
> Hi Adrian,
> 
> First of all, my apology for the confusion. The project under dubbo [1] 
> group is the official project we plan to maintain in long term for Spring 
> Boot support. I encourage you try it first and share your feedback if 
> there’s any. 
> 
> In order to not block Adrian’s work, I suggest to publish it with the 
> existing groupId/artifactId since we can always republish with the new 
> groupId/artifactId in the next release cycle after the transition 
> finishes.
> 
> To dubbo’s mentors, I am not sure if it is appropriated for my proposal. 
> Pls. correct me once you read the message since we plan to release 
> spring-boot-starter officially very soon (by the end of this week or the 
> early of the next week).
> 
> Thanks,
> -Ian. 
> 
> 1.  https://github.com/dubbo/dubbo-spring-boot-project 
 
 Hi,
 
 I need a little more information before offering an opinion.
 
 1. Who is the "we" that intends to publish the release?
>>> 
>>> [iluo]: Here “we” means dubbo development team. 
>>> 
 
 2. How will the release be named (including Maven co-ordinates)?
>>> 
>>> [iluo]: It will be com.alibaba.boot:dubbo-spring-boot-starter at this 
>>> moment. 
>>> 
 
 3. Is it intended that this code will become part of Apache Dubbo? If
 so, what stage is this code at in its transition to the ASF?
>>> 
>>> [iluo]: It’s a side project [1] of Apache Dubbo. All projects under dubbo 
>>> group [2] will be included in this transition, you could check details from 
>>> JIRA issue DUBBO-3 [3].
>>> 
>>> 
>>> 1. https://github.com/dubbo/dubbo-spring-boot-project
>>> 2. https://github.com/dubbo
>>> 3. https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3
>>> 
 
 Thanks,
 
 Mark
 
 
> 
> 
>> On 7 Mar 2018, at 5:04 PM, Adrian Cole  wrote:
>> 
>> Hi, all
>> 
>> I'm working on spring-cloud-sleuth tracing integration with dubbo.
>> We've had users requesting dubbo for a while now for spring boot
>> applications.
>> 
>> https://github.com/spring-cloud/spring-cloud-sleuth/issues/710
>> 
>> One of the commitments we made was to have dubbo tracing included for
>> spring boot 2 applications, leveraging the efforts we made in the
>> Zipkin library Brave (which similarly had a backlog of dubbo
>> interest).
>> 
>> The good news is that, I've been able to get this working, which is 
>> awesome.
>> 
>> https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing
>> 
>> I'm only waiting a couple small patches and we are ready to go! The
>> community have been great and the plugin changes quickly in the right
>> direction.
>> 
>> I ran into a glitch as I was told that the plugin I use, the "alibaba"
>> variant, is not official. Rather, the "dubbo" one was.
>> 
>> https://github.com/alibaba/dubbo-spring-boot-starter < I am using this
>> and it works
>> https://github.com/dubbo/dubbo-spring-boot-project < haven't tried this, 
>> yet
>> 
>> I would like to try the other version, but it seems to be in release
>> limbo. For example, it is 

Re: Write access to Dubbo's incubator status page

[John D. Ament]

Are you already a committer on incubator?

On Thu, Mar 8, 2018, 1:42 AM Huxing Zhang  wrote:

> Hi mentors,
>
> Please grant me the write access to Dubbo's incubator status page[1]
> if possible. I would like to update some item status.
>
> Reading the documentation points me that the status is maintained in
> svn[2].
>
> Thanks!
>
> [1] https://incubator.apache.org/projects/dubbo.html
> [2]
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/
>
> --
> Best Regards！
> Huxing
>

Re: On double dubbo starters

[kext gmail]

Hi Lan,

I think Mark means you could publish dubbo starter(also same for dubbo in 
another discussion) with ‘old’ group and ‘old’ name before transition to the 
ASF.

Best Regards,
Tang Ke

> 在 2018年3月8日，22:25，Kimm King  写道：
> 
> I think mentor means in another thread:
> we could publish something to maven central repository as usual until 
> transition is done.
> 
> 
> 
> KimmKing(kimmk...@163.com)
> == In me the tiger sniffs the rose. ==
> 
> 
> From: Ian Luo
> Date: 2018-03-08 21:40
> To: dev
> Subject: Re: On double dubbo starters
> 
>> On 8 Mar 2018, at 9:22 PM, Ian Luo  wrote:
>> 
>> Sure, then we will not publish anything to maven repository until transition 
>> is done.
>> 
> 
> Oops, I think I misunderstood. Mark, could you pls. confirm we could still 
> publish release from the “old” repositories during the transition?
> 
> Thanks,
> -Ian.
> 
> 
>> Adrian, I guess this decision shouldn’t stop your further development work 
>> since you could depend on the snapshot build anyway. We will try our best to 
>> work with Mark and other apache mentors to boost the transition as fast as 
>> possible.
>> 
>> Thanks,
>> -Ian.
>> 
>> 
>> 
>>> On 8 Mar 2018, at 5:40 PM, Mark Thomas  wrote:
>>> 
>>> On 07/03/18 11:41, Ian Luo wrote:
 Hi Mark,
 
 Pls. check my comments below.
>>> 
>>> Thanks for the additional information.
>>> 
>>> Until the code transitions to the ASF (which I hope is fairly soon), and
>>> especially if the community needs a release, then you are able to
>>> publish releases as you have done previously.
>>> 
>>> Once the code transitions to the ASF, the ASF release policy applies.
>>> Depending on where you start from, it can take a little work to get
>>> everything aligned to the policy but that only needs to be done once.
>>> 
>>> Mark
>>> 
>>> 
 
 Thanks,
 -Ian.
 
 
> On 7 Mar 2018, at 6:09 PM, Mark Thomas  wrote:
> 
> On 07/03/18 09:49, Ian Luo wrote:
>> Hi Adrian,
>> 
>> First of all, my apology for the confusion. The project under dubbo [1] 
>> group is the official project we plan to maintain in long term for 
>> Spring Boot support. I encourage you try it first and share your 
>> feedback if there’s any. 
>> 
>> In order to not block Adrian’s work, I suggest to publish it with the 
>> existing groupId/artifactId since we can always republish with the new 
>> groupId/artifactId in the next release cycle after the transition 
>> finishes.
>> 
>> To dubbo’s mentors, I am not sure if it is appropriated for my proposal. 
>> Pls. correct me once you read the message since we plan to release 
>> spring-boot-starter officially very soon (by the end of this week or the 
>> early of the next week).
>> 
>> Thanks,
>> -Ian. 
>> 
>> 1.  https://github.com/dubbo/dubbo-spring-boot-project 
> 
> Hi,
> 
> I need a little more information before offering an opinion.
> 
> 1. Who is the "we" that intends to publish the release?
 
 [iluo]: Here “we” means dubbo development team. 
 
> 
> 2. How will the release be named (including Maven co-ordinates)?
 
 [iluo]: It will be com.alibaba.boot:dubbo-spring-boot-starter at this 
 moment. 
 
> 
> 3. Is it intended that this code will become part of Apache Dubbo? If
> so, what stage is this code at in its transition to the ASF?
 
 [iluo]: It’s a side project [1] of Apache Dubbo. All projects under dubbo 
 group [2] will be included in this transition, you could check details 
 from JIRA issue DUBBO-3 [3].
 
 
 1. https://github.com/dubbo/dubbo-spring-boot-project
 2. https://github.com/dubbo
 3. https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3
 
> 
> Thanks,
> 
> Mark
> 
> 
>> 
>> 
>>> On 7 Mar 2018, at 5:04 PM, Adrian Cole  wrote:
>>> 
>>> Hi, all
>>> 
>>> I'm working on spring-cloud-sleuth tracing integration with dubbo.
>>> We've had users requesting dubbo for a while now for spring boot
>>> applications.
>>> 
>>> https://github.com/spring-cloud/spring-cloud-sleuth/issues/710
>>> 
>>> One of the commitments we made was to have dubbo tracing included for
>>> spring boot 2 applications, leveraging the efforts we made in the
>>> Zipkin library Brave (which similarly had a backlog of dubbo
>>> interest).
>>> 
>>> The good news is that, I've been able to get this working, which is 
>>> awesome.
>>> 
>>> https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing
>>> 
>>> I'm only waiting a couple small patches and we are ready to go! The
>>> community have been great and the plugin changes quickly in the right
>>> direction.
>>> 
>>> I ran into a glitch as I was told that 

Re: Write access to Dubbo's incubator status page

[Huxing Zhang]

Hi,

On Fri, Mar 9, 2018 at 11:43 AM, John D. Ament  wrote:
> On Thu, Mar 8, 2018 at 10:41 PM Huxing Zhang  wrote:
>
>> Hi,
>>
>> On Fri, Mar 9, 2018 at 11:23 AM, John D. Ament 
>> wrote:
>> > On Thu, Mar 8, 2018 at 9:23 PM Huxing Zhang  wrote:
>> >
>> >> Hi,
>> >>
>> >> On Fri, Mar 9, 2018 at 12:46 AM, John D. Ament 
>> >> wrote:
>> >> > Are you already a committer on incubator?
>> >>
>> >> No.
>> >>
>> >> When I am reading
>> >> https://incubator.apache.org/guides/ppmc.html#project_status_page, I
>> >> thought it was the PPMC's responsibility to keep the podling status
>> >> page updated.
>> >>
>> >> Either my understanding is wrong or the documentation need to clarify
>> it?
>> >>
>> >
>> > No, you're correct.  I just checked, you are a committer on incubator.
>>
>> I was not aware of it. :)
>>
>> > Someone else must have done it, not sure.
>>
>> So that means PPMC automatically become committer of incubator?
>>
>
> Any committer on a podling is also a committer on the incubator project.
> It grants them access to update our website, and maintain our scripts.

Make sense!

>
>
>>
>> >
>> > I just applied a minor fix to
>> > https://incubator.apache.org/guides/website.html
>>
>> It is not update instantly but I check your commit and figure it out.
>>
>> > please review and let me
>> > know if you have everything to update the page.  I do want to make a
>> change
>> > to the roster section, but can do that later (no reason to update roster
>> > yet).
>>
>> Checking out svn using https:// makes me able to commit. Thanks!
>>
>
> Yes, glad.  I've seen this issue a few times and was trying to figure out
> why it kept happening.  When I saw it on that page figured it out finally.
>
> BTW, you updated the roster.  I'm going to try to replace that section with
> a link to home.a.o and whimsy.a.o.

+1. I think they are duplicate.

>
>
>>
>> >
>> > John
>> >
>> >
>> >>
>> >> >
>> >> > On Thu, Mar 8, 2018, 1:42 AM Huxing Zhang  wrote:
>> >> >
>> >> >> Hi mentors,
>> >> >>
>> >> >> Please grant me the write access to Dubbo's incubator status page[1]
>> >> >> if possible. I would like to update some item status.
>> >> >>
>> >> >> Reading the documentation points me that the status is maintained in
>> >> >> svn[2].
>> >> >>
>> >> >> Thanks!
>> >> >>
>> >> >> [1] https://incubator.apache.org/projects/dubbo.html
>> >> >> [2]
>> >> >>
>> >>
>> http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/
>> >> >>
>> >> >> --
>> >> >> Best Regards！
>> >> >> Huxing
>> >> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Best Regards！
>> >> Huxing
>> >>
>>
>> --
>> Best Regards！
>> Huxing
>>



-- 
Best Regards！
Huxing

Re: On a user list

[Jun Liu]

One more question. If we create an issue in github (or JIRA, not decided yet) 
after having a discussion here the @dev list. How to ensure that the 
discussions on both sides are synchronized after the creation of github issue, 
because it seem reasonable to track on either side. For me it would happen on 
github issue then.


> On 8 Mar 2018, at 5:47 PM, Mark Thomas  wrote:
> 
> On 08/03/18 08:09, jun liu wrote:
>> Thanks for your advice to dubbo community, Adrian. 
>> 
>> I agree with the potential problems or even challenges you mentioned. But 
>> when other channels are not forced to be closed, people can still have 
>> discussions on github issues or gitter channels, only remember to bring the 
>> decision making ones here the @dev list.
> 
> My strong recommendation is that all development discussion moves to the
> dev@ list.
> 
> Projects can have a range of user support channels (IRC, Gitter,
> HipChat, mailing list, Stack overflow) as the project feels necessary.
> 
>> Finally, i’d like to see the github issue to be a pure place for tracking 
>> determined requirements, enhancements, bugs or high suspicious bugs,
> 
> That seems sensible to me. Mixing bugs and support issues in the same
> tracker might make it hard for people to work with.
> 
>> while casual discussions or decisions can be raised here. I don’t know  
>> whether a github issue should working that way, but a user/dev list would 
>> definitely helps to reach there, so i would choose to be a good boy and 
>> follow the mentor’s guidance, see what will happen using both mailing list 
>> and github issue at the incubator phase.
>> 
>> I expect to see the amazing features happen: any issues raised with apache 
>> github will be sent to the @dev list automatically after a proper repo 
>> migration.
> 
> Given Dubbo has an issues@ list I'd expect it to go there but the Dubbo
> community can choose how it wants to handle that.
> 
> Mark
> 
> 
>> Also only my own opinion, a new fellow in apache and the github community.
>> 
>> Best regards,
>> Jun Liu
>> 
>> 
>>> On 7 Mar 2018, at 4:46 PM, Adrian Cole  wrote:
>>> 
>>> Hi, folks.
>>> 
>>> I understand that conventionally apache incubator projects don't have
>>> user lists. I suspect someone more familiar can give the whole story
>>> on that, but I assume the rationale is to be a bit cautious while the
>>> project matures. Notably, this is maturing in the Apache way, conduct
>>> and community.
>>> 
>>> That said, I was a bit alarmed to see a suggestion that all users
>>> should be routed to the dev list from github.
>>> https://github.com/alibaba/dubbo/issues/1393
>>> 
>>> The reason I was concerned was just the huge following dubbo has..
>>> 2.7k watchers if not ignoring will receive this advice :) Perhaps
>>> prematurely, I'm worried that redirecting routine users to the dev
>>> list will be hard to undo once people establish a pattern. I feel we
>>> could stop that pattern up-front by having a user list and suggesting
>>> that instead.
>>> 
>>> Please bear in mind that I don't have a lot of experience with dubbo
>>> and people communicating on the "wrong list" isn't necessarily bad. I
>>> might just be a bit scared due to the scale of the existing community
>>> here.
>>> 
>>> Thoughts welcome, and if none, thanks for letting me express myself :)
>>> 
>>> -A
>> 
> 

Support unit router feature, may be a nice feature

[zonghai shang]

Support unit router feature for dubbo， new feature pr： 
https://github.com/alibaba/dubbo/pull/1438

What problems can this feature solve?

case 1:
If we have two instance of services or more, we call it serviceA(192.168.0.1), 
serviceA(192.168.0.2).

We want to invoke serviceA (192.168.0.2) first, if serviceA (192.168.0.2) is 
not available then invoke serviceA (192.168.0.1) automatically.


case 2:

If we have many relative services, We call it serviceA(192.168.0.1), 
serviceA(192.168.0.2), serviceB(192.168.1.1), serviceB(192.168.1.2), 
serviceC(192.168.3.1), serviceC(192.168.3.2)

dependencies of service:
serviceA -> serviceB -> serviceC
We can flexibly build call paths and automatically downgrade calls.

Re: Write access to Dubbo's incubator status page

[Huxing Zhang]

Hi,

On Fri, Mar 9, 2018 at 11:23 AM, John D. Ament  wrote:
> On Thu, Mar 8, 2018 at 9:23 PM Huxing Zhang  wrote:
>
>> Hi,
>>
>> On Fri, Mar 9, 2018 at 12:46 AM, John D. Ament 
>> wrote:
>> > Are you already a committer on incubator?
>>
>> No.
>>
>> When I am reading
>> https://incubator.apache.org/guides/ppmc.html#project_status_page, I
>> thought it was the PPMC's responsibility to keep the podling status
>> page updated.
>>
>> Either my understanding is wrong or the documentation need to clarify it?
>>
>
> No, you're correct.  I just checked, you are a committer on incubator.

I was not aware of it. :)

> Someone else must have done it, not sure.

So that means PPMC automatically become committer of incubator?

>
> I just applied a minor fix to
> https://incubator.apache.org/guides/website.html

It is not update instantly but I check your commit and figure it out.

> please review and let me
> know if you have everything to update the page.  I do want to make a change
> to the roster section, but can do that later (no reason to update roster
> yet).

Checking out svn using https:// makes me able to commit. Thanks!

>
> John
>
>
>>
>> >
>> > On Thu, Mar 8, 2018, 1:42 AM Huxing Zhang  wrote:
>> >
>> >> Hi mentors,
>> >>
>> >> Please grant me the write access to Dubbo's incubator status page[1]
>> >> if possible. I would like to update some item status.
>> >>
>> >> Reading the documentation points me that the status is maintained in
>> >> svn[2].
>> >>
>> >> Thanks!
>> >>
>> >> [1] https://incubator.apache.org/projects/dubbo.html
>> >> [2]
>> >>
>> http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/
>> >>
>> >> --
>> >> Best Regards！
>> >> Huxing
>> >>
>>
>>
>>
>> --
>> Best Regards！
>> Huxing
>>

-- 
Best Regards！
Huxing

Re: Consumer side Validation SPI is wrongly activated while setting validation=true for provider

[Jun Liu]

No more suggestions til now, let me track this with a github issue. Further 
questions is welcomed in here and github issue. 

https://github.com/alibaba/dubbo/issues/1386

> On 8 Mar 2018, at 4:23 PM, jun liu  wrote:
> 
> I prefer to change the current behavior, consumer side should not be affected 
> in this case, if someone care about performance, they can add validation on 
> consumer side explicitly.
> 
> Other opinions? 
> 
>> On 7 Mar 2018, at 3:47 PM, Sunshow  wrote:
>> 
>> Yes, that's my problem.
>> 
>> from the document, consumer can enable or disable validation itself.
>> 
>> On Wed, Mar 7, 2018 at 3:41 PM jun liu  wrote:
>> 
>>> Hi Sunshow, Ian
>>> 
>>> I think i have reproduced this problem, the key point is: When we switch
>>> param validation on on provider side, all consumer projects need to add
>>> necessary dependencies explicitly (param validation was force opened on
>>> consumer side). This means provider and consumer are bind together. Is this
>>> exactly your problem, sunshow?
>>> 
>>> Should we change this behavior?
>>> 
> I think it is reasonable to check validation conditions on consumer side
> before params passed to provider side as this can be more efficient. If
>>> we
> keep it this way, we will meet the problem in your case: all consumers
>>> have
> to be aware of provider side validation configurations, for example when
> provider opened validation check, consumer side have to add necessary
> dependencies.
>>> 
>>> 
>>> Best regards,
>>> Jun Liu
>>> 
 On 7 Mar 2018, at 2:44 PM, Ian Luo  wrote:
 
 Hi Sunshow,
 
 Could you pls. attach a test case to reproduce the issue you described
 here? I'd like to further investigate once I receive the reproducer.
 
 Thanks,
 -Ian.
 
 
 On Wed, Mar 7, 2018 at 2:14 PM, Sunshow  wrote:
 
> ATT.
> 
> this case consumer leads to throw
> 
> Caused by: java.lang.NoClassDefFoundError: javax/validation/Validation
> 
> even while calling no validation method, unless add all validation
> dependencies to consumer,
> 
> that's not awesome, consumer side check should be activated by consumer
> self.
> 
> one more question about ValidationFilter:
> 
> why the condition check is isNotEmpty:
> ConfigUtils.isNotEmpty(invoker.getUrl().getMethodParameter(invocation.
> getMethodName(),
> Constants.VALIDATION_KEY))
> 
> and previous version check true or false:
> if (invoker.getUrl().getMethodParameter(invocation.getMethodName(),
> Constants.VALIDATION_KEY, false))
> 
> 
> Below is the reply from @ken.lj:
> 
> 
> I think it is reasonable to check validation conditions on consumer side
> before params passed to provider side as this can be more efficient. If
>>> we
> keep it this way, we will meet the problem in your case: all consumers
>>> have
> to be aware of provider side validation configurations, for example when
> provider opened validation check, consumer side have to add necessary
> dependencies.
> 
> Please, send this problem to dev@dubbo.apache.org, and subscribe to
>>> this
> email address . We can
> decide
> which way to go after a full discussion.
> 
>>> 
>>> 
> 

Re: Ask for release process

[Jun Liu]

Thanks. We will release as usual til the transition to Apache is done.

> On 8 Mar 2018, at 5:42 PM, Mark Thomas  wrote:
> 
> On 08/03/18 09:05, Jun Liu wrote:
>> Hi, mentors
>> 
>> The dubbo core project has fixed some critical bugs and enhancements, and it 
>> should be released now according to the original plan, with version upgrade 
>> to 2.5.10. But dubbo is in Apache Incubator now, should we start a vote 
>> before release?
>> 
>> There’s no doubt that from the next version, all processes from requirements 
>> collection, development to release should be fully discussed and voted by 
>> the community here before it is actually done. But this version may be a 
>> special one, most of the works have started before incubator, and also, some 
>> users really expect for patches in this version. The contents to be 
>> released, mainly bugfix and enhancements:
>> 
>> https://github.com/alibaba/dubbo/milestone/14 
>> 
>> 
>> Should we still raise a vote for the next release(2.5.10)?
> 
> I think you are fine to make a release from the 'old' repository, using
> the 'old' name and the 'old' process. i.e. there is nothing mentioning
> 'Apache' in the name, Maven co-ordinates etc.
> 
> Once the code transitions to an ASF repository, that is when the release
> policy applies.
> 
> Mark

Re: Write access to Dubbo's incubator status page

[Huxing Zhang]

Hi,

On Fri, Mar 9, 2018 at 12:46 AM, John D. Ament  wrote:
> Are you already a committer on incubator?

No.

When I am reading
https://incubator.apache.org/guides/ppmc.html#project_status_page, I
thought it was the PPMC's responsibility to keep the podling status
page updated.

Either my understanding is wrong or the documentation need to clarify it?

>
> On Thu, Mar 8, 2018, 1:42 AM Huxing Zhang  wrote:
>
>> Hi mentors,
>>
>> Please grant me the write access to Dubbo's incubator status page[1]
>> if possible. I would like to update some item status.
>>
>> Reading the documentation points me that the status is maintained in
>> svn[2].
>>
>> Thanks!
>>
>> [1] https://incubator.apache.org/projects/dubbo.html
>> [2]
>> http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/
>>
>> --
>> Best Regards！
>> Huxing
>>



-- 
Best Regards！
Huxing

Dubbo dev-list Mail Page

[Kimm King]

hi, everyone,
As Mark's suggestion:,
Mail page you may be better off using the one hosted at Apache rather than 
markmail.
We can view all mail posts here: 
https://lists.apache.org/list.html?dev@dubbo.apache.org



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

Re: Write access to Dubbo's incubator status page

[John D. Ament]

On Thu, Mar 8, 2018 at 10:41 PM Huxing Zhang  wrote:

> Hi,
>
> On Fri, Mar 9, 2018 at 11:23 AM, John D. Ament 
> wrote:
> > On Thu, Mar 8, 2018 at 9:23 PM Huxing Zhang  wrote:
> >
> >> Hi,
> >>
> >> On Fri, Mar 9, 2018 at 12:46 AM, John D. Ament 
> >> wrote:
> >> > Are you already a committer on incubator?
> >>
> >> No.
> >>
> >> When I am reading
> >> https://incubator.apache.org/guides/ppmc.html#project_status_page, I
> >> thought it was the PPMC's responsibility to keep the podling status
> >> page updated.
> >>
> >> Either my understanding is wrong or the documentation need to clarify
> it?
> >>
> >
> > No, you're correct.  I just checked, you are a committer on incubator.
>
> I was not aware of it. :)
>
> > Someone else must have done it, not sure.
>
> So that means PPMC automatically become committer of incubator?
>

Any committer on a podling is also a committer on the incubator project.
It grants them access to update our website, and maintain our scripts.


>
> >
> > I just applied a minor fix to
> > https://incubator.apache.org/guides/website.html
>
> It is not update instantly but I check your commit and figure it out.
>
> > please review and let me
> > know if you have everything to update the page.  I do want to make a
> change
> > to the roster section, but can do that later (no reason to update roster
> > yet).
>
> Checking out svn using https:// makes me able to commit. Thanks!
>

Yes, glad.  I've seen this issue a few times and was trying to figure out
why it kept happening.  When I saw it on that page figured it out finally.

BTW, you updated the roster.  I'm going to try to replace that section with
a link to home.a.o and whimsy.a.o.


>
> >
> > John
> >
> >
> >>
> >> >
> >> > On Thu, Mar 8, 2018, 1:42 AM Huxing Zhang  wrote:
> >> >
> >> >> Hi mentors,
> >> >>
> >> >> Please grant me the write access to Dubbo's incubator status page[1]
> >> >> if possible. I would like to update some item status.
> >> >>
> >> >> Reading the documentation points me that the status is maintained in
> >> >> svn[2].
> >> >>
> >> >> Thanks!
> >> >>
> >> >> [1] https://incubator.apache.org/projects/dubbo.html
> >> >> [2]
> >> >>
> >>
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/
> >> >>
> >> >> --
> >> >> Best Regards！
> >> >> Huxing
> >> >>
> >>
> >>
> >>
> >> --
> >> Best Regards！
> >> Huxing
> >>
>
> --
> Best Regards！
> Huxing
>