On Wed, Dec 11, 2013 at 2:24 AM, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote:
> It would be great if we could get a resolution on some of the JIRA's in > legal, e.g. > > https://issues.apache.org/jira/browse/LEGAL-26 > https://issues.apache.org/jira/browse/LEGAL-27 > https://issues.apache.org/jira/browse/LEGAL-31 > https://issues.apache.org/jira/browse/LEGAL-136 +1 The continuing lack of clear resolution also impacts the Incubator. Podlings challenge us with "You say do X, but Apache Foo does Y -- where is it documented that we have to do X?" Then we go down the path of hunting up Board member quotes and past threads on legal-discuss. It would make things easier on all Apache TLPs and Incubator podlings if we could get the following elements in sync: * Apache Legal policy documentation. * http://www.apache.org/dev/licensing-howto.html * Maven's processes. * The actual LICENSE/NOTICE practices for the ASF's top ten or so most popular products. > The most critical one to the Maven PMC is LEGAL-26: Perhaps, though the way that Maven would implement LEGAL-26 (LICENSE/NOTICE in svn) is impacted by LEGAL-27 (LICENSE/NOTICE must reference *only* bundled dependencies). I'm not on the Legal Affairs committee, but I did write most of the Licensing How-To. Come January, I'd like to do what I can to move the process forward. A lot of valuable developer time has been wasted over the years rehashing these issues over and over again, and it's not like most developers relish this stuff. Clear policy documentation would be a valuable contribution to all of the Foundation's projects. Marvin Humphrey --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
