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

Hi, > They are release individually. Is it a problem after moving to ASF? No issue at all. Thanks, Justin

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

Filed a INFRA ticket: https://issues.apache.org/jira/projects/INFRA/issues/INFRA-16182 On Wed, Mar 14, 2018 at 1:46 PM, Ian Luo wrote: > To summarize, we will transfer dubbo and its relevant side projects into > github.com/apache with the prefix 'incubator-dubbo- > ',

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

Hi John, On Wed, Mar 14, 2018 at 1:05 PM, John D. Ament wrote: > In the present setup, are all repositories released together, or are they > released individually? They are release individually. Is it a problem after moving to ASF? > > On Tue, Mar 13, 2018 at 10:57 PM Von Gosling wrote: > >> H

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

Hi Justin, On Wed, Mar 14, 2018 at 10:39 AM, Justin Mclean wrote: > Hi, > >>> 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. >> >> +1 stick to github, just transfer to github/apa

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

To summarize, we will transfer dubbo and its relevant side projects into github.com/apache with the prefix 'incubator-dubbo- ', and will start IP clearance as early as possible even though this work doesn’t block the transition. Regards, -Ian. > On 14 Mar 2018, at 1

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

> On 14 Mar 2018, at 10:34 AM, jun liu wrote: > >> 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. > > +1 stick to github, just transfer to github/apache after the IP Clearance

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

Hi, > 1. Can we put the project at > https://github.com/apache/ ？ > > for example: > a. alibaba/dubbo move to https://github.com/apache/incubator-dubbo > b. dubbo/dubbo.github.io move to > https://github.com/apache/incubator-dubbo-website > c. d

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

yiji From: Von Gosling Sent: Wednesday, March 14, 2018 10:57 To: dev@dubbo.apache.org Subject: Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache Hi, I really suggest we could be better to transfer the code to the

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

In the present setup, are all repositories released together, or are they released individually? On Tue, Mar 13, 2018 at 10:57 PM Von Gosling wrote: > Hi, > > I really suggest we could be better to transfer the code to the ASF at the > first stage. But one complicated point around my hat, how co

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

Hi, I really suggest we could be better to transfer the code to the ASF at the first stage. But one complicated point around my hat, how could we arrange the repositories in the Apache Git Repository? if we hope to keep the same release pace with so many repositories. Best Regards, Von Gosling

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

Hi, >> 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. > > +1 stick to github, just transfer to github/apache after the IP Clearance > sort of things With my mentors hat on I thin

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

> 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. +1 stick to github, just transfer to github/apache after the IP Clearance sort of things > For the git repos not moving over, is th

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 th