eCryptfs could use a new logo

Bug #907131 reported by Eddie Garcia on 2011-12-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eCryptfs
Wishlist
Dustin Kirkland 

Bug Description

Why a new logo?
eCryptfs is an active, vibrant open source project, and it deserves a
logo and a mascot that reflects that! The traditional logo [1] was
created by engineers for an IBM slideshow back in 2005, and is a bit
on the stuffy side :-) Everyone uses a lock or a key for an
encryption solution, so we thought we'd do something fun and
different, so we commissioned an artist to liven up the eCryptfs logo!
 [1] https://launchpadlibrarian.net/17699533/ecryptfs_192.png

Why this design?
The font is modern, crisp, clean. A little techy even.
Highlighting the fs not only highlights the relationship to file systems but
also demonstrates the pronunciation of eCryptfs. In other words, you say
"ecrypt" and "fs" as two words.

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.

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

Thanks,

Eddie

Changed in ecryptfs:
status: New → Triaged
importance: Undecided → Wishlist

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?

Dustin Kirkland  (kirkland) wrote :

Tyler,

Yes, CC-by-SA 3.0 I think is best here. And I agree with you on the "primary" logo being the one with the icon and the text. As long as its readable at 64x64 and 192x192, we can just lay that on a flat white canvas. I'd suggest the squarish head shot of the honey badger to be the one used in Launchpad for the 14x14 icon.

Dustin

Changed in ecryptfs:
status: Triaged → In Progress
assignee: nobody → Dustin Kirkland (kirkland)
Changed in ecryptfs:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers