1,035
edits
Changes
no edit summary
* Language issue in India is like going from state to state in the US where when you go across States it's a different dialect, using same basic Sanskrit
* Currently, there is a limited number of people who access internet - it is reserved for peopel people who speak English and Hindi* There is a strong correlation between english English and PC users.
* 40-60M online. 1.1 billion total people
* There were people that Seth met on his rip who are trying to localize Firefox in their languages; two have been done Gujarati and Punjabi.
* There are 6-8 major indian Indian languages that we would like to get communities to localize; it would open up access to millions of local users.
* Met 4-5 different groups of people who are very enthusiastic about creating localized versions of Mozilla applications.
** First an englishEnglish-indian Indian version, then leading to many other languages like tamil, etc.
* The main group is called Mahiti organization
** part of their team is contracted by the Indian government to localize Open Office.
** They are very proficient and excited to localize Firefox.
** Their objective is to ship free and open source software to Non-Governmental Organization's in India.
** People that they are serving are in country side and could realy really benefit from this as it would shed light on an amazing amount of content that's being accessed elsewhere
* ACTION: Seth to point them to the [Category:L10n_Teams] pages to start with, so they can find existing groups in India and begin an in-country coordination effort first (connect existing teams)
* We discussed which path we should recommend they take e.g., official localized version with cvs status or doing a language pack - what should be appropriate
**Gujarati - strong team already exists led by ankit and nirav, connecting of the groups
**Karnathaka - make sure that this is on the list of the ones that are suggested (state of Bangalore). ACTION to Seth to verify
**En-In version - one suggeston suggestion might be to do something with GB version, new territory for this (how to grab existing build and do something with that); researching what would be involved in doing this version, L10n-drivers suggest creating a wiki page that lists set of requirements (les less formal than a bug), suggestion is to patch GB less worries about QA and more worries about build/release
* ACTION Seth to connect Mahiti to the 3 groups of localizers already working on things
**Ankit - Localizer in India who is really good, enthusiastic, knowledagble knowledgeable about our process, will get them in touch with them also, take leadeship leadership in guiding them through would offload work on our side
* ACTION: [https://bugzilla.mozilla.org/show_bug.cgi?id=389825 bug] - language selection features that google's offer in India, Mic to work with Product on this
* Another suggestion, have a special category for l10n India to get teams work toegether together - could have a newsgroup for them moz.dev.l10n.india - localization issues that span india
=Documentation=
**Mic's view - give them the choice to make (point to documentation for understanding)
**Wil - sees no issue with this approach
** Pascal - minority language, do we "trust" team in long term; advantage of language pack is don't have to support it on website and so on, should remain in language pack; if "minority" language comes up and have very organized team would be in favour of supporting them; in documenation documentation should make clear if get involved doing so for long term**Axel - is there a way to estimate how much web update work there is to do? how much maintenance work the web is for a localization team? in terms of what we expect them to do in response to e.g., bugs; how much work how often how liely likely to happen within a year; Pascal suggested there is not too much, with Google snippets (there is a problem on Google side)
* We agreed suggesting the localizer team choose their path after reviewing the Documentation is the best option
*ACTION: Mic to inform John and QA (Tim) on this decision
