> -----Original Message----- > From: Sheng Liang [mailto:sheng.li...@citrix.com] > Sent: Wednesday, August 15, 2012 3:41 PM > To: cloudstack-dev@incubator.apache.org > Subject: RE: [PROPOSAL] Breaking CloudStack into subprojects > > > Let's take the Netscaler AutoScale feature currently being > > implemented. I'm sure they must be at least touching the API, UI, some > Resources layer and DAO layer. If they were committers, do they have to > have been invited to all 4 of those subprojects? > > This is precisely the type of problem exposed by the separation. We need to > address these problems head-on and not try to prolong a large monolithic > system. > > Once we have clean separation of projects developers will be naturally > inclined to maintain the separation. Autoscaling should ideally be its own > project and not require changes to core CloudStack functionalities. > > Sheng
What you suggest makes sense but I don't think we are quite there yet. Alex is proposing we assign committers to each of the jar files (defined by him as a subproject) that are currently being created today. That seems a bit burdensome to me especially when we already have a maintainer system setup to review changes and commit patches. Will
