Hi, On Thu, Mar 8, 2018 at 5:47 PM, Mark Thomas <[email protected]> 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 <[email protected]> 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
