Changes between Version 19 and Version 20 of ApertureLicense

Timestamp:

10/10/05 21:48:14 (19 years ago)

Author:

anonymous

Comment:

--

ApertureLicense

@@ -21 +21 @@
 '''Built-in patent license''' - when you contribute code to the project, you automatically give people a royalty-free parent license for using that code, in case the code would otherwise infringe one of your patents. This prevents contributors from contributing code and coming back later to collect royalties. This patent license should be formulated in a fair way, e.g. it should cover both Aperture and derivative works.
 
-'''Built-in patent defense''' - when you sue someone (either a developer or a user) for a patent infringement related to this code, all your rights (patent- and copyright-related) for this codebase should be withdrawn. This defense should be formulated in a fair way, e.g. it should not involve infringements by a contributor outside this project.
+'''Built-in patent defense''' - when you sue someone (either a developer or a user) for a patent infringement related to this code, all your rights (patent- and copyright-related) for this codebase should be withdrawn. This defense should be formulated in a fair way, e.g. it should not involve infringements unrelated to this project, as some licenses (MPL, CPL) do.
 
 '''External deployment''' -  making a derivate work available as a service on a network to others outside your organisation should be considered as a form of distribution. The license should demand that under these circumstances the derivative should also be made available under the used open source license.