-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roger Ineichen wrote:

Hi Tres

...

Betreff: Re: [Zope-dev] z3c.javascript license question

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Martijn Faassen wrote:

...

Hi there,

On svn.zope.org we have a library called z3c.javascript. Never got released to pypi, but it did get released to download.zope.org/distribution

It basically contains a pile of javascript libraries. These have very non-ZPL licenses.

I wonder whether anyone at zope corporation ever got permission for checking these in?

What shall we do with this stuff? I'm tempted to remove it wholesale, except z3c.widget uses bits in it, and that in turn is used by megrok.form, which is how all this came to light. z3c.widget is released on pypi (though newer releases exist in download.zope.org/distribution again).

Wwe will probably be able to rewrite megrok.form to lose the z3c.widget dependency easily enough, so I'm going to propose we do this on grok-dev.

I see no ZC-employee checkins at all in the svn log, which starts in May 2006. This thread from October 2006 points out licensing issues:

http://news.gmane.org/find-root.php?group=gmane.comp.web.zope. zope3&article=19324 +1 to removal, perhaps after some kind of svn export process.: those who maintain the package should host it elsewhere. The tarballs should be removed from download.zope.org, as well.

I remember that I added a correct license header some years ago for z3c.javascript.

There are several checkins which mention adding licenses for the varioius JS libraries: the problem is that non-ZC contributors are never supposed to check in any code which they don't own, and which they can therefore license under the ZPL. The purpose of this restriction was to ensure that folks using software from the repository could be confident that they didn't need to audit licenses, because effectively everything would be ZPL: the few exceptions were supposed to have been verified as being compatible with (and equally or more permissive than) the ZPL. I think I recall that Jim ripped out an integration package for the Ext Javascript framework precisely because the licensing for Ext was initially questionable, and later became outright unacceptable. Now that the copyrights are transferred to the Zope Foundation, essentially *nobody* can check in non-ZPL code, without a special exemption from the ZF board or its delegate (nobody is yet appointed to handle this). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ6Nz6+gerLs4ltQ4RAppjAJ0ZIOWw00XtGFQiVxFumUOWr7vGvQCeKSGi Bx+MmnmOY0D11UUMxgAsnbY= =xdSO -----END PGP SIGNATURE-----

Hi! 2009/4/18 Tres Seaver <tseaver@palladion.com>: [super snip]

Now that the copyrights are transferred to the Zope Foundation, essentially *nobody* can check in non-ZPL code, without a special exemption from the ZF board or its delegate (nobody is yet appointed to handle this).

I am looking towards becoming a SVN contributor so this question interests me a lot. You mentioned the copyrights were transfered to ZF which is what I recall reading a while ago. But when I last checked http://www.zope.org/DevHome/CVS/Contributor.pdf [1] it said that contributors transfer their copyright to ZC. Is it a question of the form being obsolete? Regards, Ben. [1] Note I just checked and it returns a 404 right now...

On Fri, Apr 17, 2009 at 2:48 PM, Tres Seaver <tseaver@palladion.com> wrote: [snip

Now that the copyrights are transferred to the Zope Foundation, essentially *nobody* can check in non-ZPL code, without a special exemption from the ZF board or its delegate (nobody is yet appointed to handle this).

BTW, there is an exemption for this area: http://svn.zope.org/repos/main/non-zpl-doc-resources/ (It was created when I asked for adding some resource file for buildout.org)

From the readme file:

Non-ZPL documentation resources can be checked into this directory if you have received explicit permission from the Zope Foundation to do so. The workflow currently is simply to mail Martijn Faassen (faassen@startifact.com) with a description of what you want to do. In order to use these documentation resources in your own sphinx project, create a subdirectory here and an svn:external to that subdirectory from the sphinx project in question. -- Baiju M