> * dubbo-configcenter-archaius an empty project, since Netflix no > longer maintains it, I propose to drop this project
+1 to drop it, It’s an experimental implementation at the startup when introducing config-center concept into Dubbo, mainly to bootstrap the Zookeeper support. Some of its advantages are it's totally extensible with the underlying configuration storage types and has well-refined APIs. Now we already have our built-in zookeeper implementation, I think it’s unnecessary to maintain this project anymore especially considering it’s not maintained by Netflix anymore. Jun > On Jan 10, 2019, at 5:26 PM, Huxing Zhang <[email protected]> wrote: > > Hi All, > > I think we need to decide the next steps of projects in Dubbo[1] > group. I'd divided them by 4 categories: > > ### Dubbo RPC extension modules > > I think they are can be merge back into the core repository for the > purpose of easier release management and concentrate the > users/contributors. > > They are: > * dubbo-rpc-native-thrift maintained by Xin Wang, our PPMC > * dubbo-registry-etcd maintained by Zonghai Shang, our PPMC > * dubbo-async-processor maintained by Jun Liu, our PPMC > * dubbo-registry-nacos maintained by Mercy Ma, our PPMC > * dubbo-configcenter-archaius an empty project, since Netflix no > longer maintains it, I propose to drop this project > * dubbo-serialization-gson maintained by Ian Luo, our PPMC > * dubbo-serialization-fst empty project, already merged into core > repo, ok to drop it > * dubbo-serialization-native-hessian, maintained by Ian Luo, our PPMC > * dubbo-rpc-jms, maintained by Kimm King, our committer > * dubbo-rpc-xmlrpc, maintained by Kimm King, our committer > > ### Multiple-language SDK > > Most of the projects are maintained by external developers, I am not > quite sure how we can deal with them, maybe we need to discussed with > them, about whether we want to donate code to ASF. > > They are: > * dubbo-php-framework php client + server This project has already > signed SGA to donate to ASF > * dubbo2.js Node.js client > * dubbo-client-py python client > * egg-dubbo-rpc dubbo rpc plugin for egg Node.js framework > * dubbo-remoting-js dubbo protocol implementation of egg Node.js framwork > > There are also 2 Node.js implementations, are they going to be merged > or not? That's another question. > > ### Integration > > * dubbo-sentinel-support provides sentinel support, maintained by > * dubbo-kubernetes provides kubernates support, still work in > progress, maintained by our committer Jeff Lv > * dubbo-integration empty project, not quite sure what it does, we can > leave it there > * dubbo-spring-cloud-project empty project, it can be dropped > > ### Tools & Others > > * initializr forked from Spring initializr, should be no IP issues, I > think we can leave it there > * dubbo-spring-boot-demo This can be merge into dubbo-samples > * dubbo-benchmark benchmark project, maintained by Ian Luo, our PPMC, > I think we can move to Apache > * dubbo-logo logo files, suggest to move to ASF > * jmeter-plugins-dubbo, should be no IP issues, I think we can leave it there > * hessian-lite, a modified version of hessian separated from the core > repository, suggest to move to ASF as a standalone project > > How do you folks think? > > [1] https://github.com/dubbo > > -- > Best Regards！ > Huxing
