Ken I appreciate your effort in making the development process as open as possible. But I agree with Steve about the licensing issues.
I think the safest option is to expose your work through a series of JIRA's. If we need to make the code available immediately and/or collaborate with others we could create a branch. You could work off the branch and then Ted could apply the patches as an when they are made available. Rajith On Wed, Dec 9, 2009 at 11:15 AM, Steve Huston <[email protected]> wrote: > Hi Ken, > >> -----Original Message----- >> From: Ken Giusti [mailto:[email protected]] >> Sent: Wednesday, December 09, 2009 9:00 AM >> To: dev >> Subject: [QMF] public github repo for QMFv2 api work >> >> >> Hi all, >> >> Just fyi - I've set up a public git repo at github so I can >> develop the QMFv2 API code publicly. I've created this >> because I am not a committer, but I want this stuff available >> to all during development. >> >> git://github.com/kgiusti/qpid.git >> >> This repo is based on the apache qpid trunk repo on github. > > I was in a similar situation when I did the initial Windows port a > while back, and I went the git route too. I was advised by more senior > Apache people that it's not a good idea because it opens the door to > code getting in which hasn't been through the JIRA's "I license this > to Apache" check-off. If someone without a CLA drops code into your > git repo, then that goes into the svn repo, that's a big problem. > > FWIW, > > -Steve > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
