Re: [DISCUSS] Migrating projects under dubbo group

[Jun Liu <li...@apache.org>]

I just reviewed a PR[0] aimed at merging 'dubbo/rpc-native-thrift-for-apache-dubbo’ into the core repo, I think it’s good to go, we can merge it after the author responded my change requests on two trivial issues.

0. https://github.com/apache/incubator-dubbo/pull/3965

Ken

> On Apr 25, 2019, at 4:02 PM, Huxing Zhang <hu...@apache.org> wrote:
> 
> Hi All,
> 
> As is discussed in the graduation proposal in general@ mailing list,
> the github.com/dubbo group has some potential branding issue. To avoid
> it completely, we need to decide the short-term plan and long-term
> plan.
> 
> For the short-term plan, there are two way proposed:
> 
> 1. Rename dubbo group to another one, let's say A.
> 2. Create a new group A, and migrate all the project to under A, and
> keep the dubbo group empty. The purpose is to avoid someone to abuse
> it in the future.
> 
> I am leaning towards option 2. But I'd like to hear what other may think.
> 
> The next step is to decide what A is.  Actually naming a thing is one
> of the most difficult thing to do... I am trying to find something
> related. I checked the wikipedia page for Dubbo[1], in the history
> section, it says  Dubbo is now thought to be a mispronunciation of the
> local Wiradjuri word "Thubbo" or "Tubbo".
> 
> I think thubbo and tubbo both are good. thubbo is more different to
> dubbo than tubbo. So I prefer thubbo. How do you think?
> 
> 
> For the long-term plan:
> 
> 1. Like discussed before, all projects under group A are expected to
> be transferred to Apache (if the owner) agree with an ETA. I talked to
> most of the owners and they basically agree, the multi-language
> project are TODOs. I am trying to pull them onto list.
> 
> This projects that still listed under dubbo group includes:
> 
> * js-for-apache-dubbo
> * py-client-for-apache-dubbo
> * rpc-xmlrpc-for-apache-dubbo
> * jmeter-plugins-for-apache-dubbo
> * go-for-apache-dubbo
> * php-framework-for-apache-dubbo
> * dotnet-for-apache-dubbo
> * serialization-native-hessian-for-apache-dubbo
> * jms-for-apache-dubbo
> * dubbo.github.io
> * metrics
> * hessian-lite
> * dubbo-sentinel-support
> * awesome-dubbo
> * dubbo-remoting-js
> * egg-dubbo-rpc
> * rpc-native-thrift-for-apache-dubbo
> * intellij-idea-plugin
> * initializr
> 
> 
> If you are the project owner, could you please confirm that:
> 
> 1) are you willing to transferred to ASF or not.
> 2) if so, please give an estimated time when will you can finish transfer.
> What you will need to do includes:
> - Find the all the contributors and ask them to sign the Apache
> ICLA[2], if the contribution is trivial, this can be ignore
> - If the code belongs to your company, you need to sign the SGA[3]
> - request ASF infra to transfer the project
> 3) if not, please indicate that which group you will transfer to.
> 
> 2. Gain write access to your project after transfer
> 
> If your project has been transferred to ASF, you will lose write
> access temporally. The Dubbo community will vote you in as committer
> by following standard ASF way. This means you have to contribute to
> the project for some time in order to earn enough merit.
> 
> 3. After the transition is done, delete group A.
> 
> The community will summarize and keep track of the status here[4].
> 
> 
> [1] https://en.wikipedia.org/wiki/Dubbo
> [2] http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html
> [3] http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html
> [4] https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status
> 
> 
> 
> -- 
> Best Regards！
> Huxing