Hey,<br><br>I was trying to find a way to solve the licenses conflicts with the ExtJS guys. And now I need to back to you guys, what could you say about this?:<br><br>"""<br>You can distribute Ext JS with a ZPL extension, but Ext JS must remain
clearly GPL. It's two licenses side by side. So if you 'package' Ext
with the ZPL extension, and developers download the package with the
expectation that the whole is ZPL licensed, that is a problem. If
licensing on the SVN can include both ZPL and GPL, then that could work.<br>"""<br><br>I'm not sure if that it's possible in <a href="http://svn.zope.org">svn.zope.org</a><br><br><br><div class="gmail_quote">
On Mon, May 4, 2009 at 3:32 PM, Martijn Faassen <span dir="ltr"><<a href="mailto:faassen@startifact.com" target="_blank">faassen@startifact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Santiago Videla wrote:<br>
> Hey,<br>
><br>
> As far I understand, we can't package ExtJS and publish it on pypi....<br>
> :( Developers must download it manually from their web site.<br>
<br>
</div>All these extensive license pages which seem to add interpretations to<br>
the GPL 3.0 *plus* that you now have the understanding that you're *not*<br>
allowed to publish ExtJS on PyPI even though the GPL explicitly allows<br>
such redistribution reaffirm my belief to stay away from ExtJS due to<br>
licensing confusion. :)<br>
<br>
Note that the "open source" exception (for whatever that is worth<br>
anyway) only pertains to ZPL 2.0, which hasn't been in use for some<br>
years now. I will note that this page of the FSF *does* claim the ZPL<br>
2.1 is compatible with the GPL 3.0:<br>
<br>
<a href="http://www.gnu.org/philosophy/license-list.html#GPLCompatibleLicenses" target="_blank">http://www.gnu.org/philosophy/license-list.html#GPLCompatibleLicenses</a><br>
<div><br>
> The only thing I can imagine in order to create hurry.extjs, it's to say<br>
> in the README:<br>
><br>
> 1) Download ExtJS from here: http://.... and place it in your home<br>
> directory.<br>
> 2) Include "hurry.extjs" in your setup.py<br>
> 3) run ./bin/buildout (hurry.extjs will extract and copy ExtJS for you)<br>
><br>
> Does have any sense?<br>
<br>
</div>Yeah, something like this might work. You could simply instruct people<br>
to download ExtJS and include a <resourceDirectory> statement in their<br>
app to publish it.<br>
<div><div></div><div><br>
Regards,<br>
<br>
Martijn<br>
<br>
_______________________________________________<br>
Grok-dev mailing list<br>
<a href="mailto:Grok-dev@zope.org" target="_blank">Grok-dev@zope.org</a><br>
<a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Santiago Videla<br><a href="http://www.revolucionesweb.com.ar" target="_blank">www.revolucionesweb.com.ar</a><br><a href="http://www.linkedin.com/in/svidela" target="_blank">http://www.linkedin.com/in/svidela</a><br>
<br>Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que l@s tod@s somos.<br>