All posts by Sankarshan Mukhopadhyay

What will do when you are bored and nothing’s staying on your mind…

Yesterday a friend of mine who teaches CompSci at one of the colleges caught me on chat with the line that he was bored. Being from a school of thought which associates being bored with you-know-who’s workshop I thought it was time to get others do some bit of stuff I had never found time to check out.

So here goes:

Create a GNOME centric 2 CD Fedora based distribution. Just in case you wonder what it takes, here comes the listing of the required bits:

%packages

@admin-tools
@base-x
@dialup
@editors
@games
@gnome-desktop
@graphical-internet
@graphics
@java
@office
@printing
@sound-and-video
bsf
comps-extras

Just in case you feel lost – here’s the roadmap (look for the Anaconda Customisation links)

But the above is not enough to make your secret sauce work. Here’s some more bits of infrastructure changes you require to do:

[1] Ensure that you use a custom kickstart that always does askmethod for installs. Good for UseCases where you have a NFS/HTTP/FTP dump ready and of course a no brainer if you have the CDs at hand.
[2] Ensure that you have a rescue kickstart put in that does not format /home when re-installing
[3] Add yum to a cron that checks up the repositories on a daily/alternate day basis
[4] Shut down all unwanted services during startup
[5] Take out a few of the virtual consoles

And if you have done all this and are still not satisfied,

[1] Attempt to extend the functionality of Yumex by allowing repositories to be added through the GUI if an appropriate link-to-repo-file is passed.

[2] Take out the requirement of root user from the system or at least investigate the possibility

ps: While doing all of the above please ensure that you keep posting about your efforts to a blog/journal/website and perhaps also try and rustle up a few of the students as beta testers for this project.

Getting the work done

ICT (Information & Communication Technologies) for Development has been the happening buzzword for over a year now. A slew of reports on ICT4D ‘success stories’ in the ASEAN region and some specific to India have appeared. Surprisingly a good number of them refer to the success of the efforts without actually quantifying actually what has been done in terms of costs incurred and costs recovered. The other thing that does not get talked about or written about is the absolute lack of interest in infrastructure. ICT4D will be very much tied into infrastructure. Assume a place (and there are so many like these that you can just put a random name) where the power supply is erratic, the telephony network is in shambles and there is no semblence of a village school. How does one manage to create an ICT success there ? And this is precisely the point. In nearly all the cases of Indian ICT success stories, the chosen ones seem to have all the infrastruture details neatly sewn up and in place. The entire concept of requirement of a basic (or bare minimum) infrastructure is not talked about in the much hyped ‘funded projects’ which attract a lot of press and attention.

Lack of infrastructure also means that effective utilisation of the context of the deployment would not happen and thus the impact of the project would be much less that what is expected/projected.

Lose Control

No ! This is not an attempt to get folks to read through all my rants on FLOSS-IndicL10n-Deployment. Rather it is an attempt to figure out how to lose control and let chaos reign to get innovation going.

I have been blogging (and more often than not rambling) about this topic for so long that sometimes I am amazed as to why others don’t feel the same way. Here’s a collection of my rants from the past year:

http://sankarshan.randomink.org/blog/2005/08/31/should-we-be-taking-a-second-look/
http://sankarshan.randomink.org/blog/2005/08/29/or-why-indic-l10n-needs-to-find-its-tipping-point/
http://sankarshan.randomink.org/blog/2005/07/18/one-more-time-lets-go-for-a-complete-desktop/
http://sankarshan.randomink.org/blog/2005/05/31/getting-ahead-with-indic-localisation/
http://sankarshan.randomink.org/blog/2005/05/02/where-is-indic-l10n-nowadays/
http://sankarshan.randomink.org/blog/2005/03/08/is-this-it/

If you have gone through the links above, and reading them as on date – you would agree with me that the efforts have failed. Failed miserably to get a momentum going, failed miserably in getting a toolkit up and running, failed in doing the backend heavy lifting for the infrastructure in a coherent manner and where it hurts most – failed to get participatory model going for the community around Indic L10n. Indic (or for that matter any L10n) involves more than just the translators. It involves the distributions (and their release engineers), the local bodies who set/consult for standardisation on the various component aspects (Unicode, Thesaurus), the parties involved in creating dictionaries and spellcheckers, the developers who work on stuff like OCR, TTS and STT (among other things) and perhaps even alternative input methods that complete the experience of an Indic Desktop. The fun bit starts now.

Those who have been following the current trends in Ajax-ifying applications (del.icio.us etc) notice that a lot of the desktop use case is moving on to the web – there’s Google’s Writely (and the recent Spreadsheet applications). There’s Flickr and also the of course Picassa and others which are surely coming up. So where does this leave a complete desktop experience ? Very much where it was to begin with I would guess. The ‘desktop’ is not running away. And Indic L10n has strange ways of rearing its head. Imagine the scenario, in states like Kerala, the need for the UI in the local language might not be of great need. The state has done enough to ensure that there is a comprehension of a standard and basic level of English. What is however required in such cases is ‘Indic Support’. This does really mean the support for Input Methods, support for proper rendering and printing on the browser, a well documented method/algorithm for implementation of sorting and searching – which has long been the bane of any Indic L10n effort. The tragic bits are that in most of the cases these issues are being worked upon and resolved (and tested) – yet the information is not percolating fast enough and wide enough to get more folks excited and eager to test it out.

The time is ripe for taking the L10n stuff from pure string crunching to more on collaborative fronts involving as many folks as possible who are involved or are interested to get this going. We have crossed the first phase, we need to start planning for the second and the third stages.