Elmo/Planning

Elmo is the codename for the new version of the Mozilla localization portal.

What is Elmo?

Elmo is l.m.o, which is l10n.mozilla.org.

Elmo is an infrastructure of web apps that are intended to help the l10n community. Presently, our tools, docs, sites, wikipages, etc., all live in a fairly disorganized, disparate world that we often ask localizers to navigate to get stuff done.

To solve that problem, we spent a quarter with Chris Howse doing an information architecture study of all those disparate pieces of information. That has come together nicely now in a plan that we have to build an l10n portal that links all of that stuff in one site.

Elmo is that plan.

Wireframes

http://people.mozilla.com/~chowse/drop/l10n/wireframes/v1/

Notes on wireframes:

• http://etherpad.mozilla.org:9000/elmo-wireframes (needs updating)

Mailing list

https://lists.mozilla.org/listinfo/tools-elmo

Code

http://hg.mozilla.org/l10n/django-site

Open bugs

bugzilla, bugxhibit.

Berlin work week

See http://etherpad.mozilla.org:9000/41QLgldZvD.

Release plan

1. Fix current P1's

• We still need to be able to use the dashboard while working on the new version.

2. Create an inventory of needs vs existing assets

• Map wireframes to our current apps.
• Create the mapping of required snippets pulled from other apps for each app's views.
• Design the URLs for all views.
• See what we already have, what will need to be changed (and how) and which pieces we're missing (read on).

3. Formalize Elmo process: (laura)

• Get on real infrastructure, with config management and monitoring
• Document and use new source control and deployment process
• Get WebQA involved
• Coding standard check (e.g. inline to external "bundleable" resources)

Q2: Unordered items

• hudson + integration test coverage (Peter)
  • Move to using Hudson
  • Provide test coverage

• jinja2 templates (Peter)
  • Switch from django templates to jinja2

• workflow (stas)
  • Land the workflow app

• homepage (Adrian)
  • Get new templates into production (from Lee Tom PSDs to html first)

• Shipping / l10n stats
  • Data 1.1 (Pike) - requires new pushes/signoff
    • Adjust the data model to the new rapid release process (axel + stas)
  • (dependency on data 1.1) Merge l10nstats and shipping and get into production. (/dashboard and /shipping/dashboard should merge into one dashboard.) (peterbe + stas)

• bugsy (stas)
  • Integrate Milos improvements Q2

• metrics (laura)
  • Deploy a metrics solution (web trends?)

• drain (laura)
  • Write a spec.

• webby (stas)
  • revisit and remove in its current form

• Infrasec review===

Q3: Create new apps

[drain]

• message exchange backbone for feeds and notifications: L10n:Dashboard/Apps/Drain
• For each wireframe, see what sidebar data is required (feeds, watching and announcements).
• Create a consistent messages API for all apps that can be used to exchange data between them.
• …as well as to create in-page/feed/mail notifications for registered users.

Create an app that talks to Verbatim

• Might be a part of [webby] (see below).

[webby] Create the webby app

• handle web projects: L10n:Dashboard/Apps/Webby
• Create [webby] with its views (including snippet views) and models.

[profile] Create the profile app

• contact management and outreach: L10n:Dashboard/Apps/Profile
• Create [profile] with its views (including snippet views) and models.
• Evaluate integration options with Sigil.
• Integrate with [drain] for notifications and the "watch" feature.

[upcoming] Create the projects app

• which projects are up for l10n when: L10n:Dashboard/Apps/Projects
• Create [projects] with its views (including snippet views) and models.

[watching] Create the watching app

• create personalized dashboard pages: L10n:Dashboard/Apps/Watching
• Create [projects] with its views (including snippet views) and models.