1142372 - [Stingray] Remove tv_apps folder and move all content originally under tv_apps folder to apps folder

Status: RESOLVED WONTFIX

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

Description

[Tzu-Lin Huang [:dwi2][:tzhuang]]

Remove tv_apps folder and move all content originally under tv_apps folder to apps folder.

This is the step prior to enable Gaia unit test for Stingray project.

Comment 1

[Axel Hecht [:Pike]]

This has significant impact on localization, as that'd expose all TV apps to localizers, though as far as I can tell, they shouldn't have to deal with TV apps.

We should try to figure out something smart here to not waste time of a 100 people trying to localize fxos.

Comment 2

[Delphine Lebédel [:delphine - Use needinfo]]

Adding Howie and Joe so they are aware of this

Comment 3

[John Hu [:johnhu][:johu][:醬糊小弟]]

Hi Axel,

May I know the reason that they shouldn't have to deal with TV apps?

Comment 4

[Delphine Lebédel [:delphine - Use needinfo]]

John: this has been confirmed to l10n team since January by both Joe Cheng and Howie Chang - and reconfirmed 2 days ago once more. Partner is to be in charge of localizing these strings in their own dedicated repos. These are not to be covered by localization teams. Also, TV work is on 2.1, we have been string frozen for more than 6 months now. :Ni Howie and Joe so they can confirm this. thanks

Comment 5

[howie [:howie]]

Yes as confirmed, currently the partner is in charge of the localisation and maintains their own private repo, we are not exposing tv apps to localizers now.

This bug is a long term idea and it’s in the early stage of exploring possibility/effort.

In the case Firefox OS decides to support TV as a build in feature, we’ll surely ask l10n team's feedback and involve l10n into discussion, thank you.

Comment 6

[Evelyn Hung]

also, in our plan, it will happens on master. 

The goal is to merge both system apps, and we could use build configure to make builds for different device form factors from one code base. It's a huge work and of course "how to do localization for different builds" is one of our working items. We haven't have a detail break-down task list yet, but will definitely discuss with l10n team to know your requirements and opinion afterward. Sorry for troubling you by the lack of context here.

Comment 7

[Delphine Lebédel [:delphine - Use needinfo]]

Jumping back on this: please keep us (l10n team) in the loop going onwards with this!
I just want to note that I don't really understand the logic behind getting these tv app strings on master for localizers to translate, because they don't have access to TVs. So they will be localizing blindly. Not sure we'd want that to happen.
Just my 2 cents

Comment 8

[Delphine Lebédel [:delphine - Use needinfo]]

:evelyn, :howie: jumping back in regards to comment 6
We've seen emails going back and forth about tv_apps. l10n team would like to know if you have any updates in regards to exposing tv strings to localizers. This is a discussion we would need to have a long time in advance, and don't want to be surprised by this.
Thanks!

Comment 9

[Evelyn Hung]

Delphine, thanks for following up here. 

I totally understand this task needs a long term plan, and we suspended for a while because of your previous inputs, especially for the part that localizers need a way to build TV and see the result. I think we are on the same page, and we will definitely loop you into the planning discussion when we find a solution for localizers. Thanks!

Comment 10

[BMO Automation]

Firefox OS is not being worked on