Open Bug 852294 Opened 10 years ago Updated 10 years ago

Create a logo for L20n

Categories

(Marketing :: General, task)

task
Not set
normal

Tracking

(Not tracked)

People

(Reporter: stas, Unassigned)

References

()

Details

Attachments

(1 file)

Attached image Staś's idea
In bug 785935 we were discussing the general branding for L20n.   "L20n" is a codename but we liked it enough that we decided to go forward with it as the final brand name.

Now we'd like to give a logo :)

Can you help us please?  One direction that I'd like to explore is to emphasize the change from "l10n" to "l20n", 1 changing to 2.  See the attached image.
Thanks Stas. Do you have a sense of when you'd like this to be due? We'll get back to you with more thoughts (and possibly questions) soon, but that would be helpful for our planning purposes.
Hi Stas. Apologies for dragging this out, but we've been thinking lately about our approach to creating logos for projects like this, and the new policy is that we would like to avoid creating sub-brands below Mozilla and Firefox (except in certain public-facing exceptions like WebFWD and Mozilla Labs).

In other words, under this new policy we won't be able to create a logo for the l20n team. Any gear requests or outbound communications should just fall under the Mozilla brand.

Again, apologies for the delay in responding. Please let me know if you have any questions.
L20n has little to do with either Mozilla or Firefox, those brands won't be suitable to use for outbound messaging about l20n.

L20n is a technology and platform, more like rust, I would say, see http://www.rust-lang.org/

I expect us to use a consistent visual display of the technology name, on the website, on presentations, etc.

If you don't have the cycles to help us with that, that's fine. I just want to make sure we're on the same page that there will be a visual asset of some form, and that that won't be covered by either mozilla or firefox brands.
Thanks, Axel, my thoughts exactly.

(In reply to John Slater from comment #1)
> Thanks Stas. Do you have a sense of when you'd like this to be due? We'll
> get back to you with more thoughts (and possibly questions) soon, but that
> would be helpful for our planning purposes.

We're perfectly fine using the literal "L20n" for now, so the priority is low.  Anytime in late-Q2 or even early-Q3 should be fine if you don't have resources to commit.
You need to log in before you can comment on or make changes to this bug.