Yet we're perfectly happy to include an Apache licensed (or many other licenses) dependency with a product; and to accept numerous smaller patches under the Apache license.
It's an inconsistency and if we can't get a CLA/SGA for some piece of code that was formerly under AL 2.0, I'm not sure why it would be a blocker. Hen On Mon, Jul 18, 2011 at 5:43 PM, Craig L Russell <craig.russ...@oracle.com> wrote: > +1 > > The main thing is that Apache must be able to rely upon the license > contained in the files. > > This is the same reason that we don't routinely accept contributions that > are licensed "in the public domain". > > Just because a file says it has a particular license doesn't mean that the > contributor of that file has the legal right to contribute it. > > Bottom line: we need to establish the legal right of the contributor to > contribute any files to an Apache project. > > Craig > > On Jul 18, 2011, at 4:35 PM, Sam Ruby wrote: > >> On Mon, Jul 18, 2011 at 2:50 PM, Alan D. Cabrera <l...@toolazydogs.com> >> wrote: >>> >>> I'm just curious. Do we still need an SGA for a podling codebase that's >>> AL 2.0 licensed? >> >> Do we know that the people who placed the AL 2.0 license headers on >> that code have sufficient rights to do so? A signed statement that >> "Licensor is >> legally entitled to grant the above license." would be helpful. A >> Software Grant is probably the most straightforward way to obtain and >> record such a statement. >> >> I'm not saying that it can't be done without a Software Grant, just >> that there may be more work involved any other way. >> >>> Regards, >>> Alan >> >> - Sam Ruby >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > Craig L Russell > Secretary, Apache Software Foundation > c...@apache.org http://db.apache.org/jdo > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org