Re: Motivations; proposed alternative license
Frank Mittelbach <firstname.lastname@example.org> wrote:
> So far I have seen the comments by Jeff (who goes in a lot of detail
> through the license, for which i would like to thank him, and to
> which i intend to get back) but other than that, all I heard so far
> and repeatedly heard is "we don't like that you use clause 4 and
> therefore it is a license acceptable by us" (though in more
> elaborate words).
Well, there were my comments that preventing the modification or
removal of .ins files goes beyond what clause 4 allows. I even gave
an example where it might be completely appropriate to do such a
thing. The message should be in the debian-legal archive.
In that message I also said that that was the only thing that
definitely makes it non-free. Now I think that the renaming
requirement also goes beyond what is allowed in clause 4.
Specifically, clause 4 says that, as a special case, you can allow
changes only as patches to the original program. It doesn't say
anything about what kind of restrictions you can put on those patches,
and Debian traditionally has not allowed any additional restrictions.
Telling people that a patch must have a certain form (i.e. must rename
any file that it modifies) is an additional restriction that Debian
can not live with. Because of both practical and ideological reasons.
In a sense, I feel your pain. You want everyone's installation of
Latex to be the same to facilitate interoperability. However, free
software means that you give up some measure of control over your
creation. RMS lost a lot of control when egcs became the official
gcc, and I'm sure the Emacs-XEmacs split didn't make him happy either.
But he still is willing to give other people control.
Here is a hypothetical. Let's say that someone wants to add support
for Klingon into Latex. So they hack something together which, by
necessity, changes a few standard files, and it works for them without
breaking anything else. You reject the patch because it isn't really
a good i18n solution, it only works for Klingon. You also think that
Klingon is a silly thing to add support for, so you'll probably never
add it in. However, for the people interested in writing Klingon
(e.g. Hollywood screen writers and trek fan fiction writers), this is
a good solution. In this case, you are preventing people from having
seamless support for Klingon.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org