Can we have the maintainers take responsibility for the incoming patch stream right away?
-kevin > -----Original Message----- > From: Will Chan [mailto:will.c...@citrix.com] > Sent: Tuesday, June 12, 2012 4:46 PM > To: cloudstack-dev@incubator.apache.org > Subject: RE: Maintainer/committer model for CloudStack > > I've taken all the feedback so far and extended the CloudStack Maintainers > Guide written by John and added all the maintainers so far. There are > probably more missing but that's what we have today. If we want this list to > be its own page, we can certainly do that as well but I thought it was easier > to > see what a maintainer's role of CloudStack is and who they are currently all > in > a single page. > > http://wiki.cloudstack.org/display/COMM/Draft%3A+CloudStack+Maintainer > s+Guide > > Will > > > -----Original Message----- > > From: David Nalley [mailto:da...@gnsa.us] > > Sent: Friday, June 01, 2012 7:57 PM > > To: cloudstack-dev@incubator.apache.org > > Subject: Re: Maintainer/committer model for CloudStack > > > > So it seems we have some consensus around trying this maintainer model > > out - so now we need the existing committers to step up for some of these > 'modules'. > > I am happy to step up for packaging stuff (debs and > > rpms) and some of the related things around this such as initscripts. > > I'd like to get to the point where someone else picks debian stuff up, > > since my level of comfort and familiarity there is a bit lower. > > > > Others? > > > > --David
