We expect to agree on the following points:
1. Can we put the project at https://github.com/apache/<https://github.com/apache/?> ？ for example: a. alibaba/dubbo move to https://github.com/apache/incubator-dubbo b. dubbo/dubbo.github.io move to https://github.com/apache/incubator-dubbo-website c. dubbo/dubbo-spring-boot-project move to https://github.com/apache/incubator-dubbo-spring-boot. d. dubbo/dubbo-rpc-jsonrpc move to https://github.com/apache/incubator-dubbo-jsonrpc. e. dubbo/dubbo-feature-test move to https://github.com/apache/incubator-dubbo-feature-test . 2. If the IP clearance( and some other tasks, eg contributors cla) only really needs to be sorted out before graduation， we may work on it there not current existing github repo (https://github.com/alibaba/dubbo). Best Regards, yiji ________________________________ From: Von Gosling <vongosl...@apache.org> Sent: Wednesday, March 14, 2018 10:57 To: dev@dubbo.apache.org Subject: Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache Hi, I really suggest we could be better to transfer the code to the ASF at the first stage. But one complicated point around my hat, how could we arrange the repositories in the Apache Git Repository? if we hope to keep the same release pace with so many repositories. Best Regards, Von Gosling > 在 2018年3月14日，10:39，Justin Mclean <jus...@classsoftware.com> 写道： > > With my mentors
