216
edits
Websites/Taskforce/Proposals/Web Fonts: Difference between revisions
Websites/Taskforce/Proposals/Web Fonts (view source)
Revision as of 16:23, 9 December 2010
, 9 December 2010→Solution
Theinterned (talk | contribs) |
Theinterned (talk | contribs) |
||
| Line 25: | Line 25: | ||
=Solution= | =Solution= | ||
An ideal overall solution may be: | An ideal overall solution may be: | ||
# Either adopt an existing open font or partner with a type studio to design a "mozilla font" that is free and open. Ideally the font would have both a serif and a sans and must be available to to community to hack on; for example by adding support for more languages etc. | # Either adopt an existing open font or partner with a type studio to design a "mozilla font" that is free and open. Ideally the font would have both a serif and a sans and must be available to to community to hack on; for example by adding support for more languages etc. | ||
# this font would be promoted as an official mozilla project on the projects page: http://www.mozilla.org/projects/ and mozilla would maintain a version controlled repo for it, bugzilla etc. | # this font would be promoted as an official mozilla project on the projects page: http://www.mozilla.org/projects/ and mozilla would maintain a version controlled repo for it, bugzilla etc. | ||
# This font would be hosted by mozilla (as well as third parties like Kenest.com etc.) | # This font would be hosted by mozilla (as well as third parties like Kenest.com etc.) | ||
| Line 32: | Line 32: | ||
# Rebrand with the new font (logos, etc) | # Rebrand with the new font (logos, etc) | ||
# Use the rebrand as a big marketing opportunity to promote the use of open fonts, this font in particular, the WOFF format, the new mozilla branding as a further step away from proprietary and towards open source etc. | # Use the rebrand as a big marketing opportunity to promote the use of open fonts, this font in particular, the WOFF format, the new mozilla branding as a further step away from proprietary and towards open source etc. | ||
== To start == | |||
# Decide: '''Adopt''' an existing font or '''Partner''' with a foundry and start from scratch? | |||
## If we '''adopt''': choose a font to adopt: | |||
### What are the selection criteria for the font? | |||
### How do we run the selection process? | |||
### Vote? | |||
## If we '''partner''': choose a foundry to partner with: | |||
### How do we choose partner/ what criteria? | |||
### What arrangement do we make wit them re:sharing and rights etc. | |||
### How much work do we need to get the font off the ground? | |||
One solution is to find a font or set of fonts that Mozilla adopts and recommends for use in websites. | One solution is to find a font or set of fonts that Mozilla adopts and recommends for use in websites. | ||