Re: [Zope-dev] Legal formalities to accept log and design
On Mon, Jan 25, 2010 at 5:14 AM, Tres Seaver 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 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
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 ? Logo comes under trademark ? not copyright ? I couldn't find a any suitable license. Any CC variant ? I think something like this would be fine: http://www.python.org/community/logos/ http://plone.org/foundation/logo >> 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. >> >> One thing to note: While you or the designer work on the logo, make sure >> you have a few vector graphics like EPS files as well, those will look >> the nicest if someone wants to use the logo in a printed publication. > > > I'd personally prefer to see an SVG file. I can create a clean one from the > bitmap logo if needed. It should then be stored in the bluebream template svn. He created the logo in Inkscape and he will give us the SVG. > Baiju, when are we going to be sure we can use this logo? (in blog articles, > or > any publication). I also find it nice. He is working on the finishing work (in his free time). I told him to not go for any major alteration. We will wait some more time. Let's focus on documentation for time being. We will look into logo, website and other cool stuffs in parallel, but very slowly. 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 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 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 iEYEARECAAYFAktc20IACgkQ+gerLs4ltQ72cACg3FLV1u/nn44KQfI9NPLuc6TK T60AoNXqjQA/fybSKjtte1Wq+3G2X22a =YoIv -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] z3c.password and "failedAttempts" andSessionCredentialsPlugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adam GROSZER wrote: > Thinking this further, resource requests will have a '/@@/' (usually) > in their URL. So it might be an idea to skip those requests from > counting. Seems to me skipping anything except POST requests would be the right thing to do: suppose the user reloads the login form for some reason (maybe their browser crashes, whatever). 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 iEYEARECAAYFAktc17gACgkQ+gerLs4ltQ7YPwCgwJa9CyhDjiFUGdOrRM3Y1mzb QXMAoLSJ2LfNWSS3CygvXxvzAuIlxVOY =dJrd -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
Jens Vagelpohl a écrit : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > 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. > > One thing to note: While you or the designer work on the logo, make sure > you have a few vector graphics like EPS files as well, those will look > the nicest if someone wants to use the logo in a printed publication. I'd personally prefer to see an SVG file. I can create a clean one from the bitmap logo if needed. It should then be stored in the bluebream template svn. Baiju, when are we going to be sure we can use this logo? (in blog articles, or any publication). I also find it nice. > > jens > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.8 (Darwin) > > iEYEARECAAYFAktcSfsACgkQRAx5nvEhZLIRUgCeLmXoL0HF3Z7Z3cxThwfYekI4 > yKgAniozfiXtQAZx9adV4vl/YTkPwM+O > =7RFM > -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 ) > > ___ 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 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. 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. One thing to note: While you or the designer work on the logo, make sure you have a few vector graphics like EPS files as well, those will look the nicest if someone wants to use the logo in a printed publication. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAktcSfsACgkQRAx5nvEhZLIRUgCeLmXoL0HF3Z7Z3cxThwfYekI4 yKgAniozfiXtQAZx9adV4vl/YTkPwM+O =7RFM -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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 ? The ZF has no guidelines (except the one that are in place for using the official Zope logo). I think you are free to proceed as you want. We are happy to see that you are bringing Bluebream forward. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktcOUwACgkQCJIWIbr9KYzMpACfQ/vzD8NdNEizSi9/nusIWIWd uuEAnA7hr5zSLbSBgpjH+y+M/sCXcmJv =12oo -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] buildout + debugzope + wsgi
Hello Wichert, Well, debug needs a zope.conf which is created by the paster recipe. It could be more general in the way that you specify the zope.conf instead of the app section, but I better like to have it this way. Sunday, January 24, 2010, 11:26:21 AM, you wrote: WA> On 2010-1-24 11:11, Adam GROSZER wrote: >> Hello, >> >> I did the recipe z3c.recipe.paster:debug just in case someone needs >> it. WA> How does paster shell relate to this? WA> Wichert. -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: On the choice of friends, Our good or evil name depends. - John Gay ___ 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] Legal formalities to accept log and design
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). 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 )
[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Sat Jan 23 12:00:00 2010 UTC to Sun Jan 24 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: Sat Jan 23 20:36:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013437.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jan 23 20:38:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013438.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 23 20:40:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013439.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 23 20:42:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013440.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 23 20:44:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013441.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 23 20:46:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013442.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] buildout + debugzope + wsgi
On 2010-1-24 11:11, Adam GROSZER wrote: > Hello, > > I did the recipe z3c.recipe.paster:debug just in case someone needs > it. How does paster shell relate to this? Wichert. -- Wichert AkkermanIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ 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] z3c.password and "failedAttempts" andSessionCredentialsPlugin
Hello Jan-Wijbrand, Thinking this further, resource requests will have a '/@@/' (usually) in their URL. So it might be an idea to skip those requests from counting. Tuesday, January 19, 2010, 10:43:43 AM, you wrote: JWK> Adam GROSZER wrote: JWK> Thank you for your reply! >> Right. Well right now the lame solution is to try to count the number >> of resources needed to load the page and multiply maxFailedAttempts by >> that number. >> Other than that you _will_ want to offload resources in production. JWK> Oh, sure in _production_ I will. But what about testing and development. And JWK> counting the number of resources is highly unpredictable - esp. as I'm working JWK> on applications that can be easily skinned for different clients. >> (An other idea could be to try to identify requests that are not for >> resources, but how?) JWK> There's no real way as far as I can tell :| JWK> Even worse, if Zope were to handle one or more login page requisites, you can JWK> easily get database write conflicts as multiple "simultaneous" requests will try JWK> to increase the failed login attempts counter on the internal principal object. JWK> Can I conclude this particular feature of z3c.password is not really in use by JWK> anyone else (at least not in combination with the SessionCredentialsPlugin)? JWK> regards, JWK> jw >> Tuesday, January 19, 2010, 12:16:38 AM, you wrote: Betreff: [Zope-dev] z3c.password and "failedAttempts" andSessionCredentialsPlugin Hi, I'm looking into integrating z3c.password into an application that also uses the PAU with the principal folder, InternalPrincipals and the SessionCredentialsPlugin. One of the features of z3c.password that I'd like to use is locking out an user account after a number of failed login attempts. z3c.password provides such a feature. However, it seems this feature does not play well with the SessionCredentialsPlugin: The SessionCredentials will store the login and password that were submitted through the login form in a session. This login/password combination then is checked against the internal principal stored in the principal folder. If the password is correct then (obviously) everything is fine. When the password is incorrect, the user is directed back to the login form as authentication failed. If the page with the login form retrieves resources (like images or css of javascript files) and since the zopepublication will _try_ to authenticate every request, the wrongful login/password combination is checked multiple times for that page and its resources against the internal principal object. The internal principal mixin of z3c.password will count the number of failed checks. If you tell it to lock out an user after, say, three failed attempts, you have a problem, as the number of login page resources (thus requests) will quite easily outnumber the maximum number of attempts. Questions: is anyone using this feature of z3c.password in combination with the SessionCredentialsPlugin? If this is working for you, do you have any idea what I am doing wrong here? What type of authentication are the authors of z3c.password using? >> >> R> Probably Adam can tell you more about that. >> >> R> One solution could be to offload your resources and >> R> deliver them from Apache or Nginx Frontend. >> >> R> Regards >> R> Roger Ineichen >> Thanks for any insight here. 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 ) >> >> R> ___ >> R> Zope-Dev maillist - Zope-Dev@zope.org >> R> https://mail.zope.org/mailman/listinfo/zope-dev >> R> ** No cross posts or HTML encoding! ** >> R> (Related lists - >> R> https://mail.zope.org/mailman/listinfo/zope-announce >> R> https://mail.zope.org/mailman/listinfo/zope ) >> >> -- >> Best regards, >> Adam GROSZERmailto:agros...@gmail.com >> JWK> ___ JWK> Zope-Dev maillist - Zope-Dev@zope.org JWK> https://mail.zope.org/mailman/listinfo/zope-dev JWK> ** No cross posts or HTML encoding! ** JWK> (Related lists - JWK> https://mail.zope.org/mailman/listinfo/zope-announce JWK> https://mail.zope.org/mailman/listinfo/zope ) -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: Words are the voice of the heart. ___ Zope-Dev maillist - Zope-Dev@zope
Re: [Zope-dev] buildout + debugzope + wsgi
Hello,
I did the recipe z3c.recipe.paster:debug just in case someone needs
it.
Friday, January 22, 2010, 2:18:35 AM, you wrote:
BM> On Thu, Jan 21, 2010 at 11:47 PM, Adam GROSZER wrote:
>> Hello,
>>
>> What do we use nowadays instead of the good old debugzope script
>> with buildout and wsgi (and paster)?
>> I somehow did not find a recipe for that.
BM> Both Grok & BlueBream use zope.app.debug.debug to create
BM> a debugger from database. And then create an interactive prompt,
BM> like this:
BM>db = zope.app.wsgi.config(zope_conf)
BM> debugger = Debugger.fromDatabase(db)
BM> # Invoke an interactive interpreter shell
BM> banner = ("Welcome to the interactive debug prompt.\n"
BM> "The 'root' variable contains the ZODB root folder.\n"
BM> "The 'app' variable contains the Debugger,
BM> 'app.publish(path)' "
BM> "simulates a request.")
BM> __import__('code').interact(banner=banner,
BM> local={'debugger': debugger,
BM>'app': debugger,
BM>'root': debugger.root()})
BM> But, there is slight difference between invoking the prompt in Grok
BM> and BlueBream. Grok has "[console_scripts]" entry point to create a
BM> custom command and BlueBream use "[paste.global_paster_command]"
BM> entry point to create sub-command for "paster".
BM> BTW, BlueBream's idea is inspired by Pylons and code is stolen from Grok :)
BM> Regards,
BM> Baiju M
--
Best regards,
Adam GROSZERmailto:agros...@gmail.com
--
Quote of the day:
Every journalist has a novel in him, which is an excellent place for it.
___
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 )
