Here is a consolidated Guide to Localisation created under the collaboration of International Open Source Network and C-DAC. Barring the odd spelling errors in the text and a few glaring ones in the diagrams, this is a good preliminary read for those wanting to get a hang of L10n.
A long time back, when all of us were still thinking up magical things to do with Ankur, the most often talked about point was the price point of computing.
At LinuxAsia 2005, the last session on ICT4D hovered over and over again to the need to make computing pervasive by delivering services which are of immediate requirement. Through its various issues, i4D has also attempted to bridge the gap between localisation theory and localisation practice. The question that is relevant is that – are we there yet ?
If one looks back at how the computing hardware prices are moving, it is obvious that far better hardware platforms are available at appreciably lower prices. In this respect, Joel’s post is important.
A complement is a product that you usually buy together with another product… All else being equal, demand for a product increases when the prices of its complements decrease.
Step back for a moment and visualise the Operating System as a product. In a simplistic interpretation of the above statement, demand for OS should increase if the prices of hardware decreases. Or in more telling terms, prices of OS should be moving upwards in sync with the downward movement of computing hardware. Now, extrapolate the Operating System as a base for providing services. Thus, with the increasingly affordable prices of computing infrastructure, the demand for services would increase. This is exactly what is happening in the Indian FOSS space. So the lesson in here is that the more the complements are commoditized, the better chances the Application Software vendors have.
Does this sound like a model of Service Oriented Architecture gone wrong ? It could if you look at the wrong end of the spectrum. For a moment take a pencil and paper (or fire up the calculator program) and do some simple math. Take ‘x’ as the number of NGOs who are actively engaged in ICT4D domain (‘x’ < 'X', where 'X' denotes the total number of NGOs in the country), consider 'y' as the lowest common domain serviced by such NGOs. Multiply 'x' by 'y'. This gives you the total subset of application domains. Straightaway eliminate around 40% of the figure by assuming that these would in someway be linked to proprietary technologies. That brings a consideration of the remaining 60%. How many of such deployments would be common ? I would hazard a guess as to many-many and surprisingly enough, most would be doable through a LAMP stack.
When GRIND was being considered, it was based on the concept of being a base Operating System which will lend itself well to be customised towards a L10n Services Framework. I think that one of the ways such a framework concept could grow is by following some sound project management. So are we there yet ? I think we are there at the initial stages. The concept is sound, a few deployments around it have produced desired user feedback. And what’s more, being based on the fundamental principles of Free/Libre Open Source Software Development, taking ahead a community driven participatory model would not be difficult.
Am currently reading Built to Last : Successful Habits of Visionary Companies. It is an interesting read primarily because of the fact that the conclusions drawn from the study can be easily applied to those companies who are trying to make their mark in the Free/Libre Open Source Software Development sphere.
The following paragraph would summarise what the book tries to get across using the various examples.
The core myth, according to the authors, is that visionary companies must start with a great product and be pushed into the future by charismatic leaders. There are examples of that pattern, they admit: Johnson & Johnson, for one. But there are also just too many counterexamples–in fact, the majority of the “visionary” companies, including giants like 3M, Sony, and TI, don’t fit the model. They were characterized by total lack of an initial business plan or key idea and by remarkably self-effacing leaders. Collins and Porras are much more impressed with something else they shared: an almost cult-like devotion to a “core ideology” or identity, and active indoctrination of employees into “ideologically commitment” to the company.
A new blog.
And here is my old one.