Friday, June 20, 2014
Will the Internet kill Indian languages?
Thursday, July 11, 2013
Marathi Journalism in the Internet Age

Monday, June 03, 2013
RIP Atul Chitnis
Atul was one of the pioneers of the open source movement, popularizing Linux and open source with his numerous articles. Many years ago, as a part of the Mumbai Linux Users Group, I kept hearing of how popular the Bangalore Linux User's Group was and saw its popularity for myself when I was in Bangalore. I don't remember the year, but it was a wonderful feeling to attend the BangLinux meeting and see around a 100 FOSS enthusiasts gathered there. Over the years, I spoke at a couple of Bangalore Linux (later renamed to FOSS.IN) events and sought his help during the policy battles around OOXML and Open Standards.
With Raj Mathur and now Atul Chitnis passing away, the FOSS community has lost two of its pioneers, who will be sorely missed.
Tuesday, June 19, 2012
A quest for change in education
Saturday, April 23, 2011
The World Foresight Forum: Envisioning a better future
we would like to include your speech in the Convention, in the Seminar "Dealing with global challenges: a leadership crisis?", in particular on the topic "Development of a knowledge-based economy."
The project, an initiative of the Hague Centre for Strategic Studies, Granaria Holdings and TNO, aims at turning The Hague into the centre of the international debate on “Security, Peace and Justice for Sustainable Global Growth”, being already the de facto judicial capital of the United Nations, where institutions, such as the International Court of Justice and the International Criminal Court are headquartered.
Sunday, April 03, 2011
Moving on from Red Hat to Google
In the last year or so, there were several offers, but none of them really excited me because I was looking for a role that has a large social impact. When Google sounded me out, I thought this could be interesting because Internet penetration in India, especially the web in India languages, is one area that can have a large impact. I know that broadband, 3G, 4G etc are on their way, yadda, yadda, yadda, and Internet usage will inevitably grow, but those who have been involved in policy know that there is a great difference between having policies on paper and actually having *political will* behind those policies. For example, every politician and bureaucrat agrees that computing in Indian languages is a good idea, but our so-called software superpower of a country has not made this a reality, even as it relentlessly churns out code for the rest of the world.
Another reason for taking up Google's offer was that I'll be able to continue my involvement in open source and open standards. In some ways, it was also a good time to leave Red Hat because most of the defensive work needed to protect the open source community -- open standards, software patents etc -- have been taken care of. Apart from the FOSS non-profits like FSF and FSMI, the Indian FOSS community now has an layer of non-profits like IT For Change, the Center for Internet and Society, Knowledge Commons and others who look at FOSS from an outside-in perspective and advocate for FOSS as a social good. The setting up of the Software Freedom Law Center's India chapter has also helped give the community some sorely needed legal firepower. I feel that these developments have greatly strengthened the community.
I want to conclude by saying that I see great hope for the future, event though the current policy environment seems so bleak and depressing. is is because, in the last six-and-half years, I have had the privilege of working with many bright, passionate individuals who are working for the larger good. Some of them have left the civil service or the corporate world to work in NGOs, and most of them have the caliber to be successful entrepreneurs or business leaders but have chosen to be involved in the area of public policy. This is an exciting development that will change India's destiny.
Monday, January 03, 2011
ODF, OGG listed as standards approved for e-governance in India
The draft of the IFEG lists out the standards approved for e-governance in India. The last date for comments on this draft is 27th Jan 2011. The IFEG draft clearly says that ODF and OGG are standards approved for e-governance in India and proprietary document formats and multimedia formats are not mentioned at all. My understanding is that these standards will be included in the future Requests for Proposals (RFP) for e-Governance applications, which means that these standards will be baked-in to all future e-Governance applications.
Friday, November 12, 2010
Indian Open Standards policy finalized--major victory for the FOSS community
In the previous draft dated 25/11/2009, our major objection was to section 4.1.2 of the policy which said,
"4.1.2 The essential patent claims necessary to implement the Identified Standard should preferably be available on a Royalty-Free (no payment and no restrictions) basis for the life time of the standard. However, if such Standards are not found feasible and in the wider public interest, then RF on Fair, Reasonable and Non Discriminatory terms and conditions (FRAND) or Reasonable and Non Discriminatory terms and conditions (RAND) could be considered."The comments I submitted on behalf of Red Hat reads:.
While the term “Mandatory Characteristics” indicates that section is binding, the usage of terms like “should preferably” conveys the impression that this is non-binding. Since thousands of government agencies, systems integrators and others connected with e-Governance will look up to this policy for guidance, we request that the mandatory characteristics should be laid out clearly and unambiguously. As with the previous section, we feel that the intent and will of the GoI should be clearly expressed in this section. In any case, Sections 4.3, 4.4 and
5 deal with the exceptions.
The term “essential patent claims,” is not defined in the policy and this could prove to be a huge loophole. This term is also a new introduction and it would have been helpful to know the rationale for its introduction. Ultimately, any patent necessary for the implementation of a standard is an “essential patent claim” because a
standard cannot be implemented partially. In this context, I would like to point out that the Chinese government has issued a notification for the compulsory licensing of patents related to standards used in China. An English translation of this notice is attached with this letter for your reference.
Recommendation: We request that the wording of this section should be changed to "ALL patent claims necessary to implement the Identified Standard should be available on a Royalty-Free (no payment and no restrictions) basis for the life time of the standard.” We also request that the following statement, “However, if such Standards are not found feasible and in the wider public interest, then Fair, Reasonable and Non Discriminatory terms and conditions (FRAND) or Reasonable and Non Discriminatory terms and conditions (RAND) could be considered,” be moved to the sections dealing with exceptions. We feel that this section is the heart of the Draft Policy and placing an exception statement in the very heart of the policy will send out wrong and conflicting signals.
As you can see from the extract below, the points mentioned above have
been incorporated In the recently finalized policy. This section now reads:
4.1.2 The Patent claims necessary to implement the Identified Standard
shall be made available on a Royalty-Free basis for the life time of the
Standard.
Overall, I'd say this is a major victory for the Indian FOSS community
and more than three years of hard work have paid off. Now I need a loooooong break!
Wednesday, June 09, 2010
The challenges in using proprietary standards
Flash Co-Creator Jonathan Gay talks of the challenges they faced in using H.264 standard.
The second challenge was selecting a video codec. We wanted to use the cool new H.264 open standard but Macromedia did not feel they could afford the H.264 license fee. I believe that the capped $5M per year H.264 license fee was similar in scale to the annual Flash engineering budget at the time. The H.264 license fee model is very anticompetitive. H.264 licensing is free for very small users, expensive for medium size companies and inexpensive for very large companies. This model puts the midsize companies who could challenge the dominant companies at a significant competitive disadvantage and is the reason that we implemented the proprietary but affordable On2 codec in Flash instead of the open and expensive H.264 codec. The capped license fee also discourages large companies from building a competitor to H.264 because they can simply pay the capped license fee and know they are managing their patent risk and suppressing their smaller competitors. For example, it would have cost Macromedia $5M per year to add H.264 to Flash but it probably cost Adobe much less to add H.264 because they were probably already paying a substantial fee for their video editing products. You can probably thank the success of Flash video for the fact that streaming H.264 video over the Internet is free for another 5 years. Solving this patent license problem is probably why Google purchased On2. However, if they open source the latest On2 codec as people suspect they want to, it’s much easier to launch a patent lawsuit against them because anyone can inspect the source code. Given the large number of patents in the video space, it may not actually be possible to build an open source codec that does not inadvertently infringe on someone’s patent. The MPEG Licensing Authority solves the problem in a Borg-like way by adding any new patent challengers to their patent pool.
Thursday, June 03, 2010
Red Hat's comments on Draft Policy on Open Standards for e-Governance Version 1.1 dated May 2010
General Review Comments
Wonderful is your gift of knowledge
the more we share, the more it grows
the more we hoard, the more it diminishes
Hymn to Saraswati, the Goddess of Knowledge
Information Technology, and the Internet in particular, have opened up tremendous avenues for the sharing of knowledge. In the next two years, over two billion people (or one-third of humanity) will be connected to the Internet, making it the largest collaborative network in the history of mankind. Open standards are the most fundamental tool for the sharing of knowledge and we therefore appreciate DIT's leadership in creating the Draft Policy on Open Standards for e-Governance Version 1.1 dated May 2010.
In creating and implementing the Open Standards Policy, we hope that DIT will live up to the best of Indian knowledge traditions that placed tremendous emphasis on the sharing of knowledge. While genuine open standards foster the sharing of knowledge, proprietary standards prevent the free flow of knowledge by treating standards as a priced commodity or as trade secrets, owned and controlled by private entities. We hope that DIT will make a clear distinction between open standards and proprietary standards because this has larger implications beyond e-Governance and impacts the information society as a whole.
We recognize and respect the fact that DIT has a significant challenge on its hands when it comes to genuine open standards because many standards, currently in use, have evolved as de-facto standards that are proprietary in nature. At the same time, we request DIT to recognize the larger historical perspective, which places standards firmly in the commons; and that proprietary digital standards are an aberration of this norm. It is a well established convention of civil society that standards should be treated as a “common wealth” and belong to all, and NOT be controlled by private entities. If standards that we take for granted – like weights and measures – were proprietary standards that required royalties and OEM licenses for usage, the cost and social impact of the same can well be imagined. For example, multimedia standards are some of the most expensive standards in the world. A complete set of playback plug-ins costs around EUR 28 (approximately Rs 1,624). As we deliver e-government services right down to the village panchayats and seek to put computers in every school, the cost of these proprietary playback plug-ins could prove to be a heavy drain on the country's finances, affect IT penetration in India and thereby hinder the spread of knowledge.
On the other hand, open standards can accelerate the sharing of knowledge and the Internet and World Wide Web are the finest examples of this. For example, in 1994, Sir Tim Berners-Lee founded the World Wide Web Consortium (W3C) at MIT. It comprised various companies that were willing to create standards and recommendations to improve the quality of the Web. Berners-Lee made his idea available freely, with no patent and no royalties due. The World Wide Web Consortium decided that its standards should be based on royalty-free technology, so that they could easily be adopted by anyone.
It is therefore clear that open standards promote the public good, which is the primary responsibility of any government. The ultimate test of any open standard is – does it give us the freedom to share knowledge without any hindrance, without any terms and conditions? We hope that this is the yardstick that will be used to determine open standards for India.
Comments on Specific Sections
Section 4.1.2 of the policy states, “ The patent claims necessary to implement the Identified Standard shall be available on a Royalty-Free basis for the life time of the Standard. If such Standards are not found feasible then in the wider public interest, Fair, Reasonable and Non Discriminatory terms and conditions (FRAND) or Reasonable and Non Discriminatory terms and conditions (RAND) with no payment could be considered.”
We request that the following statement, “If such Standards are not found feasible then in the wider public interest, Fair, Reasonable and Non Discriminatory terms and conditions (FRAND) or Reasonable and Non Discriminatory terms and conditions (RAND) with no payment could be considered” be moved to the section 4.3 which deals with “Non-availability of Open Standard which meets all Mandatory Characteristics dealing with exceptions.” We strongly feel that this sentence is completely out of place, especially considering that it is currently housed in section 4.1 titled, “Mandatory Characteristics.”
We feel that section 4.1.2 is the heart of the Draft Policy and placing an exception statement in the very heart of the policy will send out wrong and conflicting signals. Also, in terms of sequence, the RAND/FRAND clause pre-empts the selection criteria listed in Section 4.4. It should also be noted that standards that are RAND/FRAND should be termed as “Interim Standards” and should NOT be termed as “Open Standards.”
For example, the H.264-encoded Internet Video format is currently free to end users until at least December 31, 2015. Once this period ends, MPEG LA, the licensing agency for H.264 may start charging royalties. Therefore, H.264 is a partially-royalty free standard, but cannot be considered an open standard because users do not have the freedom to encode and decode data and have to adhere to complex licensing conditions. Under the current wording of Section 4.1.2, H.264 may qualify as a suitable open standard for e-governance but this is clearly unacceptable in the long-term. For example, if Doordarshan uses H.264 to transmit a National Address by the Prime Minister of India over the web on 1st January, 2016, it may attract royalty that “...shall be no more than the economic equivalent of royalties payable during the same time for free television."
Therefore, we suggest, once again, that this sentence be moved to Section 4.4 and be modified to read, "If such Standards are not found feasible then in the wider public interest, Fair, Reasonable and Non Discriminatory terms and conditions (FRAND) or Reasonable and Non Discriminatory terms and conditions (RAND) with no payment, AND NO RESTRICTIONS ON REUSE, could be considered.”
4.3 Non-availability of Open Standard which meets all Mandatory Characteristics
Given the strategic importance of open source and its ability to free India from being technologically dependent on proprietary software vendors, we request that the open source community should have a strong representation in the Designated Body selecting the standards. We request that the process of selecting these Interim Standards should be an open and transparent process that seeks inputs from the public. Citizens should be clearly explained the logic for selecting these standards.
5. Exceptions for Selecting One or More Additional Open Standard in an Area
If multiple standards are selected for a particular area, the government should ensure that data is interchanged without any loss of information. If information is lost in the process of exchanging data, it would defeat the very purpose of having this policy. As with many other policies in India, we are seriously concerned that this exception clause should be used only in the rarest of rare cases and that the exception should not become the norm. Therefore we suggest that this sentence be modified to read as, “Such standard shall be compatible and bi-directionally interoperable, without any loss of data, with the already existing selected Standard.”
Going by past experience, we have seen that proprietary vendors who stand to lose their billion dollar monopolies, are willing to do anything possible to exploit every loophole available to them. Therefore, the constitution of the Designated Body is critically important. DIT must ensure that a transparent process is followed to include multiple stakeholders, including civil society in order to prevent institutional capture of the designated body. The constitution of the LITD 15 committee of the Bureau of Indian Standards is an example worthy of consideration.
Annexure Section m: Maturity -- An standard is considered mature if different implementations, commercial/open, are available, widely adopted and have been stable for some time.
We request that this be reworded to read as, “Maturity -- A standard is considered mature if different implementations in proprietary and open source software, are available, widely adopted and have been stable for some time.” It should be noted that open source software licenses do not differentiate between commercial and non-commercial implementations. The two major development models in the software world are proprietary (where the ownership of the source code is closely held) and open source (where users have the freedom to modify, share and redistribute the source code). Therefore, it would be more accurate to replace the term, “commercial/open” with the term, “proprietary and open source.”
A-I-6 Open Source: The term is most commonly applied to the source code of software that is available to the general public with relaxed or non-existent intellectual property restrictions.
The definition of “open source” is not accurate. There are specific licensing restrictions on Open Source Software. The purpose of these restrictions is to preserve the users' right to share, modify and redistribute the source code. We therefore suggest that the Open Source Definition of the Open Source Initiative be followed. It is the OSI that approves the open source licenses. The Open Source Definition is as under:
Introduction
Open source doesn't just mean access to the source code. The distribution terms of open-source software must comply with the following criteria:
1. Free Redistribution
The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.
2. Source Code
The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a product is not distributed with source code, there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost preferably, downloading via the Internet without charge. The source code must be the preferred form in which a programmer would modify the program. Deliberately obfuscated source code is not allowed. Intermediate forms such as the output of a preprocessor or translator are not allowed.
3. Derived Works
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
4. Integrity of The Author's Source Code
The license may restrict source-code from being distributed in modified form only if the license allows the distribution of "patch files" with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software.
5. No Discrimination Against Persons or Groups
The license must not discriminate against any person or group of persons.
6. No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
7. Distribution of License
The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.
8. License Must Not Be Specific to a Product
The rights attached to the program must not depend on the program's being part of a particular software distribution. If the program is extracted from that distribution and used or distributed within the terms of the program's license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the original software distribution.
9. License Must Not Restrict Other Software
The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software.
10. License Must Be Technology-Neutral
No provision of the license may be predicated on any individual technology or style of interface.
As with Annexure M, we request that the term, “commercial/open” be replaced with “proprietary and open source.” We would also like to suggest the addition of the following sentence, “The date on which the open standard came into existence will be given priority when it comes to making a choice between two competing open standards.” The reason for this is that an open standard that has been in existence longer is likely to be more mature.
Tuesday, May 04, 2010
Open Source offers more to CIOs
Open Source offers more to CIOs
“Quality. Price. Service. Pick any two,” said a very succinct placard in Damodar's tailor shop. Back in the days when clothes were tailored, Damodar was one of the best in the business and he definitely knew what he was talking about.
However, in the software industry, the emergence of open source software (OSS) has turned this dynamic on its head. It is no longer about, “Pick any two,” but “Pick ALL three.”
Take quality for a start. Studies by Coverity, have found that the number of defects per thousand lines of code is lower with OSS than with proprietary software. One of the most famous sayings in the OSS community is that “Many eyes make bugs shallow.” The open, transparent, community driven development model of open source has lead to the creation of some of the most robust software systems ever built. Those who have migrated from proprietary server operating systems to open source systems will happily testify to this fact. Is it any surprise that 446 out of the top 500 supercomputers in the world run on Linux? Or that mission critical applications like telecom billing solutions, stock exchanges and others are increasingly moving to Linux and other OSS systems?
On the price front, the industry has had to deal with the forced upgrade cycles, vendor lock-in and hugely bloated software licenses imposed by proprietary software vendors. While the development model of OSS is community driven, many commercial vendors have built business models around service and support for OSS deployments. Many top-notch system integrators around the world routinely incorporate OSS in the solutions they offer to their clients. Unlike their proprietary competitors, OSS vendors do not have to incur huge development costs and this enables them to offer high quality software implementations at prices lower than proprietary software vendors. The good news for CIOs is that OSS is no longer restricted to infrastructure software categories like operating systems and middleware, but has expanded to encompass application areas like CRM, ERP, Business Intelligence, Enterprise Portals, Content Management Systems and many others.
On the service front, everything boils down to how well the software is implemented and supported. In OSS, commercial vendors usually sell their services in the form of annual subscriptions that have to be renewed. The quality of services rendered to the client determine whether subscriptions are renewed or not. This gives OSS vendors an inherent incentive to offer good quality services. Therefore, CIOs should actively consider OSS while procuring software, especially where the OSS option is mature and meets their functional requirements.
Given the recent downturn in the economy, cost has been one of the reasons for more and more CIOs to turn to OSS. However, to be moneywise, CIOs should focus on all three aspects--quality, price and service. It may be tempting to go with OSS vendors who are the cheapest, but CIOs should evaluate the quality of skills available within the vendor organization before taking a final call. As I sum up, I cannot resist quoting from another placard in Damodar's tailor shop. “I have no quarrel with competitors who charge less. They know the value of their goods and services.”
Saturday, December 12, 2009
A quick visit to China
Friday, December 11, 2009
Assam government includes FOSS in state IT policy
The full text of Section 3.12 of the Assam Government's state IT Policy says:
(a) The Government would promote use of Free and Open Source Software (FOSS) in all the departments and State agencies, bodies and authorities.
(b) The State Government would promote manpower development and training in use of FOSS, especially in day to day office works.
(c) The State Government would promote imparting training on FOSS in schools and colleges.
(d)Entrepreneurs/ companies using FOSS for application/website development would be given preference over those using third party packaged applications.
(e)All source codes customized/developed for any State Government body shall be duly archived in a repository, and shall be made available freely to other Government departments.
(f) The Government departments and bodies would ensure that Open Document Format (ODF) is adhered to in creating and storing editable documents, data and information and all applications developed by the respective departments adhere to ODF and other Open Standards and are largely independent of Operating Systems (OS) and web browsers.
(g)The Government departments and bodies would ensure that any generic hardware procured has support for multiple Operating Systems(OS) such as Unix, Linux, Opensolaris and other open source platforms.
To download the full text of Assam's IT Policy, click here.
Friday, October 23, 2009
Even slaves were considered property: South African Minister
We cannot be in Dakar without being painfully aware of the tragic history of the slave trade. For three hundred years, the Maison des Esclaves (Slave House) on Gorée Island, was a hub in the system of forceful transportation of Africans as slaves to the plantations of the West Indies and the southern states of America. Over the same period people were being brought as slaves from the Malay Archipelago and elsewhere to South Africa. The institution of slavery played such a fundamental role in the early development of our current global economy, that by the end of the 18th century, the slave trade was a dominant factor in the globalised system of trade of the day.It is good to remember this at a time when organizations aim to justify the privatization of knowledge and ideas under the guise that this is essential for promoting innovation.
As we find ourselves today in this new era of the globalised Knowledge Economy there are lessons we can and must draw from that earlier era. That a crime against humanity of such monstrous proportions was justified by the need to uphold the property rights of slave owners and traders should certainly make us more than a little cautious about what should and should not be considered suitable for protection as property.
Wednesday, October 07, 2009
FOSSCOMM Meeting this Sunday (11th October, 2009)
FOSSCOMM (FOSS Community of India) will hold its third meeting in Mumbai at the Homi Bhabha Center for Science Education, Mankhurd (Near BARC/Anushakti Nagar).
The first meeting held in Bangalore started to process of getting the FOSS Community of India working together. After the second meeting held in Delhi in July 09, FOSSCOMM started making interventions in areas like open standards, school education etc. I hope that the Mumbai meeting will lead to the creation of working groups that will provide leadership to FOSSCOMM's efforts to accelerate the growth of Free and Open Source Software movement in India.
Those interested working with the community are invited to attend the upcoming FOSSCOMM Meeting on 11th October, 2009.
Thursday, September 10, 2009
Wednesday, August 12, 2009
Patent Woes: Speechless about the Word judgment
Judge Leonard Davis, of the U.S. District Court for the Eastern District of Texas, ordered a permanent injunction that "prohibits Microsoft from selling or importing to the United States any Microsoft Word products that have the capability of opening .XML, .DOCX or DOCM files (XML files) containing custom XML," according to an announcement by the plaintiff, Toronto-based i4i Inc.Judge Davis ordered Microsoft to pay $290 million in damages. The abstract of the i4i patent reads,
A system and method for the separate manipulation of the architectureWhile I am not a big fan of Microsoft, even I have to admit that this is crazy. But wait a minute! Didn't Microsoft get a patent last week for "Word-processing document stored in a single XML file that may be manipulated by applications that understand XML."
and content of a document, particularly for data representation and
transformations. The system, for use by computer software developers,
removes dependency on document encoding technology. A map of metacodes found in the document is produced and provided and stored separately from the document. The map indicates the location and addresses of metacodes in the document. The system allows of multiple views of the same content, the ability to work solely on structure and solely on content, storage efficiency of multiple versions and efficiency of
operation.
The abstract of the Microsoft patent reads,
A word processor including a native XML file format is provided. The well formed XML file fully represents the word-processor document, and fully supports 100% of word-processor's rich formatting. There are no feature losses when saving the word-processor documents as XML. A published XSD file defines all the rules behind the word-processor's XML file format. Hints may be provided within the XML associated files providing applications that understand XML a shortcut to understanding some of the features provided by the word-processor. The word-processing document is stored in a single XML file. Additionally, manipulation of word-processing documents may be done on computing devices that do not include the word-processor itself.So, is someone playing tit-for-tat or an-eye-for-an-eye? Mahatma Gandhi said, "An eye for an eye makes the whole world blind." In the weird, wonderful world of digital technology where greedy corporations can convert standards (that should rightfully belong in the commons) into private property, anything can happen.
Friday, August 07, 2009
The Power of Open Source Development
The Power of Open Source Development
Using open source development methodologies, John O'Hara, of JPMorgan developed a standards-based alternative to expensive proprietary middle ware
By Venkatesh Hariharan
Most literature around open source focus on using open source software. While the benefits of OSS are gaining increased recognition, some smart organizations are going a step further and applying the Open Source Development Model (OSDM) to solve problems that proved to be otherwise intractable. OSDM is based on collaboration, community and the shared ownership of knowledge and Linux is one of the best examples of how this model works.
In September 1991, Linus Torvalds released 10,000 lines of source code for Linux and licensed it under the liberal General Public License that gave anyone permission to copy, modify and redistribute the code. The only condition was that anyone making improvements to the software and redistributing the changes had to share the improvements with the rest of the community. This liberal license attracted thousand of contributors over the years who contributed their bit to improving the code base of Linux. A Linux Foundation study found that Fedora, a community Linux distribution has now grown to contain almost 204 million lines of code.
There are two reasons why Linux and other open source software have demonstrated such explosive growth. One is the growth of the Internet, which is the largest collaborative platform in the history of mankind, connecting 1.4 billion people across the world. The other is the open, participative, distributed development model of open source where users are actually encourage to contribute to the development of the software. This is in sharp contrast to proprietary software that allows very limited rights to users.
Some of the most savvy technology users are embracing the participative nature of open source software to build technologies that suit their needs. For example, John O'Hara, senior architect and distinguished engineer at JPMorgan launched AMQP (Advanced Message Queuing Protocol) as an open source project after being frustrated with developing front- and back-office processing systems at investment banks. “It seemed to me that we were living in integration Groundhog Day - the same problems of connecting systems together would crop up with depressing regularity. Each time the same discussions about which products to use would happen, and each time the architecture of some system would be curtailed to allow for the fact that the chosen middleware was reassuringly expensive,” says O'Hara.
In 2003, O'Hara embarked on a quest to standardize MOM (message-oriented middleware) technology, to enable mission critical enterprise applications to send messages to each other in a reliable and scalable manner. He decided to break from the past by using OSDM to start the AMQP project and sought Red Hat's expertise in governing open source projects. “Red Hat took the lead in establishing the legal framework for the standard; it, too, understood the issues in managing open intellectual property. The key part of doing this is to ensure that everyone contributing has the authority to do so and that there is a paper trail from every potential owner of IP through to the group effort, and that the intent to share is clear even in draft revisions of specifications. The result was a contract that clearly committed the members of the working group to promote unrestricted open middleware through AMQP.” For developing the software, O'Hara tapped iMatix, a boutique European development house that had clearly demonstrated a commitment to open source.
The AMQP project is a perfect example of what Prof. Eric Von Hippel, Professor of Innovation at MIT's Sloan School of Management calls, “user-driven innovation.” In his book, Democratizing Innovation, Von Hippel says that open source software projects are exciting examples of complete innovation development and consumption communities run by and for users. Today, users like Credit Suisse, Deutsche Börse Systems, Goldman Sachs, JPMorgan Chase Bank Inc, the TWIST consortium and others partner with IT leaders like Cisco, Red Hat, Microsoft and others in the AMQP consortium.
Ultimately, the proof of the pudding is in the eating. AMQP today has several implementations in open source and proprietary software. Imatix built an open-source implementation called, OpenAMQP. The beta version went live in 2006 and by the following year it was supporting 2,000 users on five continents and processing 300 million messages per day. Today, there are several open source and proprietary implementations of AMQP, including OpenAMQ, the original open source implementation. In a powerfully interconnected world, the open source development model used to build AMQP demonstrates the the power—and value—of collaborative software development.
Tuesday, July 21, 2009
Delaying tactics from industry associations?
I am told that industry associations have asked for more time to submit the views of their members and therefore Department of IT has postponed the next meeting of the Apex Committee to review the Draft Open Standards Policy. The meeting was to have happened on 15th July, 2009 but will now probably be held in August 2009.
Now here is the interesting bit. The industry associations asked for more time so that they could go back to their members and ask for their opinions. And here, I am trying to break down the doors of NASSCOM to submit Red Hat's opinion and what do I get? Dead silence. I hear that their deadline was June 7th and then extended to June 15th and I don't know if there is a new cut-off date. But I do know that despite writing to NASSCOM, I haven't heard back from them.
Is this one more ploy to delay a policy that has already been long delayed?
