Closed Bug 1114858 (ewe-keyboard) Opened 10 years ago Closed 8 years ago

Request to add Ewe keyboard to Firefox OS - multiple branches

Categories

(Firefox OS Graveyard :: Gaia::Keyboard, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::Keyboard
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(tracking-b2g:backlog)

Status:
RESOLVED INCOMPLETE
Project Flags:
tracking-b2g backlog

People

(Reporter: delphine, Unassigned, NeedInfo)

References

Details

Please add Ewe keyboard to Firefox OS, from 2.0 and onwards
[Blocking Requested - why for this release]:
Ewe (ee) is requested from 2.0 and onwards. Thus nominating
blocking-b2g: --- → 2.0?
Flags: needinfo?(bbajaj)
[Blocking Requested - why for this release]:

[Triage] Considering current 2.0 timing and the need from partner, nom. to 2.1 (or even 2.2?) instead for consideration.
blocking-b2g: 2.0? → 2.1?
Adding Jojo from Kasaharow to ask for input on Ewe keyboard layout.
Clearing blocking no, refer to comment in : https://bugzilla.mozilla.org/show_bug.cgi?id=1114866
blocking-b2g: 2.1? → ---
Flags: needinfo?(bbajaj)
[Blocking Requested - why for this release]:
Confirmed this morning that Bus Dev needs this in 2.0.
blocking-b2g: --- → 2.0?
[Triage]

BD has confirmed the need, recorded in Program Management mana page.
blocking-b2g: 2.0? → 2.0+
Do we know more about for when this is needed exactly?
No one is assigned or working on this. Just want to make this clear if this is urgent....
Flags: needinfo?(wehuang)
Tim: do you think you or someone on your team can take a stab at this please? (partner requirement for 2.0, which is why it's been nominated)? Thanks!
Flags: needinfo?(timdream)
Is there a spec?
Flags: needinfo?(timdream) → needinfo?(firefoxos-ux-bugzilla)
Hi Delphine:

We need information from BD for this, currently partner's R&D team is working on other region's SW so I assume this some early information via business discussion. You can check bug 1129845 (Mozilla only) for the regions partner is working on currently.

@Tony and Nisha: 

Would you help answer? thank you.
Flags: needinfo?(wehuang)
Flags: needinfo?(nmalhan)
Flags: needinfo?(aappleton)
This is the first I've heard of this. Who, if anyone, from UX was asked to work on this?
Flags: needinfo?(firefoxos-ux-bugzilla)
Wesly: I'm not on BD. Please check with them. You marked this bug as blocker on comment 6 since it's on the mana as a partner requirement.

Ok there is a huge disconnect here amongst teams it seems. I open bugs when I see a new language is requested and comitted on the mana. I can get local teams to help - when local teams exist.

Sorry but I don't think the rest is up to me to figure out.
Peiying: is this something Rubric folks might be able to help with? Sorry, would have been good to know this before-hand, given this bug was opened in December :/
Flags: needinfo?(pmo)
I do not see that this bug was ever assigned (since it was filed in December), so I am assigning it to Bruce now, as he may know the status since the Mana requirement was added last year.
Flags: needinfo?(bhuang)
i will ask Rubric about it.
Hi Ian and Devon,

We also need your help on the keyboard layout
Flags: needinfo?(pmo)
Here's something I put together based on the alphabet: http://goo.gl/7u59Di.

Would be great if we can get a UI confirmation from a local expert.  Thanks.
Flags: needinfo?(bhuang)
(In reply to Bruce Huang [:bhuang] <bhuang@mozilla.com> from comment #17)
> Here's something I put together based on the alphabet: http://goo.gl/7u59Di.
> 
> Would be great if we can get a UI confirmation from a local expert.  Thanks.

The letters above each of the keys are the options that appear when a user long presses the key.  I'm also assuming that there are no new symbol keys needed.
Hi All,

I am sure your team have already had a look at these sites:

http://www.tavultesoft.com/keyboarddownloads/%7BE3D25DA8-5C38-412D-8EA2-B3F818C9059A%7D/SIL%20Unicode%20Keyboard%20Chart%20for%20Africa%20using%20deadkeys.pdf

Ewe:     http://www.ghanakeyboards.com/support/layouts.html

We have also reached out to our translators to see what they have to say.

Best regards,
Devon
[Blocking Requested - why for this release]:

Per comment 10, we need TAM to confirm whether we do need this on 2.0 for Fire E. Denominate this from 2.0+.
blocking-b2g: 2.0+ → 2.0?
I am not aware of a specific requirement for a launch in Ghana which might necessitate the need for Ewe. We are talking to operators that have a footprint in Ghana, but there is no launch currently in discussion.

Redirecting the question to Nisha, as she is BD responsible for these Operators and will have a better idea of when a launch might happen.
Flags: needinfo?(aappleton)
Adding a reminder to keep any partner identifying and/or privileged information off of Bugzilla.
(In reply to Devon from comment #19)
> Hi All,
> 
> I am sure your team have already had a look at these sites:
> 
> http://www.tavultesoft.com/keyboarddownloads/%7BE3D25DA8-5C38-412D-8EA2-
> B3F818C9059A%7D/
> SIL%20Unicode%20Keyboard%20Chart%20for%20Africa%20using%20deadkeys.pdf
> 
> Ewe:     http://www.ghanakeyboards.com/support/layouts.html
> 
> We have also reached out to our translators to see what they have to say.
> 
> Best regards,
> Devon

Hi All,

Our Ewe linguists have confirmed that the Ewe standard keyboard is complete as per above link.
Hi Théo,
Does this bug get covered by bug 1122328? Just realize we're duplicating some of the work here.
Thanks!
Flags: needinfo?(theo.chevalier11)
Hi Bruce, answering for Theo since I know the answer: nope, that bug does not cover the Ewe keyboard.
That patch only added a generic keyboard for some African locales by default, but this is not the Ewe specific-keyboard needed. Thanks!
Flags: needinfo?(theo.chevalier11)
[Triage]

For partner working with FxOS 2.0, TAM has communicated to them to handle "languages other then what are already supported in FxOS 2.0" by their own, so this will not block 2.0.

De-mon it from 2.0.
blocking-b2g: 2.0? → ---
(In reply to Delphine Lebédel [:delphine - use need info] from comment #12)
> Wesly: I'm not on BD. Please check with them. You marked this bug as blocker
> on comment 6 since it's on the mana as a partner requirement.
> 
> Ok there is a huge disconnect here amongst teams it seems. I open bugs when
> I see a new language is requested and comitted on the mana. I can get local
> teams to help - when local teams exist.
> 
> Sorry but I don't think the rest is up to me to figure out.

Hi Delphine:

I de-nom this one since the plan is unclear now, plus what I mentioned in comment#26. Seems there is some misunderstanding here so I will find you in Vidyo for more discussion. Thanks!
As per comment 23, keyboard layout is complete and work can get started. 
ni on Bruce so he can help drive this forward :) thanks!
Flags: needinfo?(bhuang)
Update layout at http://goo.gl/7u59Di.  Adding to team backlog.
blocking-b2g: --- → backlog
Flags: needinfo?(bhuang)
This keyboard is confirmed complete: http://www.ghanakeyboards.com/support/layouts.html
blocking-b2g: backlog → ---
tracking-b2g: --- → backlog
Alias: ewe-keyboard
Close the bug due to change of roadmap.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.