FYI here's a good clarification on what must be done in LICENSE and NOTICE files when you add a dependency or copy source code into the GEODE project. Note that the linked doc hasn't passed legal review yet (but it's really helpful if you've never looked into this subject before).
Anthony Begin forwarded message: > From: Marvin Humphrey <[email protected]> > Date: January 26, 2016 at 12:08:48 PM PST > To: "[email protected]" <[email protected]> > Subject: Re: Confusion over NOTICE vs LICENSE files > Reply-To: [email protected] > >> On Tue, Jan 26, 2016 at 11:42 AM, Todd Lipcon <[email protected]> wrote: >> I started a Google doc to try to clear this up in a simple "if/then" type >> layout: >> https://docs.google.com/document/d/1eftfjrWpOG-dRkw9dZWRfcj3p_qCeE5xC-G0Y5j29Ck/edit > > Nice work! > >> I have a bunch of confusion/open questions still, and email threads don't >> seem to be the best way to clear these things up, because different people >> have different opinions. Perhaps people could take a look at the above doc >> and add comments? This could then become a reference guide (or adendum to >> the existing licensing howto?). > > The structure of this document is actually pretty close to what I had > in mind with the first draft of the licensing how-to. I think we > should seek to integrate this material into that document. > > Once we have a patch we're happy with, we should run it by > legal-discuss@apache. > > Marvin Humphrey > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
