Dubbo core only keeps the api and recommended extension. Keep the core minimum. On Thu, Aug 16, 2018 at 4:00 PM Jerrick Zhu <jerr...@apache.org> 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 >
