Hey Jakob My initial request in INFRA-7412 was based on not seeing any IP clearance [1] for the hello-samza repo. This is due to it not being apart of the initial import of the codebase and it did not originate from the project since it has been at the ASF. I'm happy to import the repo for you once the right of use has been established for the ASF, if it is taken care of within the original CCLA and can be confirmed then great.
Thanks for the due diligence on this -Jake [1]: http://incubator.apache.org/ip-clearance/ip-clearance-template.html On Wed, Mar 12, 2014 at 3:28 PM, Jakob Homan <jgho...@gmail.com> wrote: > re: Samza > > We've got a second git repository we'd like to import, > https://github.com/linkedin/hello-samza, which is a tutorial and > quickstart > on the Samza project. This was originally kept separate from the code for > two reasons (a) making it stand-alone made it easier for it just be > turn-key after cloning and (b) to make it faster to iterate on. However, > it's turned out there's lots of interest in the hello-samza itself, which > is being directed towards the podling. > > I started work on IP clearance to import it in, but when I talked with LI's > legal department about a second CCLA (per the IP Clearance page), they were > of the opinion that the original CCLA covered this repo as well: > > LI counsel on open source matters: "Hello-samza is ancillary to Samza and > thus fits within a broadly interpreted Exhibit B to the original Samza > CCLA. In other words, it's already covered, with no legal need for a new > CCLA. Also worth noting that we're the donor of both Samza and > hello-samza, so a key problem that would be resolved by having the > separate, new CCLA (i.e. substantial donation of code by a different > company) is actually a problem we do not have." > > This sounds reasonable to me and saves some paperwork. Are there any > objections to just importing the second git repo? The Samza community has > voted to incorporate the code: http://bit.ly/1lX414U > > -Jakob >
