On Jun 4, 2013, at 9:46 AM, Alan Cabrera <l...@toolazydogs.com> wrote:
> > On Jun 4, 2013, at 5:58 AM, Kevan Miller <kevan.mil...@gmail.com> wrote: > >> >> On Jun 4, 2013, at 8:46 AM, Greg Stein <gst...@gmail.com> wrote: >> >>> On Jun 4, 2013 4:22 AM, "ant elder" <ant.el...@gmail.com> wrote: >>>> >>>> This "when in doubt leave it out" approach has gone a long way at >>>> smoothing podling release reviews compared to the olden days. >>> >>> Seriously? The inserted code uses our own license! Go look at 4(d) and tell >>> me we should not insert a notice. It is both Right, and what is demanded by >>> our own license. >> >> I haven't seen a description of where this code is coming from. Is it a >> contribution from LinkedIn? Is it some open source code from LinkedIn that >> we are copying into our svn from some other project? >> >> If it's the former and LinkedIn has requested attribution for their >> contribution, then let's observe their request and add attribution to the >> NOTICE. >> >> If it's the latter *and* the subject code has a NOTICE file, then we >> absolutely must include the relevant portions of their NOTICE in our NOTICE. >> Otherwise, 4 (d) doesn't require us to do anything. Agreed? > > > The code is internal LinkedIn code that I copied with the appropriate > permissions. Attribution was requested. Cool. Thanks. So, NOTICE should contain the attribution and copyright. --kevan --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
