Yeah, good point... I was wondering this myself as I was reading through the gigantic GPL/non-GPL apps thread today. I had already sent an email to the authors to see if they would be interested in dual licensing the source seeing as, like you said, the intent of the license is very similar.
<br><br>The module is most definitely just a wrapper around the library, making it easier for any Drupal module to utilize the IXR library but doing nothing else.<br><br>Thanks for the input,<br>Jeff<br><br><div><span class="gmail_quote">
On 9/10/07, <b class="gmail_sendername">Thomas Barregren</b> <<a href="mailto:thomas@webbredaktoren.se">thomas@webbredaktoren.se</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jeff Beeman skrev:<br>> I guess I should clear things up by actually stating what I'd like to<br>> include. I wrote a module that is a simple wrapper for the Incutio<br>> XML-RPC Library (<a href="http://scripts.incutio.com/xmlrpc/">
http://scripts.incutio.com/xmlrpc/</a><br>> <<a href="http://scripts.incutio.com/xmlrpc/">http://scripts.incutio.com/xmlrpc/</a>>), which is code. It's odd to me<br>> that it's licensed under the Artistic License, and in lieu of not
<br>> hearing back from the author(s), I've decided to release it in the<br>> style of TinyMCE, telling users to go grab the library themselves.<br><br>What you are wondering can be formulated as two questions.<br>
<br><br><br>The first question is whether it is allowed to check non-GPL libraries<br>into Drupal's CVS. As Greg Knaddison pointed out, the policy of<br><a href="http://Drupal.org">Drupal.org</a> is to discourage third party libraries in general, and
<br>non-GPL libraies in particular. See<br><br> <a href="http://drupal.org/node/66113">http://drupal.org/node/66113</a><br><br>Therefore, I think you are doing the right thing by telling people to go<br>grab the library themselves.
<br><br><br><br>The second question is whether it is allowed for a Drupal module to link<br>to a library under The Artistic License. Because Drupal has GPL, your<br>module has to be available for use under the GPL as well. See
<br><br> <a href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLModuleLicense">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLModuleLicense</a><br><br>Does that prevent your module to use a library under The Artistic
<br>License? If your module is a derived work of the library, you have<br>problem. According to FSF/GNU, the Artistic License is not compatible<br>with GPL according to FSF/GNU. See<br><br> <a href="http://www.fsf.org/licensing/licenses/index_html#ArtisticLicense">
http://www.fsf.org/licensing/licenses/index_html#ArtisticLicense</a><br><br>But if your module is not a derived work of the library, you are all<br>clear. So the second question boils down to whether your module is<br>derived work of the Incutio XML-RPC Library or not.
<br><br>Since the Incutio XML-RPC Library obviously is *designed* and *intended*<br>to be used as a library, I would have said that your module is not a<br>derivate work of the library *IF* - and that is the catch - if your
<br>module did something else than just being a "simple wrapper". But as a<br>simple wrapper around the Incutio XML-RPC Library, your module must most<br>likely be characterized as a derived work of the library. And as a
<br>consequence, it cannot be legally distributed. Sorry. :-(<br><br>The best you can do is to write to the copyright holder of the Incutio<br>XML-RPC Library and ask if the library can be dual licensed under GPL to<br>you. The Artistic License and GPL are very similar in intent, so that
<br>should not be a big issue. In fact, that is exactly how it is done for<br>Perl, for which the Artistic License once were written.<br><br><br><br>Finally, there is of course a chance that my interpretation of the<br>situation is completely wrong. I am after all not a lawyer, but only a
<br>layman. So everything I have said should be taken with a grain of salt.<br><br>Best regards,<br>Thomas<br></blockquote></div><br>