MDN/Development/Google Summer of Code 2013: Difference between revisions

← Older edit

MDN/Development/Google Summer of Code 2013 (view source)

Revision as of 00:49, 18 June 2013

1,018 bytes added , 18 June 2013

no edit summary

John Karahalis

Confirmed users

1,193

edits

@@ Line 26: / Line 26: @@
 http://i.imgur.com/FTwtYFV.png
-==== Features ====
+=== Features ===
 Features are prioritized according to the following scale. Keep in mind that these priorities consider only business value, and are not adjusted for implementation difficulty.
@@ Line 45: / Line 45: @@
 ; P2 - View > Localization request : Users should be able to flag documents as being requested for translation. Users of the Localization Dashboard should also be able to filter based on these requests.
 ; P0 - Order > Last update : Users should be able to sort documents based on their last update. The default should be descending order (the oldest first, the newest last).
-; P1 - Order > Time difference > The user should be able to sort documents based on the difference between the last update of the English version and the last update of the localized version.
+; P1 - Order > Time difference: The user should be able to sort documents based on the difference between the last update of the English version and the last update of the localized version.
 ; P2 - Order > Most visited : The user should be able to sort documents based on which English ones are most visited.
 ; P3 - Order > Most voted : The user should be able to sort documents based on which ones have the most localization requests.
 ; P3 - Order > Priority : The user should be able to filter documents based on priorities set by Mozilla staff.
-; P3 - Difficulty : The user should be able to sort documents based on difficulty. Difficulty should be determined algorithmically. For example, longer content might be considered more difficult, or less technical information might be considered more easy.
+; P3 - Order > Difficulty : The user should be able to sort documents based on difficulty. Difficulty should be determined algorithmically. For example, longer content might be considered more difficult, or less technical information might be considered more easy.
 ; P3 - Progress bar: A progress bar should be provided to display the current state of MDN localization. The progress bar should convey the total number of documents that need to be localized, the number of documents that are actually localized, and the number of localized documents that need to be updated.
+; P0 - Usable scrolling behavior : The Revision Dashboard scrolls in a way that confuses users, and causes them to lose their place. The Localization Dashboard should scroll in a way that does not have these problems. The exact scrolling behavior remains to be determined. We should test different approaches (like pagination, infinite scrolling, and more) and see what works best.
+; P2 - Link to locale community page : When filtering on a locale, the Localization Dashboard should link users to a community page for that locale. The page can be used to set priorities, coordinate efforts, and more. The community page will be created and maintained by the community -- the Localization Dashboard will just need to link to it.
+== Prior art ==
+Features similar to the Localization Dashboard have already been built into other products. These features are provided here as inspiration for work done on the Localization Dashboard.
+* [https://support.mozilla.org/en-US/contributors SUMO Knowledge Base Dashboard]