> > Glad to see the actions are ongoing, and many projects are done. Could the > Dubbo community consider to make sure the Dubbo GitHub[1] org to be > processed well? Such as, > 1. Stop using the Dubbo logo. > 2. Statement clear, this org will be renamed or some other way(community > prefers) to avoid the branding concern. > I think the clear status of Dubbo ecosystem is very important.
As Justin mentioned above, the translation is under going. We cannot do it for all because we need to examine the license and make sure ICLA for each projects are signed, but, eventually we hope to move everything into Apache group except for the repo [1] which serves redirection dubbo.io to dubbo.apache.org. Now I have changed the title and the profile for dubbo group like this: Title: Apache Dubbo Ecosystem Profile: Dubbo is now incubated in ASF: https://github.com/apache/incubator-dubbo, this group is for hosting dubbo eco-system temporaryly before the transition finishes. I hope this can answer your concerns. Regards, -Ian. 1. https://github.com/dubbo/dubbo.github.io On Wed, Apr 24, 2019 at 8:13 AM Sheng Wu <wu.sheng.841...@gmail.com> wrote: > > Part of the repo was used to host dubbo.io which now redirects to > http://dubbo.apache.org/en-us/. Re the other projects it may be that a > little clean up still needs to be done but action is being taken. The > existence of this extra repo has been discussed a number of times in the > project and projects are being moved off it. e.g. [1][2] and more recently > [3][4]. > > This document probably best describes what is happening [5]. > > Glad to see the actions are ongoing, and many projects are done. Could the > Dubbo community consider to make sure the Dubbo GitHub[1] org to be > processed well? Such as, > 1. Stop using the Dubbo logo. > 2. Statement clear, this org will be renamed or some other way(community > prefers) to avoid the branding concern. > I think the clear status of Dubbo ecosystem is very important. > > Dubbo has a very wide community and connected many projects/developers, so > please consider to make sure the branding is clear before graduation. > > > This issue is is being addressed (vote has been canceled, the dependancy > removed, documentation updated and there’s a discussion started on legal > discuss on if it might in future be allowed). I also note it was the PPMC > who first noticed this issue not the IPMC. > > This is not a blocker, this comes from the same reason I asked about > branding. > Dubbo is too widely used as they said in many media(s), many > watcher(s)/star(s) in GitHub. > I am hoping it will be a good example of ASF project, and the PMC is ready > to find the license issue in first place. > > Thanks. > > [1] https://github.com/dubbo > > Sheng Wu 吴晟 > > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > Justin Mclean <jus...@classsoftware.com> 于2019年4月24日周三 上午7:19写道： > > > Hi, > > > > > 1. If graduation happens, Dubbo should be Apache branding, then why > > > dubbo GitHub org[1] is still used. Especially the exact name and logo. > > > > Part of the repo was used to host dubbo.io which now redirects to > > http://dubbo.apache.org/en-us/. Re the other projects it may be that a > > little clean up still needs to be done but action is being taken. The > > existence of this extra repo has been discussed a number of times in the > > project and projects are being moved off it. e.g. [1][2] and more > recently > > [3][4]. > > > > This document probably best describes what is happening [5]. > > > > > 2. Most star project[2] in dubbo org is using Apache mail list[3]. But > > > groupId[4] says it belongs Alibaba > > > > I would guess this is just an oversight, but if someone from the PPMC can > > comment on this that would be good. > > > > > 3. Dubbo-go[5] project exists, and also use the Dubbo name. > > > > See [5]. > > > > > Also, in the last Dubbo vote `[VOTE]: Release Apache Dubbo > > > Admin(Incubating) 0.2.0 [RC3]`. License issue hasn't been addressed > > inside > > > the PPMC(dev vote), I know LGPL is uncertain thing(maybe), but at this > > > moment, it should not be included. > > > > This issue is is being addressed (vote has been canceled, the dependancy > > removed, documentation updated and there’s a discussion started on legal > > discuss on if it might in future be allowed). I also note it was the PPMC > > who first noticed this issue not the IPMC. > > > > Thanks, > > Justin > > > > 1. > > > https://lists.apache.org/thread.html/aae8787244959aeaab0e3e83dd79036482df9e8006f0fb83e5173d87@%3Cdev.dubbo.apache.org%3E > > 2. > > > https://lists.apache.org/thread.html/f272b30bd9bb09dc605088504f8ed643bd9a3b2434c9e7ef59b6b7fe@%3Cdev.dubbo.apache.org%3E > > 3. > > > https://lists.apache.org/thread.html/1987617abc1d4989476beda9dfc9a79eb0e4750050317803b113288c@%3Cdev.dubbo.apache.org%3E > > 4. > > > https://lists.apache.org/thread.html/ec7995d2c42bafcb8f2778b1d0c6ee94bcbbc2dae11d23c41cad82d6@%3Cdev.dubbo.apache.org%3E > > 5. > > > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
