Hi All,

Recently, the SGA for the following project has been signed, and I
start to transfer these project into ASF.
* https://github.com/dubbo/dubbo-async-processor
* https://github.com/dubbo/dubbo-serialization-gson
* https://github.com/dubbo/dubbo-kubernetes
* https://github.com/dubbo/dubbo-benchmark
* https://github.com/dubbo/dubbo-logo

I checked all the contributors, all of them have signed ICLA, except
[1], who developed the Dubbo logo.
He works for Alibaba, given the copyright belong to Alibaba and the
SGA has signed, there is no need to sign ICLA, is my understanding
correct?

[1] https://github.com/bluewoft

On Tue, Mar 19, 2019 at 11:24 PM Huxing Zhang <[email protected]> wrote:
>
> Hi,
>
> I've updated the wiki page[1], with a new column called "suggested
> action" added.
>
> In addition to discussion I raised number 1,  I've checked how other
> podlings are acting:
> - The Openwhisk community move all the multi-language projects in
> external ecosystem to ASF[1]
> - The Skywalking community rename the multi-language projects in
> external ecosystem to SkyAPM[2]
> I seems each community has different behavior.
>
> Also I am adding two more discussion:
>
> 3. next action of dubbo-sentinel-support
> a) rename to sentinel-support
> b) move to sentinel-group
> c) transfer to ASF
> d) do nothing
>
> This project is about sentinel integration for Apache Dubbo, so I
> think a simple rename could solve.
>
> 4. next action of dubbo-benchmark
> a) transfer to ASF
> b) rename to benchmark
> c) do nothing
>
> Given that:
> - The project contain multiples benchmark for different serialization
> provided by Apache Dubbo
> - All the maintainers are Apache Dubbo PPMC members.
> - There is a proposal to improve the performance with this project.
> I think it is appropriate to host this project in ASF, and maintain it
> officially by Apache Dubbo.
>
> How do you think?
>
> [1] https://github.com/openwhisk
> [2] https://github.com/SkyAPM/
> [3] https://github.com/apache/incubator-dubbo/issues/2508
>
> On Mon, Mar 18, 2019 at 4:19 PM Huxing Zhang <[email protected]> wrote:
> >
> > Hi All,
> >
> > I have summarized the current status of external projects under dubbo
> > group here[1].
> > I am seeking comments from the community. Does everything look all right?
> > If it looks good, I do encourage the maintainer of the projects to
> > start to merge their project into incubator-dubbo.
> >
> > I have two issues to discuss.
> >
> > First, how to deal with the multi-language sdk? What I can think is:
> > - Ask the maintainers about whether they are willing to transfer the
> > code to ASF.
> > - If they are fine with it, sign the SGA and ICLA for the authors,
> > transfer the repository to ASF. This may introduce further question:
> >   - The maintainers will lose write access to the project, and the
> > Dubbo committers may not be familiar with other language than Java.
> > How to review the pull request?
> >   - The projects may require refactoring because license issues.
> >   - The projects must learn the ASF rules, including how to do
> > release, this may break their existing release cycles.
> > - If they are not, is it necessary to to rename the projects to avoid
> > potential branding issues?
> >
> > Second, can a forked repository transfer to ASF? For example, the
> > initializr project which host start.dubbo.io, is forked from
> > spring-io/initializr.
> >
> > [1] 
> > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status
> > [2] https://github.com/dubbo/initializr
> >
> >
> > On Fri, Mar 15, 2019 at 5:58 PM Huxing Zhang <[email protected]> wrote:
> > >
> > > Hi,
> > >
> > > Update: the dubbo-registry-etcd project [1]  has been merged into
> > > incubator-dubbo, I suggest to archive this project and make it clear
> > > in the README that it has been merged into incubator-dubbo.
> > >
> > > How do you think?
> > >
> > > [1] https://github.com/dubbo/dubbo-registry-etcd
> > >
> > > On Fri, Mar 1, 2019 at 4:32 PM jun liu <[email protected]> wrote:
> > > >
> > > > > * 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
> > > >
> > >
> > >
> > > --
> > > Best Regards!
> > > Huxing
> >
> >
> >
> > --
> > Best Regards!
> >
> > Huxing
>
>
>
> --
> Best Regards!
> Huxing



--
Best Regards!

Huxing

Reply via email to