As we can see large scale project. for example : kubernetes. docker They have many sub project. in their own repository. and release in different time line. Appreciate your time. ---------------------------- Netroby
2017-02-25 1:19 GMT+08:00 Bruce Snyder <[email protected]>: > 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 > consume these sub-projects (from Maven, from Gradle, etc.) into their own > applications. You can always use git sub-modules ( > https://git-scm.com/book/en/v2/Git-Tools-Submodules) to keep things in a > separate git repo for management purposes and pull them into another repo > this way. > > Bruce > > On Fri, Feb 24, 2017 at 7:16 AM, Von Gosling <[email protected]> wrote: > >> Hi, >> >> Does it matter if we create too many projects in apache. In our plan, we >> will contribute the integration project in the future milestones，such as >> storm, spark, flume, flink, ignite ,multi-language SDK etc. These projects >> are not fully come from Apache RocketMQ team. May be,the majority come from >> the community contributor :-) >> >> > 在 2017年2月24日，12:00，Justin Mclean <[email protected]> 写道： >> > >> > 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). >> > >> > Justin >> >> > > > -- > 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
