[Zope] Logo Guidelines for Grok and Bluebream
Hi all, preparing a brochure about Zope and friends I would like to know whether there are any guidelines for using the Grok- and Bluebream-Logo. Am I right that neither Grok nor Bluebream are trademarks owned by the Zope Foundation? TIA -- Jan Ulrich Hasecke DZUG e.V. (Deutschsprachige Zope User Group) ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Logo Guidelines for Grok and Bluebream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan Ulrich Hasecke wrote: Hi all, preparing a brochure about Zope and friends I would like to know whether there are any guidelines for using the Grok- and Bluebream-Logo. Am I right that neither Grok nor Bluebream are trademarks owned by the Zope Foundation? There is no trademark on Grok or Bluebream owned by the ZF afaik. The creators of the logos may have rights on the graphics. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJNSWQwAAoJEADcfz7u4AZjPooLwIc6syGNJuDQQM0MKgF/Fu2d lKZnQ5yvsWL7S8i2zABbQ2FEBd2X1rZXiJl/V9ds/QU0ml9DssUvFH3DGS7LCS7c cr+8dcLIBG97dx6TbKidMYkUQzb43M3GfnjltVWOt4Er/cD/8fjlCWyEgRFPDDKH OHwLjEJ/lJm98V/5W63dmdo8BGyaVBPFuay5udF1gOD2prE0t92yUoJO7zHZkTSV bihBBRJ4nDFu6dAM+CUr2NoE+LtJ0412SOt2Ev5ak8zCt5Ca2xhhJU2/3eVcQx/u m2CBQJFdNb8GzE5leCD5YJyGnPc5cE4k3Gua4JdIyKHvB52rq5YG3PfdIUhWwuYi 09Yh+33BhSPw33N+CKtvgcBVePFAPC3FhqqRDI72p+dtrlGhBnUMxTfeH7k5BxxH Fnr1CAmm6RqW/us+zDGPWOdlrtO8TDRzYqRZjC6WcelAgFjwnHRdlOtXUDeTrPPm e3Zemd5w81w9Jr80XBGLc1/Gp11Ryb0= =YUgv -END PGP SIGNATURE- attachment: lists.vcf___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Logo Guidelines for Grok and Bluebream
Am 02.02.11 15:03, schrieb Andreas Jung: There is no trademark on Grok or Bluebream owned by the ZF afaik. ok. The creators of the logos may have rights on the graphics. While I know the creator of the Grok logo, I don't know the creator of the Bluebream-Logo. Any objections to use it in a Zope related brochure edited by the german zope user group? It would be nice to have guidelines on the websites. -- Jan Ulrich Hasecke DZUG e.V. (Deutschsprachige Zope User Group) ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Logo Guidelines for Grok and Bluebream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan Ulrich Hasecke wrote: Am 02.02.11 15:03, schrieb Andreas Jung: There is no trademark on Grok or Bluebream owned by the ZF afaik. ok. The creators of the logos may have rights on the graphics. While I know the creator of the Grok logo, I don't know the creator of the Bluebream-Logo. Any objections to use it in a Zope related brochure edited by the german zope user group? It would be nice to have guidelines on the websites. I suggest to ask Baju or ask on the Bluebream list. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJNSWXtAAoJEADcfz7u4AZjZVILv0zWBWRX34oqXNxHfQYzP2rb GTUXdWcNnpHYs2+rQCMGhbZ2yEik+z2ZBRPe7aSx4zC1bBGW3BaGl8OxahS6nvaX l09Scias9kSgSKVdTEBAWoHYS4zS4EfwF5mgv6GBA9vjfzaDF0RF0cp7vxGC8Qb0 sYejxYvMgrSIKgUHV8FnvscWS6ikT/Z+odyb9N5uJdq0ezT4CJxx+snMEf1n5Jk3 p9YU4J1/NSgmZiNmCIWxtjit3afAb1ZGOxKXzAnF93uqrZEp3Hln5Nq8INiys5OX tVgu6zU08Vfscx1bpHW6KGZx6ZjhOhJZRJ9NZncPqu8y/HTOKGg/wwwEFL83Klns x+GFKpLptGd1j6oonfhG0poC9+khGEAQzafcSM4TNh0T/qO6zacdw4UEeK1ODsAS unTHpTzCMpxoIRocFMsSIT/yuYubgRJq5oO6It4cykb01QbEaedldQ34id17Vd0u GQXJyaJbaNFvRXUyoTWyjrITPZ6cVS4= =OwSG -END PGP SIGNATURE- attachment: lists.vcf___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Logo Guidelines for Grok and Bluebream
Am 02.02.11 15:10, schrieb Andreas Jung: I suggest to ask Baju or ask on the Bluebream list. I cannot find the bluebream list on gmane. I'll try the nabble gateway. But it would be nice to have it on gmane too. juh ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Logo Guidelines for Grok and Bluebream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan Ulrich Hasecke wrote: Am 02.02.11 15:10, schrieb Andreas Jung: I suggest to ask Baju or ask on the Bluebream list. I cannot find the bluebream list on gmane. I'll try the nabble gateway. But it would be nice to have it on gmane too. https://mail.zope.org/mailman/listinfo/bluebream Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJNSXyJAAoJEADcfz7u4AZj32QLvjChf0/vxUXLtXzgQfgg6czK ReYgkH84h+Iroi3vS0avX7ZQ1s86Srf0BEBbgF6CPFvmLLnbPPL/TgPZMYVHZpqN hmwa748C1MKHv+uTVy9SGOaYNV+zzH+wgUlTaafh1DgjNbnJo1RP72P+sTCSK/l4 8IGMJUiLzjcE+udyixRv4W7w7C7Eskz0vB+DW3acK4JGqbW3BILAGDbeIHO8UbnC rPZq2XzBwkDNnDjkWXUhed2ka9QST2UU1QcnslV6SR4/lhEuQb6RvXQoTlApnMqi JfKuOgqKcQwSXM4Lo77hI16kgzjfp0Ch+SySxDfAAm0sLklg6XOjAx+iE8DO6ee2 lheV1l7t8cRnPoQnZutWVo1zBAIp+JUJzVaFE+vyC4wFXZqfI6BrB1DBK5zrLgUS K4Sk5Oo8qMBRD6teK/1F+e1fyZS3eafLvVmO4jPa60PNjik6RdphOyWmI1Ui8pOa lkQt3M0B7Nbsu/mX3zZ55TWsUYNJS8o= =Z2OO -END PGP SIGNATURE- attachment: lists.vcf___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
