MDN/Projects/Completed/Localization Dashboard: Difference between revisions

From MozillaWiki
< MDN‎ | Projects‎ | Completed
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
==Project statement==
==Project statement==
The [https://developer.mozilla.org/en-US/dashboards/localization localization dashboard] project was started as a Google Summer of Code project. While what we have is a good start, it needs a lot of work before it's truly useful. This project proposal and plan is intended to cover the work needed to get it to the point where it's ready to use for real.
The [https://developer.mozilla.org/en-US/dashboards/localization localization dashboard] project was started as a Google Summer of Code project and is now available on MDN for beta users (turn yourself into a beta user in your profile!). The goal of this project is now to find out what further improvements are needed to make the l10n dashboard as useful as possible for the MDN localization community. It should increase localization activity and provide an overview of progress.


==Requirements==
==Requirements==
The following improvements are needed:
* [DONE] Display pages in need of an update (compare English doc date vs. locale doc date)
* [DONE] Filter listed pages with a topic filter
* [DONE] Display locale pages where no association (parent page) to an English is given
 
* Add alphabetical ordering (asc/desc)
* Display locale pages currently in progress of localization (current implementation needs fixing)
* Display pages not yet translated at all
* Display pages not yet translated or outdated in comparison to English and that are priority or mission critical (hand-collected in short-term maybe, by metrics in long-term)
* Switch to a better pagination (same for revision dashboard). See [https://support.mozilla.org/de/kb/revisions?locale=de here] for inspiration.
* Display "progress bars" to filtered views
* Provide a new flag "localization requested" to the filter modes and add it to the pages to request a translation / an update.


==Inspiration==
==Inspiration==
Links to pages with examples, ideas, and suggested UX prototypes.
* SUMO's l10n dashboard: https://support.mozilla.org/de/localization
 
* [https://bug834317.bugzilla.mozilla.org/attachment.cgi?id=709248 Initial mockup]
==Additional notes==


==Development resources==
==Development resources==
* [https://bugzilla.mozilla.org/show_bug.cgi?id=834317 Initial bug]


==Next steps==
==Next steps==
A list of things we need to do next.
* Discuss requirements and turn them into bugs once we have agreement.
 
* Find out how to get more feedback on existing and planned features.
* Finish planning what needs to be done.

Revision as of 14:24, 6 November 2013

Project statement

The localization dashboard project was started as a Google Summer of Code project and is now available on MDN for beta users (turn yourself into a beta user in your profile!). The goal of this project is now to find out what further improvements are needed to make the l10n dashboard as useful as possible for the MDN localization community. It should increase localization activity and provide an overview of progress.

Requirements

  • [DONE] Display pages in need of an update (compare English doc date vs. locale doc date)
  • [DONE] Filter listed pages with a topic filter
  • [DONE] Display locale pages where no association (parent page) to an English is given
  • Add alphabetical ordering (asc/desc)
  • Display locale pages currently in progress of localization (current implementation needs fixing)
  • Display pages not yet translated at all
  • Display pages not yet translated or outdated in comparison to English and that are priority or mission critical (hand-collected in short-term maybe, by metrics in long-term)
  • Switch to a better pagination (same for revision dashboard). See here for inspiration.
  • Display "progress bars" to filtered views
  • Provide a new flag "localization requested" to the filter modes and add it to the pages to request a translation / an update.

Inspiration

Development resources

Next steps

  • Discuss requirements and turn them into bugs once we have agreement.
  • Find out how to get more feedback on existing and planned features.