I would like to package a window manager named Notion. It is a fork of
the Ion(tm) window manager. Ion(tm) is released under the LGPLv2.1 with
an addendum that restricts derivative works from calling said works
Ion(tm) or using a name that implies being apart of the Ion(tm) project.
The nature of these restrictions appears to be inline with the GNU free
software philosophy, as is stated in the following paragraph:
However, rules about how to package a modified version are
acceptable, if they don't substantively limit your freedom to
release modified versions, or your freedom to make and use modified
versions privately. Thus, it is acceptable for the license to
require that you change the name of the modified version, remove a
logo, or identify your modifications as yours. As long as these
requirements are not so burdensome that they effectively hamper you
from releasing your changes, they are acceptable; you're already
making other changes to the program, so you won't have trouble
making a few more.
-- "What is Free Software?" (https://www.gnu.org/philosophy/free-sw.html
The addendum is included below for reference. The complete license,
including addendum, is available here:
Given that the software I would like to package is released under a
different name, I do not see any conflicts with Fedora's licensing
guidelines. Am I correct in my interpretations? Is this license
compatible with Fedora's "LGPLv2 with exceptions" license?
Thank you in advance for your time and any clarification you can provide.
-= Begin License Addendum =-
Copyright (c) Tuomo Valkonen 1999-2009.
Unless otherwise indicated in components taken from elsewhere, this software
is licensed under the GNU Lesser General Public License, version 2.1
reproduced below), extended and modified with the following terms:
If the name Ion(tm) or other names that can be associated with the Ion
project are used to distribute this software, then:
- A version that does not significantly differ from one of the
copyright holder's releases, must be provided by default.
- Versions not based on the copyright holder's latest release (on
the corresponding "branch", such as Ion3(tm)), must within 28 days
of this release, be prominently marked as (potentially) obsolete
- Significantly altered versions may be provided only if the user
explicitly requests for those modifications to be applied, and
is prominently notified that the software is no longer considered
the standard version, and is not supported by the copyright holder.
The version string displayed by the program must describe these
modifications and the "support void" status.
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.
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
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.
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 provide the latest release
of Ion3 (resp. the latest stable release) 28 days from release date at the
latest, or prominently notify the user that the provided version is (likely
to be) obsolete and unsupported. The latest release being provided by
default, or prominently appearing in a listing, constitutes prominent
marking of earlier releases as obsolete. Specific versions (including
modified versions) may be provided if the user explicitly requests for
those, within the 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
-= End License Addendum =-