[Repoze-dev] Licensing of sourcecodegen and Chameleon
I'm making an attempt at packaging sourcecodegen and Chameleon for Debian, but I've immediately stumbled over licensing issues. AFAIKT all code in the repoze repository shares the same license, so I plan on copying the version from http://svn.repoze.org/repoze.tm2/trunk/LICENSE.txt. Any objections to me adding a LICENSE.txt similar to both of sourcecodegen and chameleon? Would someone with upload access to pypi be able to upload new releases once I've done this? -- Brian Sutherland ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Licensing of sourcecodegen and Chameleon
Brian Sutherland wrote: I'm making an attempt at packaging sourcecodegen and Chameleon for Debian, but I've immediately stumbled over licensing issues. AFAIKT all code in the repoze repository shares the same license, so I plan on copying the version from http://svn.repoze.org/repoze.tm2/trunk/LICENSE.txt. Technically, the effect of the contributor agreement makes it possible for Agendaless to license anything contributed to the Repoze SVN repository under that license: Code committed to the Repoze source repository (Committed Code) must be governed by the Repoze Public License (RPL) or another license acceptable to both Agendaless Consulting and the Open Source Initiative. Committer will verify that Committed Code contains the text of another license acceptable to both Agendaless Consulting and the Open Source Initiative. Until Agendaless Consulting declares in writing a license other than the RPL, only the RPL shall be used. But ethically this is Malthe's code, and the code itself has no license text in it. On chameleon.repoze.org he states Chameleon is covered by the BSD License. So I'll ask him to clarify which BSD license he means. - C ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Licensing of sourcecodegen and Chameleon
2010/1/12 Chris McDonough chr...@plope.com: But ethically this is Malthe's code, and the code itself has no license text in it. On chameleon.repoze.org he states Chameleon is covered by the BSD License. So I'll ask him to clarify which BSD license he means. BSD, as-is, dont-care. As for LICENSE.txt, I think it's more than enough to state the license by name; it's not difficult to find the full license text online and to my understanding, there are never any disputes. If I'm wrong, please anybody, commit necessary changes. \malthe ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] python 2.5 support?
On Monday 21 December 2009 11:35:21 Tres Seaver wrote:
Diez B. Roggisch wrote:
zopelib was a way to get egg-based deployment of Zope prior to the fully
egg-based 2.12. You need either to upgrade to use Zope 2.12 (and drop
zopelib), or else stay on Python 2.4.
Ok, I'm happy to upgrade to zope2.12. In fact, I just installed it. But
now obviously the recipes given on repoze.org doen't work. Googling for
zope2 WSGI-integration only leads to them.
Any suggestions on how to make zope2 work with mod_wsgi?
The function, 'ZPublisher.WSGIPublisher.publish_module' is a WSGI
application: likely what you need is a your_app.wsgi module which calls
the Zope starup code and then sets that function as 'spplication'.
Something like (untested):
# foo.wsgi
from Zope2.startup import startup
from ZPublisher.WSGIPublisher import publish_module as application
startup()
If you need to wire in other configuration, etc., then you likely want
to use a PasteDeploy config file. In that case, you need an app
factory, something like:
# your_app.py
from Zope2.startup import startup
from ZPublisher.WSGIPublisher import publish_module
def zope_app_factory(global_config, **local_config):
startup()
return publish_module
and then configure that in Paste:
[app:your_app]
use = your_app:zope_app_factory
If you get this working, let us know, and we will get something like it
added to Zope or repoze.zope2.
Ok, this is what I've got so far:
from paste import httpserver
from Zope2.Startup.run import configure
from Zope2 import startup
configure('./etc/zope.conf')
startup()
from ZPublisher.WSGIPublisher import publish_module as zope_application
def application(environ, start_response):
environ[SERVER_SOFTWARE] = bob
return zope_application(environ, start_response)
httpserver.serve(application, host='127.0.0.1', port='8080')
As you can see, you need to set that environ-key - otherwise, WSGIPublisher
will die. It appears in the returned headers, but other than that it doesn't
seem to have any impact.
I found the actual code based on this post:
https://mail.zope.org/pipermail/zope-dev/2009-December/038862.html
In there, a problem is mentioned about with certain streamed content.
And I fear I've hit that problem as well - the ZMI looks as if it's missing
parts. For example, the tab's rounded corners seem to be missing, the
tree-view of the folder-structure isn't rendered correctly and so forth.
Any suggestions on this?
Regards,
Diez
--
Diez B. Roggisch
Ableton AG, Sitz: Berlin, Amtsgericht Berlin-Charlottenburg, HRB 72838
Vorstand: Gerhard Behles, Jan Bohl, Bernd Roggendorf
Vorsitzender des Aufsichtsrats: Uwe Struck
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
