MozillaZine

Forums Down

Friday December 14th, 2001

As you may have noticed, we've taken the forums down, as we are hitting our bandwidth limit with them. We're working on getting them up and running again as soon as possible.

In related news, we've added a link to our Cafe Press store where you can get cool MozillaZine appearal, which will help us keep ads off the site for good. Thanks for all your support.

UPDATE: Many people have requested some way of donating money to help us out, so we have setup a paypal account for you to do so. Simply go to paypal.com and use the email address jason@mozillazine.org to contribute. We thank you greatly for all the help, and thank the people who bought stuff at CafePress for the support as well.

Jason.


#42 Experience

by SubtleRebel <mark@ky.net>

Tuesday December 18th, 2001 9:20 AM

You are replying to this message

>As for you, I'm getting more and more sure that the loudest advocates of the Mozilla open source process have never before been involved with shipping a large software project, and do not have the background or training to understand what they are seeing.

I have plenty of experience with large software projects. My background and training also enable me to understand that a large scale closed source projects are very different from a large scale open source project like Mozilla.

In most closed source projects, a set team of programmers is assigned to each component. They may build and test their components on a daily basis, but builds of the whole project are not typically done that often. When large projects builds are done, it is not unusual for whole components to be left out because those components are unstable or even completely non-functional due to recent code checkins. I have seen these incomplete builds only a few days before final canidate builds. Crashes and regressions caused by checking in new code happen with all large scale projects -- it is just more obvious with Mozilla because we have access to full builds after every code checkin.