Re: [Zope-dev] Legal formalities to accept log and design
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baiju M wrote: > On Tue, Jan 26, 2010 at 11:08 PM, Tres Seaver wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Baiju M wrote: >> >>> What about committing SVG (source) file, so that others can modify >>> easily. >> How doe the SVG source files interact with the (TrueType, I presume?) >> font file? > > Font is TrueType, but I am not sure about how it is embedded in SVG. > >>> BTW, logos comes under trademark law, which is different from >>> copyright law. Or is it like the actual source files can be covered >>> under copyright, so that we can use a license based on copyright >>> law ? >> Committers can't check in the GPL'ed font file itself to SVN without a >> waiver from the board, nor any files which count as "derived works" (and >> therefore must be GPL'ed), unless the "derived work" is covered by the >> font exception. > > I will only commit the SVG, PNG, ICO & JPEG formats, is that Ok ? > > BTW, as I mentioned the font has "font exception". I think that should be fine. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktfu7kACgkQ+gerLs4ltQ5yyQCfYWdqyn7syethrq/RWdWwYfwk S00AoIL6FHmsaxQM/Hh4pX5m8HvpDfQa =jfln -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Legal formalities to accept log and design
On Tue, Jan 26, 2010 at 11:08 PM, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Baiju M wrote: > >> What about committing SVG (source) file, so that others can modify >> easily. > > How doe the SVG source files interact with the (TrueType, I presume?) > font file? Font is TrueType, but I am not sure about how it is embedded in SVG. >> BTW, logos comes under trademark law, which is different from >> copyright law. Or is it like the actual source files can be covered >> under copyright, so that we can use a license based on copyright >> law ? > > Committers can't check in the GPL'ed font file itself to SVN without a > waiver from the board, nor any files which count as "derived works" (and > therefore must be GPL'ed), unless the "derived work" is covered by the > font exception. I will only commit the SVG, PNG, ICO & JPEG formats, is that Ok ? BTW, as I mentioned the font has "font exception". Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Legal formalities to accept log and design
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baiju M wrote: > What about committing SVG (source) file, so that others can modify > easily. How doe the SVG source files interact with the (TrueType, I presume?) font file? > BTW, logos comes under trademark law, which is different from > copyright law. Or is it like the actual source files can be covered > under copyright, so that we can use a license based on copyright > law ? Committers can't check in the GPL'ed font file itself to SVN without a waiver from the board, nor any files which count as "derived works" (and therefore must be GPL'ed), unless the "derived work" is covered by the font exception. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktfKHUACgkQ+gerLs4ltQ4GUQCgw3iyV5Wy0Rch+lebWdI3F3X0 RowAn0LuZEvvaVT7Ho1T7gQZVA6EUebY =srCh -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Legal formalities to accept log and design
On Tue, Jan 26, 2010 at 10:13 PM, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Christian Theune wrote: >> On 01/25/2010 03:15 AM, Baiju M wrote: >>> Hi Christophe, >>> >>> On Mon, Jan 25, 2010 at 12:45 AM, Christophe Combelles >>> wrote: maybe just be sure the original author won't claim anything in the future? ie. the logo should be released with a free licence. Just to avoid the kind of troubles we had with new.zope.org >>> I will look into the concerns (GPL font exception) raised by Tres. >>> Which license would be useful for a logo ? >> >> That's actually interesting from the perspective that stuff that goes >> into zope.org SVN needs to be ZPL. The foundation might want to check >> for an exception WRT logos, maybe. > > The FSF's font exception turns out to be mostly irrelevant for Baiju's > purposes: his "document" (an image) doesn't "embed" the font itself, > but merely contains pixels generated by rendering the font. In > copyright terms, this is no different than ink on paper printed from > metal type: the font author has no claim on the ink / paper as a > "derived work" under copyright law. What about committing SVG (source) file, so that others can modify easily. BTW, logos comes under trademark law, which is different from copyright law. Or is it like the actual source files can be covered under copyright, so that we can use a license based on copyright law ? Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Legal formalities to accept log and design
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Theune wrote: > On 01/25/2010 03:15 AM, Baiju M wrote: >> Hi Christophe, >> >> On Mon, Jan 25, 2010 at 12:45 AM, Christophe Combelles wrote: >>> maybe just be sure the original author won't claim anything in the future? >>> ie. the logo should be released with a free licence. Just to avoid the kind >>> of >>> troubles we had with new.zope.org >> I will look into the concerns (GPL font exception) raised by Tres. >> Which license would be useful for a logo ? > > That's actually interesting from the perspective that stuff that goes > into zope.org SVN needs to be ZPL. The foundation might want to check > for an exception WRT logos, maybe. The FSF's font exception turns out to be mostly irrelevant for Baiju's purposes: his "document" (an image) doesn't "embed" the font itself, but merely contains pixels generated by rendering the font. In copyright terms, this is no different than ink on paper printed from metal type: the font author has no claim on the ink / paper as a "derived work" under copyright law. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktfG5cACgkQ+gerLs4ltQ5ysACgtPRMvAIFx0doVQM+egDxrg1c vZsAn1jvn7UT7d6GeN3Z72dwN+XXCblP =BiuS -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing coverage support
On Sunday 17 January 2010, Martin Aspeli wrote:
> Stephan Richter wrote:
> > On Sunday 17 January 2010, Martin Aspeli wrote:
> >> I'm using zope.testing-3.7.7, which is what comes with Zope 2.12.
> >
> > Here is what I have in effectively any package:
> >
> > [coverage-test]
> > recipe = zc.recipe.testrunner
> > eggs = pkg [test]
> > defaults = ['--coverage', '../../coverage']
> >
> > [coverage-report]
> > recipe = zc.recipe.egg
> > eggs = z3c.coverage
> > scripts = coverage=coverage-report
> > arguments = ('coverage', 'coverage/report')
>
> Thanks!
>
> As a matter of constructive criticism, it would be useful to have
> something like this on the z3c.caching PyPI page. Right now, there is no
> way that I can see to understand how the package is meant to be used
> from that page, or any of the other documentation.
>
> It'd also be useful to note that enscript must be installed for syntax
> highlighting to work. I only figured that out by reading the source.
Yeah, I agree. I talked to Ned (the author of coverage.py) last week and he
told me that the newer versions of coverage.py do HTML reporting including
syntax highlighting. I wonder whether we should simply pull in his latest
code.
Regards,
Stephan
--
Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication
Hi, Christian Theune wrote: > On 01/26/2010 03:30 PM, Souheil CHELFOUH wrote: >> Well, the first step is already to cut the dependencies and get a sane >> tree and a reusable package. >> The second step, however, if people feel like it, will be to refactor >> a bit and _that_ will need careful planning, yes. >> But, one thing at a time :) >> >> However, I'll polish a bit zope.plugabbleauth and it will be eligible >> for a release, I guess. > > Sounds like a plan. :) Cool! regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication
On 01/26/2010 03:30 PM, Souheil CHELFOUH wrote: > Well, the first step is already to cut the dependencies and get a sane > tree and a reusable package. > The second step, however, if people feel like it, will be to refactor > a bit and _that_ will need careful planning, yes. > But, one thing at a time :) > > However, I'll polish a bit zope.plugabbleauth and it will be eligible > for a release, I guess. Sounds like a plan. :) -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development smime.p7s Description: S/MIME Cryptographic Signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication
Well, the first step is already to cut the dependencies and get a sane tree and a reusable package. The second step, however, if people feel like it, will be to refactor a bit and _that_ will need careful planning, yes. But, one thing at a time :) However, I'll polish a bit zope.plugabbleauth and it will be eligible for a release, I guess. 2010/1/26 Christian Theune : > Hi, > > On 01/26/2010 03:02 PM, Jan-Wijbrand Kolman wrote: >> Hi, >> >> >> Just my quick 2 euro cents here: >> >> As far as I can tell, what Souheil did so far is no architectural change, >> but a >> change like so many in the recent past where a zope.app.something package has >> been refactored into a zope.something package and keeping backwards >> compatibility in zope.app.something. >> >> I'm not sure how this became looking way bigger than it is, except for the >> explicit requests for feedback by Souheil. He requested feedback, I guess, >> as he >> might not yet be completely confident about making these changes and needs >> some >> support - I can fully understand that myself. > > Thanks for stepping in -- in addition to Martijn whose ghost is now > haunting me ... ;) > > I think there's a communication problem here. I was asserting something > about slowing down architectural changes in general but also having the > feeling that he's talking about architectural changes and thus asking > for feedback. So Souheil naturally kept running with that ... > > Then I went off and talked about stuff I imagine "could happen" while > doing architectural changes anyway ... so that's how it gre. > > So I guess I should be writing a proposal for that stuff. > > If it's a pure dependency refactoring, well then, that's what we already > all agreed about. Isn't it? > > Christian > > -- > Christian Theune · c...@gocept.com > gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany > http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 > Zope and Plone consulting and development > > ___ > Zope-Dev maillist - zope-...@zope.org > https://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > https://mail.zope.org/mailman/listinfo/zope-announce > https://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication
Hi, On 01/26/2010 03:02 PM, Jan-Wijbrand Kolman wrote: > Hi, > > > Just my quick 2 euro cents here: > > As far as I can tell, what Souheil did so far is no architectural change, but > a > change like so many in the recent past where a zope.app.something package has > been refactored into a zope.something package and keeping backwards > compatibility in zope.app.something. > > I'm not sure how this became looking way bigger than it is, except for the > explicit requests for feedback by Souheil. He requested feedback, I guess, as > he > might not yet be completely confident about making these changes and needs > some > support - I can fully understand that myself. Thanks for stepping in -- in addition to Martijn whose ghost is now haunting me ... ;) I think there's a communication problem here. I was asserting something about slowing down architectural changes in general but also having the feeling that he's talking about architectural changes and thus asking for feedback. So Souheil naturally kept running with that ... Then I went off and talked about stuff I imagine "could happen" while doing architectural changes anyway ... so that's how it gre. So I guess I should be writing a proposal for that stuff. If it's a pure dependency refactoring, well then, that's what we already all agreed about. Isn't it? Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication
Hi, Christian Theune wrote: > On 01/26/2010 09:32 AM, Souheil CHELFOUH wrote: >> I hear you and understand you. > > Thanks. :) > >> I'm not advertizing for an immediate and brainless action. >> What I did this week end is simply to split the PAU from all the >> components provided with it (well, most of it). >> That was motivated by my current work and by the will to see the >> dependencies become cleaner and the code shorter. >> I understand that the momentum is not everything, but when I can >> dedicate myself to a task, be motivated by it and paid for it, then, I >> don't see any reasons to hold back ;-) > > Right. That's pretty much how I feel myself. ;) > >> In this case, I'll just wait for your feedbacks, zope devs, and we'll >> take the time (obviously) to do the things correctly. > > I know that it's always nice to be able to immediately reap the fruits > from your work and I hate it having to go with "about to be outdated" > code with a project, but in the long run some patience will get us further. > > Thanks for understanding! > >> Let me know what you guys think, about what has to be done, when you can > > Something we need to sort out is keeping "open reviews" or "open > proposals" on the radar. > > Can you please add a blueprint here: > https://blueprints.launchpad.net/zopetoolkit/ > > Also, can you add a proposal page to the documentation that points out > what you already implemented and what you intend to achieve globally? Just my quick 2 euro cents here: As far as I can tell, what Souheil did so far is no architectural change, but a change like so many in the recent past where a zope.app.something package has been refactored into a zope.something package and keeping backwards compatibility in zope.app.something. I'm not sure how this became looking way bigger than it is, except for the explicit requests for feedback by Souheil. He requested feedback, I guess, as he might not yet be completely confident about making these changes and needs some support - I can fully understand that myself. regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing 3.8.7: downgrade the deprecation warning
On Tue, Jan 26, 2010 at 7:49 AM, Marius Gedminas wrote: > Any ideas about > fixing the deprecation warning caused by renormalizing.py? All it does > is > > 'import doctest' > > which, due to Python's unfortunate import semantics, is interpreted as > > 'from zope.testing import doctest' > Ideas? It's not real pretty, but you can do absolute imports in Python 2.4 like so: import imp name = 'doctest' doctest = imp.load_module(name, *imp.find_module(name)) Manuel uses this technique to import doctest (Manuel also has a submodule named "doctest"). -- Benji York ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing 3.8.7: downgrade the deprecation warning
On Jan 26, 2010, at 7:49 AM, Marius Gedminas wrote: > I got tired of seeing things like > > /home/mg/tmp/buildout-eggs/zope.testing-3.8.6-py2.5.egg/zope/testing/testrunner/debug.py:23: > DeprecationWarning: zope.testing.doctest is deprecated in favour of the > Python standard library doctest module > from zope.testing import doctest > > and since zope.testing's trunk hasn't got the problem fully licked yet > (importing zope.testing.renormalizing causes a deprecation warning > about zope.testing.doctest), I created a 3.8 branch based on the last > public zope.testing release (3.8.6), downgraded the DeprecationWarning > into a PendingDeprecationWarning, and released zope.testing 3.8.7. > > zope.testing's trunk is henceforth known as 3.9.0pre. Any ideas about > fixing the deprecation warning caused by renormalizing.py? All it does > is > > 'import doctest' > > which, due to Python's unfortunate import semantics, is interpreted as > > 'from zope.testing import doctest' > > Perhaps a > > from __future__ import absolute_import > > would help at the top? But it's only availably starting from Python > 2.5, and I think zope.testing wants to be compatible with Python 2.4 > too. > > Ideas? There's always the pre-2.5 icky __import__ hack for this if you need it. You probably know it, or I can look it up if you want, but that's the only approach I know of for this kind of issue in pre-2.5 Gary ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.testing 3.8.7: downgrade the deprecation warning
I got tired of seeing things like /home/mg/tmp/buildout-eggs/zope.testing-3.8.6-py2.5.egg/zope/testing/testrunner/debug.py:23: DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python standard library doctest module from zope.testing import doctest and since zope.testing's trunk hasn't got the problem fully licked yet (importing zope.testing.renormalizing causes a deprecation warning about zope.testing.doctest), I created a 3.8 branch based on the last public zope.testing release (3.8.6), downgraded the DeprecationWarning into a PendingDeprecationWarning, and released zope.testing 3.8.7. zope.testing's trunk is henceforth known as 3.9.0pre. Any ideas about fixing the deprecation warning caused by renormalizing.py? All it does is 'import doctest' which, due to Python's unfortunate import semantics, is interpreted as 'from zope.testing import doctest' Perhaps a from __future__ import absolute_import would help at the top? But it's only availably starting from Python 2.5, and I think zope.testing wants to be compatible with Python 2.4 too. Ideas? Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Mon Jan 25 12:00:00 2010 UTC to Tue Jan 26 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jan 25 20:36:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013449.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jan 25 20:38:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013450.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 25 20:40:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013451.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 25 20:42:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013452.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 25 20:44:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013453.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 25 20:46:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013454.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] quitting the ZTK steering group
On Tue, Jan 26, 2010 at 11:20, Christian Theune wrote: > I think this has to do with too little communication going on within the > steering group (one of the founding premises was to do as little > "backroom" communication as possible which ended up in no backroom > communication, which IMHO doesn't allow us to function as a group). The positive thing to take out of this is how well things have worked anyway. Apparently the Steering Group did not work as a group, but things got steered pretty well anyway. Admittedly through intense slogging on email lists, but that would have happened without the steering group as well. This community builds a loose sort of almost-consensus about the future by long discussions on zope-dev, and that's OK. People then act, or not, based on that almost-consensus. The steering group acknowledged this from the start by saying that discussions should be in the open, so as not to leave the rest of the community in the dark. And even if the steering group didn't work, this process has worked, although possibly through insane amounts of work on Martijns part. Without that work, the process will probably be a lot slower. But it will still work. So no reason for panic. :) So again, Martijn, thanks for trying so hard with the steering group. Even if the group didn't make a difference, you did, and with or without the group, I'm sure you will continue to make that difference. But now we need to look forward towards 4.0 of the ZCA. Onwards and upwards! :-) -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing coverage support
Christian Theune wrote: >> As a matter of constructive criticism, it would be useful to have >> something like this on the z3c.caching PyPI page. Right now, there is no > > That's a typo, right? D'oh; z3c.coverage, I meant. >> way that I can see to understand how the package is meant to be used >> from that page, or any of the other documentation. >> >> It'd also be useful to note that enscript must be installed for syntax >> highlighting to work. I only figured that out by reading the source. > > Also, if this functionality is useful, I'd rather see this folded into > the mainstream runner. +1 > At some point, the test runner recipe could also be provided by the > zope.testing package itself IMHO. +1 Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] quitting the ZTK steering group
Hi, I'm just putting in some 0.02EUR here to give some feedback about the current state. On 01/22/2010 10:27 PM, Martijn Faassen wrote: > Hi there, > > This is to announce my withdrawal from the Zope Toolkit steering > group. I'm also sad to see you go -- hopefully with the chance of seeing you back and taking this as a motivation to improve zope-dev in a way that might make you come back in some future. ;) (I'll address the zope-dev list in the remainder of the post, so please excuse me for addressing you in third person from now on.) > I withdraw from the Zope Toolkit steering group for two reasons: > > * The steering group is not working as a group. Most steering group >members haven't been doing much steering. This left me by myself to >try to give direction. I cannot blame the others for committing >their time differently, but this isn't the balance of work I signed >up for. > > * Trying to steer the ZTK took a large amount of my energy. The >discussions are quite draining and the benefit to me has not >been worth the frustration. > > In the past year we've made large changes to the dependency structure > of packages, cleaning it up. We've also improved compat testing and > dependency analysis infrastructure a lot. > > That's the technical part. The community consequences are also > important. We've been able to redefine the focus of various projects > under the Zope umbrella. Separating the concern of the ZTK from Zope 3 > made another refocusing project like BlueBream possible, and made more > clear the relation Grok and Zope 2 have with the libraries in the ZTK. > > I think there is a lot more that can be done, but I don't want to feel > responsible for it. I agree with Martijn that we didn't get the steering group going as well as we thought. We haven't analyzed the issue yet, one part being that Martijn was able to act much more timely than Jim, Stephan and I are able to. I think this has to do with too little communication going on within the steering group (one of the founding premises was to do as little "backroom" communication as possible which ended up in no backroom communication, which IMHO doesn't allow us to function as a group). > Here is my analysis of problems with the ZTK: > > * Unclear leadership situation. I tried to resolve this by founding >the ZTK project and steering group in the first place. Besides the >time investment problems mentioned before, this (my?) leadership is >also not fully accepted, or its judgment is not fully trusted. > > * Even though endless discussions take place, communication is >frequently poor and frustrating at the same time. Bigger changes >take too much energy to discuss. People give up even trying to >cooperate and do it alone as it's a way to get things done. This >creates a vicious cycle. > > * The commitment of parties to work together on the ZTK is >fragile. Witness Zope 2 withdrawing from the ZTK quickly >after some disagreements (with me). > > My commitment to leading the ZTK as a community project has now > disappeared as well. I am primarily interested in the development of > Grok. I came to the ZTK to tackle important issues for Grok, and now am > going to focus my attention on Grok again. This means that I may > contribute to the vicious cycle I mentioned above, but so be it. > > What this means for the ZTK or the steering group I do not know. The ZTK > matters to me as a foundation to Grok. In a wider sense, I believe that > a broader base of people using the ZTK is good for the Zope community > and Grok as well. I also believe a person or group who offers leadership > and has a final say is healthy for the project -- just random interested > people voting -1 or +1 or -1000 or +1000 on the mailing list is a recipe > for stagnation. We will have to see what the steering group, or anyone > else, will come up with. As much as I admire the amount of work that Martijn was able to put although it wasn't sustainable I think that the point of the steering group can't be to micro-manager discussions about larger improvements. I'm happy to see long discussions going on in general, but at least I don't have the ability to follow them right away. I think we need to balance speed with other qualities of our process. For one example: I didn't yet read the thread about the reversing of changes in the SVN. But honestly reverting someones work that wasn't agreed upon before is perfectly fine. SVN doesn't loose those changes anyway and if you don't get reverted then we were able to act quicker than having lengthy discussions at all times. Right now, I think I need to ponder the structure for a while and discuss with Stephan and Jim how they think about what's happened. Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope an
Re: [Zope-dev] Zope 3.4 and the way forward
Hi Marius, On Wed, Dec 30, 2009 at 4:37 AM, Marius Gedminas wrote: > So, what's the way forward for existing Zope 3.4 (KGS) users? I hope you might be heard about "BlueBream". My ideas is to create a successor to "Zope 3". As part of this effort, I started working on a KGS based on zopetookit: svn://svn.zope.org/repos/main/bbkit/trunk Well, I don't want to speak more as we don't have anything to show. Anyway, here are few links: http://wiki.zope.org/bluebream/BlueBreamWiki http://bluebream.zope.org/doc/1.0/index.html BTW, I am fine if anyone focus on a ZopeApp KGS to upgrade from Zope 3.4 KGS. Then, BueBream will use that KGS. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] quitting the ZTK steering group
* Martijn Faassen [2010-01-22 22:27]: > This is to announce my withdrawal from the Zope Toolkit steering group. I'm saddened to hear this. I feel that many if not all of the things you were trying to set in motion in our community are desperately needed. I'm sorry to hear that you have been worn out trying. Thanks for all the energy you've put into this. Wolfgang ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 3.4 and the way forward
On 12/30/2009 12:17 AM, Martijn Faassen wrote: > Hey, > > Marius Gedminas wrote: >> So, what's the way forward for existing Zope 3.4 (KGS) users? >> >> Rewrite our apps so we don't depend on anything in zope.app and switch >> to the ZTK? > > That's not possible as far as I can see, as the Zope 3.4 KGS doesn't > support this. No zope.container yet, for instance, so no way to get rid > of zope.app.container. It's only possible to start such an app rewrite > once you're on the ZTK. (we don't know whether it's possible to complete > such a rewrite. we will have to see) > >> Band together and release a Zope 3.5 KGS, which would be a strict >> superset of the ZTK 1.0? > >> Band together and release a ZopeApp 1.0 KGS which would be a strict >> superset of the ZTK 1.0? > > Yes. Possibly a Zope 3.5 KGS that extends that further, I'm not sure. > >> (In which case, why not call it Zope 3.5 KGS?) > > Because Grok can use the ZopeApp 1.0 KGS as well. So can Zope 2 users > who need to upgrade away from zope.app packages. (I think!) > >> Forget all this open-source sharing stuff and maintain our own separate >> versions.cfg files with ad-hoc version mixes? > > I'm trying to remember this open source sharing stuff and avoid ad-hoc > version mixes where we can. > >> Personally, I'd prefer option 1 (if there were docs to tell me what to >> do to get rid of zope.app, which is implausible) or option 2. > > I prefer option 3 (ZopeApp KGS), because there's a greater opportunity > for that old open source sharing thing. And also because it would help > us get rid of the somewhat confusing "Zope 3" terminology. Hmm. Just because I've been lagging and do get some newcomer questions here and there: is there an overview of what KGSs exist and what they "mean"? Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Adapter registration in ZCML provides IUserPreferredCharsets lost ?
On 01/11/2010 06:25 AM, Chris McDonough wrote: > Baiju M wrote: >> On Mon, Jan 11, 2010 at 10:22 AM, Baiju M wrote: >>> Hi All, >>> There was an adapter registration provides IUserPreferredCharsets. >>> I can see it has moved to zope.i18n.locales with some others here: >>> http://svn.zope.org/zope.app.i18n/trunk/src/zope/app/i18n/configure.zcml?rev=98208&r1=95495&r2=98208 >>> >>> But, I cannot see it ever reached here ? >>> http://svn.zope.org/zope.i18n/trunk/src/zope/i18n/locales/configure.zcml?rev=75140&view=log >>> >>> Can I add it there ? >>> >>> Instead of "zope.app.publisher.browser.ModifiableBrowserLanguages", >>> I will use the new location: >>> "zope.publisher.browser.ModifiableBrowserLanguages" >> >> This will make zope.publisher as dependency for zope.i18n, which may not be >> a good idea. Please suggest me where we will move this ? > > I don't know exactly where to move this, but making zope.publisher a dep of > zope.i18n would be bad. Right. I think we might not currently have a good place for putting in cross-concern "default policy" rules. IMHO this isn't a responsibility of any of the involved packages (zope.i18n/zope.publisher). Does zope.app.i18n still exist? In that case the ZCML statement might continue living there. Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] vocabularies missing wihtout zope.app.schema
On 01/11/2010 02:26 PM, Roger wrote: > Hi all > > I'm not happy with the current vocabulary registry > concept. Please note that vocabularies have had a successor concept for a while: sources. They are much cleaner and split their concerns for various aspects much more nicely. They don't provide a registry concept, though. Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication
Hi, On 01/26/2010 09:32 AM, Souheil CHELFOUH wrote: > Christian, > > I hear you and understand you. Thanks. :) > I'm not advertizing for an immediate and brainless action. > What I did this week end is simply to split the PAU from all the > components provided with it (well, most of it). > That was motivated by my current work and by the will to see the > dependencies become cleaner and the code shorter. > I understand that the momentum is not everything, but when I can > dedicate myself to a task, be motivated by it and paid for it, then, I > don't see any reasons to hold back ;-) Right. That's pretty much how I feel myself. ;) > In this case, I'll just wait for your feedbacks, zope devs, and we'll > take the time (obviously) to do the things correctly. I know that it's always nice to be able to immediately reap the fruits from your work and I hate it having to go with "about to be outdated" code with a project, but in the long run some patience will get us further. Thanks for understanding! > Let me know what you guys think, about what has to be done, when you can Something we need to sort out is keeping "open reviews" or "open proposals" on the radar. Can you please add a blueprint here: https://blueprints.launchpad.net/zopetoolkit/ Also, can you add a proposal page to the documentation that points out what you already implemented and what you intend to achieve globally? Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication
Christian, I hear you and understand you. I'm not advertizing for an immediate and brainless action. What I did this week end is simply to split the PAU from all the components provided with it (well, most of it). That was motivated by my current work and by the will to see the dependencies become cleaner and the code shorter. I understand that the momentum is not everything, but when I can dedicate myself to a task, be motivated by it and paid for it, then, I don't see any reasons to hold back ;-) In this case, I'll just wait for your feedbacks, zope devs, and we'll take the time (obviously) to do the things correctly. Let me know what you guys think, about what has to be done, when you can - Souheil 2010/1/26 Christian Theune : > Hi, > > On 01/26/2010 09:06 AM, Souheil CHELFOUH wrote: >> Hello, >> >> I took the liberty to start the work by a first simple move : >> splitting apart what is "strictly" about PAU's core and the rest. >> PAU and some plugins have been put in : >> http://svn.zope.org/repos/main/zope.pluggableauth/trunk/ >> >> The rest has been kept in: >> http://svn.zope.org/repos/main/zope.app.authentication/branches/zope.pluggableauth-trollfot/ >> >> The tests pass and nothing has been changed but the imports. >> >> I people could already give me their feelings about it, it would be >> very constructive. >> There is still a lot of code that might need work. My concern was >> about the factories and the events. >> They look unnecessary to me in the core. I'm not sure, however, that >> people want to split that part. >> >> I hope to get some feedback so I can go on with the work and not lose >> the current momentum. > > As Martijn left the steering group, we're currently in discussions on > how to proceed internally. > > One thing I'd like to mention here is that we do need to be careful > balancing momentum with other qualities of the work we do: you want > feedback and I'd like to give feedback. I can't drop the regular work I > do on the spot for that though. > > And I think architectural changes don't need to be implemented within > days or weeks. > > Christian > > -- > Christian Theune · c...@gocept.com > gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany > http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 > Zope and Plone consulting and development > > ___ > Zope-Dev maillist - zope-...@zope.org > https://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > https://mail.zope.org/mailman/listinfo/zope-announce > https://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication
Hi, On 01/26/2010 09:06 AM, Souheil CHELFOUH wrote: > Hello, > > I took the liberty to start the work by a first simple move : > splitting apart what is "strictly" about PAU's core and the rest. > PAU and some plugins have been put in : > http://svn.zope.org/repos/main/zope.pluggableauth/trunk/ > > The rest has been kept in: > http://svn.zope.org/repos/main/zope.app.authentication/branches/zope.pluggableauth-trollfot/ > > The tests pass and nothing has been changed but the imports. > > I people could already give me their feelings about it, it would be > very constructive. > There is still a lot of code that might need work. My concern was > about the factories and the events. > They look unnecessary to me in the core. I'm not sure, however, that > people want to split that part. > > I hope to get some feedback so I can go on with the work and not lose > the current momentum. As Martijn left the steering group, we're currently in discussions on how to proceed internally. One thing I'd like to mention here is that we do need to be careful balancing momentum with other qualities of the work we do: you want feedback and I'd like to give feedback. I can't drop the regular work I do on the spot for that though. And I think architectural changes don't need to be implemented within days or weeks. Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication
Hello, I took the liberty to start the work by a first simple move : splitting apart what is "strictly" about PAU's core and the rest. PAU and some plugins have been put in : http://svn.zope.org/repos/main/zope.pluggableauth/trunk/ The rest has been kept in: http://svn.zope.org/repos/main/zope.app.authentication/branches/zope.pluggableauth-trollfot/ The tests pass and nothing has been changed but the imports. I people could already give me their feelings about it, it would be very constructive. There is still a lot of code that might need work. My concern was about the factories and the events. They look unnecessary to me in the core. I'm not sure, however, that people want to split that part. I hope to get some feedback so I can go on with the work and not lose the current momentum. - Souheil 2010/1/26 Christian Theune : > On 01/22/2010 07:59 PM, Souheil CHELFOUH wrote: >> Hello guys, >> >> I'm coding some stuff, using zope.app.authentication and this package >> appears to do too many things, in my opinion. >> Would it be wise to cut off some of the functionalities ? The pure PAU >> components could go in a dedicated package, like >> zope.pluggableauthservice >> The whole handling of principals, groups and folder makes it a bit >> hard to read and introduces a lot of redundancy if we wish to roll our >> own things. >> What do you guys think ? > > Yeah, I think it would be nice to give that code a refactoring. Whenever > I work with it I feel the urge to do so. > > There's also subtle API annoyances that I'd like to get rid of but don't > remember exactly right now. > > How about a specific proposal? > > Christian > > -- > Christian Theune · c...@gocept.com > gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany > http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 > Zope and Plone consulting and development > > ___ > Zope-Dev maillist - zope-...@zope.org > https://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > https://mail.zope.org/mailman/listinfo/zope-announce > https://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing coverage support
On 01/18/2010 05:34 AM, Martin Aspeli wrote:
> Stephan Richter wrote:
>> On Sunday 17 January 2010, Martin Aspeli wrote:
>>> I'm using zope.testing-3.7.7, which is what comes with Zope 2.12.
>>
>> Here is what I have in effectively any package:
>>
>> [coverage-test]
>> recipe = zc.recipe.testrunner
>> eggs = pkg [test]
>> defaults = ['--coverage', '../../coverage']
>>
>> [coverage-report]
>> recipe = zc.recipe.egg
>> eggs = z3c.coverage
>> scripts = coverage=coverage-report
>> arguments = ('coverage', 'coverage/report')
>
> Thanks!
>
> As a matter of constructive criticism, it would be useful to have
> something like this on the z3c.caching PyPI page. Right now, there is no
That's a typo, right?
> way that I can see to understand how the package is meant to be used
> from that page, or any of the other documentation.
>
> It'd also be useful to note that enscript must be installed for syntax
> highlighting to work. I only figured that out by reading the source.
Also, if this functionality is useful, I'd rather see this folded into
the mainstream runner.
At some point, the test runner recipe could also be provided by the
zope.testing package itself IMHO.
Christian
--
Christian Theune · c...@gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1
Zope and Plone consulting and development
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
