Mozilla 1.0 Development Process
Friday March 1st, 2002
mozilla.org drivers have posted the plan for the road to 1.0, and how the tree will be managed. Basically, the tree will be under driver control for the entire time following the 0.9.9 branching, which is occurring right now. Large landings will have to be placed on the Patch Landing Tool so that email@example.com can know what will be going into the tree, and when. Click the Full Article link to get the whole scoop.
#24 Fair enough
by choess <firstname.lastname@example.org>
Friday March 8th, 2002 12:49 AM
You are replying to this message
I'm not really prepared to speak on the overall state of the culture at Netscape, as I don't feel familiar enough with what its employees are doing. I will say that I'm generally uncomfortable with the fact that one company is bearing most of the burden for developing the project, and I'm trying to push for increased commenting and documentation to attract more corporate contributors. Having a more distributed developer base would insulate us better from the vagaries of any one company's attitude. I think we're already starting to attract such contributors (such as Worldgate, which is currently giving us Randall Jesup, Master of Perf, and timeless), but more contributors need to be "growing" into peers, potential module owners, super-reviewers, etc., since the burden of these tasks tends to fall on people who are also expected to contribute large quantities of good code.
One of the major issues discussed at the recent Moz East Coast dev meeting was that post-1.0, people seem to like the idea of moving away from Mozilla as an application suite (i.e., "just like Netscape, but without the branding!") to a more modular style: Mozilla as platform (XPCOM, XPConnect, XUL, etc.) with the browser alone at the core and other apps attached as the user pleases. There are still both technical and social hurdles to be dealt with (slashing dependencies, deciding what does go in the tree/builds and gains the benefits of distribution, testing, and enforced non-breakage), but I think this is ultimately the way to go in broadening our developer base and escaping the "Netscape-with-the-serial-numbers-filed-off" mindset.