[Zope-dev] Zope Tests: 6 OK

2010-01-25 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list.
Period Sun Jan 24 12:00:00 2010 UTC to Mon Jan 25 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: Sun Jan 24 20:37:34 EST 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013443.html

Subject: OK : Zope-2.11 Python-2.4.6 : Linux
From: Zope Tests
Date: Sun Jan 24 20:39:34 EST 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013444.html

Subject: OK : Zope-2.12 Python-2.6.4 : Linux
From: Zope Tests
Date: Sun Jan 24 20:41:34 EST 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013445.html

Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux
From: Zope Tests
Date: Sun Jan 24 20:43:34 EST 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013446.html

Subject: OK : Zope-trunk Python-2.6.4 : Linux
From: Zope Tests
Date: Sun Jan 24 20:45:34 EST 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013447.html

Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux
From: Zope Tests
Date: Sun Jan 24 20:47:34 EST 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013448.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] Legal formalities to accept log and design

2010-01-25 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Baiju M wrote:
 On Mon, Jan 25, 2010 at 5:14 AM, Tres Seaver tsea...@palladion.com wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Christophe Combelles wrote:
 Jens Vagelpohl a écrit :
 On 1/24/10 13:08 , Baiju M wrote:
 Hi,
 I would like to know the legal formalities required
 to accept a logo (with special font).
 Also I would like to know the same for web design.

 Is there any guideline for Zope Foundation ?

 BlueBream team want to use a logo designed by an external person:
 http://muthukadan.net/bluebream/bluebream-logo-v1.png
 The font used there (Perizia: 
 http://fedoraproject.org/wiki/Perizia_fonts) is
 designed by the same designer and released under GPL.

 One of my friend has offered a web design for the site (not done yet).
 All that's perfectly fine. As Andreas said, there are no guildelines, as
 long as you are not using material that's already trademarked and
 copyrighted.

 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
 Using a GPL font for the logo surely won't force us to abandon the ZPL,
 no reason for concern there. The logo is nice, by the way.
 Fonts and the GPL are complicated[1].  As that essay notes, under U.S.
 copyright law, the look of a font cannot be copyrighted, which ought
 to mean that an image which contains pixels derived from rendering the
 font is not a derived work of the font:  it doesn't contain a copy or
 transformation of anything copyrightable.

 However, the issue gets muddy, even before you consided non-U.S. law.
 So, before checking the image into the zope.org SVN repository (which
 forbids any GPL'ed content without explicit approval), please check to
 see that the font author has used the FSF's standard font exception
 clause[2]:

  As a special exception, if you create a document which uses this font,
  and embed this font or unaltered portions of this font into the
  document, this font does not by itself cause the resulting document to
  be covered by the GNU General Public License. This exception does not
  however invalidate any other reasons why the document might be covered
  by the GNU General Public License.

 If not, ask for the author to include that clause in the license for the
 font (and document that to the foundation board, if the exception is not
 published with the version of the font you use).  Or ask for a more
 permissive (non-copyleft) licence, such as one of the Creative Commons
 licenses.  If neither of those options is available, then I would ask
 the foundation board for permission to check in the image.


 [1] http://www.fsf.org/blogs/licensing/20050425novalis
 [2] http://www.gnu.org/licenses/gpl-faq.html#FontException
 
 The font is Released under GNU GPL v3, with font exception. (from font file)
 
 http://hiraneffects.blogspot.com/2008/03/thanks-perizia-is-now-font.html?showComment=120514836#c7861527171323151625

Great.  AFICT, that removes any doubt about the copyright status of the
font as used in the logo.  You should be able to check it in, if you
made it yourself, or if the designer who made it for you did it under
terms which transfered ownership of the image copyright to you (as an
employee or as work-for-hire)./   


Tres.
- --
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAktd3qcACgkQ+gerLs4ltQ6GDgCfd9zIzcYyA/ktKCYjUVredsdz
3+MAn2TtWuEU5f0xltBLwFSrUR1BKWOn
=YYJb
-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

2010-01-25 Thread Christian Theune
On 01/25/2010 03:15 AM, Baiju M wrote:
 Hi Christophe,
 
 On Mon, Jan 25, 2010 at 12:45 AM, Christophe Combelles cc...@free.fr 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.

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.testing coverage support

2010-01-25 Thread Christian Theune
On 01/17/2010 04:34 PM, Martin Aspeli wrote:
 Attila Oláh wrote:
 
 You can get the same result as with `pwd` by using --coverage=../../coverage
 
 D'oh! The current path is parts/test (via zc.recipe.testrunner). I did 
 *not* expect that.

 
 I think this needs to be documented at least, though I think it would 
 make more sense if the current directory was, well, the current 
 directory. :)

Suggestion: if one enables coverage reporting, we should print the
actual directory where the reports go or alternatively we could print
the working directory when the test runner produces output 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] zope.app.authentication

2010-01-25 Thread 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-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 )