Commercial Partners' Trademark Pages

NEW
Assigned to

Status

Marketing
Design
3 years ago
a year ago

People

(Reporter: Jeff Garver (use Need Info pls), Assigned: Jennifer Balaco)

Tracking

Details

(Whiteboard: Creative Collective Project)

(Reporter)

Description

3 years ago
>>Project/Request Title:
Commercial Partners' Trademark Pages

>>Project Overview:
Mozilla has a lot of trademarks and logos - and a lot of pages on the website relating to trademarks.  When we enter into a commercial arrangement (e.g., Firefox Desktop distribution deal, Fennec distribution, Firefox OS, etc) there is a trademark license.  Given all of our trademarks and various pages - there is confusion as to what marks are specifically licensed for certain commercial deals.  (If you go to our main trademark page - it lists all of our marks and how all should be used - yet we (typically) do not license all of our marks to our commercial partners.  We would like to set up several pages/urls that can be specific to types of commercial arrangements and that list only the marks they are to be licensed - along with appropriate usage rules.  The goal is to make it less confusing both for our partners and internally within Mozilla (if our partners our confused, more likely they will use the wrong marks or misuse them).

>> Creative Help Needed:
Copy:    No 
Design:  No 
Video:   No 
Other:  pulling together data and making easy to understand by product

>>Creative Specs:
can we talk - I keep getting passed around on this and Sean suggested I fill in this form....thx jeff garver

>>CTA and Design:
want to discuss how best to get this done....

>>Expected Launch Date:
2015-04-30

>>Mozilla Goal:
supports all Mozilla products - Firefox, Firefox OS and Firefox for Android

>>Mozilla Creative Collective:
Yes

>>Points of Contact:
jgarver@mozilla.com,
(Assignee)

Comment 1

3 years ago
Hi Jeff, 

I just sent an invite to meet about this for next week on Wednesday. Hopefully this time works for you. Let me know if you have any questions before then.
You need to log in before you can comment on or make changes to this bug.