Hi. Agree with KimmKing.
Adding apache/pixiu should go incubate it first, not simply add it. After all if it can pass directly, then dubbo-a becom apache/a directly, then dubbo-b becom apache/b directly, then dubbo-a becom apache/a directly... In the end we might receive 114514 amazing repos from dubbo. That will be a total disaster. haohongfan <haohongfan2...@126.com> 于2021年10月18日周一 下午2:40写道： > +1 agree > > > > > > At 2021-10-18 14:21:04, "stocks alex" <alexsto...@apache.org> 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 >
