Re: On RocketMQ community projects

2017-01-08 Thread Justin Mclean
Hi, > As Apache Flink and Apache Storm use Apache License, I think it's OK to > host these modules in rocketmq incubator repo. Assuming I understand correctly in that you are writing new code to integrate with Apache Flink and Apache Storm and place that code in the RocketMQ repo that’s 100% O

Re: On RocketMQ community projects

2017-01-08 Thread Roman Shtykh
This approach looks good to me. Roman Shtykh On Monday, January 9, 2017 10:28 AM, Willem Jiang wrote: We have lots components[1] in Apache Camel which provide the integration of the third party projects, all of them are Apache Licensed and we have no trouble to host these components in

Re: On RocketMQ community projects

2017-01-08 Thread Willem Jiang
We have lots components[1] in Apache Camel which provide the integration of the third party projects, all of them are Apache Licensed and we have no trouble to host these components in Apache Camel repository. But if the third party projects don't use the Apache License, we hosts these components i

Re: On RocketMQ community projects

2017-01-04 Thread Roman Shtykh
Honestly, I don't know how many Apache projects have evolved :) But I think you are right. And this could also be just because they didn't think about integrations at the beginning. To my mind, it won't cause any problems to keep everything together if it is gone through reviews, but it's up to

Re: On RocketMQ community projects

2017-01-04 Thread Von Gosling
Good idea, roman :-) AFAIK, at first, some other apache projects do not use these model. Util they are enough mature, they began to consider to keep integration withe core code base. Am i right ? > 在 2017年1月4日,17:47,Roman Shtykh 写道: > > IMO, having extention/ or contrib/ directory (Storm app

Re: On RocketMQ community projects

2017-01-04 Thread Roman Shtykh
IMO, having extention/ or contrib/ directory (Storm approach you mentioned) and letting people create integration modules via PRs is good enough. As another example, the same approach is also taken, for instance, by Apache Flink [1]. Also, keeping integration modules together with the core code b

Re: On RocketMQ community projects

2017-01-04 Thread Von Gosling
I am not sure what kind of form if we move these RocketMQ community projects into the Apache community, as the extension module or another way ? Recently, apache Storm PMC member has contact me , hoping to move rocketmq-storm integration Project move to its extension module.We also received com

Re: On RocketMQ community projects

2017-01-04 Thread Willem Jiang
+1 for moving those project into Apache if there is no any legal issues. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, Jan 4, 2017 at 9:43 AM, Roman Shtykh wrote: > Folks, > I think an import

On RocketMQ community projects

2017-01-03 Thread Roman Shtykh
Folks, I think an important part of RocketMQ project growth will be an integration with other platforms.Currently, there are a couple of such integrations [1], but they are a bit outdated and not all of them have Apache license. Shall we make them Apache licensed? Shall we keep them in [1]? I wou