Comment 1 for bug 907131

On 2011-12-21 01:37:59, Eddie Garcia wrote:
> The traditional logo [1] was created by engineers for an IBM slideshow
> back in 2005, and is a bit on the stuffy side :-)

Did you really expect more from kernel hackers? :)

> Everyone uses a lock or a key for an encryption solution

Agreed, it is good to get away from that.

> Why the honey badger?
> The honey badger has few natural predators due to its thick skin and
> ferocious defensive abilities, much as eCryptfs adamantly defends your
> data against even the most determined attackers.

Clever! The honey badger isn't something that I would have associated
with data encryption software, but after looking at him for a few hours,
he's really grown on me. Your explanation brings it full circle. :)

> I’m happy to contribute the original logos on behalf of Gazzang to the
> eCryptfs project under the CC-by-SA license.

Thank you! It looks great! This was a really thoughtful contribution
from Gazzang!

So, to be clear on the formalities, we're talking about CC by-SA 3.0
(http://creativecommons.org/licenses/by-sa/3.0/) and the attribution
should be made to "Gazzang", right?

I think the "primary logo" (the one with the mascot and the wording) is
appropriately named and should be the logo we most prominently use.
However, Launchpad seems to restrict us to logos of 14x14, 64x64, and
192x192 pixels. I haven't scaled down the primary logo yet, but I have a
feeling it isn't going to work in one of those sizes. I guess we would
have to go with one of the mascot images across the eCryptfs Launchpad
site. Have any thoughts or know of any workarounds, Dustin?