Hi Ram, For a start, we need Vijay and anyone else who's worked on this code to sign the ICLA and scan and send it to [email protected]. http://www.apache.org/licenses/#clas. Citrix has already signed the corporate CLA and we have authorization to sign ICLAs for submissions to Apache, so there's nothing internal that you need to do.
Thanks, Ewan. > -----Original Message----- > From: Ram Ganesh [mailto:[email protected]] > Sent: 02 August 2012 10:02 > To: Pranav Saxena; David Nalley > Cc: [email protected]; Vijay Venkatachalam; Alena > Prokharchyk; Deepak Garg > Subject: RE: What to do with Autoscale: was: Re: [6/11] AutoScale changes in > Apache master > > David, > > We did discuss the AutoScale feature in the apache forum, followed the > process by creating a topic branch and follow patch process as and when they > arise. As Vijay\Deepak have no committer privileges we had to route it > through pranav. Functional specs is available at > http://wiki.cloudstack.org/display/DesignDocs/Auto+Scale+Feature. If there > are gaps in the process followed please let us know > > Thanks, > Ram > > > > -----Original Message----- > > From: Pranav Saxena > > Sent: 02 August 2012 18:28 > > To: David Nalley > > Cc: [email protected]; Vijay Venkatachalam; Alena > > Prokharchyk; Deepak Garg; Ram Ganesh > > Subject: RE: What to do with Autoscale: was: Re: [6/11] AutoScale > > changes in Apache master > > > > Hi David , > > > > As I mentioned in my previous mail , Vijay Venkatchalam and Deepak > > Garg are the authors for the backend code and me , Jessica and Sanjay > > have been responsible for the UI development for this feature. Vijay > > has sent out a mail to the cloudstack dev community regarding the " > > Autoscale" feature. I think you happened to miss the mails sent by > > Vijay and Deepak in this regard. And whatever code has been merged > > later on after the creation of the asf/autoscale branch has been sent > > through review requests on the dev ML. > > > > Kindly have a look at the mails sent by Vijay and let me know whatever > > decisions I have to abide by . I will be more than happy to follow > > your advice. > > > > Thanks & Regards, > > Pranav > > > > -----Original Message----- > > From: David Nalley [mailto:[email protected]] > > Sent: Thursday, August 02, 2012 5:46 PM > > To: Pranav Saxena > > Cc: [email protected]; Vijay Venkatachalam; Alena > > Prokharchyk; Deepak Garg > > Subject: What to do with Autoscale: was: Re: [6/11] AutoScale changes > > in Apache master > > > > On Fri, Jul 27, 2012 at 10:03 AM, Pranav Saxena > > <[email protected]> wrote: > > > Hi David, > > > > > > This commit was based on addition of a new feature called AutoScale > > on which few guys from Bangalore have been working on , including me . > > Since this feature was supposed to be pushed in today y , so we had to > > create a new branch asf/autoscale ( pulled out of 3.0.x - citrix > > private branch ) and push the changes there. This was as per Alena's > > request that I should proceed by pushing the changes for the Autoscale > > feature (since I am the only committer here in Bangalore) by creating > > a new branch on apache and the author( Vijay ) would send out an email > > on the cloudstack dev list , mentioning about the Autoscale feature. > > We'll be merging some more changes very soon. > > > > > > @Vijay - could you please elaborate on the Autoscale feature ? > > > > > > Thanks & Regards, > > > Pranav > > > > Pranav, et al. > > > > This is still problematic. For the time being, lets hold off on > > additional commits to this branch till we get some of the process and > > IP issues sorted. > > > > First, who are the authors for the code that's been committed to this > > branch, you mention 'a few guys in BLR', but who are they specifically? > > > > Second, as a group the project needs to decide if we want to include > > this feature, and if so, how we will handle inclusion. (There are a > > number of potential options here, the PPMC could send it through IP > > Clearance at the Incubator, or a Software Grant, or something more > > simple.) Don't be surprised if this involves deleting the branch or > > reverting the commits and handling submission in some other manner. > > > > --David
