I've been in the high tech industry for over 20 years now and have read about Open Source projects for almost as long. Although the core practices behind open source have their origins in academia and have been used for decades, the term itself didn't become widely used and referenced until the 90's. Almost a decade ago, I was lucky enough to sit in a room full of hacker professionals into the wee hours of the morning listening to John Warnock (founder of Adobe) and Eric Raymond (a strong open source advocate) in a friendly debate on the pros and cons of open source. I don't remember the exact words of the debate but I remember it all began when Eric suggested to John that Adobe should open source Photoshop. John's reply was, to paraphrase; "Now why in the world would we do that?" And thus began the debate.
It's been almost a decade since that night and this past week I was again lucky enough to be exposed to a sequence of events surrounding open source. On Feb 27, 2007, the Mozilla organization released a new version of FireFox to the world. A security update for two versions of the browser, 1.5.0.10 and 2.0.0.2. Within a few hours of the installing the update, other developers and I began running into problems running web sites we were developing or maintained. After some regression testing with different versions of Firefox to positively identify the 2.0.0.2/1.5.0.10 update broke web sites, I opened a bug on Mozilla.org for the problem. What happened after that has left me pleasantly amazed.
At 19:12PST on 2007-02-24, I opened the following bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=371576Within the first 30 minutes after opening the bug, the bug began getting properly categorized, flagged, was assigned to a developer, and 4 people attached themselves to the bug. Within a few hours a test case had been added to the bug, and the cause of the problem was tracked down to the lines of code in the source. By the next day the magnitude of the problem and its affects on web sites worldwide was identified. Within a couple days further isolation and regression testing identified the proper fix, and 5 days after the bug was opened the issue was resolved.
We had been experiencing the problem in sites using a specific
AJAX environment, but within the first two days the Firefox developers quickly isolated the code level cause of the problem and reported that it would render a lot of web sites worldwide un-usable. (If you're really interested in the technical details behind the problem, read through the details and history in the bug link above.)
Like I mentioned before, I'm amazed! Amazed at the speed and thoroughness the Firefox team works. Within a week they verified the bug, created a test case, identified the offending code, created a fix regressed against other issues, and resolved the problem. Within a week! To put this in perspective, in the corporate world if an end-user customer like myself submitted a bug against a piece of commercially available software, I would be lucky to get a real-person acknowledgment of the problem within a week. A fix within a week would never happen. Try reporting and getting a fix that fast for Microsoft's Internet Explorer. Or even Apple's Safari, and boy am I am Apple fanatic.
So why can't we expect that kind of response in the corporate world? Because in the corporate world the issue would have to get reported through proper channels, put into queues with hundreds and thousands of other bugs, discussed at bug review meetings, prioritized against marketing schedules for updates and new revisions, assigned to development, testing, and release teams beginning the path through all the processes all those respective departments follow. All that process takes time. Even at some of the most responsive software companies today, it still doesn't happen anywhere as fast as it does in the open source world.
Now, I should mention about this time that the actual deployment of an update to Firefox to resolve the problem is still in-progress. By "deployment" I mean the release of a publicly available update to Firefox for the world to begin installing. But one of these days real soon, Firefox users around the world will see their browser ask for their permission to update to a version like 2.0.0.3 (or 1.5.0.11 depending on what version they are running). Right now there are FireFox developers and courageous testers running patched versions with the fix to verify the problem is in fact gone and no new problems have arisen. Even if that thorough testing process takes another couple weeks, which I hope it does, the response time fixing this problem will still be amazing.
For all my non-technical computer friends out there, I won't begin discussing the pros and cons of open source projects. Cyberspace is full of hundreds and maybe thousands of articles, debates, postings, blogs, etc. about the ups and downs of open source. If you're really adventurous, Google "open source debates" or search for "
open source" on Wikipedia and pull up a comfortable chair and begin surfing. When people ask me about my opinions on open source projects, I answer with the same initial sentence.
"Open source is not for every product."
Now I should follow that with an additional sentence. "But it does work and Firefox is the perfect example of a successful open source project." There's a good reason why Firefox has been successful around the world and enjoying a growing number of users every day. Firefox is worked on by a dedicated team of talented individuals who listen to their customers and respond accordingly. They are not tied to desks in the corporate world and they are empowered to make things happen. And they do that every day.
Kudos to the Mozilla Firefox development team!
(p.s. If you don't use Firefox, you should give it a try. Find it here)