Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-05-12 Thread Jie Tang
feel free to reach out with any new idea. > > > > > > -- Original -- > From: "Bruce Snyder";<bruce.sny...@gmail.com>; > Date: Mon, Mar 13, 2017 09:43 PM > To: "dev"<dev@rocketmq.incubator.apache.org>; > > Subject: Re

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-05-10 Thread dongeforever
out with any new idea. -- Original -- From: "Bruce Snyder";<bruce.sny...@gmail.com>; Date: Mon, Mar 13, 2017 09:43 PM To: "dev"<dev@rocketmq.incubator.apache.org>; Subject: Re: [DISCUSS] How to handle sub projects of RocketM

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-03-13 Thread Bruce Snyder
.@qq.com [ > > > 1018815...@qq.com] > 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

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-03-13 Thread yukon
as soon as possible, and I insist that > the > >> > > first way may be more suitable for RocketMQ. > >> > > > >> > > Any voices are welcome. > >> > > > >> > > Regards, > >> > > yukon > >> > > >

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-03-13 Thread Bruce Snyder
; > Regards, >> > > yukon >> > > >> > > >> > > >> > > >> > > >> > > On Sat, Feb 25, 2017 at 9:28 AM, dongeforever < 1018815...@qq.com [ >> > > 1018815...@qq.com] > wrote: >> > > +1 all

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-03-13 Thread yukon
e quality. > > > > > > -- Original -- > > From: "Willem Jiang" < willem.ji...@gmail.com [willem.ji...@gmail.com] > >; > > Date: Sat, Feb 25, 2017 08:58 AM > > To: "dev" < dev@rocketmq.incubator.apache.o

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-03-09 Thread Xin Wang
feel free to use it, otherwise I may lack confidence in > the quality. > > > -- Original -- > From: "Willem Jiang" < willem.ji...@gmail.com [willem.ji...@gmail.com] >; > Date: Sat, Feb 25, 2017 08:58 AM > To: "dev" < dev@ro

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-03-09 Thread yukon
rocketmq.incubator.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

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-02-24 Thread dongeforever
: "Willem Jiang" <willem.ji...@gmail.com>; Date: Sat, Feb 25, 2017 08:58 AM To: "dev" <dev@rocketmq.incubator.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 proje

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-02-24 Thread Willem Jiang
+1 for managing the components in the same repo if we just integration those projects with RocketMQ. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb 24, 2017 at 11:33 AM, Von Gosling

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-02-24 Thread Bruce Snyder
When it comes to neatly organizing each sub-project, you must consider if you will release all sub-projects at once or individually. Also, consider whether or not these are extensions to RocketMQ or external (as in not part of or extensions to RocketMQ) in some way. Also consider how users will

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-02-23 Thread Justin Mclean
Hi, > +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 :-) Just remember that unlike SVN checking out a subtree in Git can be painful (look up sparse checkouts or branch filters).

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-02-23 Thread Von Gosling
+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 写道： > > Hi, > > How about creating a git repo named "incubator-rocketmq-externals", all

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-02-23 Thread yukon
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

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-02-23 Thread Bruce Snyder
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

Re: [DISCUSS] How to handle sub projects of RocketMQ

2017-02-23 Thread Justin Mclean
Hi, > 2. Create separate apache repos, but this way may produce overmuch repos of > RocketMQ, and I'm not sure this is allowed. It’s fine to have multiple repos. > 3. Keep these projects in[1], provide links and introductions in README or > our rocketmq-site. IMO -1 to that as it fragments

[DISCUSS] How to handle sub projects of RocketMQ

2017-02-22 Thread yukon
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