MozillaZine

Full Article Attached Mozilla Bug Week

Monday October 22nd, 2001

Many of you are familiar with the Bug Day's that we started a few years ago. Well, with the number of people wanting to help out skyrocketing these last few months, gerv@mozilla.org and others have decided that a bug week was in order. They'll be running it from Saturday October 27th to Sunday November 4th, and they'll have plenty of smart people on hand to help folks learn the bug system, learn how to use the various other web tools, and of course, learn some tips on how to contribute code to the Mozilla effort. Click the Full Article link to get all the details.


#37 Re: It's the autonomy, stupid!

by kiko <kiko@async.com.br>

Wednesday October 24th, 2001 3:32 PM

You are replying to this message

Eeeek. mpt, maybe I didn't understand your point so well, because I don't agree at all. Mozilla.org is a very special place to many people outside netscape, and calling it "a way not to run an OSS project" is just oversimplifying.

Mozilla is a very large project, and one of the few OSS projects where there is a very large and opinionated community involved. This has a lot of impact on the way development happens, and it also influences our beloved UI. To say it's a failure is simply ignoring these problems and saying "a proper OSS project wouldn't do these things so badly".

The fact is that most OSS projects fare evil when there is a large codebase involved. Some people might scream Linux, and I say "look into the Linux development process and judge for yourself". Some people might scream Debian (and I'll agree it's an example of a project with a lot of success) and still I'll point out the major differences in the kind of software produced (and the modularity acheivable). People love a browser too much.

An OSS project has to acheive a balance between developer motivation, proper modularity and quality. Larger projects suffer more; that's just the way it is. In a closed source environment, because nobody's watching, it's easier to brush stuff under the carpet and call them post-1.0 features. The lack of somebody with a stern call for 1.0 does mean we sit around waiting for it to happen longer; it doesn't mean we're doing a bad job developing the browser, however.

I don't ever like to be negative when analyzing mozilla.org's actions because I know we're in a tight spot and nudging forward has produced better results than pointing out problems. So I cheer us on, <*@netscape.com> included (perhaps foremost), before digging back into the code.