PEN Source development is fast. Patching and development using this paradigm is particularly fast owing to modularity. Any change to the code is rather predictable within the isolated black (glass rather) boxes, so patches can be issued without laborious patching. Then comes the introduction of innovation and incorporation of code that leads to beautiful complex systems (video) very rapidly.

See video! Really, please do. I’m waiting. After I had wiped the coffee off my screen and keyboard from the excitement (well, figuratively-speaking), I came to realise that another trait of Open Source development is that it’s very responsive to user demands and needs. It’s nice to be able to submit a feature request of a bug or a patch to a project and then receive it from the development team the next cycle, for free. It’s nicer to know that millions more benefit from the same changes/inclusion, which gives the 15 pixels of fame many crave for.

IEBOLD machines—or more generally—closed-source E-voting remain problematic. There must be transparency for trust and validation. A standard, old-fashioned and paper-based election has the whole protocols recorded, so votes involve supervision and public understanding. Likewise, algorithms should be made public. The public can then spot bug and make suggestions (patches) until the code is bug free and can be trusted. Is there any ‘paper trail’? If so, how is it encoded? Proprietary formats? Many question clearly arise.

UPLICATE entries are some of the evil residues of sites where editorial involves many people. There are ways of preventing duplicates (dupes), but none is perfect.

I personally find Digg’s dupe detector somewhat flawed because, by the time the user finds matches based on similarity, much of the entry (and effort) has already been put into it. The user is thus tempted never to retract and concede the submission. Netscape, on the other hand, checks for title and URL similarity (identity only) in-line.

Wishlist items:

• Have matches that are more ‘fluid’ appear on the side while input is entered (not just exact matches)
• Permit the user to preview without entering a channel and without tags. This enables the submitter to check for dupes before giving some supplemental information. I am aware that it requires some parsing of the text, which is harder than using tag-based similarity.
• What would be nice is an option for supplemental items, URL’s, and followup news. Maybe have a hierarchical connector between related items, or at least some linkage that connects an item with a correction, clarification, op/ed, etc.

Season of the playful penguins from Oyonale

OR the past few years I have been advocating Open Source technologies, which I confidently argue will pummel proprietary equivalents. Packages mature in a layered fashion (thanks, GPL!), which makes them too hard to beat over time. They strengthen at a high pace owing to parallel development while the costs of code are minimal or non-existent. Their complexity is high and level of functionality breathtaking.

Take PHP-Nuke for example. Sure, I have this (software) package installed in a couple of places, but it doesn’t make me a prick (pardon the subtle pun). It makes me efficient and it makes any projects economically viable. So, why is it that such projects mature so nicely? I guess one can always harness some PHP skills by looking at that transparent (non-binary) code and rely on ‘heredity’ from prior project. When a project contains some of people’s ‘DNA ‘footprint’, there is individuality, creativity and self-expression involved. This leads to greater dedication, a sense of responsibility, and ownership. And money can by all means be made in this process of self-expressions. Take for instance the Linux patchmaster/janitor, Andrew Morton, who left to join Google while working on the kernel, still.

Open Source software is bound to be the sole winner. Give Open Source a few more years and find out for yourself. Check it out, mate. Checkmate!

Out from afar I continue to observe an American domination that expands through integration, acquisitions, and a worrisome process of ‘innovation’ takeover. Here is an example from yesterday’s technology section.

Yahoo!’s shopping spree is showing no signs of letup. During the past 18 months, the online media and search giant has acquired photo sharing startup Flickr, social bookmarking site Del.icio.us, and Upcoming, a user-generated social events calendar. It has also tried to acquire social networking site Facebook for upwards of $1 billion.

Microsoft, Oracle, and Google (among a few others) are no exception. Microsoft in particular has been buying plenty of startups in order to penetrate the Web. Larry Ellison eliminated Open Source threats by buying them off (this includes an attempt to snatch MySQL, having led PeopleSoft to their demise). And while Oracle uses Linux very heavily and has seen a sharp rise in profits, it all makes you wonder where the global industry is headed. Technology is not the only sector affected. Giants such as MacDonald’s or Wal-Mart are there to remind us that they can go global and eliminate mom-and-pop stores in the process. Ultimately we may all find ourselves enslaved to few powerful players whose leaders accumulate billions.

This is made worse when large players liaise in order to squash any emerging threats (disruptive technologies such as Open Source software). Essentially, they promote their own agendas using seemingly-infinite powers and resources. As an example:

Why the world needs openness, not interoperability

This NAC/NAP lovefest would be laughable if it weren’t such a kick-in-the-teeth to the rest of the industry, enterprise IT, and all Internet users. A Cisco/Microsoft oligopoly stalls implementation, stifles innovation, and makes the network less secure. In this way, Cisco and Microsoft are standing in the way of progress.

Unless legistlation changes, only the universe is the limit. Corruption, lobbying, and shilling do not help either.

AST month I discussed the need to generalise and open one’s own resume, as means of being fit for more jobs, as well as never be bound to one commercial product or vendor. This led me to have a quick look at my personal pages which I wrote several years ago. As the footers indicate, the introduction and CV page are well out-of-date. I have not bothered to get them updated for years, but I still maintain my real (full length) CV, which is not public anymore. It’s usually out-of-date as well, for the reasons I describe below.

I write down ‘patches’ on my PDA whenever an suitable addition is pending, for the CV or other documents that I maintain for some purpose (all written in L^AT_EX). The extended CV, adjoined with a personal lift journal that I retain, is already approaching 100 pages in length. As my mind has a limited capacity for remembering past events and achievements (sometimes reusable, e.g. for other formal and much-required documents), over the years I decided to write them down whenever they cropped up in my mind. So that’s how the idea of accumulating ‘patches’ to documents (notably the CV) was born. Writing text can be assimilated to the model of writing code.

NLY a year ago, before ODF became the ISO standard, I had to engage in lengthy and complex arguments over formats. I was doing fine by my own, but the issue of exchange arises in wider public arenas. Not anymore though. The crowning of ODF gives all the protection that I require. Here is an anonymised E-mail that I have just sent.

>Dear Roy
>>
>> Please can you email a sample of your presentation file so
>> that the IT guys here can find the relevant software and
>> load it onto the equipment in the lecture room.
>>
>> Please send it by return

Hi [anonimised],

This file is in OpenDocument Presentation format, which
is the international standard for presentations (ODF). One
common applications that handles it is OpenOffice 2. I
understand that Microsoft intends to catch up with the standards
in Office 2007, essentially by supporting ODF through a plugin.

Many thanks in advance,

Roy

I will be presetning at Oxford University later this week.