- Derived works that do not satisfy the above terms must be renamed so
- that they can not be associated with the Ion project, their executables
- must be given names that do not conflict with the original author's
- version, and this author may not be referred to for support.
-
- Modules and other (standalone) extensions to Ion must also be named
- so that they can not be confused to be supported by the original
- author. If "Ion" occurs in the name, it must be in the form
- "Foo for Ion" instead of "Ion Foo", etc.
-
- This name policy notice may not be altered, and must be included in
- any altered versions and binary redistributions. It may only be
- removed when using small portions of the code in unrelated projects.
-
- The original author and the Ion project retain the same rights to
- your modifications that it would have under the LGPL or GPL without
- these or similar additional terms.
-
- If you fail to follow these terms, you lose the rights granted to
- you by the LGPL.
-
-Explanations:
-
-Significant change: Bug fixes are a priori insignificant as additions.
-Basic changes that are needed to install or run the software on a target
-platform are a priori insignificant. Additionally, basic configuration
-changes to better integrate the software with the target platform,
-without obstructing the standard behaviour, are a priori insignificant.
-Everything else is significant. The author reserves the right to refine
-the definition of significant changes on a per-case basis. Please consult
-when in doubt.
-
-Distributions: For example, suppose an aggregate distribution of software
-provides an `installpkg` command for installing packages. Then the action
-`installpkg ion3` (resp. `installpkg ion`) should within a reasonable
-delay install the latest release of Ion3 (resp. the latest stable release),
-or prominently notify the user that the provided version is not or may not
-be the latest. The action `installpkg ion-3ds-20070318` may at any date
-install this particular mentioned release. Likewise, the action `installpkg
---support-void-featurex ion3` may apply additional patches to the latest
-Ion3, within the further constraints set above.
-
-The intent of these terms is to curb the power that "distributions", as
-the primary sources of software for many users, have in defining what
-is perceived as Ion. By providing significantly modified versions and
-out-dated development snapshots without prominently mentioning this fact,
-they do not present the work in a light that the author can agree with,
-and create a burden of dealing with (new) users seeking for support for
-such versions.
+ Versions for which the above conditions are not satisfied, must be
+ renamed so that they can not be associated with the Ion project, their
+ executables must be given names that do not conflict with the copyright
+ holder's version, and neither the copyright holder nor the Ion project
+ may be referred to for support.
+
+ In the text of sections 0-2, 4-12, and 14-16 of the LGPL, "this License"
+ is to be understood to refer to the LGPL extended with these terms and,
+ where applicable, possible similar terms related to the names of other
+ works forming a whole. Sections 3 and 13 of the LGPL are void. Where
+ contradictory, these additional terms take precedence over the LGPL.
+
+End of terms.
+
+
+Explanations
+
+Trademarks: With the terms above primarily appealing to copyright law,
+should any of the indicated trademarks be found invalid, does not excuse
+you from the conditions imposed by those terms. The use of these names
+in contexts other than redistribution of this software and modifications,
+is outside the scope of the terms above, and governed by applicable
+trademark or other laws.
+
+ With regard to modules and other extensions to Ion(tm), the permission
+ is hereby granted to use "Ion" as part of the name, provided that it
+ occurs in a form suggesting that the work is supported by neither the
+ copyright holder nor the Ion project: "Foo for Ion" instead of "Ion Foo",
+ etc.
+
+Significant change: Bug fixes are insignificant as additions. Basic changes
+that are needed to install or run the software on a target platform, are
+insignificant. Additionally, basic/small configuration changes to better
+integrate the software with the target platform, without obstructing the
+standard behaviour, are insignificant. Everything else is significant,
+unless expressly declared otherwise by the copyright holder.