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, firstname.lastname@example.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.
#72 Re: Re: Newsforge - Learning from Mozilla
Friday October 26th, 2001 2:56 AM
You are replying to this message
>> a more schedule-driven approach <<
> You don't think "We want 0.9.10 to be Mozilla 1.0; if we have to slip one milestone, so be it, but not more than one" isn't schedule-driven? <
It's a big improvement over the "we don't have a schedule -- we're open source -- we'll ship whenever we feel like it" party line that was de rigeur up until Brendan Eich's recent message. That was a big step forward. Now let's see you show that you're taking it seriously.
>> a heightened level of professional accountability <<
> What exactly is that? It's an empty snipe. <
I'm sorry to hear that you feel that way. Pervasive immaturity is your leadership's biggest problem; it's at the root of most of your other problems. It's reflected in things like evasiveness, hand-waving, defensiveness, cliquishness to the point of cultishness, suddenly changing answers without acknowledging that you've changed them, playing fast and loose with facts and numbers, saying you'll keep your chief after she was fired (precisely for her lack of accountability), and similar childish antics. I am sure that your senior management at Netscape has gotten quite as sick of this run-around as I have, and that this _emotional_ reaction to your rascally, irrepresible slipperiness has a lot to do with the fact that you are now being threatened with dissolution. You would do well to take a good hard look at this issue of attitude. It's critical to the survival of your project in its current form..
(Yeah, I know, saying that to guys in their twenties is pointless. Oh well.)
>> reduction of the open bug count <<
> How exactly do you suggest we speed up this process? Engineers are working as hard as they can. Suggestions as to how to prevent 50% of the new bugs filed per day ending up as dupes within a week would be particularly welcome. <
You need resources. You will have to pay them. The volunteer model does not offer adequate reward for serious QA and support work.
I'm not saying anything here that I haven't said before. I am, however, pointing out that if you tie a request for resources to something your management (or sponsorship, if you insist on denying the reality of Netscape's role) cares about, they might just be willing to listen. For instance, "we need a half-dozen support staff to screen the incoming bugs before they go into the QA database, and the same number of fresh QA people to sift through the existing bug queue, to make a January deliverable," that's the sort of thing technical managers give serious consideration to, if you can back up the numbers.
>> and a renewed focus on aesthetics at the level current consumers expect <<
> I haven't seen you breaking out Patch Maker and submitting UI patches. :-) <
Not my job, dude. I have a job. I'm nearing the end of a sixty-hour week and writing to you during compiles. Why should I work for you for no money? The lion's share of work on your project is compensated, and as far as I'm concerned, the unpaid contributors are suckers. I wonder how they'll feel when and if Netscape gives up on open source and takes the only realistic Mozilla branch back inside the firewall. See the recent /. thread on Lutris Enhydra by any chance? No open source project has every gotten to anything like a professional stage of development without large amounts of professional compensation expended for the commercial benefit of a particular company.