This is one of the requirements of incubation, so it will be taken care of there - but it's good for those communities to be aware of it when making their decision.
The GPL doc you refer to is actually about the combining of ASL and GPL works being possible at all, regardless of the requirements here. The following are some guidelines, though it'd be best to consider individual cases on legal-discuss@ which will have to happen during incubation. As for what you can depend on/include as an ASF project, GPL is not possible because it affects the license of the whole. LGPL may be possible, but only if optional and not distributed with the application. There is ongoing discussion around this. The key point is that the ASF retain its ability to distribute software that doesn't have conditions beyond those in the ASL (yes, there are some exceptions out there). Cheers, Brett On 11/9/05, Bruce Snyder <[EMAIL PROTECTED]> wrote: > Even beyond the requirements of incubation, there exists a whole host > of issues surrounding the use of code with a license other than AL. I > know that ServiceMix and WADI integrate such code. So how is this to > be sorted out? For example, I know that the ASF has a long-standing > policy on the use of GPL compatibility: > > http://www.apache.org/licenses/GPL-compatibility.html > > In addition to the whole GPL can of worms, how about the TranQL > requirement for Oracle and DB2 JDBC drivers? >
