[Wikimediaindia-l] Localisation and internationalisation bugs affecting Indic language communities

From: Srikanth Lakshmanan &lt;srik.lak(a)gmail.com&gt; To: Wikimedia India Community list &lt;wikimediaindia-l(a)lists.wikimedia.org&gt; Cc: WMF Localisation team &lt;localisation-team(a)lists.wikimedia.org&gt; Subject: Re: [Wikimediaindia-l] Localisation and internationalisation bugs affecting Indic language communities Message-ID: &lt;CA+30aUNZiw70guq189DLp0wF2ttgiJxL5VNDZeBP3+R3pBqGyQ(a)mail.gmail.com&gt; Content-Type: text/plain; charset="iso-8859-1" On Wed, Feb 22, 2012 at 10:54, Sumana Harihareswara &lt;sumanah(a)wikimedia.org&gt;wrote;wrote: There is nothing to be distressed here. They are called "black hole" for the reason anyone(apart from the filer / folks who conversed) might not be able to easily spot them. In most cases the bugs lack update from the filers / language communities. But again if the filer is from one generation and has retired, who does the follow up? Ideally language support teams must do it. But all of us know Indic communities have very few people to look into these and the common pattern I have found across few communities I have interacted is that spending time on bugzilla / improving technology/language support is not going to change things big way, so I might as well be contented (Ex:- "Why Narayam when js works fine") with whats there and do my editing. But at some point, communities need to focus on these, as and when the communities grow, they will also get contributors who are interested in supporting the language technically. The quote was from one of the bugs I remember seeing on bugzilla, said by someone on a totally different bug nothing related to localization. The point I implied quoting it was "process for the sake of it doesn't help much beyond a point". Adding tracking bugs does not impact the age of the bug. The bugs remain open either because they are hard to solve / lack of bandwidth / lack of input / variety of other reasons, not because no one is tracking them. Adding a tracking bug wont magically fix the bug / help in the getting it to closure. But tracking bug serves useful especially for anyone new to see what are problem areas, how can I help fix / test / not report duplicate bugs etc. Another point, Not all Indic wikipedia related issues are i18n issues, though there might be heavy overlap. There are site requests like changing logo,namespace, installing extensions <<whatever>>. The point to note is, when someone does these things in any Indic community(which already have tiny community), please keep the community widely posted / document these somewhere.Not just issues, but solutions/workarounds, gadgets used, things like abuse filter rules(if any) and its rationale behind etc. This will help someone else in your community(who may come years later) to follow up even if you retire / had forgotten. Fortunately Tamil Wiki community did that from the beginning(at least the major ones,if not everything) in the form of a page[1] and I was able to go through,know the past issues,update it after almost 2 years! I felt a tracking bug might be easier to track on issues than a page, so I just created one. This problem is not restricted to bugzilla. This may even happen in say in translation or anything, where only a subset (ideally 1-2 in a community of 10) involve in the activities and do not document / pass over the knowledge properly.Smaller Wikipedias must not rely on select individual on anything so much that they become extinct/dormant after their wiki-time (Insert story of Bishnupriya Manipuri) I hope Shiju is reading and might be able to relate to it / research on solutions :) [1] http://tawp.in/r/3hl -- Regards