Technetra

Archive for November, 2004

Book Review: The Definitive Guide to Plone

Friday, November 26th, 2004

Earlier this year I was evaluating a couple of content management systems (e.g., Bricolage, Typo3, Plone) for a project. Every system had compelling features, but Plone provided the best overall feature set (e.g., search, templating, workflow, user management) in a single package. Plone runs on top of Zope, a popular Python-based open source web application server. Many consider Zope to be Python’s killer-app, similarly Plone may be one of Zope’s killer-apps. After my initial experimentation with Plone, I was really impressed with its ease of use and the power and flexibility of its page templating system. Strengths aside, Plone’s online documentation did not adequately address advanced topics. I often found myself sifting through bits of online howtos and other people’s examples to understand how to do certain things. Not only was this time consuming but also hit-or-miss.

The Definitive Guide to Plone

The Definitive Guide to Plone

Enter The Definitive Guide to Plone by Andy McKay. This book provides a series of task-driven chapters with practical information necessary for you to develop great web applications in Plone. The reader is assumed to be knowledgeable about HTML, CSS, the Web, and Python (for advanced features of Plone). Each chapter begins with an overview of what will be covered and uses examples to clarify concepts. A novice user can read cover to cover and come away with a working knowledge of Plone and be able to create relatively sophisticated web sites. A more advanced user can skim the chapter outline, pick and choose topics of interest and quickly find answers.

Who is the author? Andy McKay is a core developer of the Plone CMS project and an active contributor to a variety of Python-based open source projects. McKay also maintains ZopeZen.org, a web site dedicated to Zope applications and extensions. All the examples in this text were reviewed by well-known Zope authority Michel Pelletier, co-author of the Zope book.

McKay aims for the novice user in the first four chapters. Beginning with a high-level introduction to the benefits of content management, then on to installing Plone, and finally how to do basic content editing and customizations. Those of you getting started with Plone will find the chapter on customizations to be most helpful. It shows you everything from changing a folder’s default page to altering navigational tabs, further demonstrating Plone’s flexibility. You’ll notice that some of the text in this section is fairly self-explanatory (i.e., form field descriptions). You should be able to get going with a moderate Plone site after reading this section.

The next six chapters (5-10) go under the hood of Plone, and aims for administrators and developers. Templating is one of the first stumbling blocks when learning to use Plone, remarks McKay. To that end, McKay provides an excellent introduction to the building blocks of Plone’s templating machinery, Template Attribute Language (TAL) and Macro Expansion TAL (METAL). McKay goes on to show you how to develop Script (Python) objects and web forms. Next, McKay breaks down Plone’s concept of “skins” — images and styles surrounding the content, using the NASA Mars Rover website as an example. McKay moves on to discuss content workflow, one of the more complex features in Plone. Although he manages to explain individual concepts (e.g., states, transitions) well, he could have used some tougher (more real-world) examples to help readers tie in these concepts. Finally, the last two chapters in this section explain how to setup site permissions and users, and also integrate Plone with other systems (e.g., Apache, LDAP). Users looking to customize an existing Plone site should pay special attention here. Be sure to try out the examples, they will help you understand the concepts faster.

The last four chapters tackle advanced topics such as developing custom content types with Python code and Archetypes, indexing, and scalability. McKay provides an in-depth comparison of two approaches for creating new content types. First, using Python code to define content attributes, and second using Archetypes — a schema-based framework. McKay points out that Archetypes is the preferred way for development of products and content types by the Plone team. You can even use UML tools to model your content type, then generate a schema using ArchGenXML. From caching policies to Zope Enterprise Objects, the final chapter presents several techniques for improving your Plone site’s performance.

The Definitive Guide to Plone fills the gap between the inadequacy of online howtos and the need to read through someone’s example to find out how a particular thing is done. Users of all experience levels will benefit from the authoritative knowledge of the author. The writing style is clear, to the point and neutral. If you want to improve your productivity with Plone, look no further.

Don’t Feed Their Cash Cow!

Tuesday, November 23rd, 2004

“Price-slashing” by monopolistic proprietary software companies masks the high costs customers still unwittingly pay. And when this false economy is endorsed by governments and industry leaders, the digital divide can only widen.

The Microsoft XP Starter Edition is a drastically abridged version of the Windows productivity suite. This slimmed-down, local-language product, which is to be sold with new systems in India and other developing countries, is expected to cost less than half of today’s basic Microsoft Windows XP Home Edition.

A somewhat disingenuous spin has been offered by supporters claiming that this new packaging represents a paradigm shift of availability and affordability. At around US $36, it is being projected as a tool to narrow the ever widening digital divide. Sadly, top government ministers and important industrial leaders have lent their weight and prestige to help sell this concept to a population that has yet to achieve full literacy or to acquire the requisite technical skills to question the wisdom of this approach.

Quite frankly, the true cost of bargain-priced proprietary software is a persistent widening and deepening of the cyber canyon. The canyon exists at multiple levels.

At the ordinary user level, even at half price, crippled proprietary software constitutes over 10 per cent of the cost of the cheapest computing systems. That’s hardly a bargain. Plus the Starter Edition is anywhere from 18 to 36 times more expensive than the street-smart, full-glory edition. But the real cost lies in being locked into an information processing and storage model that you cannot escape. Proprietary data formats and secret processing capabilities produce a captive cash cow that can be milked by an enterprising vendor forever. The lock-in that creates a cash cow for the vendor forms a jail for users trapped on the other side of the digital divide.

Moreover, when payment for any legitimate software is shunned, the attraction of official but crippled software diminishes. Users inevitably demand the latest, fanciest versions. Unfortunately, this will tie them to an economic system whose side effects poison the common well by promoting a gray market industry where corruption breeds corruption, software customization is impossible, and the government is denied sales tax revenues. Instead of promoting a digital revolution, a lurching cyber zombie is created. The inertia and legacy of a poisoned system discourages the realization that open technologies can lead to greater freedom of choice and more robust solutions, with no adverse side effects.

The cyber canyon dramatically widens at the top. It’s here, at the national level, that inaccessible and limited-use software stunts the growth of an indigenous technology industry. It prevents the nurturing of regional and global partnerships whose egalitarian collaboration can inspire everything from fundamental R&D to world-class products and high-margin services.

Government ministers and industry leaders in developing economies delude themselves whenever they promote software that costs anything more than US $0. Paying for commercial packages, even those that are artificially crippled, is simply not cost-effective when discretionary wealth is lacking. Constrained by ground realities, the vast majority of users have not even begun simple transactions, let alone the sophisticated office or organizational automation required to fully exploit complex commercial packages. Ultimately, the promotion of unnecessary proprietary software by governments and industry leaders encourages piracy because of cost, misuse, and the passive adoption of other people’s tools for the application of technology. Such negative dynamics serve only to perpetuate the digital divide.

Only a nation-by-nation open source software policy can begin to close the digital divide from the top. When user-friendly software with adequate functionality and no strings attached costs nothing, and when technologies endorsed by positive feedback and open, collaboratively built knowledge empower local developers and entrepreneurs, why not kick-start the local automation revolution with open source software?

The rich framework of open source software and methods provides the foundation for integration into a universal digital landscape. Otherwise precious resources are wasted on being locked into someone else’s cash cow.

Review: Fedora Core 3

Monday, November 22nd, 2004

The Fedora Project has recently released Fedora Core 3 (FC3). Having used Fedora Core 2 for a while now, I was more than looking forward to this new release. FC3 brings together the 2.6.9 kernel, GNOME 2.8, KDE 3.3, X.org X11 windowing system 6.8, and SELinux (Security-Enhanced Linux) to provide a completely open source platform with stability and performance for desktop and server environments alike.

Installation

A full installation (via NFS Image) went smoothly and took approximately 35 minutes. The Python-based graphical installation environment, Anaconda, hasn’t undergone any major changes. However, there are some minor additions to a couple of configuration screens. Firewall configuration now lets you turn on/off four common service ports (e.g., ssh/http(s)/ftp/smtp). On the same screen, there is an option to set the warning level for SELinux to one of three presets (e.g., Disabled/Warn/Active). FC3’s additional language support now includes Indic languages (e.g., Hindi/Bengali/Tamil/Kannada).

GNOME Desktop Features

While the last release of GNOME (2.6) was mostly a bug-fix release, GNOME 2.8 includes a host of new features and improvements that make it more user friendly. A noticeable change to the default desktop is the new “Add to Panel” dialog. Now, the user is given a single dialog to add new applets and launchers to the panel, which is much friendlier than the maze of menus displayed in the last release.

Another nice addition to GNOME 2.8 is Vino, a remote desktop application (VNC client) which lets users remotely log into your GNOME desktop. Vino provides password protected remote desktop access and remote login confirmation. Note that, manually confirming each remote login may be safer than using a password, since VNC’s authentication scheme could be better (perhaps using PAM).

A new network tool (gnome-nettool) gives you a graphical interface for everything from network device statistics to running DNS lookups, port scans, traceroutes, pings, and more. This is especially useful when you run into those somewhat “invisible” network problems.

If email is one of your most important communications tools, you will appreciate the great features in Evolution 2.0, GNOME’s integrated email/groupware client. You can send signed or encrypted email messages using S/MIME (Secure Multipurpose Internet Mail Extension). Evolution Connector provides enhanced support for Microsoft Exchange servers. Finally, avoiding junk mail (spam) gets easier with integrated support for SpamAssassin and improved filtering.

Perhaps the most significant change in GNOME 2.8 is the new mime system. Instead of associating actions with MIME-types, they are associated with files, since most users think about files, not MIME-types. You can associate an application with a particular file by simply choosing the desired application from a list in the “Properties” dialog for that file. When I tried to register a new application (which was not listed in the “Open With” list), a simple file selector dialog listing all the files in /usr/bin was displayed. This can be quite confusing to new users, so hopefully it will get cleaned up before the next release.

Finally, one of the best new features of GNOME 2.8 is its tighter integration with hardware using D-BUS and the Hardware Abstraction Layer (HAL). Now, when you plug in a removable storage device (e.g., USB pen drives), an icon will appear automatically in the “Computer” window on your desktop.

Desktop Applications

Users will notice faster load times during startup and improved performance when opening or saving large files in the version of OpenOffice (1.1.2) shipped with FC3. Better integration with both GNOME and KDE provides a more consistent user experience across the entire suite.

The Firefox Web browser and Thunderbird email client have finally arrived in Fedora. Both packages offer excellent standards compliance and performance, not to mention great features. Note that Fedora shipped with Firefox 1.0 pre-release, but expect an updated 1.0 RPM soon.

Multimedia applications XMMS and RhythmBox don’t support MP3 files out-of-the-box due to licensing issues. So if you have an MP3 collection, you’ll most likely have to install a fully functional version available from freshrpms.net. Real Networks’ open source Helix Player is a great addition to this category, although I had trouble playing SMIL files from a news website. I was able to resolve this problem by just installing Real Player 10.

Fedora’s package management tool (system-config-packages) still lacks the ability for users to install new packages from online resources. Currently it simply lets users add/remove packages from the installation media. It would be great to see this tool as a front-end for command-line utilities like Yum. For now, you’ll want to use a package like Synaptic.

SELinux

When SELinux was first included in Fedora Core 2, the default “NSA strict” was just that, too strict. A single policy proved impractical across different user environments. SELinux in Fedora Core 3 takes a different approach. Instead of a one-size-fits-all policy, specific daemons (e.g., dhcpd, httpd, and others) considered to be most vulnerable to attacks are targeted. All other system processes run under standard Linux security, termed the “unconfined_t” policy. A configuration tool (system-config-securitylevel) is provided to enable or disable the targeted policy of each specific daemon. For more information about Fedora’s SELinux implementation, check out this FAQ.

Wrapping Up

Having used Fedora Core since its inception in 2003, I have been impressed with its ever improving stability and performance. I feel that significant enhancements across various subsystems (e.g., 2.6 kernel, ALSA, GNOME-VFS) in the latest release have contributed to a much better “it just works” experience for the user. And I hope that with every new release of Fedora, Linux achieves wider acceptance on the desktop.

Penguin-Powered Partners

Tuesday, November 16th, 2004

Three IT powerhouses — IBM India, C-DAC and IIT-Bombay — entered into an alliance this October to set up the Open Source Software Resource Center (OSSRC), the first of its kind in India. The three partners signed a fancy Rs 50 million (5 crores) agreement, which covers investments to be made over the next three years.

The objective of the OSSRC is to foster significant open source development in India by establishing a development portal and spearheading significant proof-of-concept projects. The center will undertake activities to increase the understanding of OSS models, and to develop high-quality training programs. It plans to offer OSS-based authoring tools and mark-up languages, teacher training and a content repository. The center will target the development of a national pool of students, faculty and professionals with OSS skills.

Once the present framework of the center gets established, other academic and research institutes in the country will be able to plug into the endeavor as well.

During the inauguration of the OSSRC on October 6, in Mumbai, organizations and individuals active in the OSS community in India bore witness to significant new commitments made by the Indian government in support of the open source movement.

K.K. Jaswal, secretary, Department of Information Technology (DIT), Ministry of Communications and Information Technology, Government of India, said, “We are convinced that a free operating system (OS) provides the perfect strategy for constructing digital bridges between the multi-dimensional disparities that exist in our country today. The government follows a pragmatic approach by opting for cost-effective solutions. Now that open source software is blossoming in India, as it is around the world, we need to develop significant OSS capabilities and institute the resources that support and enhance its growth.”

Jaswal added, “Open source software has altered the computing landscape. This center will help in expanding the open source segment of the Indian software industry and create a new skill set. Through this resource center, we can unleash the potential of India’s software developers. Opting for open source software is not just a cost consideration, but to provide young talent entrepreneurial encouragement.”

S. Ramakrishnan, director general, C-DAC, said, “The acceptance of the open source software-based solutions and standards provides an ideal opportunity for countries to develop new players and products, with minimal investments. Our vision is to establish the OSSRC as an institution of excellence, with an aim to leverage private sector resources through a public-private-partnership model in India.”

IBM explained that it is investing two-thirds of the cost of the center to “bring the benefits of information technology to different sections of the community.” The managing director of IBM India, S. Annaswamy, added, “This investment results in the growth of open source software, which will help in expanding the open source segment in the Indian software industry.” IBM will provide the hardware, software and management support, as well as participate in the setting up of the OSSRC.

There were some concerns about the participation of other groups in the planning and implementation of this center. But IBM assured participants that the center would be a true community resource, whose benefits would reach everyone active in the development and advocacy of free and open source software in India.

Interview: Are You Ready to Rock with Michael Tiemann

Sunday, November 14th, 2004

An Interview with Michael Tiemann on his first ever trip to India.

Linux For You’s editor, together with technologists Robert Adkins and Alolita Sharma, met Michael Tiemann, vice president, open source affairs, Red Hat, on his first visit to India in October 2004. Tiemann, with a long string of successes — from being the 23 year old developer of the GNU C++ compiler, to co-founder of a very successful software company Cygnus Solutions, is today part of Red Hat’s founding team and eager to push the benefits of open source to the global frontier. In this wide-ranging interview, Tiemann shares his vision, enthusiasm and entrepreneurial spirit.

Q: What brings you to India?

MT: Well, this is my first trip to India and India is well known as an emerging player in the IT market. I have always been fascinated by major trends. And so that might explain why, even though free software was just in its infancy when I started learning about it and writing code in 1987, I saw the dynamics of the free software model being incredibly powerful. It reminded me of that famous quote from Archimedes — “give me a long enough lever and a proper fulcrum and I can move the world.” I saw that kind of dynamics with free software. When I contemplate the resources available in India and the kinds of problems that can be solved, it is a second-to-none opportunity for change.

I see India as a country, as a population, as a group of people struggling with other groups of people to all make life better for everyone. Our CEO, Matthew Szulik, met President Abdul Kalam during his visit to India in January 2004. Szulik came back and he gave a speech at Red Hat about that meeting and the Indian president’s passion to improve hundreds of millions of lives. Whatever good intentions other presidents may have, no [other] president has that opportunity. It was inspirational to me and I think, to Red Hat that we are working with commercial and public sector leaders who have that kind of vision in India.

Michael Tiemann

Michael Tiemann

Q: What is your mission at Red Hat?

MT: My title is Vice President, Open Source Affairs. Not many people know what a Vice President, Open Source Affairs means or does. But what I do is discuss technology policy and strategy with the public and private sector. There are two other people that have the term “affairs” in their titles in the US. Venkatesh Hariharan has that title here in Red Hat India. Tom Rabon is Vice President, Corporate Affairs and Mark Webbink is Deputy General Counsel focusing on legal affairs for open source. Rabon does public policy and strategy, Webbink does legal policy and strategy and I do technology policy and strategy. So those three form a miniature cabinet for how we understand and how we advocate and how we move forward as the world changes and we help change it.

Q: You really do have a global world view then.

MT: Absolutely.

…what I see is if you look at the population of available resources in India, despite any constraints, there will be somebody who basically says, ‘why can’t I change the world?’ Out of India’s population of 10 million people, is there not one Linus Torvalds?

Q: How do you see the official Indian approach to open source which claims to be neutral?

MT: I am still learning. This is my first visit, however, when people tell me that their policy is to be neutral, I take what I think is a responsibly skeptical approach. You know “What do you mean by neutral? What is the real benefit you are looking for?” Some people claim to be technology or policy neutral and it’s not really true. But at the same time, I don’t think that the Indian government owes us anything. I think it is our responsibility to understand what the challenges are, to understand the opportunities and then to successfully advocate for that. If the government is willing to listen and we have something to say I am sure that something will happen.

Red Hat’s responsibility as a business is to be able to transform all the successes that the entire market has into our own success in terms of profitability, and in terms of sustainability. I’m very proud of what we’ve been able to do.

Q: What is your advice to IT firms and CEOs in India who are sitting on the fence? They know there is a lot happening on the open source front but don’t know whether its time to jump in or to just wait and watch for now.

MT: The first thing is that it is important to make an informed decision. There is an incredible amount of FUD (Fear, Uncertainity and Doubt) out there and people who are telling the story badly, or telling the story wrongly. Some of these are well intentioned people and some of them do not have good intentions. Let me give you an example of how the story should be told.

A couple of weeks ago, I visited an IT services company in the US. A billion dollars a year in revenue, and US$ 50 million a year in profits. Nothing has changed for four years, they’ve been flat. They held an internal conference for all their IT people. 500 people from around the world showed up from Japan, India, Canada, US, etc. [They] came to one location and the CEO kicked off the meeting and said, “The time has come that we have to re-engineer the company and we’re going to do it with open source.” A lot of things are going to break. It’s going to be painful and things are going to change. But this company has been around for many years and every 10-12 years we go through this and when we finish it, we are stronger, we are in better positions, we’re more competitive, and we’re more profitable. They specifically identified a strategy based on lowering operating costs, because they are an IT services company. That’s one dimension.

A second dimension is improving developer efficiency. And what they have discovered and what many IT organizations would admit if they were just a little bit truthful, is that they internally have all these stovepipes where an application takes on a life of its own and before you know it they have 50 ways of doing the same thing. This is very inefficient and it also leads to inflexibility. When they want to offer customers new solutions, they can’t because half of the solutions are in one stovepipe, and the other half are in another. They can’t combine.

And this CEO believes, and I agree, that the open source development model, when properly practiced, leads to the kind of modularity, the kind of code reuse and sharing, the kind of interoperability that will dramatically improve their internal operational efficiency. Now there is a third piece which the CEO did not even know about, which I believe is also possible and which I will be promoting not only to him but to everybody. That is the work that Eric von Hippel, professor, Massachusetts Institute of Technology’s Sloan School of Management, pioneered with “user-driven innovation”. I believe that open source provides a superior way to change the customer relationship from “vendor-customer” into “collaborators” so that innovation happens where innovation happens best — not limited to “if it doesn’t come from the vendor you can’t do it”.

It’s my belief that solving the TCO problem, solving the developer efficiency problem, and making progress in user-driven innovation is the hat trick which will define IT competitiveness for the next 10 years. Then something else will happen.

Q: In the example you cited, the CEO was of a services firm. What if the CEO is of a product firm like Adobe?

MT: Adobe is a very interesting story. Adobe came up with Postscript. They filed to become public and they said in their prospectus “we’re going to make Postscipt standard open and publish it”. They went public and then they started changing their mind. One of my co-founders of Cygnus went to the CEO of Adobe, and reminded him, “You know, you said in your prospectus that you would do this as an open standard.” John Warnock, Warnock admitted, “I guess we did”. If you Google this story you will find that Warnock has turned it into a success story about how, if Adobe had not published Postscript, other people would have challenged and destroyed the standard, etc.

If you look at that story it is the counter-proof of Sun’s Java story. So whether by design, by accident or by some combination of the two, Adobe created and sustained its market through openness even as a product company.

The design of the Postscript language permitted arbitrary participation and arbitrary collaboration. I think there is an increasing trend. I would suspect that across all the projects on SourceForge, if you look at which ones began as open source and which ones began as proprietary and then opened up for whatever reason, that a growing percentage [shows] that people are deciding that open source is a suitable transformation strategy for a product. You might say, well gosh, these companies are dumping their orphans to the care of the world. But let us not forget the great contribution that some orphans have made to the care of the world. I think that it proves that ultimately open source is a more sustainable model because the reverse case, people starting with open source and then taking it proprietary, like VA Linux…

Q: or Sistina?

MT: Yes, but we fixed that problem :) But in the case of VA Linux, I would say, they went from a company with the potential to change the world, to yet another product company.

…the Indian president’s passion to improve hundreds of millions of lives, a billion lives. Whatever good intentions other presidents may have, no [other] president has that opportunity. It was inspirational to me and to Red Hat that we are working with commercial and public sector leaders who have that kind of vision in India.

Q: But you will have a very hard time convincing any Indian product company of that story.

MT: Rewind 10 years, go to America, same story. I have not changed my position in 17 years on open source and free software. I used to play ultimate frisbee, a very fun and very fluid game. My position was called “deep” which meant it, my job was to go and catch the long pass. There was one crucial time where I just did not stretch quite far enough. My teammate said to me, “Michael, if you want to get in the air you have to let go of the ground”. Ever since I’ve been able to stretch a little bit farther. But here’s the good news. The good news is that everyday, life is telling them “if you want to get into the air, you have to let go of the ground.” It just requires that one time that they hear it.

Q: But even Red Hat might not remain in business very long if it was only an open source product company, it would not scale.

MT: I agree with you and let me say that same thing in a different way. The world does not owe Red Hat a living. We are in business because we identify and deliver value to customers. God did not say, “if you build a product, you will be successful.” And God did not say, “if you do open source this way you will forever be a growing company.” What happens is the market says, here’s how far we can go, and here’s how far we’d like to go, and if you have any intelligent ideas about how we can get from here to there, tell me in 15 minutes. The market drives it. And Red Hat has changed a lot. When Red Hat went public our gross margins were 48 per cent as an open source “product company”.

In our most recent public earnings call, our blended margins were 80 per cent, and our enterprise subscription gross margins were over 90 per cent. Would you rather be 48 per cent gross margin or would you rather be say 80 or 90 per cent? The reason we improved is not because we raised prices. The reason we improved is because we found a better way to deliver more value to customers. It turned out, in our case, that there were many more customers who received much more value having a long-term, defined, supportable enterprise product than those who wanted to buy a short shelf-life retail offer. Go figure.

Q: Some people contend that Red Hat is going to be the next Microsoft. What is your reaction?

MT: The first thing that I would say is that Red Hat represents choice. And we represent choice in a number of different ways. But it’s all tied to that central notion of open source and our belief that “choice equals freedom equals power”.

So what we build are solutions that give customers choice. If they choose to download and choose to support themselves, that’s a choice. We do not run around and sue people who are supporting themselves. We do of course protect our trademarks but, as far as what kind of relationship they want with their hardware vendor and whether they want to have a direct relationship with our company, it’s their choice.

We are beginning a lot of discussions with systems integrators and with value added resellers. I’m sure those relationships will expand so that even more choice exists. But fundamentally, we believe that choice has value. In fact, at a Harvard conference, I ran up to an economist and started talking about the value of option values. And she said, “Absolutely right, take my class.” Everybody’s selling! In the case of Microsoft, what they are offering is a choice of one. You look at the cost of exit. It’s clearly, with them, a one choice world.

So if we are able to achieve great margins while offering choice and freedom, I think that’s the new generation of technology company. And just in time. Look at the technology challenges that India is facing. Look at the technology challenges that the whole world is facing in terms of access and in terms of information. This revolution can’t come too soon.

…Some people [in government] claim to be technology or policy neutral and it’s not really true. [While] I don’t think that the Indian government owes us anything, if they are willing to listen and we have something to say I am sure that something will happen.

Q: Often companies like Red Hat and other MNCs come into India and pitch the wrong products and services because they do not realize the level of infrastructure in developing economies drives the market toward the desktop instead of advanced server solutions. How does Red Hat adjust to the ground realities of countries like India?

MT: So here is my “Law of the Hacker”, which is that “with a big enough crowd there is at least one”. And crowds get pretty big in India. When I talk strategy with people, sometimes I talk with CIOs of the most conservative companies. Many of these companies are intellectual deserts: conformity, bureaucracy, process, and all the rest of that stuff. The CIO sits and says, “Michael, I would love to solve this problem, these viruses are killing us. I’ve got row after row of infrastructure that I just can’t do anything with. What should I do?” And I basically would say, “There are two things you can do. The most positive thing you can do is to let people know that they won’t get into trouble for being successful. And the second thing you can do is just don’t fire the guy when you find out he has been successful with Linux.”

When we went to Wall Street, we had a series of four meetings with one of the largest investment banks on Wall Street. At the first meeting we sat down and talked about our Linux strategy. And they said well, it all sounds well and good, but it will never work in this firm. The Law of the Hacker: One of the guys in the back started sort of smiling and said, “We already have it runni
ng on 75 servers.” And the manager said, “What?”. “You know all those file and print servers in building X, they’re all running Linux.” And he was a bit surprised.

Then we had a second meeting which included some of the same players plus a higher level manager. The previous manager introduced us and said, “Well, I guess we do run about 75 of their servers, but nothing really in the enterprise.” Again somebody in the back of the room was smiling and said, “Actually it’s more like 150. And now we’re also doing ‘blah, blah, blah’”.

We had a third meeting with subsequently higher level managers. The conversation went, “Aside from the 150 servers it’s really not in the firm. Er, That number is now 250.” At the fourth meeting it was 475, at which point they just said your next meeting will be with the CIO and CTO and we’ll get this thing done. If they had fired the person who had done the 75, maybe there would still be 150, but they wouldn’t talk about it.

This is the “trickle up” theory. Look at my own story. Nobody told me to do the GNU C++ compiler. Nobody told that me I could, but nobody told me I couldn’t. Well, theoretically, the GPL said I could. The GPL said welcome, if you want to hack it, may the source be with you. It was an absolutely fantastic experience. I single handedly brought to life that compiler. When I gave a talk at ATT Bell Labs, which is where C++ came from, there were 35 people in the audience who were directly working on ATT’s native code compiler. They had been working on it for a period of 5 years and had never released it. And here comes this 23 year old, who put his first release out single-handedly in 6 months. Now, of course, Richard M Stallman did a lot of work, but imagine what it felt like to me as an individual that with a little bit of hard work, 18 hours a day, 7 days a week for 6 months I could send an announcement to a public mailing list, and say “please download this and send me bugs.” I got a bug back almost instantly. That’s what kept me going. So what I see is if you look at the population of available resources in India, despite any constraints, there will be somebody who basically says, “why can’t I change the world?”

With the availability of Fedora for example and certainly with your magazine generously publishing the occasional Fedora CD, we’re providing close to 4 CDs of source code ready to change the world. Out of India’s population of 10 million people, is there not one Linus Torvalds?

Q: Any message for the developer community? What’s going through my mind is like a guitar player standing on stage asking, “Are you ready to ROCK?”. And waiting for the developers to yell back. If all I can hear is a cricket, then that means I’m in the wrong auditorium. I know the developers are there somewhere.

MT: We will know that the developer community has really come of age when not only have we identified the great developer that everybody respects. But we also have the egotistical one, and we have the one that is mostly wrong, and we have the one who is shilling for somebody else. You know, the whole mix. That is just the way the world is. I’m willing to suffer many fools to be able to talk to one wise person.

Q: What is your message to Sun? Sun’s current rhetoric seems very divisive of the open source community.

MT: To say the same thing in a different way. Sun is externalising their own schizophrenia to the open source community. That kind of contagiousness is not necessarily good. I would say two things to Sun. The first thing I would say is — IBM, HP, Dell are all proving that you can sell billions of dollars of hardware with a good open source partner and a good open source strategy. I know there are customers that would be happy to buy Sun if they had a better story with respect to their own Linux strategy. The second thing I would say is — if they want to fly they need to let go of the ground.

Q: In the Indian scenario, where resources are limited and an engineer might be the only bread earner of the family, letting go of the ground could be scary.

MT: You are making an argument of averages without looking at the true population. At an average level, you are absolutely right. The average engineer cannot afford to make that leap. But when you look at the standard deviation across the whole population, I guarantee that there is an engineer who could walk home that night and say let’s do it, let’s rock! And their family would support them.

…if we [Red Hat] are able to achieve great margins while offering choice and freedom, I think that’s the new generation of technology company. And just in time. Look at the technology challenges that India is facing. This revolution can’t come too soon.

Q: And that’s the engineer who will become the next Linus Torvalds from India.

MT: That’s right.

Q: Red Hat is sometimes perceived, rightly or wrongly, especially after its withdrawal from the desktop retail market when it introduced Fedora, as being more interested in corporate success than in community well-being. Can you address that concern?

MT: If we gave a wrong impression last year when we launched Fedora, shame on us. We have been doing everything that we can, to better represent what we are trying to do. For example, look at Stateless Linux which we announced about 3 weeks ago as a way of providing secure managed desktops, through re-architecting everything from the Linux install process to application resources, etc. That received very positive responses from the community. We got about a dozen people from the community saying “I’ve been trying to solve this problem too, here’s how I’ve been doing it, what can you reuse?” So we are thrilled. I think the way we improved the perception of Red Hat was – we stuck to our goals and we decided that it was going to be our patience and dedication that would achieve the results, not marketing spin. Denials in the press don’t really help. It’s taken about a year to transform that community skepticism into trust, but we are very committed and I think that every day more developers are willing to acknowledge that whatever motives they ascribe to Red Hat, the commitment and the outcomes are consistent with their values and therefore, in their eyes, Red Hat is being a good community member. And if we are making a profit and we are growing, good for us.

Sun’s Red Hatting Game

Monday, November 8th, 2004

Boxed in by falling market share, Sun needs to learn to fly with all players in the open source community.

Sun’s President Jonathan Schwartz seems to have learned the fine art of posturing from the master. In a campaign worthy of Sun co-founder Scott McNealy’s earlier Microsoft bashing, Sun has now targeted Red Hat with venom and vitriol. Since Sun’s settlement prevents it from throwing punches at Microsoft, is Red Hat just a convenient punching bag? But one has to question Sun’s wisdom of picking on a dramatically smaller company. Why not go after IBM, the 800-pound gorilla? At the same time that Sun is proud to contribute to the open source community, it is equally proud of its proprietary products. Ditto IBM. Schwartz should understand that titans with similar portfolios are much better crowd-pleasers in the boxing ring.

Me Too!

To pump up Sun’s anti-Red Hat campaign, Schwartz is using all available channels - from his personal blog, to the press. His message is simple - don’t forget Sun. Sun is an original stakeholder in the open source game. Its contributions include NFS, OpenOffice and many other technologies. However, instead of working collaboratively to grow the nascent market for everyone, this divisive campaign splinters and seeks to control the OSS community. Replacing solutions of the OSS community that’s forgotten its many debts to Sun Microsystems with Sun-controlled solutions is, after all, what the OSS pioneers have always wanted, right? Hello, Jonathan, are you still with me?

The Real Trouble with Sun

No upstream development model - One of the key differences between Sun’s software engineering model and Red Hat’s is in their mode of development. Sun’s controlled and private development model contrasts with Red Hat’s upstream development model. In the upstream approach, various contributors who are part of the open source community work on the features and functionality of Linux, Apache or Webmin, in both large and small projects. Red Hat is just one player in this broad and deep stream of talent. It then captures, enhances and packages value from the many willing, upstream contributors. Sun’s model, on the other hand, is handicapped by the relatively shallow pond of in-house innovation applied to a few prioritized features in Solaris and other products. This slows its ability to compete in the constantly evolving and fast-growing technology market.

Desperate tiger - Despite forays into software as well as services, Sun is still a hardware company. Unfortunately, expensive proprietary products can no longer compete with cheap commodity hardware. Sun’s strategy has been to cut hardware prices to regain market share, and at the same time try to devalue the growing attraction of commodity Intel hardware bundled with OSS. Armed with a pride of proprietary technologies and a robust patent portfolio, a cornered tiger may display claws and fangs much longer than SCO’s, another similarly cornered tiger from the old Unix jungles.

The Challenger

To be a better citizen in the open source community, what does Sun need to do? It faces the same challenge that afflicts other large proprietary vendors including Microsoft.

Sun needs to learn this “upstream thing”. That is, how to share in a product-and-services mix that incorporates the contributions of others, at the same time giving back to the community to enhance its value for everyone. Sun has been very good at sending contributions “downstream” but has never been able to learn the trick of full reciprocity. Sun just has to observe, among others, Red Hat. Sun will quickly see that to work collaboratively and to enhance, package and then return a better product to the community, produces a spiral of innovation and value. This upward spiral benefits everyone, including Sun! It is the pride of ownership that blinds people like Jonathan Schwartz and Scott McNealy. They may be innovators, and even great contributors, but they are incapable of being collaborators. Real collaboration requires the full sharing and acceptance of other players’ abilities and contributions, as much as one’s own.

© 2000-2009 Technetra. All rights reserved. Contact | Terms of Use

WordPress