Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache

[zonghai shang]

Here are directory of project structure changes:

project name    import to apache         apache project name    description
alibaba/dubbo   yes     apache/dubbo
        core repository

dubbo/dubbo.github.io   yes     apache/dubbo-website
        official site

dubbo/dubbo-ops
        yes     apache/dubbo-ops
        monitor&admin features

dubbo/dubbo-spring-boot-project
        yes     apache/dubbo-spring-boot
        support for spring boot

dubbo/dubbo-docs
        yes
        apache/dubbo-docs
        documentations

dubbo/dubbo-rpc-jsonrpc
        yes
        apache/dubbo-jsonrpc
        jsonrpc extension

dubbo/dubbo-docker-sample
        no      -       demo

dubbo/dubbo-resources
        no
        -       -
dubbo/dubbo-feature-test
        yes
        apache/dubbo-feature-test       feature test

dubbo/dubbo-http-demo
        no
        -       demo

dubbo/dubbo-ws-demo
        no
        -       demo



Here are main changes:

  1.  dubbo/dubbo.github.io renamed to apache/dubbo-website after import to 
apache.
  2.  dubbo/dubbo-spring-boot-project renamed to apache/dubbo-spring-boot after 
import to apache.
  3.  dubbo/dubbo-rpc-jsonrpc renamed to apache/dubbo-jsonrpc after import to 
apache.
  4.  dubbo/dubbo-feature-test rename to apache/dubbo-feature-test after import 
to apache.
  5.  The remaining submissions to the apache project rename the prefix dubbo 
to apache.

Reasons for suggesting structural adjustment:
   1. I suggest adjusting because the naming is clearer and easier to 
understand.
   2. Refer to existing apache projects apache/commons-io, apache/commons-lang, 
apache/commons-math and so on.

Welcome everyone to make suggestions.