+1 to include its impl directly into Apache Dubbo repo from the respective of easy-maintenance.
If a side project is an Dubbo's extension, it is easy to maintain it to keep it in Dubbo group when it is immature, but once it's mature enough (not to hurt the main project), we should move it into Apache Dubbo repo, instead of moving it Apache group as a separated project since it is easier to maintain it. Thanks, -Ian. On Tue, Jan 8, 2019 at 5:47 PM Mercy <mercybl...@apache.org> wrote: > Hi, > > I'd like to take the dubbo-registry-nacos as a registry > implementation and put the source code into dubbo branch 2.6.6+, what's > your opinion? > > Kind regards, > > Mercy > > 在 2018/12/25 下午5:44, Huxing Zhang 写道: > > Hi, > > > > On Sun, Dec 23, 2018 at 4:48 AM Justin Mclean <jus...@classsoftware.com> > wrote: > >> Hi, > >> > >>> Yes, both of them are Dubbo ppmc member.cI think we need a software > grant here, shall we? > >> Give both people involved have signed ICLAs and the code in Apache > licensed it’s probably not required. It may depend on who actually owns the > code (usually the company those people work for but it depends on their > employment conditions and contract). > > According to my knowledge, I think the company owns the code. It's > > better to have a software grant there. > > > >> Thanks, > >> Justin > > > > >
