<br>The current Drupal CVS policy doesn't differentiate between GPL and non-GPL. The current policy is <span style="font-weight: bold;">no third party code</span>. As it's been explained to me, if users can get the code somewhere else, it doesn't belong in Drupal's CVS.
<br><br>Nedjo suggested some revisions to the CVS policy to make it easier for developers to include small javascript libraries back in March (<a href="http://drupal.org/node/124978">http://drupal.org/node/124978</a>), but AFAIK the policy is still no third party code... GPL compatible or otherwise.
<br>
<p><a name="_MailAutoSig"><span style="font-size: 10pt; font-family: Ari;">___</span><span style=""></span></a></p>
<p><span style=""><strong><span style="font-size: 10pt; font-family: Arial;">Kevin Reynen</span></strong></span><span style=""><span style="font-size: 10pt; font-family: Arial;"><br>
Integrated Media Coordinator<br>
Reynolds School of Journalism and<br>
Advanced Media Research<br>
University of Nevada, Reno</span></span></p>
<br><br><br><div><span class="gmail_quote">On 9/10/07, <b class="gmail_sendername">Anton</b> <<a href="mailto:anton.list@gmail.com">anton.list@gmail.com</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;">
On 10/09/2007, J-P Stacey <<a href="mailto:jp.stacey@torchbox.com">jp.stacey@torchbox.com</a>> wrote:<br>> My own rather basic reading of the law is that, as long as GPL and non-GPLed<br>> software types are not bundled together, then you're "more or less OK". You
<br>> can infer my legal credentials from the fact that I use such obscure<br>> terminology. But this would mean that you can link your non-GPL application<br>> dynamically to GPL libraries, but you can't compile them in statically; you
<br>> can develop the TinyMCE bridge, but the consumer of the software has to<br>> fetch TinyMCE separately.<br><br>No the reason TinyMCE isn't bundled with its bridge module isn't<br>because of incompatible licenses but Drupal policies on only allowing
<br>GPL code in CVS.<br><br>TinyMCE has a GPL compatible license (LGPL), so there is nothing wrong<br>license wise with bundling up TinyMCE with a Drupal module and<br>distributing it from your own server as a combined work under the GPL.
<br>The same is true with any other code with a GPL compatible license.<br><br>So although distributing a SMF bridge module (which sparked this<br>debate) appears to violate the GPL, distributing the TinyMCE bridge<br>module wouldn't.
<br><br>--<br>Cheers<br>Anton<br></blockquote></div><br>