Arabic UI BugBash: Difference between revisions

 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Arabic/UI Bug Bash =  
= Arabic/UI Bug Bash =  
(still under construction, please visit again regularly for updated information!)<br/>
'''Please check regularly for updated information! We are adding to this page all the time.'''
 
Firefox OS, The operating system by Mozilla, has gone too far in development and we've been working on improving Arabic language and Right-To-Left (RTL) User Interface in it for too long, so now the time to test this has come.
Firefox OS, The operating system by Mozilla, has gone too far in development and we've been working on improving Arabic language and Right-To-Left (RTL) User Interface in it for too long, so now the time to test this has come.
During this event, the Bug Bash, you are welcome to help us test and find issues related to Arabic Localization and/or RTL UI in '''Firefox OS 2.1'''
During this event, the Bug Bash, you are welcome to help us test and find issues related to Arabic Localization and/or RTL UI in '''Firefox OS 2.1'''
Line 19: Line 20:
== What ==
== What ==
This bug bash is mainly to identify:
This bug bash is mainly to identify:
* any possible localization issue in the Arabic language
* Translation or localization issue in the Arabic language
* identify UI Bidirectional issues
* UI display issues, in whic RTL and/or bidi scripts are improperly displayed, in terms of alignment, overlap, truncation, and so on.


== Prerequisites ==
== Prerequisites ==
Line 39: Line 40:


== Flashing Instructions ==
== Flashing Instructions ==
Most people will be using the Firefox OS Simulator, which includes the latest builds:
* Simulator: https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/
* Simulator: https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/
** '''UPDATE!''' The WebIDE has replaced the App Manager. Look here: https://developer.mozilla.org/en-US/docs/Tools/WebIDE
** '''UPDATE!''' The WebIDE has replaced the App Manager. Look here: https://developer.mozilla.org/en-US/docs/Tools/WebIDE
If you have a Flame (or similar) device you will need:
* A mini USB cable so your phone can talk to your computer.
* The Android Developer Bridge (ADB) to "see" your device.
** http://developer.android.com/tools/help/adb.html
* In the Developer settings of your device, please make sure Developer > Debugging via USB > ADB and DevTools is on.
** Debugging via USB defaults to Disabled, so you'll need to turn it on to flash your device.
Now you're ready to get the latest Flame build. Visit:
* Flame: https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame%27s_software
** Please use Production master builds: http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central-flame/


* Geeksphone (Peak or keon): https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Geeksphone
* Geeksphone (Peak or keon): https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Geeksphone
* Flame: https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame%27s_software (Please use Production master builds, http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central-flame/ )


== Prizes (Mozilla Swag \o/) ==
== Prizes (Mozilla Swag \o/) ==
* best blocker bug
* best bug
* most number of blockers
* most number of really, really important bugs
* most number of bugs
* most number of bugs in general
* best glitch / weirdest bug
* best glitch / weirdest bug


Line 67: Line 78:
* On the next page, click "Firefox OS." Next, will now see bug fields to complete.  
* On the next page, click "Firefox OS." Next, will now see bug fields to complete.  
* Click the "Show Advanced Fields" button.
* Click the "Show Advanced Fields" button.
* '''IMPORTANT:''' Copy and paste this tag into the "Whiteboard" field: [fxos-arabic-bug-bash-2.1]. This will enable us to create and, later, to find all of the bugs found during the bug bash, award prizes, and so on.
* '''IMPORTANT:''' Copy and paste this tag into the "Whiteboard" field: [fxos-arabic-bug-bash-2.1]. This will enable us to create and, later, to find all of the bugs found during the bug bash, award prizes, and so on. You can also use this Bugzilla template http://goo.gl/4QS0zF
* For "Component" select "Gaia:L10N" in the list.
* For "Component" select "Mozilla Localizations:Arabic/ar" if the issue is an Arabic translation issue, or "Gaia" + name of the application if it's a Firefox OS bug.
* '''IMPORTANT:''' Make your bug a blocker for the appropriate Meta bug by adding one of the following Meta bug numbers to the "Blocks" field:
* '''IMPORTANT:''' Make your bug a blocker for the appropriate Meta bug by adding one of the following Meta bug numbers to the "Blocks" field:
** RTL Meta: {{Bug|906270}} (for UI display issues of bidi and RTL scripts)
** RTL Meta: {{Bug|906270}} (for UI display issues of bidi and RTL scripts)
Line 81: Line 92:
A Meta is a bug with a global topic that under it we collect every other bug related to that topic. Take the example of RTL Meta, every issue related to RTL will go under it, however Arabic-related bugs will go to the Arabic Meta.
A Meta is a bug with a global topic that under it we collect every other bug related to that topic. Take the example of RTL Meta, every issue related to RTL will go under it, however Arabic-related bugs will go to the Arabic Meta.


== How does a correct RTL interface look like ? ==
== What does a correct RTL interface look like ? ==


[[File:Firefox_OS_Settings_Interface_in_RTL.png|thumbnail|left]]
[[File:Firefox_OS_Settings_Interface_in_RTL.png|thumbnail|left]]
* Items are aligned right, not left.
* There are no overlap issues. Text should not collide with or run over UI elements. Text should not be hidden by UI elements, like icons (and vice versa).
* Text input should flow from right to left.
* Tell us what YOU think! You know the Arabic language better than we do: tell US what you think the interface should look like and how it can improve to meet your needs and expectations.

Latest revision as of 01:05, 2 October 2014

Arabic/UI Bug Bash

Please check regularly for updated information! We are adding to this page all the time.

Firefox OS, The operating system by Mozilla, has gone too far in development and we've been working on improving Arabic language and Right-To-Left (RTL) User Interface in it for too long, so now the time to test this has come. During this event, the Bug Bash, you are welcome to help us test and find issues related to Arabic Localization and/or RTL UI in Firefox OS 2.1

When

Tuesday August 26 2014

  • 5PM CET/9AM PST
  • The bug bash will last 3 hours. You may join or leave at whatever time you wish

Where

Please set up Vidyo software ahead of time and check a day or 2 before the bug bash that it's working correctly.

Who

Anyone is welcome (please check prerequisites though to make sure you know what's going on)

What

This bug bash is mainly to identify:

  • Translation or localization issue in the Arabic language
  • UI display issues, in whic RTL and/or bidi scripts are improperly displayed, in terms of alignment, overlap, truncation, and so on.

Prerequisites

To find bugs:

To participate with others during the bug bash:

  • Speak the Arabic language and/or know how bidirectional (Bidi) and/or right-to-left (RTL) scripts are supposed to work and look in the user interface.
  • Have Vidyo software installed (optional, since there's also an irc backchannel: #bugbash)

To file bugs:

Flashing Instructions

Most people will be using the Firefox OS Simulator, which includes the latest builds:

If you have a Flame (or similar) device you will need:

  • A mini USB cable so your phone can talk to your computer.
  • The Android Developer Bridge (ADB) to "see" your device.
  • In the Developer settings of your device, please make sure Developer > Debugging via USB > ADB and DevTools is on.
    • Debugging via USB defaults to Disabled, so you'll need to turn it on to flash your device.

Now you're ready to get the latest Flame build. Visit:

Prizes (Mozilla Swag \o/)

  • best bug
  • most number of really, really important bugs
  • most number of bugs in general
  • best glitch / weirdest bug

Related pad

https://etherpad.mozilla.org/Arabic-UI-BugBash (still under construction)

FAQ

I found a bug! What's next?

Since the Bug Bash will be about both RTL and Arabic, there are two main Meta bugs (i.e. "parent" or "umbrella" bugs for each category, to keep bugs organized and easy to find).

If you see a bug, first decide if it's related to the Arabic language, or to the behavior or appearance of RTL or bidi script in the user interface, or if it is another issue.

If the bug is definitely related to the Arabic language, or bidi or RTL UI, then here is how to file your bug:

  • Create a new bug by clicking "File a new bug" on the https://bugzilla.mozilla.org homepage.
  • On the next page, click "Firefox OS." Next, will now see bug fields to complete.
  • Click the "Show Advanced Fields" button.
  • IMPORTANT: Copy and paste this tag into the "Whiteboard" field: [fxos-arabic-bug-bash-2.1]. This will enable us to create and, later, to find all of the bugs found during the bug bash, award prizes, and so on. You can also use this Bugzilla template http://goo.gl/4QS0zF
  • For "Component" select "Mozilla Localizations:Arabic/ar" if the issue is an Arabic translation issue, or "Gaia" + name of the application if it's a Firefox OS bug.
  • IMPORTANT: Make your bug a blocker for the appropriate Meta bug by adding one of the following Meta bug numbers to the "Blocks" field:
    • RTL Meta: bug 906270 (for UI display issues of bidi and RTL scripts)
    • Arabic Meta: bug 1055447 (for translation and other issues specific to the Arabic language itself, vs. the display of a scrip in the UI).
  • Create a brief (50-100 characters) Summary.
  • Describe the bug in as much detail as possible. Include the steps someone else should take to reproduce the bug.
  • Click the "Submit bug" button.

Thank you! We are forever grateful for this work.

What is a "Meta" ?

A Meta is a bug with a global topic that under it we collect every other bug related to that topic. Take the example of RTL Meta, every issue related to RTL will go under it, however Arabic-related bugs will go to the Arabic Meta.

What does a correct RTL interface look like ?

  • Items are aligned right, not left.
  • There are no overlap issues. Text should not collide with or run over UI elements. Text should not be hidden by UI elements, like icons (and vice versa).
  • Text input should flow from right to left.
  • Tell us what YOU think! You know the Arabic language better than we do: tell US what you think the interface should look like and how it can improve to meet your needs and expectations.