Mozilla Brochure 1.0

A few weeks ago I posted a draft version of a Mozilla brochure. We received a lot of useful feedback on the design and text and we’ve included many of those suggestions in the 1.0 version (PDF warning). This is intended to be a living document that will change as the community grows, so please feel free to send more suggestions and we’ll make new versions as needed. If there’s interest in also having this brochure in other languages, I’ll be happy to work with the localization community to make that happen.

Note that the file posted here is a lower resolution version and some of the images may look fuzzy. We’ll print the brochures from a higher quality version.

Although the brochure was originally intended to be given to people who are new to Mozilla, I think that this will also be useful for people who are already actively involved. As part of the discussion about the Mozilla Foundation’s future, there have been some efforts made to be more precise about what the community is now. It make sense that we need to have a clear understanding of where we are today before we can figure out where we want to be tomorrow.

With this brochure we’ve had to define and describe some things about Mozilla that I don’t think have been written down before. We’ve also had to figure out how things within the community are structured and organized so that we could explain it to people who didn’t already know about it. Hopefully this brochure will help us go from ‘I can’t really define Mozilla, but I know it when I see it’ (to paraphrase Reality Bites) to ‘Here’s what Mozilla is and what we’re doing’.

10 thoughts on “Mozilla Brochure 1.0

  1. Spanish translation can be downloaded here: Brochure.doc Brochure.docx

    ODF version to follow as soon as I can complete the Office plugin download!

    While the whole document is up for review and suggestion from fellow Spanish speakers, I’ve highlighted the parts I am most doubtful about.

    Please ping me at percy @ my website for suggestions and corrections.

  2. Better yet extract the text to PO files and people will be able to use the Verbatim infrastructure to localise it.

    In the translate toolkit we have a project to support ODF but yes SVG would probably be a better option but not to localise directly but to allow text to be extracted from the format. Working directly on the source file is always a problem.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s