Hi Yukon, I have submitted the request and the response told me that it may take up to an hour for it to be created. My experience is that it can take considerably longer at times. I will keep checking the Incubator private list for the notification.
Bruce On Mon, Mar 13, 2017 at 6:02 AM, yukon <[email protected]> wrote: > Hi Bruce, > > Since there is no other opinion, could you please help create a git repo > named "incubator-rocketmq-externals" for us? > > And let's start the migration process for these sub projects. > > Regards, > yukon > > On Fri, Mar 10, 2017 at 1:46 PM, Xin Wang <[email protected]> wrote: > > > I give a +1(non-binding) for rocketmq-external. > > > > - Xin Wang (vesense) > > > > 2017-03-10 11:53 GMT+08:00 yukon <[email protected]>: > > > > > Hi, > > > > > > > > > Recently, there has been much discussion about this issue, IMO, > RocketMQ > > > community has reached a consensus that these sub projects should > migrate > > > from GitHub to ASF. > > > > > > > > > But, there are two ways to reach our goal. > > > > > > > > > 1. Create a uniform ASF git repo for all the sub projects named > > > "incubator-rocketmq-externals", all sub-projects assembled in this > repo. > > > It can reduce management and delivery costs and users can take a quick > > look > > > at ecological map of RocketMQ and find what they want quickly. But as > > > Justin said, many collaborative development over sub-projects may be > very > > > painful. > > > > > > > > > 2. Create separate git repos for various sub projects, it's feasible as > > > Bruce said. But this way may bring extra management and delivery costs. > > > > > > > > > IMO, we should decide a way as soon as possible, and I insist that the > > > first way may be more suitable for RocketMQ. > > > > > > Any voices are welcome. > > > > > > Regards, > > > yukon > > > > > > > > > > > > > > > > > > On Sat, Feb 25, 2017 at 9:28 AM, dongeforever < [email protected] [ > > > [email protected]] > wrote: > > > +1 all external projects in one place, same repo or better the same > group > > > > > > As a user, I would be glad to see these integrated projects in a > managed > > > central place and feel free to use it, otherwise I may lack confidence > in > > > the quality. > > > > > > > > > ------------------ Original ------------------ > > > From: "Willem Jiang" < [email protected] [[email protected]] > > >; > > > Date: Sat, Feb 25, 2017 08:58 AM > > > To: "dev" < [email protected] [[email protected]. > > > apache.org] >; > > > Subject: Re: [DISCUSS] How to handle sub projects of RocketMQ > > > > > > > > > > > > +1 for managing the components in the same repo if we just integration > > > those projects with RocketMQ. > > > > > > Willem Jiang > > > > > > Blog: http://willemjiang.blogspot.com [http://willemjiang.blogspot.com > ] > > > (English) > > > http://jnn.iteye.com [http://jnn.iteye.com] (Chinese) > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Fri, Feb 24, 2017 at 11:33 AM, Von Gosling < [email protected] > [ > > > [email protected]] > wrote: > > > > > > > +1, one repo for all external projects in Apache Group. it can reduce > > > > management and delivery cost. Also let it under Apache and Apache > > > RocketMQ > > > > umbrella :-) > > > > > > > > > > > > > 在 2017年2月24日，11:23，yukon < [email protected] [[email protected]] > > 写道： > > > > > > > > > > Hi, > > > > > > > > > > How about creating a git repo named "incubator-rocketmq-externals" > , > > > all > > > > > sub-projects assembled in this repo. > > > > > > > > > > IMO, it's a a manageable way, users can take a quick look at > > ecological > > > > map > > > > > of RocketMQ and find what they want quickly. > > > > > > > > > > Regards, > > > > > yukon > > > > > > > > > > On Thu, Feb 23, 2017 at 10:54 PM, Bruce Snyder < > > > [email protected] [[email protected]] > > > > > > wrote: > > > > > > > > > >> All projects should have a separate git repo to keep things as > > > separate > > > > as > > > > >> possible. This will also help to simply the delivery of each one > > > > >> independently. > > > > >> > > > > >> If, at some point, you want to provide some sort of distribution > > that > > > > >> includes multiple projects, that's not a problem. But the source > for > > > > each > > > > >> individual project should remain in separate git repos but be > > included > > > > in > > > > >> the overall Apache RocketMQ project. > > > > >> > > > > >> It's fine to keep all sub-projects' wiki and web related stuff > > within > > > > the > > > > >> RocketMQ space. It just needs to be clear which content is a > > > > sub-project. > > > > >> > > > > >> Make sense? > > > > >> > > > > >> Bruce > > > > >> > > > > >> On Thu, Feb 23, 2017 at 12:52 AM, yukon < [email protected] [ > > > [email protected]] > wrote: > > > > >> > > > > >>> Dear mentors, > > > > >>> > > > > >>> As we know, RocketMQ has a GitHub organization off Apache[1], and > > > there > > > > >> are > > > > >>> three mini projects are currently going through rapid iterative. > > > > >>> > > > > >>> rocketmq-console-ng will provide a ops dashboard for RocketMQ, > > > > >> rocketmq-jms > > > > >>> will provide a new client to support JMS 2, while > rocketmq-flume-ng > > > > will > > > > >>> integrate RocketMQ with Apache Flume. > > > > >>> > > > > >>> Except these three projects, we will unite the power of the > > community > > > > >> fully > > > > >>> to develop more sub projects in the future, which can integrate > > > > RocketMQ > > > > >>> with Ignite, Flink, DistributedLog, and so on. > > > > >>> > > > > >>> So we wonder where these projects should be placed? We found some > > > > >>> alternative ways after doing a survey: > > > > >>> > > > > >>> 1. Add a folder in apache/incubator-rocketmq/ to place these > > > projects, > > > > >> like > > > > >>> incubator-rocketmq/modules/rocketmq-console-ng. But these > > projects' > > > > >>> releasing is independent, even some projects' releasing should > > > consider > > > > >> the > > > > >>> integrated project, like rocketmq-flume's releasing should > consider > > > the > > > > >>> Apache Flume's release schedules. > > > > >>> > > > > >>> 2. Create separate apache repos, but this way may produce > overmuch > > > > repos > > > > >> of > > > > >>> RocketMQ, and I'm not sure this is allowed. > > > > >>> > > > > >>> 3. Keep these projects in[1], provide links and introductions in > > > README > > > > >> or > > > > >>> our rocketmq-site. > > > > >>> > > > > >>> We want to know mentors' advice, and we would appreciate your > help. > > > > >>> > > > > >>> [1]. https://github.com/rocketmq [https://github.com/rocketmq] > > > > >>> > > > > >>> Regards, > > > > >>> yukon > > > > >>> > > > > >> > > > > >> > > > > >> > > > > >> -- > > > > >> perl -e 'print > > > > >> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\ > > "YC;VT*" > > > > );' > > > > >> > > > > >> ActiveMQ in Action: http://bit.ly/2je6cQ [http://bit.ly/2je6cQ] > > > > >> Blog: http://bsnyder.org/ [http://bsnyder.org/] < > > > http://bruceblog.org/ [http://bruceblog.org/] > > > > > >> Twitter: http://twitter.com/brucesnyder [http://twitter.com/ > > > brucesnyder] > > > > >> > > > > > > > > > > > -- perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bsnyder.org/ <http://bruceblog.org/> Twitter: http://twitter.com/brucesnyder
