dubbo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zonghai shang <yiji.git...@hotmail.com>
Subject 答复: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache
Date Tue, 13 Mar 2018 16:02:17 GMT

Thanks for your reply.

question 1:

After use prefixed as "incubator-dubbo" for project name, can we rename project on the table:

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

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

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

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

dubbo/dubbo-docs
        yes
        incubator-dubbo-docs
        documentations

dubbo/dubbo-rpc-jsonrpc
        yes
        incubator-dubbo-jsonrpc
        jsonrpc extension

dubbo/dubbo-docker-sample
        no      -       demo

dubbo/dubbo-resources
        no
        -       -
dubbo/dubbo-feature-test
        yes
        incubator-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 incubator-dubbo-website after import to apache.
  2.  dubbo/dubbo-spring-boot-project renamed to incubator-dubbo-spring-boot after import
to apache.
  3.  dubbo/dubbo-rpc-jsonrpc renamed to incubator-dubbo-jsonrpc after import to apache.
  4.  dubbo/dubbo-feature-test rename to incubator-dubbo-feature-test after import to apache.
  5.  The remaining submissions to the apache project rename the prefix dubbo to incubator-dubbo.

question 2:

For the git repos not moving over, because it is only used as a demonstration, it is not a
dubbo core feature.

question3:

if we switch to our internal git, we have some tasks not complete yet, eg:

  1.  about ip clearance
  2.  check all contributors cla
  3.  and so on

Do we have to complete taskts (see eg: 1. ip clearance and so on) related to the dubbo project
in the existing github  or we can first move over to internal git before completing this tasks.
________________________________
发件人: John D. Ament <johndament@apache.org>
发送时间: 2018年3月13日 23:39
收件人: dev@dubbo.apache.org
抄送: zonghai shang
主题: Re: Suggestions on the organizational form of the code repository after confirming
the submission of the dubbo code to apache

All repositories coming in for dubbo will be prefixed as "incubator-dubbo", this is a requirement.

Are you looking to continue to use github as the primary repository location, or switch to
our internal git? I'd recommend github since you're already there.  For the git repos not
moving over, is there any reason they would not come over?

John

On Tue, Mar 13, 2018 at 11:30 AM zonghai shang <yiji.github@hotmail.com<mailto:yiji.github@hotmail.com>>
wrote:
Sorry, E-mail support for forms is not friendly, Here is a picture of the project structure
change.

Here are directory of project structure changes:
[X]

Here are main changes:

  1.  dubbo/dubbo.github.io<http://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.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message