Hi: Maybe we should think highly of encouragement instead of management. Just like https://github.com/rocketmq, all integration projects stay under the same organization instead of one repo. They are independent and also easy for users to find what they need. As we have control for these repos, we are able to control the quality of releases. The only problem is the package name, as they are not apache repos, they cannot not use package name of "org.apache.XXX", but they may share another name prefixed with "rocketmq.io", or some other good prefixes. So the current state is OK. Move these projects into apache repos, either one repo or many, is not a good idea, especially in the early stage, as normal contributors do not have permission to commit to the apache repos. Maybe the right time to do so is when the sub project is mature and important.
Best Regards dongeforever ------------------ Original ------------------ From: "Justin Mclean";<[email protected]>; Date: Wed, Mar 8, 2017 05:48 PM To: "dev"<[email protected]>; Subject: Re: Podling Report Reminder - March 2017 Hi, > we hope to one repository for all RocketMQ integration projects, is it ok ? j One or many repo are possible and ether are fine. It??s up to the PPMC. > I??m also wondering how sustainable / scalable the "3 guys review mechanism?? > is going to be going forward. Anyone have any thoughts on that? > > Is there any suggestion or good choice about RTC mode :-) Most projects I??m involved in are CTR than RTC so perhaps my view is off here. However no other project use this style of review AFAIK and I??m just wondering how scalable it and if it may put people off contributing? I don't think it??s an issue but my be good to have some discussion on the list about this. Thanks, Justin
