Mozilla India l10n - Status and Ideation

[Rajesh Ranjan]

Hi All,

I have prepared a spreadsheet (inspired from Indic language status page created by Karunakar) conatining status of Indian languages @ Mozilla products on the basis of the status present on l10n.mozilla.org. Please correct the in the spreadsheet below if you find discrepancies:

https://docs.google.com/spreadsheet/ccc?key=0Ap4lnG3I1lO4dGFlNjJXQXUyZ1lVeW53ank3cjluckE&usp=sharing

Please provide your input for creating and maintaining a vibrant localization community in India for Mozilla on the pad below. India is a huge country and has great diversity. We need to fill Mozilla with some more colours of languages of India along with maintaining the existing languages. Your idea, support and contributions are welcome:

https://etherpad.mozilla.org/mozilla-india-l10n-taskforce

Thanks!

regards,
--------------
Rajesh Ranjan 

[arky]

Before talking about the coverage of all Indic languages let us first
look at the status of existing languages and their sign-off status[1]
today.


Firefox 5 : Tamil (ta)

Firefox 16: Bengali(bn-IN) Gujarati (gu-IN) Kannada(kn) Maithili(mai)
Malayalam(ml) Oriya(or) Punjabi(pa-IN)

Firefox 17: Hindi(hi-IN) Marathi(mr)

Firefox 18: Telugu(te)

Firefox 21: Assamese(as)

It would be good idea first to focus in bringing all these existing
languages up to date. Let us continue to track existing locales
and address any problems that are blocking them.

Also it is important to make sure both Firefox and web parts are
translated to ensure that localized builds are discoverable.

Use the growing Mozilla India community to reach out and promote
our localized builds. Use this network to identify and mentor
new contributors.

We have had many requests for new locales from India: Tulu(tcy), Bodo
(brx), Sindhi (sd), Kashmiri(ks-deva), Santhali (sat), Bhojpuri (bho)

I'll be happy to mentor and help create sustainable localization
communities in India

Cheers

--arky

[1] You can view the translation status of your language at the
following in page: https://l10n.mozilla.org/teams/<locale-code> and team
pages are at https://wiki.mozilla.org/L10n:Teams:<locale-code>

[Rajesh Ranjan]

----- Original Message -----

> From: arky <ar...@mozilla.com>
> To: dev-l...@lists.mozilla.org
> Cc:
> Sent: Friday, April 26, 2013 1:05 PM
> Subject: Re: [Dev-l10n-in] Mozilla India l10n - Status and Ideation
>
> On 04/24/2013 02:03 PM, Rajesh Ranjan wrote:
>> Hi All,
>>
>>
>> I have prepared a spreadsheet (inspired from Indic language status page
> created by Karunakar) conatining status of Indian languages @ Mozilla products
> on the basis of the status present on l10n.mozilla.org. Please correct the in
> the spreadsheet below if you find discrepancies:
>>
>>
> https://docs.google.com/spreadsheet/ccc?key=0Ap4lnG3I1lO4dGFlNjJXQXUyZ1lVeW53ank3cjluckE&usp=sharing
>>
>> Please provide your input for creating and maintaining a vibrant
> localization community in India for Mozilla on the pad below. India is a huge
> country and has great diversity. We need to fill Mozilla with some more colours
> of languages of India along with maintaining the existing languages. Your idea,
> support and contributions are welcome:
>>
>> https://etherpad.mozilla.org/mozilla-india-l10n-taskforce
>
>
> Before talking about the coverage of all Indic languages let us first
> look at the status of existing languages and their sign-off status[1]
> today.
>

Have you ever signed off...do you know the difficulty in signing off? If yes, you would never paste a status on the basis of sign off.

>
> Firefox 5 : Tamil (ta)
>
> Firefox 16: Bengali(bn-IN) Gujarati (gu-IN) Kannada(kn) Maithili(mai)
> Malayalam(ml) Oriya(or) Punjabi(pa-IN)
>
> Firefox 17: Hindi(hi-IN) Marathi(mr)
>
> Firefox 18: Telugu(te)
>
> Firefox 21: Assamese(as)
>

It is possible if you go by sign off you will see the same status after 5 years as well.

Please check here: http://www.mozilla.org/en-US/firefox/all/

> It would be good idea first to focus in bringing all these existing
> languages up to date. Let us continue to track existing locales
> and address any problems that are blocking them.
>
> Also it is important to make sure both Firefox and web parts are
> translated to ensure that localized builds are discoverable.
>

I heard you for Narro and now you probably started liking pootle. hg is there also. Please guide the community!

> Use the growing Mozilla India community to reach out and promote
> our localized builds. Use this network to identify and mentor
> new contributors.
>
> We have had many requests for new locales from India: Tulu(tcy), Bodo
> (brx), Sindhi (sd), Kashmiri(ks-deva), Santhali (sat),  Bhojpuri (bho)
>
> I'll be happy to mentor and help create sustainable localization
> communities in India
>
> Cheers
>
> --arky
>
> [1] You can view the translation status of your language at the
> following in page: https://l10n.mozilla.org/teams/<locale-code> and team
> pages are at https://wiki.mozilla.org/L10n:Teams:<locale-code>
>
>
>

> _______________________________________________
> dev-l10n-in mailing list
> dev-l...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n-in
>

[arky]

Hi Rajesh,

On 04/26/2013 03:24 PM, Rajesh Ranjan wrote:

>
> It is possible if you go by sign off you will see the same status after 5 years as well.
>

Now the sign-off process is well documented[1]. The status listing
posted in previous posting comes from this dashboard[2].

>
>> It would be good idea first to focus in bringing all these existing
>> languages up to date. Let us continue to track existing locales
>> and address any problems that are blocking them.
>>
>> Also it is important to make sure both Firefox and web parts are
>> translated to ensure that localized builds are discoverable.
>>
>
> I heard you for Narro and now you probably started liking pootle. hg is there also. Please guide the community!
>

Over last few years I have been mentor teams. My goal has been to try
reduce the technical barrier of entry for localizers. There are
many tools[3] that can be used for localization, each have their pros
and cons.

Let us work on a road plan of how we can go about creating and
maintaining a vibrant localization community in India.


Cheers

--arky


[1] https://developer.mozilla.org/en-US/docs/Localization_sign-off_reviews
[2] https://l10n.mozilla.org/shipping/app/locale-changes/fx22
[3] https://wiki.mozilla.org/L10n:Tools

[Dwayne Bailey]

On 26 April 2013 09:24, Rajesh Ranjan <rajes...@yahoo.com> wrote:

> ----- Original Message -----
>
> > From: arky <ar...@mozilla.com>
> > To: dev-l...@lists.mozilla.org
> > Cc:
> > Sent: Friday, April 26, 2013 1:05 PM
> > Subject: Re: [Dev-l10n-in] Mozilla India l10n - Status and Ideation
> >

> > On 04/24/2013 02:03 PM, Rajesh Ranjan wrote:
> >> Hi All,
> >>
> >>
> >> I have prepared a spreadsheet (inspired from Indic language status page
> > created by Karunakar) conatining status of Indian languages @ Mozilla
> products
> > on the basis of the status present on l10n.mozilla.org. Please correct
> the in
> > the spreadsheet below if you find discrepancies:
> >>
> >>
> >
> https://docs.google.com/spreadsheet/ccc?key=0Ap4lnG3I1lO4dGFlNjJXQXUyZ1lVeW53ank3cjluckE&usp=sharing
> >>
> >> Please provide your input for creating and maintaining a vibrant
> > localization community in India for Mozilla on the pad below. India is a
> huge
> > country and has great diversity. We need to fill Mozilla with some more
> colours
> > of languages of India along with maintaining the existing languages.
> Your idea,
> > support and contributions are welcome:
> >>
> >> https://etherpad.mozilla.org/mozilla-india-l10n-taskforce
> >
> >
> > Before talking about the coverage of all Indic languages let us first
> > look at the status of existing languages and their sign-off status[1]
> > today.
> >
>

> Have you ever signed off...do you know the difficulty in signing off? If
> yes, you would never paste a status on the basis of sign off.
>
> >

> > Firefox 5 : Tamil (ta)
> >
> > Firefox 16: Bengali(bn-IN) Gujarati (gu-IN) Kannada(kn) Maithili(mai)
> > Malayalam(ml) Oriya(or) Punjabi(pa-IN)
> >
> > Firefox 17: Hindi(hi-IN) Marathi(mr)
> >
> > Firefox 18: Telugu(te)
> >
> > Firefox 21: Assamese(as)
> >
>

> It is possible if you go by sign off you will see the same status after 5
> years as well.
>

> Please check here: http://www.mozilla.org/en-US/firefox/all/
>

> > It would be good idea first to focus in bringing all these existing
> > languages up to date. Let us continue to track existing locales
> > and address any problems that are blocking them.
> >
> > Also it is important to make sure both Firefox and web parts are
> > translated to ensure that localized builds are discoverable.
> >
>

> I heard you for Narro and now you probably started liking pootle. hg is
> there also. Please guide the community!
>

Since this is ideation I would like to jump in and add my two cents to
ideas.

Firstly, many of you followed some of the discussion about Mercurial and
Pootle. I think what was missed in that discussion was the fact that as
Pootle admins and developers we have limited resources. We need to deploy
those to have the greatest positive benefit for the most people.

So with that in mind, please do send us ideas of what you would need in
Pootle to help you grow your community effectively. Maybe thinking about
what you think others would need, rather then what you would need is a good
way of creating good ideas that benefit the most people.

The accesskey issue was raised and we're looking at some options for that.
The simple near terms solution is this. If you don't have a script that
allows accesskeys just ignore then and ignore the accesskey check. Our
scripts will do the right thing. Creating a more elegant solution will
take longer.

We look at all ideas and issue, but we do prioritise based on most benefit.

Hope that helps a bit.

>
> > Use the growing Mozilla India community to reach out and promote
> > our localized builds. Use this network to identify and mentor
> > new contributors.
> >
> > We have had many requests for new locales from India: Tulu(tcy), Bodo
> > (brx), Sindhi (sd), Kashmiri(ks-deva), Santhali (sat), Bhojpuri (bho)
> >
> > I'll be happy to mentor and help create sustainable localization
> > communities in India
> >
> > Cheers
> >
> > --arky
> >
> > [1] You can view the translation status of your language at the
> > following in page: https://l10n.mozilla.org/teams/<locale-code> and team
> > pages are at https://wiki.mozilla.org/L10n:Teams:<locale-code>
> >
> >
> >

> > _______________________________________________
> > dev-l10n-in mailing list
> > dev-l...@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/dev-l10n-in
> >
>
> _______________________________________________
> dev-l10n-in mailing list
> dev-l...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n-in
>

--
Dwayne

*Translate*
+27 12 460 1095

[Chris Hofmann]

I propose that we move this discussion to a set of points that we can
turn into a plan.

Here are the action items that I can see from the discussion and my
experience in observing and working within the community in India that
might be turned into a 4 point plan.

1. Get any Indian locale that is lagging on string updates for recent
desktop releases up to date, and signed off. As Arky mentioned this is
the list here that we are currently tracking to get locales caught up.
https://l10n.mozilla.org/shipping/app/locale-changes/fx22 The first
thing to do towards increasing awareness and market share of Mozilla and
Firefox in any country is to build great software. The sign off process
is directly designed to make sure localization work is completed, that
its reviewed and tested, and that we have good communication about each
of these steps between the localization teams and release drivers.
Nearly all localization teams are effectively using the sign off process
now. Rajesh, if there are problems or difficulties you are having with
the sign off process please be explicit about these problems and lets
get them addressed. Maybe file bugs if there are actionable things to
do, but the process is actually pretty simple.

2. Lets find a way to continue to improve and promote the localization
that are already shipping. As mentioned, the usage numbers for all the
current Indian locales is unexpectedly low. We need to find ways to
increase awareness around the availability of these locales and to
promote there use. Maybe though specially download pages that just
highlight Indian languages, maybe though affiliate or other programs
that we have used in the past. Lets brainstorm for other ideas. In the
recent 50+ events in 90 days was this a topic of discussion? Lets
capture things that can be done to drive Hindi and other language use on
Firefox to significantly higher numbers. Maybe another amazing 50+
events in 90 days with the main topic of these meetings being "lets find
a way to boost marketshare in India" could have dramatic impact.

3. Lets get teams formed, sprints happening and add the new languages
on desktop that Arky mentioned on the desktop. Tulu(tcy), Bodo (brx),
Sindhi (sd), Kashmiri(ks-deva), Santhali (sat), Bhojpuri (bho).

4. When the above list is accomplished we should be on a better path
for desktop, and in position to move toward mobile, first on Andriod,
where we don't need partners, and then on FirefoxOS where we will need
partners for shipping phones. If you have ideas on possible partners
lets collect them and get them to our business development staff that
are doing the out reach to possible partners. The localization of
Firefox for Android and FirefoxOS is relatively simple and will be quick
for many teams, but we first need to iron out the technical means for
which we will provide distribution of those builds. Android was not
really set up for localized app distribution in the way that we have
been used to on the desktop, and we are searching for work-arounds and
other solutions there. You can follow along in bug 972077.


-Chris Hofmann

On 4/26/13 3:02 AM, Dwayne Bailey wrote:
> On 26 April 2013 09:24, Rajesh Ranjan <rajes...@yahoo.com> wrote:
>
>> ----- Original Message -----
>>
>>> From: arky <ar...@mozilla.com>
>>> To: dev-l...@lists.mozilla.org
>>> Cc:
>>> Sent: Friday, April 26, 2013 1:05 PM
>>> Subject: Re: [Dev-l10n-in] Mozilla India l10n - Status and Ideation
>>>

>>> On 04/24/2013 02:03 PM, Rajesh Ranjan wrote:
>>>> Hi All,
>>>>
>>>>
>>>> I have prepared a spreadsheet (inspired from Indic language status page
>>> created by Karunakar) conatining status of Indian languages @ Mozilla
>> products
>>> on the basis of the status present on l10n.mozilla.org. Please correct
>> the in
>>> the spreadsheet below if you find discrepancies:
>>>>
>> https://docs.google.com/spreadsheet/ccc?key=0Ap4lnG3I1lO4dGFlNjJXQXUyZ1lVeW53ank3cjluckE&usp=sharing
>>>> Please provide your input for creating and maintaining a vibrant
>>> localization community in India for Mozilla on the pad below. India is a
>> huge
>>> country and has great diversity. We need to fill Mozilla with some more
>> colours
>>> of languages of India along with maintaining the existing languages.
>> Your idea,
>>> support and contributions are welcome:
>>>> https://etherpad.mozilla.org/mozilla-india-l10n-taskforce
>>>
>>> Before talking about the coverage of all Indic languages let us first
>>> look at the status of existing languages and their sign-off status[1]
>>> today.
>>>

>> Have you ever signed off...do you know the difficulty in signing off? If
>> yes, you would never paste a status on the basis of sign off.
>>

>>> Firefox 5 : Tamil (ta)
>>>
>>> Firefox 16: Bengali(bn-IN) Gujarati (gu-IN) Kannada(kn) Maithili(mai)
>>> Malayalam(ml) Oriya(or) Punjabi(pa-IN)
>>>
>>> Firefox 17: Hindi(hi-IN) Marathi(mr)
>>>
>>> Firefox 18: Telugu(te)
>>>
>>> Firefox 21: Assamese(as)
>>>

>> It is possible if you go by sign off you will see the same status after 5
>> years as well.
>>
>> Please check here: http://www.mozilla.org/en-US/firefox/all/
>>

>>> It would be good idea first to focus in bringing all these existing
>>> languages up to date. Let us continue to track existing locales
>>> and address any problems that are blocking them.
>>>
>>> Also it is important to make sure both Firefox and web parts are
>>> translated to ensure that localized builds are discoverable.
>>>

>> I heard you for Narro and now you probably started liking pootle. hg is
>> there also. Please guide the community!
>>
> Since this is ideation I would like to jump in and add my two cents to
> ideas.
>
> Firstly, many of you followed some of the discussion about Mercurial and
> Pootle. I think what was missed in that discussion was the fact that as
> Pootle admins and developers we have limited resources. We need to deploy
> those to have the greatest positive benefit for the most people.
>
> So with that in mind, please do send us ideas of what you would need in
> Pootle to help you grow your community effectively. Maybe thinking about
> what you think others would need, rather then what you would need is a good
> way of creating good ideas that benefit the most people.
>
> The accesskey issue was raised and we're looking at some options for that.
> The simple near terms solution is this. If you don't have a script that
> allows accesskeys just ignore then and ignore the accesskey check. Our
> scripts will do the right thing. Creating a more elegant solution will
> take longer.
>
> We look at all ideas and issue, but we do prioritise based on most benefit.
>
> Hope that helps a bit.
>
>
>

>>> Use the growing Mozilla India community to reach out and promote
>>> our localized builds. Use this network to identify and mentor
>>> new contributors.
>>>
>>> We have had many requests for new locales from India: Tulu(tcy), Bodo
>>> (brx), Sindhi (sd), Kashmiri(ks-deva), Santhali (sat), Bhojpuri (bho)
>>>
>>> I'll be happy to mentor and help create sustainable localization
>>> communities in India
>>>
>>> Cheers
>>>
>>> --arky
>>>
>>> [1] You can view the translation status of your language at the
>>> following in page: https://l10n.mozilla.org/teams/<locale-code> and team
>>> pages are at https://wiki.mozilla.org/L10n:Teams:<locale-code>
>>>
>>>
>>>

[Sankarshan Mukhopadhyay]

On Fri, Apr 26, 2013 at 9:04 PM, Chris Hofmann <chof...@mozilla.com> wrote:

> 1. Get any Indian locale that is lagging on string updates for recent
> desktop releases up to date, and signed off.

[snip]

> 2. Lets find a way to continue to improve and promote the localization that
> are already shipping.

In recent times the Mozilla India team(s) have met at a large number
of events and, organized meetings - have the issues that you point out
above been a part of the discussions? There has been a prior post
about plans for this year (and, perhaps beyond) - are these points
covered in the plan?

[Chris Hofmann]

On 4/26/13 8:42 AM, Sankarshan Mukhopadhyay wrote:
> On Fri, Apr 26, 2013 at 9:04 PM, Chris Hofmann <chof...@mozilla.com> wrote:
>
>> 1. Get any Indian locale that is lagging on string updates for recent
>> desktop releases up to date, and signed off.
> [snip]
>
>> 2. Lets find a way to continue to improve and promote the localization that
>> are already shipping.
> In recent times the Mozilla India team(s) have met at a large number
> of events and, organized meetings - have the issues that you point out
> above been a part of the discussions?

good question. I know that Arky and Jeff have had discussions with
localization
leaders on how to get desktop locales up-to-date, and progress is being made
in many areas there; but I'm not sure that we have written down anything
explicitly about dates or events are explicitly targeted at improving
the localization
that we already have.

> There has been a prior post
> about plans for this year (and, perhaps beyond) - are these points
> covered in the plan?

If a good plan is documented and already in place lets certainly use
that one.

If many plans already exist lets consolidate into a single plan and
document somewhere.

I guess the first thing is to try and pull together a set of links to
list anything that looks
like a plan or good idea, and get a few people reviewing and refining
that, then establish
some owners/drivers for areas of the plan.

-chofmann

[arky]

On 04/26/2013 11:01 PM, Chris Hofmann wrote:

> If many plans already exist lets consolidate into a single plan and
> document somewhere.
>
> I guess the first thing is to try and pull together a set of links to
> list anything that looks
> like a plan or good idea, and get a few people reviewing and refining
> that, then establish
> some owners/drivers for areas of the plan.

+1

Recently Rajesh and few others have started this new initiative.

https://wiki.mozilla.org/India/community/task_force/l10n


Cheers

--arky

[Sankarshan Mukhopadhyay]

On Fri, Apr 26, 2013 at 9:04 PM, Chris Hofmann <chof...@mozilla.com> wrote:
> 2. Lets find a way to continue to improve and promote the localization that

> are already shipping. As mentioned, the usage numbers for all the current
> Indian locales is unexpectedly low. We need to find ways to increase
> awareness around the availability of these locales and to promote there use.
> Maybe though specially download pages that just highlight Indian languages,
> maybe though affiliate or other programs that we have used in the past.

There is a somewhat "elephant in the room" to this conversation.
Discussing whether it would be appropriate to offer 2 seasons (2
cycles of 3 months each) of "translation bounties" in order to get new
contributors into the translation and l10n process. Enabling the
language teams to sign-off on a successful attaining of target %-age
of contributions in order for the contributor to be eligible for the
bounty should ensure that both the team and the contributors have some
reason to chase success metrics.

With low downloads and usage of the localized builds, which may partly
be due to lack of awareness of their availability, it would be
difficult to demonstrate to a new contributor in the l10n process that
they are "making a difference".

To follow up on the observation from Soumya's email later in this
thread, if existing l10n contributors are staying away from events,
this is something that both the local community and the L10n drivers
should work together on. Assessing whether the events have an agenda
of l10n is as important as is the understanding of the reason why
existing contributors would be staying away.


--
sankarshan mukhopadhyay
<https://twitter.com/#!/sankarshan>