Deprecated: register_widget_control is deprecated since version 2.8.0! Use wp_register_widget_control() instead. in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/functions.php on line 4853

Deprecated: register_sidebar_widget is deprecated since version 2.8.0! Use wp_register_sidebar_widget() instead. in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/functions.php on line 4853
Random thoughts and serendipity | A collection of jottings on various issues that excite no one else | Page 6

One browser too many

It struck me this morning that I end up using too many browsers. For example, at this precise moment, I have Firefox, Chromium, Seamonkey, Epiphany and Opera being used for all the content that I need to take a peek at. Which is a far cry from the days of having shell access and, using the console to browse. These days, I tend to complain about the browser experience on my e71 more than on the Maemo. Which says a lot about what I am using to be online.

And, all because at some point in time I had a kickstart that pulled in Firefox, Epiphany and Seamonkey. Chromium looks to be a decent enough browser in spite of that annoying bit about not being able to handle Complex Text Layout. Remember to read this fine blog post if you want to set it up for Leonidas/Fedora 11.

Speaking of Firefox, at some point recently, I was using a boatload of add-ons to aid my browsing habits. The one that did come in handy was the Tree Style Tab add-on. It did reveal interesting patterns in the paths that I follow while browsing. Another nifty add-on is the Split Browser one, couple it with Tabs Open Relative and, you have a much more intuitive experience while browsing.

Update: The comments led me to Feedly, which I find to be awesome.

তুমি কেমন করে গান করো হে গুণী,
আমি অবাক্ হয়ে শুনি কেবল শুনি ।।
সুরের আলো ভুবন ফেলে ছেয়ে,
সুরের হাওয়া চলে গগন বেয়ে,
পাষাণ টুটে ব্যাকুল বেগে ধেয়ে
বহিয়া যায় সুরের সুরধুনী ।।
মনে করি অমনি সুরে গাই,
কন্ঠে আমার সুর খুঁজে না পাই ।
কইতে কী চাই, কইতে কথা বাধে —
হার মেনে যে পরান আমার কাঁদে,
আমায় তুমি ফেলেছ কোন্ ফাঁদে
চৌদিকে মোর সুরের জাল বুনি

Elections, candidates and questions

The final list of candidates for the GNOME Foundation 2009 Elections are out. The statement(s) from each of the candidates are somewhat shorter than what they used to be. However, given that it is as good a time as any to ask questions to the candidates, I figured a couple of them below (the appropriate forum has the questions already) would not be out of order:

  • What are the specific areas of the Foundation’s focus and strategy where you think you can contribute as a change agent ?
  • What, in your view, are the top 5 requirements (from a strategic perspective) of the GNOME communities/tribes/groups world-wide ?

As always, it would be an interesting year for the Foundation with lots of coolness coming up.

pem and the art of expense management

I was looking for an alternative to keeping track of expenses via a spreadsheet. Given that it isn’t too intuitive, the alternative was scribbling it on pieces of paper and then collating them when I have time.

Somewhere along the way came pem. This command line tool is elegantly simple to use. Having the developer nearby also means that I can “demand” features in the software. Prasad has blogged about his recent release. I just love the fact that it allows me to publish a simple report of expenses by category. Comes in very handy to produce a report for Max. I have been using it for a while to keep track of the “Community Architecture” related expenses that I am accountable for.

Highly recommended. By the way, this blog entry is being written with the offline client for WordPress called Lekhonee. If you have been using WordPress and, desired an offline client, give this a try. The developer could do with some feedback as well.

ps: Contrary to rumour, pem isn’t pjp expense manager 😉

A letter for Sayamindu

Dear Sayamindu,

It is good to see you blogging after a break. Now that you have got the rant off your chest, I hope you are feeling better. Catharsis does work.

You ask, somewhat rhetorically, as to why you should bother ? There are a lot of layers to that question really. Should you bother about coaching your peers and juniors in the “right” things ? Or, should you be bothered about the employment bits that make all the education and years spent so irrelevant ?

I firmly believe that you should bother. In fact, I hold on to the theory that you should get agitated enough to be bothered more than you are currently. There is no escaping the fact that the world is changing and, with it, the patterns of employment. Traditionally, Indian IT companies of the SWITCH and now TWITCH group have hired freshly minted software engineers by the ark-load. In fact, there are times when I have wondered about how do they end up managing the task of the massive hires. When you hire at that quantum, the focus is less on skills and, more on whether there is “aptitude” as measured by some tests devised by the departments involved. And, since there is an extensive “training” of the new hires involved as part of the cycle, it is comfortable for them to assume that basic knowledge would be drilled into them eventually.

It isn’t really about Python. I guess the issue here is do the folks whom you guide and, for a very valid reason, feel responsible for, realize and accept that there are opportunities outside of the traditional TWITCH group ? Or, that, given accomplishments, they can actually be spoilt for choice in terms of assignments they land up with ? Sadly enough, my experiences have been somewhat negative. Since getting into a services sector job hasn’t been too difficult, students seem to have become complacent (and, yes, I know that this is a grossly general statement) and, decided not to exercise their choice to “be excellent”.

Choosing to become a zombie is an easy decision. Choosing not to and thus striking out a path for themselves requires courage. So, the question I ask is – what can we do to instill that courage in the folks we encounter ? What can be done so that they can be brave enough to reject a call to mediocrity and, embrace the discipline and strength needed to really “innovate” ?

It is a sad fact of life that B players generally hire Cs. So that they can appear smart to the outside world. How can we coach the students to aspire for nothing less then being an A and, demand the very best of their employers ?

So, the question isn’t really “Why should I bother ?” – it is “What can we do to change the system ?”

The number of comments on your blog does prove that there are a large group of people unhappy with the current state of things. The larger that group is, and, the more work that gets done, would be the starting point of things changing.

~sankarshan

ps: Be bothered. That’s the only path to sanity.

Of books again

Spent a greater part of the day reading A Better India, A Better World by Narayan Murthy. And, for better or, for worse, re-read a few parts of Imagining India: Ideas For The New Century by Nandan Nilekani.

There is nothing much to be said about the book from N Murthy. A collection or, more aptly, a collation of his speeches and writings these are collected around various themes. A basic point which the publishers might have considered is the selection of font and size. A book that is wholly text matter based requires a much pleasant font and comfortable spacing rather than the close-spaced result that one sees in the book. There are a few things that stand out when one reads the collection:

  • his speeches tend to have repeated imagery and quotes and, a bit of sameness that becomes jarring if the book is read as a whole
  • while the speeches employ rhetorical flourishes, the writings, especially in the columns of business journals have a much sharper edge and clarity
  • “Be the change you want to see” is a theme oft repeated and, provided for via various examples. And, I did end up liking a number of the anecdotes.
  • The sections on Values, Leadership and, various addresses to the students are worth a re-read.

All said, I had a different set of expectations from the book. Probably, that was one reason I ended up re-reading segments from Nandan Nilekani’s book. Narayan Murthy has been somewhat “up there” and, expecting a bit more insight in terms of vision isn’t asking for the moon. So, whereas Nilekani’s book does a thorough overview of a situation and digs dip down into nuts and bolts operational parts, Murthy’s writings tend to remain a bit on the “preachy” side. And, somewhat dispassionate. The book is worth reading if one has heard or, read him infrequently, else, borrow a copy to read up the section on Values. Might be worth it.

I know what happens each summer

The onset of summer is generally characterized by stifling heat, mangoes and, a rush of CVs from students who want to do summer internship projects. That is, GSoC notwithstanding. It happens each summer, unfailingly and inevitably. There are two specific trends that are observed in the CVs:

  • most of them are from students pursuing some form of Computer Science and Engineering or Information Technology
  • a larger percentage of them would be making their first contributions to the world of FOSS if they end up working on a FOSS project

The first part is an area that sometimes make wonder if we cannot reach out to folks from other streams to spend their summers productively. There is an increasing need to have cross-discipline interaction and, while CompSci and IT may be an easier path to matchmaking, how do we end up getting other people interested as well. For example, say folks from the Arts and Fine Arts, other Engineering disciplines etc. Ideas and comments welcome on that.

The way to solve the second part of the problem is somewhat simpler – devise a very “high touch” mentor-protege driven system wherein the first_time_participant is given an intensive orientation in the basics of how to participate in a project, how to provide bug reports, how to create patches etc. Additionally, teaching them the basics of using FOSS infrastructure bits like mailing lists, IRC, version control systems and so forth. The point of failure in this path is of course when there is a project/task to be identified and handed over to the student to attempt to solve. The following issues come up:

  • most upstream projects do not seem to have bugs/tasks marked with something like “student project” which makes it a somewhat tedious job to sift through a whole lot of possibilities before hitting on a particular cache of tasks
  • there are no ‘defined’ upstream mentors for the tasks, so, even though a student might be able to deliver most of the tasks by {him|her}self, there is a lack of upstream ‘buy-in’
  • the above two couple together to the conclusion that there is no proper assessment of the time estimate for a task/project

I often hear the question that “if there isn’t any interest from upstreams, why not get them working on projects that are relevant for problems at hand ?” And, the answer to that is something along the lines of “having first time participants contributing to upstream projects is a quicker means to coach them into good citizens than having them think up, design and deliver their own projects”. There are days I wish that each upstream had something like “summerprojects.upstream.domain” kind of filtered view of tasks/projects with a mentor who could provide a bit of abstract/summary of what that task means. It isn’t really a big ask – and a little bit of push from the bodies that oversee the project could make this happen.

And, since the upstreams are nothing but what their contributors make them out to be, I keep on doing my bit to coax and cajole them into seeing the value in this. Especially so because with each passing summer I notice that the caliber of the students are somewhat on the upside of the scale.

Digital Content in Local Languages: Technology Challenges

I was reading through an article of the same name by Vasudeva Varma. Barring a whopper of a statement, the author does a reasonable job of pointing out some of the areas that needs to be worked on. To begin with however, let’s take that statement:

For example, Hindi is rendered properly only on Windows XP and beyond. Though there are some efforts to create Indic versions of the Linux, largely there is very little support for Indian languages.

It is a bit out out of context but nevertheless it is worth pointing out that one would have expected a bit more accuracy from the author. Especially because availability of Indian languages and their ease of use on Linux distributions have improved significantly. And, folks who use the Indian language Linux desktop on a regular basis for their usual workflow are somewhat unanimous that “things do work”. In fact, it would have been nicer if the author had taken the time to test out a few Linux distributions in the native language mode to identify the weak points. Most of the upstream projects do have very active native language projects with a significant quantum of participants from Indian language communities. For example, translate.fedoraproject.org, l10n.gnome.org, l10n.kde.org etc are the ones that come to mind immediately.

At a larger level, I would whole heartedly agree with the author that there exists gaps which need to be filled up. For example, with the desktop and applications getting localized, there is an urgent need to have “Cookbook” like documentation in native languages primarily for desktop applications. There is a greater need to improve existing work on the following:

  • spell checkers
  • dictionaries
  • OCR

for the various Indic languages so as to enable a more wholesome usage of desktop applications. Sadly enough, a large bulk of the work around the above three bits are still “in captivity” at the various R&D initiatives across institutes in India with not much hope of being made available under an appropriate license allowing integration into FOSS applications.

The other part of the equation are folks who create content or, collate content ie. the writers and the publishers. To a large extent, there is a dearth of large volume of local language content on the Internet. And while it could have been said that the difficulty with Linux and Indian languages was a show stopper, it isn’t really so any more. “Better search” has been a buzzword that has been around for a while, but till the time a quantification of better does happen, it isn’t impossible to get along with what is available right now. The primary barriers to input methods, display/rendering and printing have been largely overcome and, the tools that allow content to be created in Indian languages are somewhat more encoding aware than before. With projects like Firefox taking an active interest in getting things going around Indic, I would hazard a guess that things would get better.

Which brings us to the Desktop Publishing folks. I have talked about them and the need to figure out their requirements a lot of times. Suffice to state, the DTP tools need to be able to handle Indic stuff far better than they do now. And, probably we do have the work cut out there.

Google Summer of Code 09 etc

This time around, the variety of proposals which have been selected for The Fedora Project & JBoss.org combination are awesomely nice. Congratulations to all those who did make it and, for those who could not – I’d say that this is a learning opportunity and, we would look forward to your continued participation and contributions to the project. There is plenty we can learn from each other and, these are the times to make use of the opportunities

Turns out that India has the second highest number of accepted proposals. I recall reading earlier that the number of proposals/applications from India was significantly high as well. However, I’d say that this is just a beginning and 101 isn’t really a number to be going to town about. Sure it is better than where we were 3 years ago. But, the world has also progressed since then and, we just cannot keep on benchmarking without adjusting for that change. There are certain trends which are nice though. Things like second time applicants, applicants turned mentors. These indicate the willingness to participate, to contribute, to collaborate and to coach – all important ingredients in the great rush to become a better FOSS citizen.

It is a privilege to be a mentor because it gives one a chance to read the proposals before hand, help in scrubbing and polishing them and, to take a dipstick test into the trends of FOSS adoption and awareness in the country. And, the T-Shirt is a nice incentive 😉 Among the few things that do come to mind include the need by all the projects to lay frameworks that can coach the young participants more effectively – work towards bringing them up to speed throughout the year and, show them how to think. The last point was hammered home in a number of proposals that seemed to have a distinct lack of originality. While we rejoice and blog triumphantly about the increase in India’s contribution, we need to keep in mind that this is just a start of the contribution process and, the virtuous cycle ends when the contributors of today become confident enough to take the role of mentors of tomorrow.

I am sure that the following have been written again and again, but I’d say it is never enough. For those who want to participate in GSoC and work towards a good application, it would be nice to keep in mind some of the following.

  • Participate early, participate continuously – a project can become confident of the student’s ability to deliver if there exist proof that the student has what it takes to take the idea from a concept stage to a deliverable. So, do not land up on a project during GSoC, give it some deep thought and engage in a structured fashion much earlier so that the developers know who you are and what you can do.
  • Think, don’t just read – if there is constant participation, anticipating a potential GSoC project becomes much easier. Thinking about it in the perspective of relevance and value to the project gives it the much needed shine. This also means that it is easy to write a proposal around an idea than just verbatim copy of the text of the idea into the proposal
  • Talk, don’t just write – it is important to indulge in public discussion of the ideas, the proposed paths and initiate discussion. GSoC proposals are not fire-n-forget type documents. They need constant attention
  • Listen, don’t just talk – a good proposal is one that discusses it with potential mentors and, can evolve through discussions and suggestions. Keeping eyes and ears open to good ideas also demonstrate a willingness on part of the candidate to become a better contributor and a good participant

Global <-> local

In all the years that I have been interacting with the various upstream FOSS projects, reasoning and convincing various groups to have a ‘local’ view of issues that complements the global strategy has been an uphill task. Sometimes it is just that interpersonal relations have been able to overcome the curve. At other times, it has just been a constant pegging away with facts, data points and a regular representation of issues that validate the need to approach and integrate local issues within the fold of the greater goals of the project. Either way, it makes me happy to see another project realize the need to align the views and inputs of the local participants and, figure out ways and means to respect their inputs and listen to their feedback.

The Regional Groups aspect of OpenOffice.org has gone a bit unnoticed and somewhat unloved (and, it has been my fault since I do not recall talking too much on this). This would be one area where it would be good to have a few folks stand up and take ownership as a steward.

In other news of the day, I have an @gnome.org alias for myself (thanks SysAdmins). Sadly, it has the usual pain of making a botched job of my actual name and, by now, I am so used to folks chopping up my first name every way they feel that I am more amused and less bewildered at the lack of appreciation of names.

A collection of jottings on various issues that excite no one else