Changes

Notes from Seth's trip to India, for more information see Seth's [[http://www.blog.mozilla.com/seth blog]]

* 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 sandscrit Sanskrit limitation on * Currently, there is a limited number of peole people who access internet - it is reserved for peopel who speak English and Hindi. * There is a strong correlation between english and PC users. * 40-60M online. 1.1 billion total peopleall amazing languages and * There were people that Seth met on his rip who are tryin trying to localize firefox Firefox in the their languages. ; two have been done gujarati Gujarati and punjabiPunjabi. * There are 6-8 major indian languages that if we could would like to get communities to localize. ; it would open up access to millions of local users. before inspiring anyone to do anything official. wanted to touch base with our team to be prepared ot respond. got tonnes of interest from * Met 4-5 different groups of people wnatin to do lcoalized versionwho are very enthusiastic about creating localized versions of Mozilla applications. first ** First an english-indian version, then leading to many other languages like tamil, etc.mahiti * The main group is called Mahiti organization - ** part of their team is contracted by indian govenrmen the Indian government to lcoalizer open officelocalize Open Office. they ** They are very proficient and excited to localize firefoxFirefox. want ** Their objective is to be able to do it so they can ship fre free and open source software to ngoNon-Governmental Organization's in indiaIndia. people ** People that they are serving are in country side and could realy benefit from this. as it would shed light on an amazing amount of content thtthat's being accessed and the need for localized software and showed us how much they've already contributed elsewhere* ACTION: Seth to open source. they'd like point them to help. we have high standards that they'd need to adhere to. the [http://wiki.mozilla.org/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* The list of languagelanguages they'd like to tackle are: tamil, hindi, karnathaka, spengali, english-indian, gujarati (taken care of), punjabi, kelugu. told * We did inform them we do have existing efforts in one form or another. wanted to put them in touch with those team so that if they could contribute they would. : **Tamil - we have rough/tough team for Tamil**Hindi is probably not as good a state as it should be**Spengali is Runa who is working with RedHat. Redhat is big player in field who are tying to get localization in the field/India.would benefit a great deal from thei connectingkelugu **Kelugu - have two registration bugs for thisACTION connct mahiti to the 3 groups of localizers already working on thingswhat's process to ensure we are ready to help them do what they need to do; first is to check l10n:teams first step to check in with thoseAnkit - really good, enthusiastic, knowledagble about our process, will get them in touch with them also, take leadeship in guiding them through would offload work on our sideKelugu - get someone to create a bugzilla account**Punjabi - strong team, good and established**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 might be to do something with GB version, new territory for this (how to grab existing build and do something with that); researchign researching what would be involved in doing this version, L10n-drivers suggest creating a wiki page that lists set of requirements (les formal than a bug), no idea if have resources suggestion is to do it, could resort to manpower answer with new resources but this is last resort, bettter is patch GB less worries about QA and more worries about build/release* ACTION: bug Seth to connect Mahiti to the 3 groups of localizers already working on things**Ankit - language selection features that google's offer Localizer in India who is really good, enthusiastic, knowledagble about our process, will get them in touch with them also, take leadeship in india Mic (guiding them through would offload work with product)on our side* ACTION: [https://bugzilla.mozilla.org/show_bug.cgi?id=389825bug] - language selection features that google's offer in India, Mic to work with Product on thismaybe * Another suggestion, have a speical cateogy special category for l10n india India to get teams work toegether - could have a newsgroup for them moz.dev.l10n.india - localization issues that span india

* We discussed lang pack vs building a localizationneed ; Axel asked for feedback on whether we do languages as language packs only?mic* Example, Galecian, official language in Spain, long history of people giving up **Mic's view - give them the choice to make (point ot to documentation for understanding)say Galecian, official lanuage in Spain, long histoy of people giving up this is something we should clearly articulate in the documentationACTION: Mic to inform john and QA (tim)**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 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 to happen within a yearpascal - ; Pascal suggested there is not too much, google with Google snippets (there is a problem on google 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

api * API for amo AMO - will discuss we need a follow on discussion

next * Next week's call will take place on THURSDAY August 9th instead of usual Wednesday