Extension lifecycle: How to get from the idea to the extension (short), finding testers for first development versions, stabilizing and maintaining code, submission to AMO and how AMO editors make public and review it, conditions for hosting on AMO, getting the extension localized for broader international acceptance, how to keep up to date with AMO, Mozilla products and your extension [Archaeopteryx]

Mozilla Mission and Identity

I'd like to have a series of sessions relating to Mozilla identity, mission and relationship to other open source and "open" projects. I'm thinking of the following; comments, suggestions welcome. Other session leaders very welcome as well; it's helpful to me to participate without leading sometimes.

The Firefox brand: what it means and how to use it [jslater] (additional note: this might work well in a trademark/partnerships/logo track with some sessions that Harvey and Kev are developing) Medium Presentation (projector)

Discussion on targeted community development and localization. How do we do a better job of recruiting, and bringing critical localizations and communities into the mix in upcoming releases? [chofmann/sethb]

size: 50-100 people

equipment: projector & screens

style: presentation followed by discussion

timing: 30-60 minutes

How can we scale better across all our products in more languages including emerging markets like Asia, Africa, etc. [Mic/Chofmann/Axel]

size: 50-100 people

equipment: whiteboards, projector & screens

style: free thinking, open brainstorming, inspirational

timing: 60 to 90 minutes

Problems of small translation teams with the l10n process. What can be done to make translation easier and more effective? [erdal]

size: 50-100 people

equipment: projector & screen

style: small presentation, discussion/brainstorming

timing: 60-90 minutes

moz2po and the rest of the Translate Toolkit - How to use them for Mozilla localisation, and some features that you might not be familiar with. Come and help to shape the next development phase of the tools which will specifically address Mozilla requirements (dwayne/friedel)

size: +-70

equipment: projector

style: presentation, discussion

timing: 60-90 minutes

Narro - Find out how you can speed up the localization process, increase the translation quality, make translations open to anyone and use Narro for translating almost anything [Alexandru Szasz aka alexxed]

size: 50 people

equipment: projector

style: presentation, discussion

timing: 60 minutes

Localizing SUMO - What should be the localization policy of SUMO? How do we get coverage for more locales for product help and prioritize knowledge base articles for translation? Do we want to ensure tier 1 locales always have all prioritized articles translated, or do we want it to be community-driven? [djst/mconnor]

size: 25-50 people

equipment: whiteboards

style: discussion

timing: 60 minutes

India - starting a viable, sustainable, smoldering Mozilla movement in a zany market. What are the opportunities for webtools and for l10n? [arun / sethb]

size: 15-20 people

equipment: whiteboards

style: discussion

timing: 60 minutes

QA on translation - Presentation of the pt-PT and french automated QA system - discussion of how to use QA and related translation memories. (Philippe and João Miguel Neves)

size: +-70

equipment: projector, computer, internet access

style: presentation, discussion

timing: 40 minutes

Anloc (pronounced Unlock) - adding 10 African languages to Firefox. An introductions to the Firefox localisation component of the global Anloc project. Discussion on how to help, support and mentor African Firefox localisers that will grow the African language community and sustain their localisation efforts. (Dwayne)