On 10/23/14, 5:23 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> When did he say that? > >Here: >"I have trouble visualising how any ASF project could have /mandatory/ >dependencies on anything from the B-list." The above quote is from the general@ thread and was not written by anyone on this list. > >I guess it depends on what mandatory means, if it's needed to in order to >work and isn't optional then we probably have a large issue. We can go ask the poster what he meant, but I am going to assume he is either mistaken or is concerned there is a dependency on some source code. For us, Falcon has a required dependency on a category B binary. I do not see any information in [1] that says that is not allowed. The installation of the modified binary package requires that you accept the CPL license for Jburg before executing the rest of the install. Here’s the section on Category B, partially condensed: *How should so-called "Weak Copyleft" Licenses be handled?* Each license in this category requires some degree of reciprocity; this may mean that additional action is warranted in order to minimize the chance that a user of an Apache product will create a derivative work of a reciprocally-licensed portion of an Apache product without being aware of the applicable requirements. Software under the following licenses may be included in binary form within an Apache product if the inclusion is appropriately labeled: * CDDL, Versions 1.0 and 1.1 <http://www.sun.com/cddl/> * CPL 1.0 <http://www.opensource.org/licenses/cpl1.0.php> (I shortened this list) By including only the object/binary form, there is less exposed surface area of the third-party work from which a work might be derived; this addresses the second guiding principle of this policy. By attaching a prominent label to the distribution and requiring an explicit action by the user to get the reciprocally-licensed source, users are less likely to be unaware of restrictions significantly different from those of the Apache License. Please include the URL to the product's homepage in the prominent label. (I removed a paragraph here) This is colloquially known as the Category B list. Also, note that the main SDK has a required Category B binary dependency on the OSMF.swc. -Alex [1] http://www.apache.org/legal/resolved.html