Evaluating Commercial Open Source Projects
Thursday April 22nd, 1999
A recent Forbes article characterized Mozilla as a "flop". The article had so many inaccuracies that I felt a rebuttal was required. At the same time, I felt that some light needed to be shed on the differences between commercial Open Source projects and "all volunteer" Open Source projects. What follows (click "Full Article" below) is a rebuttal to the assertions in the Forbes article and my opinion on what can reasonably be expected from a commercial Open Source project.
As always, the opinions are my own, and do not reflect the opinions of mozilla.org (which MozillaZine is not affiliated with).
#36 Re:Evaluating Commercial Open Source Projects
by Ganesh C. Prasad <firstname.lastname@example.org>
Saturday April 24th, 1999 2:48 AM
You are replying to this message
Mozilla may take another 4 months to appear, or 6, or 12.
But when it does, it'll be the browser to beat all browsers. There's absolutely no doubt about that.
The important thing is not to get the developers into a deadline mentality. No software project does well when they're coding to deadlines, whether it's Open Source or Closed Source.
Gnome found out the hard way with their "1.0" release which was more a "0.9". They shouldn't have targetted the LinuxWorld Expo for their release. They should have released it when it was ready.
Dear Mozilla developers, don't bother what the world says. Keep on quietly coding. When the product is ready, we'll all know. Best regards, and more power to you,
Ganesh C. Prasad