MozillaZine

Full Article Attached Mail/News Performance Effort Underway

Friday November 2nd, 2001

Seth Spitzer today sent an update out about what the Mail/News team is doing to meet their goals for Mozilla 1.0. They'll be focusing almost 100% of their effort for at least the next two milestones (0.9.7, 0.9.8) on Footprint and Performance of the various parts of Mail, News, and Addressbook. Not only will they be focusing on it, they'll also be locking down their part of the tree and only accepting performance or footprint fixes. Very few exceptions will be made. Click the Full Article link to see Seth's full post.


#185 Re: Re: Interesting arguments

by choess <choess@stwing.upenn.edu>

Friday November 9th, 2001 12:24 AM

You are replying to this message

I don\'t think this is an either-or question. Given the amount of work NS employees do on major modules, it\'s clear that the project would pretty much go dead in the water without their involvement. OTOH, if Netscape were suddenly to face the responsibility of doing all their own QA + bug triage + maintaining small-but-useful-non-core-feature foo, bar, and baz, it would also throw a serious cog in the pace of development.

I think of the organization of individuals in the developer community as being a loose hierarchy: you have your uber-coders, most of whom are employed by Netscape, your demi-uber-coders (both volunteers and NS intern-type-people), and Teeming Millions like me of volunteer QA\'ers. The top of the hierarchy are the people who are fixing involved, nasty bugs and keeping the core functioning. The next level down does some of that, but they also engage in things like large-scale non-programming projects (helping keep Bugzilla running, etc.), or will often tend their own enclave somewhere in a module (i.e., bz is responsible for getComputedStyle(), bbaetz has ftp viewer and gopher, rbs is coordinating MathML). The Teeming Millions triage bugs, make testcases, resolve the 30% or so (guesstimate) of bugs filed daily that become duplicate/invalid/wontfix, write small patches, and so on. Obviously, the uber-coders are key to keeping the project running, but they need the rest of the hierarchy to run interference for them, complete features that might otherwise be pushed off indefinitely (see getComputedStyle(), above), and generally take care of bugs that it would be a waste of their paid time to have to go through.

In short, I\'d find it hard to call volunteers \"much less relevant\"; losing volunteers would result in a tremendous price in terms of the completeness and polish of the application.