Apple Public Source License 2.0 now a "Free Software License"
Open Source now accessible using Apple IDs
The Darwin team at Apple is pleased to announce that version 2.0 of the Apple Public Source License has been certified as a "Free Software License." APSL 2.0 includes numerous changes and simplifications to make it even easier to use Apple Open Source software as part of your programs. To indicate acceptance of APSL 2.0, you can now use your new or existing "Apple ID", rather than having a separate Darwin account.
Apple Public Source License 2.0 now a "Free Software License"
Apple is pleased to announce the 2.0 version of the Apple Public Source License. It improves upon the OSI-approved APSL 1.2 by conforming to the definition of Free Software Licenses, as certified by the Free Software Foundation. We are grateful to Richard Stallman for his many helpful comments in this process. APSL 2.0 is also being submitted to the Open Source Initiative to certify its continued compliance with the Open Source Definition.
The Apple Public Source License 2.0 includes numerous changes to make it even easier for Open Source developers to use and comply with, including:
-
Source distribution is only required for "External Deployment", allowing individuals and corporations to do private internal deployments
-
An option to distribute source only to those receiving binaries, rather than always having to distribute to the general public
-
Simpler, clearer, and more symmetric licensing terms
The full text of the APSL is available from the following locations:
http://www.opensource.apple.com/apsl/2.0.txt (full text)
http://www.opensource.apple.com/apsl/2.0-redline.pdf (diffs from 1.2)
A summary of all the major changes is included below. We hope you find these changes helpful.
Sincerely,
The Darwin Team at Apple
July 29th, 2003
Major Changes in Apple Public Source License 2.0:
1. Licensees will only be required to release source code of Modifications they "Externally Deploy" (new Section 1.4, and Sections 2.1, 2.2). "External Deployment" is defined to cover the external distribution of APSL'ed code or use of APSL'ed code to provide a service (including content delivery) to a third party through electronic communication with that party.
What this means is that internal modifications can now be kept private by both individuals and corporations. Previously all internally deployed modifications, except those of an individual for his/her own private use or those for internal R&D, had to be disclosed. Consequently, the old definitions of "Deploy" and "Personal Use" (Sections (old) 1.4 and 1.8) have been deleted.
2. Language has been added to Sections 2.1 and 2.2 to clarify that licensees may use and distribute Covered Code internally and externally, and for commercial or non-commercial purposes. This is not a substantive change, but the fact that commercial use is permitted (and always has been) was apparently not clear to some licensees in the past.
3. Licensees will now have the choice of providing source code to either just the users of the code or (as before) to the general public (Section 2.2(c)).
4. The Licensee's grant of rights clause (Section 3) has been simplified and made more symmetric.
5. The Termination clause relating to patent suits (Section 12.1(c)) has been narrowed such that the license will terminate only if a licensee _initiates_ an action for patent infringement against Apple. It will not terminate in cases where Apple first sues the licensee and they file a countersuit.
| 
