On Aug 7, 2012, at 8:12 PM, Ewan Mellor <ewan.mel...@eu.citrix.com> wrote:
>> -----Original Message----- >> From: David Nalley [mailto:da...@gnsa.us] >> Sent: Tuesday, August 07, 2012 3:42 PM >> To: cloudstack-dev@incubator.apache.org >> Subject: Re: where features are developed was: Review Request: Merge >> Kelven's VPC code for Vmware into asf vpc branch >> >> On Tue, Aug 7, 2012 at 4:59 PM, Ewan Mellor <ewan.mel...@eu.citrix.com> >> wrote: >>> That makes a lot of sense to me, thanks Chip. >>> >>> For those public repos for non-committers, I presume that they can't >> use Apache infrastructure, so Github would be the natural choice. We >> have a mirror there now (as of last week) so people can clone and work >> there. How does that sound? >>> >>> Regarding the third point, I don't know what the ASF requires in >> terms of authorship indicators in commit messages. We obviously need >> all authors to have signed the ICLA, but other than that I don't know >> of a written policy. Unless there's something contradictory, putting >> the Author names in the commit message seems reasonable to me. >> >> >> The below has some guidance: >> http://apache.org/dev/committers.html#applying-patches >> >> Essentially some annotation needs to be made, but there is no absolute >> practice; so comments are fine. > > Thanks David, that looks good to me. > > So can we give this process the first go through, using the autoscale branch? > We've got the branch ready to go, if I understand correctly, so we just need > Vijay or Deepak to make sure that the authors are all appropriately credited > (and that everyone has signed the ICLA). Then we should be able to start > reviewing that branch for merge into 4.0. > > Ewan. > > Mentors: can you provide some input here? Does this approach seem reasonable from an ASF perspective? Also, I'd be interested in what the rest of the community thinks. -chip
