The Future: The Mozilla Foundation and the End of Netscape
Thursday July 17th, 2003
There's a lot of confusion surrounding Tuesday's creation of the Mozilla Foundation and the disbanding of the Netscape browser development team.
While a major loss, the end of Netscape does not mean the end of Mozilla. There is no way that AOL can revoke the Netscape and Mozilla Public Licenses and make the code proprietary. The Mozilla code will continue to be available to all. AOL has also agreed to transfer the Mozilla trademark and other intellectual property (much of it dating back to when Mozilla was Netscape's mascot) to the new Mozilla Foundation. Netscape-owned hardware (such as the mozilla.org servers) will also be transferred to the new organisation. AOL will continue to employ some Netscape staffers, such as Asa Dotzler, for a couple of months to help with the transition.
The Mozilla Foundation marks the first time that the Mozilla project actually has a legal existence (mozilla.org was always just a more informal group). This new organisation, which is hoping to gain non-profit status under California law, will continue mozilla.org's work of guiding development. Teams such as mozilla.org staff, drivers, reviewers and module owners will continue to work as before. In addition, there will be a new Board of Directors, made up of Mitchell Baker, Brendan Eich, Christopher Blizzard and some new faces, including Open Source Applications Foundation head Mitch Kapor. The Mozilla Foundation will be funded by donations from individuals and companies, such as Sun Microsystems and Red Hat. AOL will provide $2,000,000 of funding over the next two years.
Up until this point, mozilla.org has produced builds of Mozilla for development and testing purposes only, with end-users encouraged to download distributions from vendors such as Netscape. However, the new Mozilla Foundation plans to target end-users directly. The beginnings of this strategy can be seen with the redesign of the mozilla.org front page.
#42 Re: Re: Future of Gecko?
Thursday July 17th, 2003 5:09 PM
You are replying to this message
While the gecko developers will certainly be trying to make this true, one issue I see with the standalone apps is that, when the back end fails to do something they need, they sometimes check in some "not part of build" crap in ifdefs to make it work for them (instead of filing a bug on the back end to get the issue addressed in a reasonable way).... This does not help embeddors who want the same functionality, and does not help make the back end more maintainable.