Summary

  • Netscape’s March 1998 source release opened Communicator code to outside work, but the first outside-modified revision was still developer-only source, not a ready browser.
  • Licensing, integration, product releases and institutional custody changed at different speeds; Mozilla’s 2003 foundation acquired a defined set of project assets and AOL’s pledged support, rather than proving financial independence.

The date that made Mozilla possible was also a warning about what “release” meant. On March 31, 1998, Netscape published the first developer release of Communicator source. Ten days later, mozilla.org posted a revision changed by outside developers. WIRED reported that it was source only: contributors should expect build problems, unfinished features and bugs. A person looking for a browser to download and use had come to the wrong page.

That gap was built into the project’s first steps. Netscape’s January announcement joined two decisions that are often blurred: making its current Communicator product free and promising source for a future version. The source arrived on a later date and under different conditions. In its April account, mozilla.org said Netscape planned to incorporate selected public changes into the branded Communicator executable. That executable could include code licensed from other companies and not present in the public source tree. Access to code and access to the complete product were separate facts.

The license also preserved a company’s special position. The Netscape Public License granted broad rights to use, modify and distribute covered code, but its amendments gave Netscape additional rights over Netscape-branded versions and other products. The license excluded trademark permission, and it addressed third-party code that Netscape could not release. Netscape’s own FAQ said it needed room for existing product lines, contracts and components; it also said it wanted changes returned to the shared code base. These are the company’s explanations, not a neutral verdict about which license would have been best.

Mozilla’s answer to the integration problem was an organization. The archived mozilla.org mission described a team that would set technical direction, collect changes, help contributors synchronize, publish source releases, maintain forums and track bugs and roadmaps. It expressly said the group was not the primary coder. Distributed authorship therefore did not remove coordination: a public code tree still needed someone to decide what became the next common release.

The code’s legal path required more work too. In 2001, Mozilla began moving much of its code toward an MPL/GPL/LGPL tri-license, partly to address compatibility concerns raised by developers. The project’s relicensing FAQ says permissions had to be obtained from contributors; it also excludes “Mozilla Classic,” its name for the original 1998 Communicator source, from that effort at the time. “Mozilla was relicensed” is too broad a summary. The scope depended on the file, its contributors and the rights available.

Mozilla 1.0 arrived on June 5, 2002, as a major release of both a browser suite and a development platform. The official release page described binaries as test builds and said the project provided no end-user support. That notice does not measure how many people used the software; it does show that a major version number alone did not settle its audience or service commitments.

A different boundary moved on July 15, 2003. Mozilla.org announced a foundation to continue the project’s daily operations. Its release said AOL pledged $2 million over two years, along with equipment, domain names, trademarks and other intellectual property, and transition help for key personnel. The foundation’s later tax filing names the Mozilla trademarks, Mozilla Public License, computers and website rights among the assets transferred from AOL. The legal home changed; sponsor support remained part of the launch.

This sequence fits the running-code test in a practical sense: ask what people could actually build, run, ship and maintain at each stage. The March source drop enabled participation; it did not itself produce a supported consumer browser or settle ownership of the project’s name and future. Mozilla became more than a Netscape source release through years of integration, licensing and product work—and through a transfer of organizational custody. Openness was a series of working arrangements, not a single switch.

Sources and limits

The dates and license terms are documented in Netscape’s archived NPL 1.0, the project’s NPL FAQ, and the mozilla.org mission. WIRED’s 10 April 1998 report provides a contemporary account of the first outside revision. Mozilla’s relicensing FAQ, Mozilla 1.0 release page, 2003 foundation announcement and foundation filing document the later transitions. Original Netscape January and February 1998 press-release links in Mozilla’s archive currently fail to load; dates are corroborated by the archive, WIRED and Mozilla participants’ later accounts. These sources establish formal rights, releases and stated roles, not adoption totals or the foundation’s long-term financial independence.

Sources: Netscape January release, Netscape mozilla.org announcement, NPL 1.0, Netscape license FAQ, mozilla.org mission, WIRED April 1998 report, relicensing FAQ, Mozilla 1.0 release page, Mozilla 1.0 announcement, Mitchell Baker’s 2018 retrospective, historical license index, 2003 Foundation announcement, Foundation filing.