> -----Original Message----- > From: br...@porterclan.net [mailto:br...@porterclan.net] On Behalf Of > Brett Porter > Sent: 01 August 2012 18:08 > 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 > > [Snip] > > I don't like the phrase "the ASF branch of CloudStack". If I may be a little > blunt: for this project to be successful, Citrix will need to stop thinking of > Apache CloudStack as a downstream destination for features, and instead as > an upstream for their future releases. This is a pretty huge shift in the > mental > model for developing features, but incredibly valuable for growing a > community around them. I understand getting a first release out here will > make that easier, but that's not a blocker to starting to do it now.
We are precisely trying to make Apache the upstream. This code is something that we're trying to submit to the project for exactly that reason -- so that 4.0 can be the upstream. Nobody at Citrix wants ASF to be the downstream. We are going through a transition period here where code was held out of the master branch because of all these policy issues that weren't resolved. Now that we know what we're doing with our code and where it's going, we want to get it into 4.0 so that we can make a clean break and have all the code in one place at Apache. > As far as how work like this gets accepted, I had a draft last week when David > beat me to it and wrote this summary to the list: > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack- > dev/201207.mbox/%3CCAKprHVZvxjbNC3vXb2GeTwhjGusbWYAOKuzBmCYP > 2VY1LwMFBg%40mail.gmail.com%3E > > Everyone participates as an individual, regardless of their affiliation. > Committers need to comply by sections 5 and 7 of their ICLA ( > http://www.apache.org/licenses/icla.txt). If there is work being submitted > by multiple people, then all ASF projects fill out an IP clearance form for > each > work to record its origin. It isn't necessarily an onerous process, but it's > not > one that should be the normal way of doing work. ICLAs we can do. I will make sure that everyone who has worked on this branch has signed the ICLA. However, we do need to work out a process for accepting changesets with multiple authors. It is very normal for two people to work on something and for this to turn into a single changeset ready for review. This is inevitable in cases where people are buddy-coding, or where junior staff are having their work checked internally, or where it's talking to something on the far side (NetScaler 10 in this case) that is being developed in parallel. It is also very common when working with foreign teams (I have seen it a lot when working with Japan) because most developers inside those teams can't speak English and can't engage in the review process. We absolutely have to be prepared for someone to show up with a patch who says "I am submitting this on behalf of X, Y, and Z". Ewan.