Steve I'm probably going to sound a little bit "arsy" as we say in England. I don't mean to - I'm not criticizing what's happened, but as mentor I need to make some points here.
1) Having an Apache ICLA from people who contributed to GitHub does not count. The Apache ICLA makes statements about contributions to Apache. Code that is contributed to the Github is not covered. So when you then contribute that code from GitHub into Apache then it is not covered. Looking back in the mailing list I see that you were poorly advised on this front. I apologize for not picking this up earlier and not commenting at that time. 2) This is a subset of a wider problem. The management of IP within Apache is a huge part of the governance of code, and it cannot be bypassed without serious consequences. Having you decide if there is an ICLA in place and accepting code on that basis completely bypasses the well documented Apache process that is the responsibility of the (I)PMC. Luckily the whole point of incubation is to learn these lessons, so at this stage this isn't serious. But on the other hand, I can't leave this undiscussed either! 3) Its not your responsibility to decide whether contributions are significant or not. A significant contribution in one person's eyes might be insignificant in another's. The whole Apache project started out from "a few bug fixes". Without seeing the patches go by, the community cannot judge the quality of contributions. Finally, I would be happier if there was a date by which the GitHub code will be re-integrated into the SVN and our GitHub tree decommissioned. Paul On Wed, Oct 1, 2008 at 5:48 PM, Steve Huston <[EMAIL PROTECTED]> wrote: > Hi Paul, > > FYI on the committers... I'm intensely aware of the licensing and IP > considerations. I didn't let anyone have write access to the github > repo without an Apache ICLA on file. One person emailed me changes - I > didn't read those until the ICLA was submitted. > > The code done by people other than me amounted to a few bug fixes. > Useful, no doubt, but not new features. > > -Steve > >> -----Original Message----- >> From: Paul Fremantle [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, October 01, 2008 12:07 PM >> To: [email protected] >> Subject: Re: Understanding the code repo situation with GitHub >> >> >> I think its important for graduation that all code is managed on the >> Apache SVN. While I can see that the approach you took prior to >> commitership was useful, it isn't a good model generally within >> Apache. For example, if other non-committers or even committers did >> contribute code to GitHub then the record of that will not propogate >> into the SVN. Non-committers are explicitly encouraged to submit >> patches, so the rest of the community gets to see the contributions, >> and in this case that wouldn't have happened. >> >> I'm glad to hear it is being phased out. >> >> Thanks >> Paul >> >> On Wed, Oct 1, 2008 at 3:32 PM, Steve Huston >> <[EMAIL PROTECTED]> wrote: >> > Hi Paul, >> > >> >> Do we still have "active" code in GitHub? Can someone enlighten > me >> > as >> >> to the situation? >> > >> > Since I have a github repository related to Qpid, I'll >> answer from my >> > point of view. >> > >> > The qpid-port github repository I created was mainly driven >> because I >> > hoped to share this with other people interested in Windows and I >> > didn't have subversion commit permission. Github was a suggested >> > alternative. >> > >> > Now that I do have subversion commit permission, I'm unlikely to >> > continue on github for qpid work. I'll be merging the Windows port >> > changes back to subversion and the qpid-port github repository > will >> > not be actively maintained and may be removed. >> > >> > -Steve >> > >> > >> > >> >> >> >> -- >> Paul Fremantle >> Co-Founder and CTO, WSO2 >> Apache Synapse PMC Chair >> OASIS WS-RX TC Co-chair >> >> blog: http://pzf.fremantle.org >> [EMAIL PROTECTED] >> >> "Oxygenating the Web Service Platform", www.wso2.com >> > > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com
